Give context on the use case / what you’re trying to achieve
When setting up actions in ontology, the submission criteria and become complex, especially when being deployed to support multiple actions for a specific use case. Right now, user would have to enter the same submission criteria for X actions. I would like the ability to at a minimum clone the submission criteria to allow for pasting to use for another action. A higher level strategy would be the ability to set up a submission criteria strategy that can be applied to actions that share the same parameters, object references, etc that would allow for singular management.
** Why you can’t do it today / work-arounds **
For one of the workflows where we have ~ 20+ actions covering 8+ objects where the submission criteria is the same, we have placed the checks in the workshop that is used to manage the 8+ objects and pass and true/false to the action from workshop to enable updating. This, however usage of the action outside of the workshop in an effective manner.
** Why will this make a huge difference for you or your business? **
This would reduce time and potential errors in managing the submission criteria for workflows, especially those with many objects and actions that share the same submission requirement. The value is in the theme of development efficiency and consistency.
