Workflow states are when Custom States can get very useful, but also quite complex.
If you remember the “list of fruits” example we did a while ago, that had a temporary list of items that could be selected/deselected … that is all workflow custom state based. You are changing a list held in a custom state based on actions.
This was very helpful. Can you give me some usage cases where a custom state would be used as opposed to setting a condition? Trying to get my mind inspired on how I can use these in my apps…
But the ultimate reason for me to use custom states in a workflow setup, is so that the custom state can perform other functions at the same time.
For example, if I want a button to change color when latched (conditional), AND also to change an item in my database when latched (non-conditional), then I would use a custom state in a ‘workflow’ setup.
If you want it so the button can keep it’s current state for the next time the user logs in, then you would need to use a flag/state in your database. For this i usually create a new field called ‘flags’ as a yes/no type.