Guardrail posts, messages, and best practice information
I was reviewing this post for an answer, but didn't quite find what I was looking for
https://collaborate.pega.com/discussion/complete-list-guardrails
I appreciate the inventory of messages exists, but determining what's using those messages isn't easy.
I'm looking for an inventory of Guardrail compliance messages but also an inventory of how those are being used and when was that usage introduced? It would be helpful to have this info documented somewhere for reference by all of us when we're trying to determine best/next steps for our applications.
For example, I recently upgraded our system to 7.2.2 and noticed a rule I was editing now has an unjustified warning I'd never seen before. The warning didn't appear until I opened the rule for modification in a new version, and it was an altogether minor warning but it causes some confusion when we're suddenly wondering whether this problem is really a problem, how long has it been a problem, is it something I really need to look into more closely, etc. I'm curious as to when this was introduced and what the meaning of it (ie - why was this suddenly important to capture as a Warning). I basically told my teammate to honor the warning but "don't go searching for other cases where we may need to make this change" (in this case, simply adding formatting to the text fields in the correspondence rule did the trick)
If anyone out there happens to read this and knows of a resource, please ping me and let me know.
I was reviewing this post for an answer, but didn't quite find what I was looking for
https://collaborate.pega.com/discussion/complete-list-guardrails
I appreciate the inventory of messages exists, but determining what's using those messages isn't easy.
I'm looking for an inventory of Guardrail compliance messages but also an inventory of how those are being used and when was that usage introduced? It would be helpful to have this info documented somewhere for reference by all of us when we're trying to determine best/next steps for our applications.
For example, I recently upgraded our system to 7.2.2 and noticed a rule I was editing now has an unjustified warning I'd never seen before. The warning didn't appear until I opened the rule for modification in a new version, and it was an altogether minor warning but it causes some confusion when we're suddenly wondering whether this problem is really a problem, how long has it been a problem, is it something I really need to look into more closely, etc. I'm curious as to when this was introduced and what the meaning of it (ie - why was this suddenly important to capture as a Warning). I basically told my teammate to honor the warning but "don't go searching for other cases where we may need to make this change" (in this case, simply adding formatting to the text fields in the correspondence rule did the trick)
If anyone out there happens to read this and knows of a resource, please ping me and let me know.
***Updated by moderator: Lochan to add documentation request ID***
Accepted Solution
Pegasystems Inc.
IN
Jeremy and Pankaj,
Thank you for identifying and confirming a documentation requirement. I have created a request to the Pega documentation team on our internal portal. The request ID is updated under the Related Support Case Number field, in the original post above. I will keep you posted on any updates on this request.
Regards,
Pegasystems Inc.
IN
So basically you want a list of warning along with possible reason written somewhere for developer ready reference like we have all PEGA ALERT listed along with reason and remedies.
EPAM Systems, Inc.
ES
I have reviewed the link shared by you, it covers all the information regarding Guardrail warnings.
I researched regarding Pega alerts, if you want any information regarding them.please refer to this link :- https://docs-previous.pega.com/performance/alerts-alert-analysis-tools-and-usage-guidelines
It contains list of all in-built alerts.
Kindly notify me, if it helped you.
Wells Fargo N.A.
US
Thanks for the feedback. Unfortunately, still not exactly what I'm looking for to this point. Let me try another angle:
Some condition has to be met to raise a guardrail message.
Is there a catalog of the "Pega provided/default" conditions provided/posted somewhere?
J
Pegasystems Inc.
IN
Unfortunately we don't have such catalog available. However I feel it is good idea to have one either as help or PDN article. Could you raise a feedback request for the same.
Thanks :)
Accepted Solution
Pegasystems Inc.
IN
Jeremy and Pankaj,
Thank you for identifying and confirming a documentation requirement. I have created a request to the Pega documentation team on our internal portal. The request ID is updated under the Related Support Case Number field, in the original post above. I will keep you posted on any updates on this request.
Regards,
Pegasystems Inc.
US
The Help for "Working with messages" contains some info on this. Basically, any instance of Rule-Message where "Category" = Warning is a guardrail message (since 7.1.7). You can generate a report of Rule-Message instances the same as for any other rule type.
The rule's "Severity" is used when composing the guardrail score, and the "Application impact" describes what kind of problem is reported. I will work on improving the Help. You can also search the Help for Rule-Message and for Guardrails.