|
A name RuleSet is indeed an instance of the rule-rule-ruleSet name type. Since each instance of each type of reference rule or "belongs to" a RuleSet, each defines RuleSet as an important subset of PegaRULES rules in the database. A name RuleSet is an important consideration: 1. Access control 2. Grouping of interrelated rules 3. Manage Rules 4. Move applications from system process to commander. Now we will learn about the rules in PRPC.
A RuleSet is a container for components of your application that store a related set of business rules. It is what you put into production or ship to a customer. RuleSets offer security, version control, and the ability to deploy (or move) your application to a different Process Commander environment. Before you can build an application, you must first create a RuleSet.
A ruleset had two parts i.e rule set name and ruleset version.
Ruleset name: Which describes the RuleSet's name and other attributes.It should have a maximum of 64 characters.
Ruleset Version: which specifies the Version of the RuleSet.It is divided into three sections separated by a hyphen: Major, Minor, and Patch.
Want to Become a Master in Pega? Then visit here to Learn Pega Training
While creating a new RuleSet, you can pick an existing RuleSet as its prerequisite or a parent. By this, we can establish a relation between Rule and RuleSet. A RuleSet is inherited and contains existing characters and features from a parent. A RuleSet always requires at least one RuleSet as a prerequisite, and Pega-ProCom is considered a prerequisite in creating a new RuleSet in most cases. For your application, Process Commander RuleSet consists of standard work management capabilities which can be used to construct blocks.
Create rules and categorise them based on purpose, usage, and dependency; in that way, you can maintain and develop the application with ease. To create a new RuleSet, you need to follow the below steps:
Step one - go to the application.
Step two - select the new option
Step Three - establish the Rule
Step Four - select the SysAdmin
Step Five - select the Rule set version
On Selecting Rule Set Version, a new Pop-Up will be opened as follows. Just give the RuleSet name.
There are three versions represented in the XX, YY, and ZZ format.
XX - a Major Version that releases the partial application
YY - a Minor Version, a temporary release, or Advancements of the application.
ZZ - is a Patch Version where you can fix bugs and patches while running the application.
Related Article : Pega Rules
The major version is the partial release of the application.
Minor version represents the interim release or enhancements of the major verison.
The patch version represents the fixing of issues and bugs in the application. In this patch version, you can fix the bugs even while running the application.
Want to know more about Pega,visit here Pega Tutorial !
Create a RuleSet to identify, store, and manage a set of rules that define an application or a significant portion of an application. Per application, you may require five to eight RuleSets. This is generally generated while using the Application Accelerator; you do not need to create them with the RuleSet form.
The way you use RuleSets in your application has significant design and deployment implications. Several RuleSets may be appropriate for large and complex applications. Ever since you develop a RuleSet, consider the purpose, use, and dependencies of existing RuleSets and the new RuleSet.
Select-->application-->structures.
To see a list of RuleSets in your application (including those on which your application is based) as well as a list of prerequisites for each RuleSet.
To generate RuleSet and version rules in versions prior to V6.1, use the New RuleSet and New RuleSet Version forms, in both. Beginning with V6.1, you can create both rules in the New RuleSet Version form at the same time. The Versions tab allows you to create versions for a specific RuleSet.
Access: To view a list of all RuleSet rules in your system, use the Rules Explorer.
Development: As a best practice, use a wizard, such as the Application Accelerator, to create the initial set of RuleSets you require.
When you create a new RuleSet, you also create an initial RuleSet version XX:YY:ZZ.
Now we will explore the different rulesets and their purposes.
Related Article : Pega Frameworks
These RuleSets offer services that are included in the base PRPC and are generally accessible. The application rule PegaRULES:06-03 specifies the correct order and versions of these RuleSets. The descriptions that follow are only a general indication of the context of the features that are available.
By using record explorer, you can see the complete list of RuleSets in your system.
Some of the RuleSets given below are locked as they depict the way Pega 7 platform features function.
PURPOSE : initially empty but support the Rule Check-in approval process and utilised by developers using that process.
It is not a mandatory RuleSet for client systems which Are Checked by the Autonomic Event Services product. Autonomic Event Services (AES) is an an optional product that monitors, retrieves, organises and displays Pega 7 Platform system statistics and warning conditions at the enterprise, cluster, and node levels.
It is an optional RuleSet, and it administers the Business Intelligence Exchange
Is a part of the AES product and an optional RuleSet Pega Decision Engine is an optional tool and supports the Decision strategy Manager. The Decision category contains rule types that define computations and comparisons. At runtime, these rules calculate a result, or a decision, that causes processing in the application to continue along a particular path.
Pega cust foundation ManagementIt is an optional RuleSet and a part of the Test Framework
Pega app Test ManagementIt is not a mandatory tool and is part of Test Management Framework.
It is an optional RuleSet, The Pega Web Mashup, previously called as the Internet Application Composer (IAC) allows you to Install a Pega 7 Platform application as a gadget on Pega composite application pages
Pega Relationship ViewerIt is an optional RuleSet, The Pega Web Mashup, previously called as the Internet Application Composer (IAC) allows you to Install a Pega 7 Platform application as a gadget on Pega composite application pages
Pega forecasterit is not useful
Pega mobileis used as a Pega mobile application, and its Products.
It is a special processing rule which is a reserved one. It should not be referred to the RuleSet configuration.
Pega RepositoryIt is not used for general purposes; it is a reserved tool
Pega’s unique controlsprovide access to third-party UI facilities in Non-self-generated section. When you save the self-generated section, then Pega 7 derives sources of HTML from the design tab.
Pega Relationship viewerit is not a compulsory RuleSet. It is a part of The Test Management Framework (TMF). TMF is an optional application that administers best practices for development and testing of new applications and provides necessary modifications to Existing applications.
it provides accessibility but an optional RuleSet
Pega-WorkManager Pega-WorkSourceit is reserved for a particular purpose.
Top 40 frequently asked Pega Interview Questions !
Conclusion
In the above blog post we had discussed about the pegg ruleset in a more detailed way. Had any doubts please drop your queries in the comments section.
Related Articles :
Batch starts on 4th Apr 2023, Weekday batch
Batch starts on 8th Apr 2023, Weekend batch
Batch starts on 12th Apr 2023, Weekday batch
When a rule is saved then RuleSet validation is performed. In RuleSet validation mode we need to define a prerequisite RuleSet version for each RuleSet and its version. Rule resolution is not affected by RuleSet validation in run time but will be available only at design time.
To add the Pega RuleSet, follow the steps :
©2023 HKR Trainings. All rights Reserved.