A frequent request is that sessions have at least X number of papers. A less common request is for session chairs to only be allowed to add a maximum of N number of papers.  If we had a setting (similar to table fields, checkboxes, et al.) to set the minimum and maximum number of papers, it would be great. If we could do it by session type, and that would allow sessions without any papers at all to be finalized, that would be a dream come true. 

Most sessions' clients' workflows require emails both on session creation AND session finalization. At some point in the past, the Session Creation email was repurposed to be sent only on Finalization.  Every sessions' client usually asks at least once for emails for both states--some ask year after year.  It would be really helpful to have a System Email for Session Creation and Finalization. 

Complex conferences spread over multiple days often have session chairs and other participants who show up in many many panels.  Having a "show me my panels" feature for session hosts/chairs/participants (maybe hooked into the logic that allows them to see the "start session" button, so we'd have a starting point of where/how to search) would enable them to have a single place to look for all the sessions they're responsible for.  

It would be nice to have the option when setting up a form to allow users to check all available options at once. This occurs relatively frequently with checkbox arrays, and it would be beneficial to allow it.  

Overview: I know the standard workflow for Form Templates are more likely to be repeated use of the same field, but since it's possible to build a complete form within the template builder, being able to add a "base" alias inside the template itself would speed things up.

Example Use Case: I had a situation this week where I had to reuse the same form 37 times to create a post-conference evaluation form. Since each attendee could have attended every one of the 37 sessions, the form had to be inserted 37 times over and over, and that was a great benefit to have it pre-built. 

In order to have a manageable use of the form variables, however, each form with 15 to 20 questions had to have the alias rewritten to make it usable in any use-case scenario. Using auto-generation would've resulted in a spaghettified mess that would take weeks to unwind. It would've been much easier and quicker to just add an id to the end of a "base alias" that had been created from within the template builder. Even cutting and pasting took a long time form-to-form.

It was mentioned that I suggest this as a feature request if it's viable to do so.  In most cases, it will probably go unused, but for the situations like my use case, it would save a great deal of time.