When your application initiates a work object, a predefined model populates key property values, such as urgency, that directly affect the work object's relative priority and placement in operator worklists. As work objects progress towards resolution, core property values such as priority and status, are continually updated to reflect the current stage of processing.
Each work object has a unique ID that is computed by combining a system-assigned number and a prefix defined as in a pyDefault model in a ruleset. For example, PR-1003 could be a work object related to a purchase requisition application. The following table shows the prefixes currently defined in Pega Smart Claims Engine for Healthcare.
|Application||Work object||Applies to|
|EG||Group Claim Processing||PegaHC-CE-EG-Work-EventGroup|
You can change this prefix or create additional prefixes by modifying the entry in the Details tab of the application rule.