2/20/14

Video

Close

Transcript for Work Parties

Describe a Work Party and Work Party Roles; Define Data Party Class
A work party represents an entity that needs to be notified about the progress or status of work.This can be a person, organization or business and they typically receive email or some other form of correspondence. For example, our loan application process includes two work parties: the Loan Agent and the Loan Officer. When a Loan Agent begins processing a loan request theres an option for adding the Loan Officer as a new Work Party. Selecting the Loan Officer associates pertinent information like their first name, last name and email address with the work object. As application processing continues the system can send notifications to the work party. In PRPC we use the Work Parties rule to define these entities. Here is a simple Work Parties rule named Default. Using the rule form we define who can participate in the work item by configuring each work party by role. A role concisely describes the party and their part in the process. Here we see the two work parties defined for the loan application process. The Loan Agent responsible for processing the work and the Loan Officer underwriting the loan. Work party roles map to existing data classes in PRPC. The Data-Party class contains commonly used properties and user interface rules for capturing and storing work party information. The Data-Party subclasses contain specialized rules that map to specific work party roles. Other roles include: An individual, like a loan applicants spouse, which would map to Data-Party-Person, a business, government or non-profit organization which correspond to the Com, Gov and Org classes respectively, and, as weve seen in our example, PRPC Operators which map to the Operator class. PRPCs flexibility allows you to extend Data-Party and create your own work party roles as needed. Lets take a quick look at the New work form again. The .New harness is one place we see work party information displayed. The harness includes fields from Data-Party, a section from Data-Party-Operator and the user interface necessary to add additional work parties.

Describe Work Parties and the Clipboard

Using the Clipboard we can look at the page structure of the Data-Party classes and their properties. With the loan application process started we see the Loan Agent work party displayed in the new work form.

https://academy.pega.com/prweb/PegaSSO/WmhSmvRrQ7qWntq73M7R4oiuqIskpuJu*/!THREAD1?pyActivity=%40baseclass.pzTransformAndRun&pzTra

1/3

2/20/14

Video

Next we click the clipboard icon. This launches the Clipboard tool we use for reviewing and debugging our page structures and properties. In PRPC, when a work party is associated with a work item a built-in property is embedded into the work item called .pyWorkParty. The property is defined as a Page Group of class Data-Party. The Work Party role, in this case LoanAgent, is specified as the index. As we add a second work party to the work item and refresh the Clipboard youll see .pyWorkParty contains the details of each work party. If we click on the Loan Agent Page we see the details stored in the work item and associated with the work party role.

Configure a Work Parties Rule

Lets look at the configuration settings of an existing Work Parties rule. We can find it under the Process rule category and the Work Parties rule type. By convention, the rule is named Default and when we open it the Valid Parties tab is displayed. The rule was created by the Application Accelerator and is based on the roles we specified in the wizard. A role concisely describes the work party and their part in the process. Standard roles exist like Operator and Manager and or we can create custom roles like LoanOfficer. For this example lets focus on the LoanAgent role as we step through the configuration settings. First, the Party Label is the unique name we see displayed in the user interface. Its used here, for example, in the new work form. The Party Class field references the data class that contains the properties well use to store the work party information. Data-Party-Operator is the standard class used for work parties directly involved in processing a work item. There are five standard classes available or you can create your own. The Data Transform field references a Data Transform rule that initializes properties for the work party and sets their value. VOE stands for Visible on Entry. Checking the checkbox for the selected work party displays party information on the new work form by default. Otherwise an Operator must choose a work party manually. When the Required checkbox is checked the work party will automatically be associated with every work item created in the system. The List Parties that may repeat field allows for the addition of multiple instances of a single work party role. Simply specify the role you want to repeat in the field. This, for example, is useful for adding dependents to an auto or life insurance policy.
https://academy.pega.com/prweb/PegaSSO/WmhSmvRrQ7qWntq73M7R4oiuqIskpuJu*/!THREAD1?pyActivity=%40baseclass.pzTransformAndRun&pzTra 2/3

2/20/14

Video

One way we use the Work Parties rule is to associate it with a starting flow rule. In this case the StartMortgage flow. On the Process tab, below the Work Object Creation Settings section, we see the Default Work Parties field referencing the Default rule. This allows Operators to specify work parties from the new work form.

Add a Work Party from Assignments; Route to Work Parties

We typically add work parties to a work item when it is created using the new work form. But PRPC also lets us add a work party while the work item is being processed using an Assignment. Lets take a look at the UnderwriteLoan flow rule and the Credit Report assignment by opening the properties panel. On the Local Actions tab in the Local Action field we can use SmartPrompt to select AddParty. Now, when a work item reaches the Credit Report assignment, the operator will have the option to add a new work party. We can also route work to a work party from an Assignment. Again using Smart Prompt, we can select the ToWorkParty routing activity and specify the work party we want to receive the work. In this case well route the assignment to the Loan Officer.

https://academy.pega.com/prweb/PegaSSO/WmhSmvRrQ7qWntq73M7R4oiuqIskpuJu*/!THREAD1?pyActivity=%40baseclass.pzTransformAndRun&pzTra

3/3