Nobuyuki

PRPC promotes a set of best practices for design and implementation of applications.

For examples, see these PDN articles:

• Ten guardrails to success
• Ten best practices for performance load testing

You can use the Application Guardrails landing page to see these various metrics:

• Compliance Score
• Summary
• All Warnings
• Charts

Additional information is available in PRPC help on the Application Guardrails landing page and it's features.

Other best practices that do not impact the Application Guardrails landing page but are great resources:

• Top Ten usability guardrails
• Naming standards for Case Lifecycle Management components, and for records, classes, tables and other objects

Hope this helps,

Sean

Pega Academy

Hi Sean,

Thanks for quick reply. The links you suggested were very beneficial for me.

Ideally I want to get another tip also.

Can you provide me with the way to retrieve all the logics used for Guardrail verification ?

I am expecting to get all logics in spreadsheet.

For instance,

(Columns are severity, type, waning, message)

Row 1:

Moderate Best Practice     warning

Activity Elimination

Use of activity rules should be limited. For most situations, better, more purpose-based configuration options exist.

Row 2:

Caution Maintainability   warning

Activity Elimination

Consider refactoring this activity into a data transform. Data transforms are easier to read and maintain than activities and provide most of the same capabilities.

And I also want to know how respective items affect the compliance score. 

Regards,

Nobuyuki Tateno 

Nobuyuki

I don't have a spreadsheet available however the following details available from Pega Help should point you in the right direction:

Application Guardrails Landing Page https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm

Warnings

https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm

These two documents do a good job of explaining what is being represented on the Application Guardrails landing page and even references the internal rules that are being used to generate the logic for the warnings to be displayed.

Hope you find this useful,

Sean

Pega Academy

It is also possible to view the complete inventory of warnings by looking at the instances of the Rule-Message class.  As of Pega 7.1.7, Rule-Message instances encapsulate all warning messages, and you can view the entire inventory by expanding the Designer Studio Record Explorer to

Technical > Messages.

The landing page includes several filtering options to assist in finding the messages you are looking for. If you are on an earlier version than 7.1.7, the entire inventory is considerably more challenging to obtain because the warnings are hard-coded into activity-checking logic steps that fire when rules are saved.