Would like to see an intermediate state between enabled and draft for IWA schedules

Most of our application teams have their schedules set up in the non-prod environments to mimic production, including the run cycles. This simplifies the production promotions as we can copy the objects and change the workstations they run on for production.

However, in most cases they do not want their jobs running in the non-prod environments except when doing specific testing, as doing so can interfere with development, other testing as well as being a licensing concern. They may test individual schedules periodically, and also may run a full end-to-end test of their schedules.

Putting schedules in "DRAFT" state however prevents manual submission. We are working around this currently by having a calendar that is used in the non-prod environments as an exception run cycle to prevent items from being added to the plan except when testing is in progress. By doing this however we are having to manually remove that run cycle when promoting changes to production.

What would be nice to have is an intermediate state, where schedules are not in the plan, but the run cycles can be established without placing the schedule in DRAFT mode. The other facet of this request would be we need a simple way to indicate that testing is going to occur and we need to add schedules in this new state to the plan when it is generated next.