As a workflow admin I want to be able to define a set of schema wide workflows that can be overridden or augmented at the space (project) level.
Be able to turn off schema workflows in a space.
Be able to "lock" to a specific version of a workflow in a space.
Be able to duplicate schema workflows and customise in a space.
Be able to add new workflows in a space.
|
Practical use of functionality?
Override a workflow on a project when the contract requires it to be a non-standard project with non-standard processes. |
|
|
What is the impact of not doing this?
The work around of putting lots of workflows into the schema and choosing them will not scale to 100s of projects and will likely have performance impacts. (We also don't want to revert to one schema per project.) |