rule check in without warning justification
Hi,
Is it possible to prevent developers from checking in their code if there are unjustified warnings?
--Prasanth
Accepted Solution
Pegasystems Inc.
IN
Hi Prasanth, Good morning!
- would it be convincing to enable Rule check-in approval process on ruleset version to ensure the warning to be justified? OR
- need to override RULE-OBJ-ACTIVITY RULE- PRECHECKIN to enforce user to justify the warnings before rule check-in
- For each --> pxWarnings --> Pre-condition (pxIsWarningJustified=true, skip iteration else continue) --> Page-Set-Messages --> "Message - Please Justify warnings"
- need to test this overwrite during bulk process (bulk check-in, re-validate & Save...)
- For each --> pxWarnings --> Pre-condition (pxIsWarningJustified=true, skip iteration else continue) --> Page-Set-Messages --> "Message - Please Justify warnings"
Please share your thoughts/observations, Thank you!
psahukaru
GovCIO
US
Yes Prasanth. Check this rule: CheckForCustomWarnings and you need to customize it in your RSV. We did the changes for our team to generate the multiple warnings.
Thanks,
Ravi Kumar.
Virtusa
US
Ravi,
When we try to save as the rule CheckForCustomWarnings in application RSV, we are getting "Please correct the flagged fields before submitting the form .—
This instance conflicts with Final record RULE-OBJ-ACTIVITY @BASECLASS CHECKFORWARNINGS #20130919T000349.611 GMT (Pega-WB:07-10-01)" error. Any help
This comment has been branched out as a new node and the new thread can be followed here