More about Work Parties rules
|
|
Enter all your Party Roles for the application in one or a few Work Parties rules, one for each of your work types, and name each Default
.
Before creating a Work Parties rule, select or create appropriately configured data classes. Choose a data class that:
Eligible standard classes include:
A specific standard HTML rule (per class) named PartyDisplay
determines which fields appear for each party role. Find or create this instance in each of your Data- class (or in a class from which your Data- class inherits such as Data-Party or Data-).
Before completing the Work Parties form, familiarize yourself with the Data- classes that define each party role.
Plan the party role configuration
When you create a Work Parties rule, you determine the following:
The Role and Party Prompt fields on the Valid Parties tab are visible to application users. When you localize an application, create a language-specific Work Parties rule for each base Work Parties rule. For example, the following can appear in a Work Parties rule for a French-speaking locale:
Determining the class of a party
No field in a work item identifies the class of a party — for example whether the party with the role Lawyer is of the class Data-Party-Person or a Data-Party-Com. To learn this call the standard function getPartyClass(appliestoclass, workpartyname, rolename), part of the PegaProComUtilities library. Identify the key parts of a work party rule in the first two parameters, and a work party role in the third parameter.
For example, the following expression obtains the class of the Interested party in a work item in the PegaSample application:
=@getPartyClass("PegaSample", "Default", "Interested")
harness forms, locale, originator, work party role | |
Internationalization and localization — Concepts and terms | |
Atlas — Standard work parties rules |