Creating a rule in dev studio:
To make sure that your project meets the customer requirements and saves time, create data instances and rule with reusable features of the application. You provide a distinct identity to every rule you create by combining a rule name, type, set of rules and class.
If you require more control over the creation and reuse of a rule, you may create the rule in the Dev Studio. When you are creating the rule, the new record form will ask you to provide information like identifier, rule type, ruleset and class. This information will help you in identifying the rule uniquely in your application. This combination will enable an application to call the right rule while the case is being processed through a process called rule resolution. With Rule Resolution, Pega Platform identifies which rule is appropriate to execute when a rule is called by the application.
In Dev Studio, the word records are used to refer to rules, properties and other objects in the Pega Platform. Rules can be accessed from the navigation menu of the Dev Studio by clicking on Records and selecting the rule type to view the rules list of this rule type.
Want to Become a Master in Pega? Then visit here to Learn Pega Training
Various methods for creating rules in Dev Studio:
There are several ways to access the New Record form depending on the way a new rule is created. The way the rules are created will determine how much information is entered automatically.
Pega Certification Training
- Master Your Craft
- Lifetime LMS & Faculty Access
- 24/7 online expert support
- Real-world & Project Based Learning
Following are some of the ways in which rules are created:
- Creating a rule from the create menu: If we create an SLA in Pega this way, then by default, the rule type, ruleset context, and application are specified.
- Creating a rule from App Explorer: If we create an SLA in this way, then by default, the rule type, ruleset context, apply to a class and application are specified.
Pega Rules
Open the existing rule and save as: If we create an SLA in this way, then by default, the Rule Type, ruleset context, apply to a class, application, SLA definition and identifier are specified.
Organizing rules:
To better manage your application, organize its components and the rules logically and consistently. Rules can be grouped into classes and rulesets so that we can reuse them conveniently while application development. Consequently, you cut down on development costs and time.
Organization of rules into rulesets:
Organize rules into rule sets for identifying, storing, and managing the set of rules that will define the application's reusable element. When the rules are grouped into a ruleset, you can save time, as the entire set of rules can be reused in different applications of your system instead of creating or reusing individual rules.
Organization of rules into classes:
To manage your applications more efficiently, organize the rules into classes. A class will describe a set of rules or objects like activities, properties and HTML forms that are accessible to other child classes or instances of the class.
Classes are organized into a hierarchy, where the system will search from the present class upwards by searching for a ruler to be applied.
Want to know more about Pega,visit here Pega Tutorial !
Subscribe to our YouTube channel to get new updates..!
Deleting a rule:
The rules that are not relevant to the application can be deleted.
Rule Resolution:
It is a search algorithm that is used by the system to find out the suitable rule instance to apply for the entire processing. With the help of automatic rule resolution, time can be saved, and you can ensure that resources are implemented in a way that is most effective in a particular scenario.
Changing the scope of the rules:
You can Customize your application for specific business requirements by changing the scope of the rules. For example, a rule can be moved to another class or ruleset in order to be able to use the rule in another part of the application.
Checking out a rule:
In order to avoid accidental rule conflicts or modifications, that could arise from more than one developer using the same rule, check out the rule. This will make the rules to be securely locked and modified. By checking out the rule before editing it, you can avoid unnecessary rule changes that would result in maintaining a better quality application and also saves time.
Visit here to learn Pega Training In Bangalore
Restoring a rule to its previous state:
In the course of developing the Pega Platform application, we can cancel the recent rule changes and can replace them with the previous copy, even though another developer has developed the newer copies.
Most frequently asked Pega Interview Questions
Exploring the rules in the application:
It would help if you examined the rules that define all the application features of those rules. Scrutinizing those rules before defining the program's new features will help you avoid duplicate resources. Therefore, it reduces the application development cost and time.
In this post, we have gone through the information related to Pega rules in detail. Hope you found this information helpful.
Other Related Article:
About Author
Kavya works for HKR Trainings institute as a technical writer with diverse experience in many kinds of technology-related content development. She holds a graduate education in the Computer science and Engineering stream. She has cultivated strong technical skills from reading tech blogs and also doing a lot of research related to content. She manages to write great content in many fields like Programming & Frameworks, Enterprise Integration, Web Development, SAP, and Business Process Management (BPM). Connect her on LinkedIn and Twitter.
Upcoming Pega Certification Training Online classes
Batch starts on 13th Dec 2024 |
|
||
Batch starts on 17th Dec 2024 |
|
||
Batch starts on 21st Dec 2024 |
|