Action Type Groups to manage submission criteria as user stories

Similar to object type groups it would be great to group action types.

Current painpoint:

  • Keeping track of hundreds of action types spread across different modules within a usecase can be pretty exhausting. Searching for action types according to submission criteria is not possible - e.g. to find misconfigurations, and keeping them up-to-date or configuring them is exhausting as well.

  • Very often, we have similar authorization on similar actions types e.g. when modifying or deleting an object. Or modifying and deleting different objects within the same userstory.

Pain solved:

  • Get an overview of parameter names and quickly see if action types e.g. for creating an object and modifying an object drift too much apart in their UX.
  • Group action types per userstory and govern the submission criteria for the userstory - referencing the parameters in respective action types. - If an action type is part of multiple user storys, the respective submission criteria are added as an “or” condition with the other userstory.
  • It becomes clearer which user stories require which action type - could be easier to find relevant ontology components when defining an OSDK (for a custom widget within a userstory).
  • in Workflow builder, you could easily group by userstory and see which components are involved or maybe even intersect.
  • Usecase admins could get their own userstory “admin maintenance and support” and receive the corresponding action types.
  • Quickly check / unittest if certain users could execute the actions under the condition that certain parameters are set.
  • The result would be a venn diagram: The userstory has certain submission criteria which are true for all action types in that userstory while each action type can have additional submission criteria which would then contain less boiler plate (group assignments / owner checks) and deal more with the actual userstory-specific conditions referring to parameter values to cover edge cases or prevent data corruption.

Managing more than 150 action types with 54 object types + relations, workshop modules, python functions repo + 3 Custom widgets that are within the same widget set, this would save me a lot of headache.