Skip to main content

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

Work object naming conventions

Updated on April 26, 2021

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.

ApplicationWork objectApplies to
TSTTest ClaimPegaHC-CLM-Work-Claims-Test
ECEvent ProcessPegaHC-CE-EM-Work-Event
ACAction CodePegaHC-CE-AM-Work-ActionCode
RARandom AuditsPegaHC-CE-PM-Work-RandomAuditProcess
EGGroup Claim ProcessingPegaHC-CE-EG-Work-EventGroup
PEPayment ErrorPegaHC-CLM-PaymentError
SYSSystem ConfigurationPegaHC-CE-SC-Work-Configuration
CXTClaimsXten RecommendationPegaHC-CE-RC-Work-CXTRecommendations
SBAccident SubrogationPegaHC-CE-PR-Work-AccidentSubrogation

You can change this prefix or create additional prefixes by modifying the entry in the Details tab of the application rule.

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