Best way to define new workflow states

The default states are Open, In Progress and Done. If for a particular workflow and/or types we need more states, what is the recommended way to model this?

  1. Add more states to the State (workflow) field? This would mean they would only be relevant for some entity types, does that cause complications building views that include multiple types?

  2. Add a separate Single Select field to model a completely independent workflow state. This then has to be replicated across all types that need combining.

Any guidance much appreciated!

Any changes to the choices of the workflow state only affect the database where the changes are made - they’re not global.
So you can have totally different workflows for different types of entities.
If you do want to re-use the same workflow, but you don’t want to replicate it for all databases that need it, consider creating a database of entities to represent the workflow states, and create many-to-one relations to it from all the databases that need it (and maybe store this database in a space with read-only access, so users can’t change the choices).

1 Like

It really depends on the context of your process and workflow.

I generally like to use Workflow / State for clearly defining the most important stages in your process or sub-process

Then supplement the State with a more detailed Single Select field, if necessary.

I’m not sure if there is a downside to using Workflow vs Single Select as you can use them interchangeably in most cases. Except that Workflows have a defined sequence and final state when it comes to automation.

Below is my recent use case of having both States and Single Selects for task management using a board view. Where the Single Selects are used for not-so-linear states that supplement the primary states of Open, In Progress and Done.

Workflow fields have the advantage of bing able to be updated inline in some circumstances (i.e. without having to open the entity)