Nice @randomanon that is the type of little tricks that can really allow somebody to build modularly and not have to repeat themselves. In my plugin I’m finding little ways to incorporate these strategies I use into the plugin itself. They really allow you to build one thing that can control all of your data processing needs.
They are great. Below is video example of the workflows for a test app, on the page in which the user takes the test.
One area that I am already planning on updating is an ability to have my local storage not just write on a single action, but to write and then read from the same action via an optional yes/no field on the action.
For custom state setting…you can no have a single trigger event with two actions where the actions have conditions on them as to whether or not to set the custom state value from yes to no as they will compete with each other in the workflow and custom state will not be set properly. Other than that, there are times when you have different numbers necessary.
In the video above there are two trigger events with same condition except one looks at the number as 0 and the other as greater than zero…it is just sometimes more maintainable to see those conditions on the trigger event rather than needing to click into the workflows to see the single action with the one condition (but of course that is just a developers preference).