When designing workflows, there are certain actions that users want to make that are not within the scope of an adaptor e.g. add a new field, remove fields, call a new workflow, or send acknowledgment, among others. These typically require users to add new steps and hack their way around with the common adaptor.
With Action/Transformer steps, users will
be able to perform simple independent operations in their workflow without writing code via a simple interface.
Examples of operators are listed below:
-
Save to database
-
Send acknowledgment
-
Add new fields with static/calculated values to data in state
-
Create a new data schema
-
Add a counter field
-
Call another workflow as a step etc.
When the action has to do with data, we can call them transformers but if they control the state of a workflow, we call them actions.