App Studio and asset reuse

In App Studio, use relevant records to encourage the reuse of Rules in App Studio and the Case Designer.  

As your organization implements its maturity model, more reusable enterprise assets become available. Manage these common assets through a center of excellence (COE).  

The following figure shows how an organization avails the reusable enterprise assets:

Relevant records designate records of a Case or data type as necessary or reusable in a child class. Relevant records for a Case Type can include references to fields (properties), views (sections), processes (flows), user actions (flow actions), correspondence Rules, paragraphs, harnesses, Service-Level Agreements, And When Rules that are explicitly important to your Case. For a data type, relevant records designate the most important inherited fields (properties) to include for that data type. 

The relevant records can include records that are defined directly against the class of the Case Type or data type, as well as fields inherited from parent classes. 

Designating a record as a relevant record controls most prompting and filtering in a Case Type and Data Designer. For example, user actions and processes that are marked as relevant records are displayed when adding a Step in the workflow of a Case Life Cycle. 

Fields marked as relevant for a Case Type define the Data Model of the Case. Processes and user actions that are relevant are displayed as prompts in the Case Type to encourage reuse. Views that are relevant are displayed as reusable Views. 

When creating fields, Views, Processes, and user actions in App Studio, Pega Platform™ automatically marks them as relevant records. Relevant records can also be manually designated on the Relevant Records landing page. Additionally, you can add a relevant record by using the pxSetRelevantRecord activity in Dev Studio. 

The records that are no longer relevant to be reused in App Studio can be marked inactive. By marking the records as inactive, you can narrow the list of relevant records to be populated in App Studio without deleting the records.

For more information, see Relevant records for Rule reuse.

The Reuse Library helps you reuse assets from your application's built-on stack or enable components that you download from Pega Marketplace for use by your application. You can reduce the time and cost of development by creating assets in common layers that are reusable in multiple applications. With the Reuse Library, you can search for, filter, review, add, and open reusable assets from multiple categories in the App Studio. 

The Reuse Library contains the following features:

• The Reuse Library has three categories where the reusable assets are displayed: Case Type, Data Objects, and Logic. The Logic tab displays When, Decision Tree, Decision Table, and Data Transform Rules. 
  Note: The Rules must be marked as relevant records to be displayed on the Logic tab. 
• You can search and filter the assets for each category. 
• The system displays each reusable asset as a clickable tile and enables you to add or edit your assets. 
• You can add components from Pega Marketplace in the Components section by clicking Manage. 

The class that the system creates for Reuse Library is Pega-Ext-ExpExplorer-Library.

For more information, see Managing reusable assets in the Reuse Library,

Configuration Sets help users change application settings at run time and adjust an application in a no-code way. They minimize the need for Rule overrides and custom Rule changes. 

Configuration Sets are a set of configurations that the system creates and displays based on the configuration name. The system also creates a property Rule in the background. During run time, you can edit the configuration in App Studio. 

While creating a Configuration Set, in the Configuration scope list, you can specify as application, which implies the configuration can apply to assets in the entire application, such as Data Model and UI elements, or you can specify Case Type, which means that the configuration can apply to assets related to a selected Case Type, such as Case Type and Data Model, or Views in the Case Type. When you select Case Type, you can select a single Case Type or select all to apply to all Case Types. 

Manage Configuration Sets creates a new category for a configuration set. Add Configuration Sets to add a new configuration in a specific category. 

With the introduction of Configuration Sets in App Studio, you can minimize or avoid the usage of dynamic system settings or application setting Rules created from Dev Studio.  

The system creates property Rules for Configuration Sets in the class of the configuration category. 

The system stores instances of the configuration values in the Data-Configuration-Setting class.  

Pages in the portal provide users with the ability to efficiently plan work and perform the management tasks. By using landing pages, you can populate pages with fields and controls. Pega Platform provides ready-to-use landing pages such as Dashboard, Explore Data, and Reuse Library. 

For more information, see Landing pages.

Check your knowledge with the following interaction: