Skip to main content

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

Adding a work pool for business conditions

Updated on December 3, 2021

The cySetWorkPools data transform contains the work pools that may be selected as the scope for a business condition with a source of Case. To make more of your work pools selectable as the scope for a business condition, update the transform.

Pega Customer Service Implementation Guide
  1. In the header of Dev Studio, search for and open the cySetWorkPools data transform.
  2. Click the Add a row icon.
  3. In the Action column, select Append and map to.
    Result: A child row is created.
  4. In the parent row, change the Target to .czWorkPools.
  5. In the child row, select .pyClassName as the Target.
  6. In the Source column, enter the work group class name in quotation marks, for example, "PegaCA-Work-Service-Brokerage".
  7. Define a label for the source.
    The label identifies the work pool in lists on the Business conditions page.
    1. Click the Add a row icon to add a child row.
    2. Select .pyLabel as the Target.
    3. In the Source column, enter the label in quotation marks, for example, "Brokerage".

    The following figure shows a new work pool that is configured in the cySetWorkPools data transform.

    Data transform for defining new work pools
    Data transform with a new work pool configured

  8. Click Save.
  9. Follow the steps in "Configuring business conditions" to verify that the new work pool appears for selection on the Business conditions page.


Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

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