Seems like workflows seem to be designed to go from 0% (not started) to 100% (done)
How would one account for super-states / alt-states like “archived”/"backlog’ or “failed”/“rejected”?
For example in software dev a feature request can have the following states: requested (0%) → planning (25%) → working (50%) → in-review (75%) → completed (100%)
It can also have ‘super-states’ which may temporarily or permanently take the prospect out of the default state flow. Example: getting moved to backlog, or getting closed for various reasons
Another example is in a simplified CRM workflow: outreach (0%) → proposal (33%) → negotiation (66%) → closed (100%)
This would also have ‘super-states’ which may temporarily or permanently take the project out of the default state flow. Example: getting moved to rejected
A final real-life example is we are trying to track the status / state of our clients from Proposal (0%) → Onboarding (50%) → Active Client (100%). But what happens after the relationship with the client ends?
I added the Former Client state and the state icon seems to go back to 66%? Should I just move the Former Client to first and have it be 0%?