Skip to main content


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

Bulk processing

Updated on March 29, 2022
Applicable to UI Kit applications

Process cases in bulk to save time and resolve work faster. Bulk processing is less error-prone than individual case processing.

For example, managers can use bulk processing to transfer a large number of cases to a specific user for processing, update the urgency for multiple cases, or send out a message about many cases to a specific user.

Developers can instantly apply common flow actions to many cases. For example, they can adjust service-level agreement times and add a note to all cases at once.

Note: Only Pega Platform applications that you build with UI Kit support bulk processing.

  • Creating cases in bulk

    Create cases in bulk to define case details, such as labels and work statuses, in one step without manually interacting with individual forms. For example, in an insurance application, you can save time by creating multiple cases for home, car, and life insurance in bulk.

  • Updating cases in bulk

    Update cases in bulk to set the values of case labels and descriptions in one step, without manually interacting with individual forms. As a result, you save time and reduce the risk of small errors in case details.

  • Running flow actions in bulk

    Run the same flow action for multiple cases at once by using the Bulk actions form. You can work on many cases without impacting their path toward resolution. For example, you can extend a service-level agreement (SLA) or transfer a set of assignments to a user.

  • Troubleshooting errors in bulk processing

    When you process cases in bulk, you might encounter errors. To resolve common issues that prevent you from processing multiple cases, follow the respective guidelines for each problem scenario.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us