3.2 Workflow Start Date/Launch Date Addition

Step 1: When generating a new workflow a user will now have the option to enter either the workflow start date or the workflow launch date.
Step 2: They can select what option should take precedence when generating the workflow

Step 3: If using workflow start date: 

Step 3.1:  Select the workflow start date, this can also be a date in the past. 

Step 3.2: The system will calculate the associated hrs for completion/approval for each step and provide the user with the expected step start date and expected end date.

Step 3.3: When the start date arrives the notification emails will be sent, if the start date is in the past the emails will be sent at the point of workflow generation to the step completers and the first step will move to in progress. 

Step 3.4: If there are no perquisites set up, the emails will detail all the steps which have an action required and all the steps will move to in in progress.

Step 4: If using workflow launch date: 

Step 4.1: The system will work from the final step in the workflow backwards to the first step. 

Step 4.2: The expected completion date for the last step will be the launch date. 

Step 4.3: The system will calculate the associated hrs for completion/approval for each step and provide the user with the expected step start date and expected end date.

Step 4.4: Based on the timings set up in the template the user will have visibility of the expected start date of the first step, when this date arrives, emails will be sent to the step completers. 

Step 4.5: If there are no perquisites set up, the emails will detail all the steps which have an action required. 

Step 4.6: If the launch date is set and the first step of the workflow is in the past, the emails will be sent at the point of workflow generation and the first step will move to in progress. 

Step 4.7: If there are no perquisites set up, the emails will detail all the steps which have an action required and all the steps will move to in in progress.

Step 5: Addition of a toggle to hide/show the expected start/end dates of each step, above the steps table in a workflow. Option is stored on the user level, so if you selected 'Show Expected Start/End Dates', they will always show until you choose to hide them.

Step 6: If a workflow is paused then resumed and new dates entered these will also update the dates for each step as expected.

Step 7: If the expected start date is in the future the assigned step completer does have the option to start the step earlier than expected start dates if required. From this point the workflow would continue based on the revised timelines.