We have created a 50+ task Workflow that performs Onboarding processes that use to be manually requested: New Bitbucket Project, New Bitbucket Repos, New Artifactory Repos, ServiceNow configuration updates, and provisions Azure Cloud Resources.
This workflow has a number of steps that will cause issues if the "Restart from here" link is clicked after execution.
We would like the ability to HIDE this link based on Task or Workflow configurations.
Please note, we want the ability for the user to go to the "Designer" view and restart Tasks and Phases to still remain. We want to avoid users from just trying the link.
by: Adam R. | 2 months ago | User interface
Comments
Further explanation, by allowing the user to click the "Restart from Here" link, the workflow may create additional Bitbucket projects, repos, etc. that will need to be manually cleaned up. we want to prevent the curious from clicking this link.
At the same time, we do not want to prevent the expert user from being able to go to Designer View and restart a task or phase.
Thank you for the idea and the use case.
Do you see this as a workflow-level setting in the Execution view (Steps), controlling whether restarts are completely prevented for a workflow, or disallowed from a specific step onwards?
I think this needs to be at a task level/phase level.
EXAMPLE FLOW:
Phase 1 - Inputs and Validations, Restart can occur on input tasks but not on validation tasks.
Phase 2 - Provisioning performed for Bitbucket, Artifactory, ServiceNow changes, and Azure - No RESTART but user can still go to Designer View to retry a failed task.
Phase 3 - Reporting tasks (restart does not matter)
We’re considering making Restart functionality available for User Input tasks, while disabling it for other task types.
Would this approach work for your use cases?
I think this approach will help for some of the use cases.
But, we want to prevent a users going into a previous Workflow Task and clicking the "Restart from Here" button on ANY executed tasks.
We could have a few hundred tasks within a single workflow and re-starting at random points will cause issues (manual clean-up/Ops tickets).
It might make sense to discuss this in a meeting and go over the use cases.