You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Sometimes we have instances where designers use complex event handlers with multiple conditions and parameters to be considered. They often use a combo of simple event handlers with complex conditional statements (mostly If orders). This issue relates to mostly design of this process rather than it being a frustrating problem.
Describe the solution you'd like
Implement an event handler where one can supply a list of conditions which need to be true to execute the order.
Describe alternatives you've considered
There are multiple ways to already do this but to keep our Nodes consistent (they are responsible for our model and controlling the structure of how orders will eventually be executed) this method is quite nice. Ensuring that this is an event handler rather than forcing this to always be related on our node, ensures that designers have multiple choices to execute their nodes and orders. We provide some form and idea of model but designers can break this pattern if they choose to - avoiding restriction of creativity completely.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Sometimes we have instances where designers use complex event handlers with multiple conditions and parameters to be considered. They often use a combo of simple event handlers with complex conditional statements (mostly If orders). This issue relates to mostly design of this process rather than it being a frustrating problem.
Describe the solution you'd like
Implement an event handler where one can supply a list of conditions which need to be true to execute the order.
Describe alternatives you've considered
There are multiple ways to already do this but to keep our Nodes consistent (they are responsible for our model and controlling the structure of how orders will eventually be executed) this method is quite nice. Ensuring that this is an event handler rather than forcing this to always be related on our node, ensures that designers have multiple choices to execute their nodes and orders. We provide some form and idea of model but designers can break this pattern if they choose to - avoiding restriction of creativity completely.
The text was updated successfully, but these errors were encountered: