Pega Interview Questions and Answers
1. Explain in brief about Pega.
Pega is a platform that allows the user to develop apps, perform integration with the external system and easily implement mobility. It also helps in managing the case life cycle, extensive user interface design, managing the decisions and implementing the Davos and Robotic Automation, and reporting. It is built on Java and has its latest version as 8.2 which also stands for Build for Change.
2. What are the different types of classes that PRPC support?
The different types of standard classes available are.
- Base class: It is the ultimate base class, and Its Child Classes are working -, Data-, Rule-, Assign-, History-, etc. Pega always supports two types of classes which are abstract classes and concrete classes.
- Abstract Classes: These classes end with ‘-‘ and abstract classes cannot create any work object instances.
- Concrete Classes: It does not end with ‘-’, and abstract classes will create work object instances.
3. What is the difference between Page and Page List property, how are they implemented?
- Page property refers to a particular class and is used to access the property of that class.
- Page List Property also refers to a particular class, but it’s a collection of individual pages of the same class which can be accessed through numeric indexes.
4. Explain about Work Object?
- A work object is the primary unit of work completion in an application and the primary collection of data that a flow operates on.
- When an application is used, work objects are created, updated, and eventually closed (resolved).
- Every work object has a unique ID (property PID), an urgency value, and a status (property pyStatusWork).
5. How to trace SLA in Pega?
Ans: The steps to trace SLA in Pega are:
- Terminate the agent.
- Delay it.
- Initiate the agent.
- Delay it again.
- In the requestors, select the delayed requestor and click on the tracer.
- Send this case to a particular assignment containing the SLA within 60 seconds.
6. What are the different types of layouts available?
Ans: The following are the different layouts types available.
- Column layout.
- Grid layout.
- Portal layout.
- Dynamic layout.
7. What is the ruleset in Pega?
Ans: A RuleSet in Pega is a collection of rules of business that defines an instance. The ruleset is an essential subset of PegaRULES that is necessary to reference instances in the database.
8. Describe the Access group in Pega and its functionality?
Ans: An access group in Pega is an example of a Data-Admin-Operator-Access Group class that creates a set of RuleSet for the requestors. The developer defines access groups and assigns them to different users.
Access Group controls the security based on the job functions. It is the instance of Data-Admin-Operator-AccessGroup. Various aspects that can be controlled through an access group are
- Default and available types of works (also called work pools).
- Primary rulesets (Access Control to rulesets).
- Assigned roles.
- Portal layout.
- Default ruleset for making changes (Default ruleset whenever the user creates/ saves as the rule).
9. Name the Declarative rules in Pega?
Ans: The declarative rule is an instance of a class derived from Rule-Declared.
- They allow for automatic processing of Property values.
- No need to be called explicitly.
- No need to run in a sequential fashion.
- The system manages re-evaluation when it detects a change.
The declarative rules in Pega are.
10. What is the difference between Page-Validate and Property-Validate methods?
This method is used to validate all the properties present on a page. If a page contains embedded pages, this method works recursively to validate all the properties. This method consumes a lot of system resources and takes more time. If you want to validate specific properties use the Obj-Validate method with the Rule-Obj-Validate rule.
This method is used to impose restrictions on property value. Use the Edit validate rule along with the Property-Validate method to impose restrictions. You can validate multiple properties using the Property-Validate method.
11. Explain case management in Pega?
Ans: Case management in Pega enables a user to adapt to the unpredictable, event-driven or automatic changes in a case and its processes. It pools real-time adaptation with unique solutions for every case to suit ad-hoc additions. It also saves the case as a template for future applications.
12. What are the advantages of case management in Pega?
Ans: The advantages of Pega case management are.
- Improve the processes of case management with holistic support.
- Increase the efficacy of case-flow for automatic and dynamic response.
- Ensures consistency and removes errors with context-based and real-time management.
- Lessen time, costs and effort needed to implement case management.
13. Explain the Decision Tree rule.
- Decision trees are instances of the Rule-Declare-DecisionTree rule type.
- The decision tree accepts one input property value but can evaluate numerous properties. It is best used for complex if/then/else statements.
- It can capture and present business logic in the form of one or more if/then/else conditions.
- It can be referred to three other rules from the decision shape of the flow rule.
- In the activity, we can evaluate the decision tree using the Property-Map-decision tree.
- Decision trees can be referring to Rule-Declare-Expression.
14. Differentiate between Decision Table and Decision Tree.
- The logic implemented in the decision table is if, else if condition.
- In the decision table, if the first condition is true, it will not check the remaining conditions/if the first condition is false, then only it will check the next condition.
- For simple logic, we can go to the decision table.
- The logic implemented in the Decision Tree is if, if condition.
- In a decision tree, if the first condition is true or false, it will check all conditions and it will return results.
- For simple logic, we can go for a decision tree.
15. Explain about map value rule.
Ans: A map value rule is a rule that converts one or two input values, such as latitude and longitude numbers, into a calculated result value, such as a city name. The rule uses ranges for the input value or values and a matrix to look up the result. Map value rules are instances of the Rule-Obj-MapValue rule type. This rule type is part of the decision category.