Groups ("folders") use the Roles and connections field to record relevant connections, providing a role reference for each connection. These connections can be directly set by editing the group.
Purpose of group-level connections
Group-level connections have three purposes.
-
Defining specific functional connections. Some connections serve a particular function within the group. For example, the "config" connection identifies a module that configures the group's process and status rules. Modules such as Insight and Notification Manager provide functionality to groups through specific references.
-
Providing connections for workers. Workers within the group may require certain connections. For example, if a group handles tasks for a specific supplier, the connection to the supplier may be identified using the "supplier" reference. A group can contain multiple connections with the same reference.
-
Establishing inheritable roles for connection groups. In connection groups, a role can be set while the connection is left as null (shown as "Folder role"). This establishes a global association of that role with the group. This association is inheritable. For example, if a folder contains multiple supplier connection groups and is assigned the "supplier" folder role, then each supplier connection is globally recognized as a "supplier."
Inheritance and Blocking
Group-level connections are inherited down the group hierarchy, meaning that connections set at a higher-level group also apply to lower-level groups. However, an option in the Roles and connections allows inheritance from parent groups to be blocked if necessary.
Connection groups
For each connection, a corresponding connection group is automatically created. This group functions as an inbox for tasks received through the connection and helps to identify the connection itself. The connection group may contain a folder structure to represent subdivisions of work, such as different projects or inboxes for specific recipients.
The Send process step type path option specifies a sub-folder when sending a task to a partner. This can be defined using a combination of path and/or name.
Roles and connection resolution
A group can use the Roles and connections field to identify connections and assign them roles. These roles help look up connections when creating new workers or resolving connections in calls. For example, an "auditor" role may be associated with a connection to an audit organization. Workers within that group, or its sub-groups, can use that connection when an auditor is required.
If the default (null) link is used in Roles and connections, this is referred to as "Group role" and establishes a role for the group itself. This is commonly used for connection groups or their parent groups to define the role that connections take, such as "supplier."
Standard Roles
Some roles are used by standard components:
process or process.role
These connections provide definitions for new processes, effectively acting as the process providers for the group.
If a role suffix is added, it is passed to the process provider to filter the available process definitions.
subscribe or subscribe.entity
These connections receive published data. See Publish and subscribe.
If an entity suffix is added, only data for that entity is passed.