As a person looking at a project's workflows, I want the list to tell me which ones are in production, so that I can see the state of the project without opening each one.
Part of #4852 (Sandbox DevX epic). Phase 2.
Outcome
The workflows list names each workflow's state in the same words the editor uses.
The toggle in the Enabled column already is the lifecycle: turning it on publishes the workflow and records a version, turning it off takes it out of production. Only the name is left over from before the lifecycle existed, when the only thing a workflow had was whether a trigger was switched on. So the list and the editor describe the same thing two different ways, and the list's way is the one nobody uses any more.
Scope
- With experimental features on, the column names the state: draft or live on an ordinary project, on or off inside a sandbox, matching the editor.
- Without the flag it stays exactly as it is. Those users have no lifecycle, so naming one would be the feature leaking out of the flag.
- Decide what the toggle should do for a workflow that cannot be edited in the editor. Today the list can publish something the editor holds read-only, and the two should agree.
- Worth considering whether a live row should also carry who published it and when, the way the editor's version list does. Twenty workflows is where that question gets asked.
Notes
Raised while checking the feature before a staging release. Deliberately left out of that release: the column is not wrong today, only old, and renaming a surface with no test coverage at the last minute is how a release goes bad.
As a person looking at a project's workflows, I want the list to tell me which ones are in production, so that I can see the state of the project without opening each one.
Part of #4852 (Sandbox DevX epic). Phase 2.
Outcome
The workflows list names each workflow's state in the same words the editor uses.
The toggle in the Enabled column already is the lifecycle: turning it on publishes the workflow and records a version, turning it off takes it out of production. Only the name is left over from before the lifecycle existed, when the only thing a workflow had was whether a trigger was switched on. So the list and the editor describe the same thing two different ways, and the list's way is the one nobody uses any more.
Scope
Notes
Raised while checking the feature before a staging release. Deliberately left out of that release: the column is not wrong today, only old, and renaming a surface with no test coverage at the last minute is how a release goes bad.