In a similar way to auto-start, there will be instances where we would want the workflow to move onto another stage when the conditions and validations are met, without the user having to do this.
- If using the Custom API to create objects (e.g. Evals), then this would require this Custom API as a stage, followed by an additional stage to populate the values of the new record by using conditions. The user doesn't care that this is a two stage process - for them it's a single process to create a fully populated Eval. We shouldn't ask them to have to manually movce the stage on
- When a user makes a record inactive, we'd like to end the workflow for them, but instead they have to choose the finish stage off the action button, then decide whether they are finishing due to an object closing, or being made inactive.
- When a control is collected, we'd like to automatically move it to an awaiting collection stage (to make use of the operations)
|Component||End User UI|
|Priority||High - Critical|