Unable To Create A Trigger For A Connection In Integration Service As No Processes Found For 'Process To Execute' Dropdown

News Knowledge Base
1

While creating a Trigger for a connection in Integration Service, why are there no processes available in 'Process to execute' despite processes being available in Orchestrator Modern folders and Robot role assigned to the user?

Issue Description:

While creating a Trigger for a connection in Integration Service, there are no processes available in 'Process to execute'. This is observed even when the user has the 'Robot' role assigned in Orchestrator and there are processes available in Orchestrator.


Resolution:

This issue is observed when the User was part of only the 'Everyone' group in Automation Cloud. In Orchestrator, when only the Robot role was assigned to the user for folders, the processes were not visible during Trigger creation.

When the 'Automation Developer' role was assigned to the user in the folder, the processes were visible.
This role has the minimum folder-level permissions needed to execute processes and will not impact setups / automation. This is a default role, which cannot be edited.

Read more on,