Question

13
Replies
1992
Views
JonnyGar Member since 2009 91 posts
BNY Mellon
Posted: 5 years ago
Last activity: 5 years 1 month ago
Closed

How to do effective rule revalidation?

Looking to have a consistent, modern approach to revalidating rules.

Taking off from a PDN document initially written for v5.4...

https://pdn.pega.com/system-operations/how-to-revalidate-all-rules-in-a-ruleset

the description for BulkValidateSave says "Run the validation and save the record without updating its history."

And yet the code updates the pxUpdate* properties and writes a message to history -- that seems to contradict the description.

RevalidateAndSave requires us to filter by class (why? why not all rules in a ruleset?) Reviewing the docs for RevalidateAndSave... "If an instance passes validation, the History tab is updated with your Operator ID, the current date and time, and current system in the Updated row. For rules, a history detail instance is added with your Memo and the notation Bulk Update."

Which is, not exactly what we want. Updating the pxUpdate* properties is not ideal, since it gives the false impression that the user made a substantive change to the rule.

It would be prudent to have fields distinct from pxUpdate* (which imply that an actual change has been made). Why not create new fields called pxValidate*

Additionally, it would be helpful to have a Validate button on a ruleform, which would simply run the validation, but not update the pxUpdate properties (and not save a record in history)

***Updated by moderator: Lochan to add Categories***

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Case Management
Moderation Team has archived post
Share this page LinkedIn