Group connections

Groups ("folders") use the Roles and connections field to record connections relevant to the group, providing a role reference for each connection. This can be set directly be editing the group.

Group-level connections have three purposes.

  • They can specify a connection that has a particular purpose for the group. For example, the "config" connection is used to identify a module that configures the group process and status rules. Some modules, such as Insight and Notification Manager, provide functionality to groups through specific references.
  • They specify connections that might be used by workers within the group. For example, if a group contains tasks for a single supplier, the connection to the supplier might be identified using the "supplier" reference. A group can contain multiple connections with the same reference.
  • For connection groups (see below), a role can be set but the connection set to null (shown as "Folder role"), which means that the connection is globally associated with that role. This is also inheritable. For example, if you have a folder of supplier connection groups with a "supplier" folder role, then each of the supplier connections is globally identified as a "supplier".

Group-level connections are inherited down the group hierarchy, so that connections set at a higher-level group also apply to lower-level groups. There is an option in the Roles and connections field to block inheritance from parent groups.

A group is automatically created for each connection, known as the "connection group". This acts as an inbox for tasks received through the connection, and is also used to identify the connection. The connection group may have a folder structure within it which represent subdivisions of the work, such as different projects or inboxes for tasks intended for different recipients. The Send process step type path option is used to specify a sub folder when sending a task to a partner, which can be specified using a combination of path and/or name.

To keep track of recipient folders, the connection group for the sender end of the connection can set an Address book field to list the folders within the partner's connection group to which tasks can be sent. This might seem the wrong way around, and that the recipient should specify the address book. However, the connection group at the recipient's end is under the control of the sender, and it is the sender that specifies the folders within it. The folder structure at the recipient's end is a hint to the recipient of how incoming tasks should be handled, but it is up to the recipient to then handle the tasks accordingly.