Configuring a Work Party

Work Parties

 Work parties allow you to refer to a case participant by role, without knowing any identifying information.

Applications commonly use a work party as the recipient of correspondence.

Work parties are sometimes used to assign work.

How to Add a Work Party to a Case

Adding a work party to a case requires two actions:

Defining the party using a Work Parties rule.

Populating the party when performing a case.

Pega creates a Work Parties rule named pyCaseManagementDefault for each case type.

When you add or modify a work party for a case type, use the copy of pyCaseManagementDefault created automatically for you in the class of the case type.

 

Define the Work Party Using a Work Parties Rule

Add the work party to the pyCaseManagementDefault work parties rule for the case type.

In this example, a customer is the subject of a dispute resolution case, while a customer service representative (CSR) is the owner of the case and responsible for resolving the dispute.

 

Work Party Considerations

When you create a work party, consider the following information:

What information do you need to know about the party? (For example, do you only need the name and email address, or do you also need the party’s marital status?)

How do you obtain the information to populate the party details? Do you expect the user to enter this information? Can you copy the information from session information or case data?

Is the information available when the case is created, or does the information become available during case processing?

Are multiple instances of the party associated with the case? (For example, does the case involve one customer, or several customers?)

When you create a work party, consider the following information:

What type of case participant do you need to model?

Is the participant an individual or an organization?

Does the party work on the case, or just receive status updates?

Work parties are derived from the Data-Party class.

Data-Party contains rules to describe a party, such as properties to store identifying information.

Pega provides five child classes that build upon the rules in Data-Party.

Child classes represent specific types of persons and organizations.

The party class describes the person or entity and determines how the participant interacts with others in the business process.

Data-Party Child Classes

1. Data-Party-Com models a business that has a web domain ending in .com.
2. Data-Party-Gov models a government agency.
3. Data-Party-Org models a non-profit organization that has a web domain ending in .org.
4. Data-Party-Operator models a case participant with a Pega login.
5. Data-Party-Person models a case participant who lacks a Pega login.

Populate the Work Party with Case Data

After the work party is populated, configure your process with participant-specific information.

To populate the party with existing data, use the addWorkObjectParty API activity. Add API activity to the Action tab of a flow action rule, or call the activity by adding a utility shape to the appropriate process.

To allow case workers to add party information during case processing, use the AddParty flow action. Add this flow action to an assignment or stage as a local action.

To prompt case workers to provide party information when creating a case, select the VOE? option for the party on the Work Parties rule form. When enabled, Pega automatically presents users with fields to enter required information.

 

Configuring a Work Party for a Case Type

To use a work party in a case, add the work party to the  pyCaseManagementDefault rule in the class for the case type. 

In the Application Explorer, expand the appropriate
case type, then select Process > Work Parties > pyCaseManagementDefault.

Click the Add a party icon to add a work party to the  rule.In the Party label field, enter a unique name that indicates your work party's relationship to a case, such as Lawyer or Design Manager.

Move off the Party Label field to show the Role field populated with the party label, omitting spaces and special characters. The role identifies the party on the clipboard. Each work party is a page within the WorkParty page group, and the role is used as the page index.

Select an option from the Party class list to identify the class used to describe the party. The party class must be either the Data-Party class or one of its descendants.

Optional: Enter a label in the Party Prompt field to provide an optional descriptor for the party. You specify a party prompt to differentiate the party from another party with the same party label.

Optional: Press the Down Arrow key in the Data transform field and select the name of a data transform that runs when users add the work party to a case. The data transform defines initial values for the work party. Copy information such as a first name or email address to the work party.

Optional: Select the VOE? (Visible on Entry) check box to prompt users to add the work party when a case is created.

Optional: Select the Required? check box to indicate that this work party must be present in every new case.

Optional: Add the party role to the Party list in the List parties that may repeat section to allow more than one instance of your work party to participate in a case.