Guided Application Development Using Guardrails

Question 1

How does PRPC assist a user in developing a well performing application.

Answer 1

Guardrails. While they are not errors they are important messages that help to ensure that the application created follows the know best practices for Pega 7. It is important that the user follow them.

Question 2

What happens is a user does not follow best practices?

Answer 2

Increased development time
Features not implemented correctly
Less maintainable
Overall the user is adding undue risk to the applicaiton

Question 3

What does a guardrail consist of?

Answer 3

A severity level and a warning type.

Question 4

What are the three different levels of severity?

Answer 4

Severe - Most serious (highest level) indicates a serious guardrail violation. These are typically things that pose the highest risk, such as things that can impact data integrity. For example,
if we were to create a Data Transform and we added an action that Pega 7 determines to be unreachable we would trigger a severe guardrail.
Moderate - Indicates a moderate guardrail violation. These are typically things that can have medium and long term effects on the project if left unresolved, such as things that can impact maintenance.
Caution - Indicates the least serious type of violation. These are typically things where there is a recommended better way to accomplish the goal.

Question 5

What are some primary examples of types of Warnings?

Answer 5

Data Integrity
Performance
Maintainability

Question 6

What type of warning IDs a rule that may adversely affect application or system performance?

Answer 6

Performance Warning

Question 7

What is a maintainability warning?

Answer 7

Maintainability warnings occur when a rule uses custom code or activities, which can result in maintenance and upgrade issues over time.
The most common guardrail for this is the Custom Code guardrail which can happen in most of the rule types.

Question 8

What are the three tabs on the guardrail landing page?

Answer 8

Dashboard, Summary and All Warnings

Question 9

Can you ignore or not follow a guardrail?

Answer 9

Yes, There will always be exceptions to guardrails. We will find that we need to “justify” certain guardrail warnings because there simply is no other way to implement the given solution. However, if we can minimize these exceptions, or justifications, we will build better applications that are Built For Change