Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Adding a parallel process to a stage

Updated on May 11, 2022

Support your business process events that do not require a run-time order by adding a parallel process to a stage. Parallel processing speeds up case resolution as different case workers can complete parallel processes simultaneously.

For example, if your business goal is to review a job candidate, you can create two parallel processes: one for conducting a job interview, and one for reviewing documents that the candidate provides. A hiring manager can interview the candidate, while an HR worker reviews the documents.

For relevant training materials, see the Parallel processing module on Pega Academy.

  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click Life cycle.
  3. In the Case life cycle section, hover over a stage, and then add a process:
    • To add a new process, click MoreAdd parallel processNew process.
    • To add a new multistep form, click MoreAdd parallel processNew multistep form.
    • to reuse an existing process, click MoreAdd parallel process, and then select the process in the list.
  4. In the text field, replace the default process label with a descriptive name.
  5. Click Save.
Result: At run time, the process starts when a case enters the stage.
For example: The following figure shows a stage that includes two parallel processes. A hiring manager can conduct a job interview while an HR worker reviews documents.
Parallel processes
A stage with two parallel processes.
What to do next: Add meaningful tasks to your parallel process by adding steps. For more information, see Steps in a case life cycle.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us