Class Scheduling Feature Requests

Could an end date be set for the future actions?

I think it'd be worthwhile to implement custom emailing for instructor preference forms. If I'm a department scheduler, it seems like it'd be convenient to be able to send out preference forms to my entire department and view their responses without having to leave the platform. As of now, I'd have to copy a generated url link and then email the faculty manually. We have custom email templates for requests and events, so it seems like something worth doing for preference forms, too. Note that the utility of this implementation depends on department instructor data being up to date, which it should (necessarily) be if department schedulers are assigning faculty to every course.

Right now the fields to choose from when selecting logic jumps are very limited. It would be very helpful if we could expand the options to include additional fields, including custom fields in the field options. For example, we would like to be able to route requests based on if a custom field is not empty or has a particular value.

Certain fields should not be editable based on the existing values in other fields. This is relevant for situations where the majority of classes should not modify a particular field, but a number of classes still need to. The volume of modification is not feasible as workflow. For one example, Section Start Date/End Date fields should only be editable if the selected session is DD1, DD2, or DD3. In summary, we are looking for the ability to edit a field based on parameters that are set within the section/course. Thanks [NAU]

It would be very helpful when looking at the requests if the Term the request was for is indicated in the list, either in a separate column or even added in the Request Type column. Then we can see at a glance which ones may be more time-sensitive. I know about the filter but that has to be redone every time you click on an individual request and then come back to the full list.

For a Section Change Request, the associated Workflow contains the logic that if the request is rejected, then the request is returned to its author. However, once the request is returned to the author, the request cannot be edited by the author. The author can only reject their own Section Change request from the Request Toolbox page, or approve and re-submit the same request. I am assuming the author should have the ability to modify their requests for re-submission to the next stage in workflow. Thanks [NAU]

The ability to create logic jumps in scheduling workflows based on all pre-built and custom field options within the section modal, course modal and user profiles.