Assessing Guardrail Compliance

Pega monitors your application for configurations that lead to maintenance or performance issues. By addressing these issues, you improve application quality and prevent performance issues for users.

Guardrails

1. To help you develop high-quality applications, Pega monitors your application for compliance with application design best practices (guardrails).
2. When a rule in your application violates one or more guardrails, Pega notifies you with a rule warning that prompts you to review the deviation and update your application prior to release.

Compliance Score

1. The compliance score measure overall compliance with Pega 7 Platform best practices.

   Measures the number of rules with severe/moderate warnings, compared to the number of rules with caution level warnings or no warnings.

   Indicates the impact of complex or custom code on application maintenance and performance.

2. Use the compliance score to measure the quantity and severity of rule warnings in your application.

How to Access the Guardrail Compliance Score

1. Use the Guardrails landing page to assess application quality.
    Select Application > Guardrails from the  Designer Studio menu. 
2. Review the compliance score and any rule warnings.

Compliance Score Rankings

Pega assesses the rules in your application and calculates the compliance score on a scale of 0-100, where 100 is the best possible score.

1. A score of 90 or greater indicates your application is in good standing.
2. A score of 80-89 indicates your application needs review for improvement.
3. A score below 80 indicates that your application requires immediate action.

Warning Summary Tab

1. The Guardrails landing page also categorizes the rules in your application that include warnings.  
2. The Warning Summary tab presents two bar charts that report the number and severity of rule warnings in your application, organized by rule type.Use the information on this tab to determine which parts of your application generate the greatest number of rules with warnings.

How to Analyze Risk Areas

1. Use the Compliance Details tab to view three options for analyzing risk:

   Warning impact: The severe and moderate configuration issues to address before release.  
   Warning age: The age of the warnings in your application. 
   Application risk introduced by operator: The developer(s) responsible for introducing the behavior generating the warnings.

2. Resolve the issues in the Warning impact section first.   
3. The list is organized by warning type, and highlights the warnings with the greatest impact on the compliance score.
4. Click each number to view the list of rules that violate guardrails.  
5. The rule that contains the warning opens when a rule warning is selected.
6. Pega displays the rule warning at the top of the rule form.

Read more

Import and Export Bulk Excel Data in PEGA

Pega provides a variety of rules to do Import and Export Bulk Excel, but in this case, we will use "MSOParseExcelFile" for Pega Read Excel File and "MSOGenerateExcelFile" for Pega Write Excel File.

MSOParseExcelFile (Pega Read Excel File)
Logic pseudocode:

• Upload binary template
• Set Parameter for MSOParseExcelFile
• Create a new Page List for accomodate Excel Data 
• Call MSOParserExcelFile
• Looping the page list from Excel Data
• Open the case using obj-open by pyID
• Update the case value base on excel mapping
• save - commit
• remove page

Here is the template Capture.



Here is the Activity Capture for MSOParseExcelFile

MSOGenerateExcelFile (Pega Write Excel File)
Logic pseudocode: 

• Upload binary template
• Read Data (from DB, Clipboard, etc)
• Mapping the value as binary template
• Call MSOGenerateExcelFile 

Here is the Template Capture


Here is the Activity Capture for MSOGenerateExcelFile

Read more

Accessing Applications

System architects use the Designer Studio to configure applications. To ensure that application developers work on the correct application, Pega provides a system to manage user access to each application.

How Users Access an Application

When users log on to Pega — Pega grants the user application access based on the operator record configuration.

Pega manages user access through a combination of three items of information:

1. Operator 
2. Access group
3. Application

Operator Record

In Pega, each user is represented  by an operator record.

The operator record contains information  about the operator, such as their name,  position, organizational hierarchy, and  location.

Access Group

Each operator is a member of an access group.

1. The access group record describes a set of privileges for users. 
2. Privileges are available to users who belong to the access group. 
3. The access group also indicates the portal through which the user interacts with Pega. 
4. An operator can belong to any number of access groups. 
5. Only one access group is active at any time.

Application

Each access group references a specific application.

The privileges available to members of the access group apply only to the referenced application.

How Pega Determines the Application a User Opens

To log on, a user enters their ID and password.

The ID corresponds to a unique operator record listing a set of access groups. 

The password authenticates the user.

The active access group determines the application to run

Allowing a User to Access an Application

To allow a user to access an application, you add the appropriate access group to the user's operator ID record.

Each access group has a unique name that references both the application name and the access level.

Read more

The Role of the System Architect

A successful Pega application requires collaboration between three parties to solve business problems.

1. Business stakeholders
2. Business architects
3. System architects 

 

Types of Systems Architects 

1. Lead System Architects

• Direct the technical effort on a project

• Work with business architects (BAs) to design an application architecture

• Design the architecture to reuse application assets as much as possible

• Meet quality goals, including application performance

2. Senior System Architects

• Supervise development of a particular process or user interface (UI) form

• Add technical details to specifications

• Translate application requirements into

• guardrail-compliant feature designs

• Identify opportunities to reuse

• assets within the application design

3. System Architects

• Configure and unit test individual application elements such as correspondence and automated decisions
• Help draft processes and user
  interfaces during DCO sessions

Read more