Brian Hamner (hamnb)
Senior Specialist Solutions Consultant - 1:1 Customer Engagement
Pegasystems Inc.
hamnb Member since 2019 3 posts
Posted: June 12, 2019
Last activity: June 12, 2019
Posted: 12 Jun 2019 8:52 EDT
Last activity: 12 Jun 2019 10:05 EDT

Best Practices using built in Document Categories and Validation rules

Later versions of Pega introduced the concept of using a Stage Entry Validation specific to document categories. A case designer can specify what document categories must be attached to the case before the case can progress into that stage. If a user attempts to progress the case into that stage, he/she is given an message indicating what documents are missing.

I wanted to query the community to see the different ways this has been used. And more specifically, how can this be used to AUTOMATICALLY determine what documents are missing at a point in the case, and automatically assign tasks to a customer's worklist to provide them.

Ideally, a case designer can call the built in function that is being used under the covers of the Stage Entry Validation (documents) at any point in the process. Having the ability to call it as part of a When would allow you to determine if the docs are present and send out the request automatically. This would provide more automation than a backoffice worker attempting to approve to the next stage, seeing the error message from stage validation, then manually assigning the task to get the missing documents.

I realize you can use decision tables and when rules on the pyattachments.category, but was looking to make better use of the out of the box validations.

Anyone know how to do this?

Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.