Processing Group components
A Processing Group is a component that lets you manage multiple trading partners in one place. Instead of editing the Trading Partner step list in each process, you add, change, or remove trading partners in the Processing Group. The process logic stays the same.
Processing Groups support multiple communication methods and document standards. Each trading partner in a group still uses one document standard, but you can group partners by organization to report on them and share metadata, such as contact information.
Creating a Processing Group
- On the Build tab, click Create New, and then select Processing Group.
- Optional: Rename the component.
Deploying a Processing Group
Processing Groups deploy independently of processes. You must deploy a Processing Group before a process can use it. Each trading partner in a deployed Processing Group uses one trading partner connection license.
To deploy a Processing Group, go to the Deployments page.
If you use legacy deployment, go to the Deploy page and select Processing Groups from the components list.
Using a Processing Group in a process
- Open the Start step set to the Trading Partner option, or open the Trading Partner step.
- Select Use a Processing Group component.
- Select your Processing Group from the drop-down list.
Adding trading partners
On the Members tab, click Add a Trading Partner to add a trading partner to the group.
Setting up routes
The Routes tab controls two things: how routes are structured, and which process runs when the Processing Group is specified in a Process Route step. Choose the structure based on how your trading partners send documents.
- Structure routes on documents when all trading partners use a standard document structure. Partners that do not use a standard document format can call a different process. Specify each of these partners individually with the Add Standard option.
- Structure routes on partners when documents do not use a standard structure. You can set an individual trading partner to use its own process. You can also set individual document standards and document types to use a process other than the default.
Routing documents
A Process Route step can use a Processing Group. You do not need route keys to do this. Routes inherit from the Processing Group by default, so you specify only the overrides.