Hidden transitions for end-users

What is the challenge?

• In workflows with fixed transitions, sometimes we want to move to gate transitions usings approvals, but sometimes we want to trigger the transition using automations based on a required field. In order to accomplish this behavior, we need to create a transition, for the automation to work, but end-users can skip the approval.

What is the impact?

• Creating loopholes in fixed transitions

Describe your idea.

• Allow to "hide" transitions, so they can be used only by automations rules and not by end-users