Top Pega Interview Questions With Answers

Q. What is the difference between Page-Validate and Property-Validate methods?

Page-Validate method is used to validate all the properties present on a page. If a page has embedded pages, this method works recursively to validate all the properties. This method consumes lot of system resources and takes more time. If you want to validate specific properties use Obj-Validate method with Rule-Obj-Validate rule.

Property-Validate method is used to impose restrictions on a property value. Use Edit validate rule along with Property-Validate method to impose restrictions. You can validate multiple properties using Property-Validate method.

Q. What is difference between Edit validate and Edit Input rules?

Edit Validate: Use edit validate rule to validate the property value using java code. Edit validate rules can be used property-validate, Rule-Obj-Validate and Property rules.

Edit Input: Edit input rules converts user entered data into required format. For example is the user enters date MM/DD/YYYY format, edit input rule coverts this date into DD-MMM-YYYY (required format). Again we need to write java code for this transformation.

Q. Where assignments will be stored in pega rules database?

Work List related assignments are stored in pc_assign_worklist.

Work basket related assignments are stored in pc_assign_workbasket.

Q. Where work objects will be stored?

Work Objects are stored in pc_work table by default. however if you want to store the work objects in a user created table, follow the below mentioned steps.

Create a schema similar to pc_work table. (The best thing is to copy the pc_work schema and modify the table name and constraints name if any)

Change the class group mapping (Data-Admin-DB-Table) to the newly created table.

Q. If I have 3 different work objects in my application, how to store them in three different tables?

Open/Create the Data-Admin-DB-Table instance for each class and mention the table name. By doing this the individual work objects will be stored in the new table you mentioned in the Data-Admin-DB-Table instance. This is a best practice if there too many object instances for each class.

Q. What is StepStatusGood, StepStatusFail rules?

StepStatusGood is a when condition defined in @baseclass, this when rule checks whether the value of pxMethodStatus property is “Good”.

StepStatusFail is a when condition defined in @baseclass, this when rule checks whether the value of pxMethodStatus property is “Fail”.

Q. How to make any rule as a favorite to your manager?

Delegate the rule to manager.

Q. Where can i see the paramater values in the clipboard ( values ..) i am passing one activity to other ?

No its not possible in clipboard, but you can see in tracer by clicking page name which in step method column.

Q. How to import rules using pzinskey

Open the rule, from that pick the pzinskey, go to prdbutil and using the pxinskey export the rule Import that zip file where you want.

Q. Difference between activity and utility?

An activity is an instance of the Rule-Obj-Activity rule type. An activity is the fundamental sequential processing unit of the Process Commander system.

The shape in a Visio flow diagram, references an activity that updates a work object, but does not require user interaction and input. Your system includes standard activities for utility tasks, and you can create additional ones.

Each utility task references an activity with an Activity Type of Utility ss from utility shape we can call activity but vise versa not possible.

Q. Difference between obj-open and obj-open-by-handled

Obj-Open : we will get multiple records from table based on the criteria from the specified class. Or Opens an instance of a given class

OBJ-open-handle: here we have have to pass the pzInskey as a instance handle, this mehod will open only one record at time. Or Open object by handle to the pzInsKey value
The handle of an instance is a unique key, in an internal format, assembled by the system that identifies an instance in the PegaRULES database. It may differ from the visible key generally used to identify instances. (Every instance has a unique handle, but more than one instance may share the same visible key.) For rule instances, the handle includes system-generated identifying values (including the create date and time) that make it unique.

Use the Obj-Open-By-Handle method only if you can determine the unique handle that permanently identifies which instance to open. Otherwise, use the Obj-Open method.

Q. Inheritance concept in the pega (rules, class)

Rules: inheritance that can maximize reuse of your rules while allowing localized overriding as appropriate. Also called polymorphism, inheritance allows a rule created for one class (possibly an abstract class) to be applied to other classes that inherit from it.

Class inheritance searches for rules from a concrete, lower class, up the class hierarchy to find available rules.

Two types of class inheritance — directed inheritance and pattern inheritances

Q. Performance of our work in the pega is measured using?

DBTrace: DBTrace is a feature in the Performance Analysis Tool (PAL) that creates a detailed log of calls to the PegaRULES database. DBTrace displays SQL statements sent to the database and the time spent for each operation.

PAL: This data is stored in “PAL counters” or “PAL readings.” PAL stands for Performance AnaLyzer, and is a collection of counters and timer readings, stored in the requestor, that an application developer could use to analyze performance issues in a system.

PAL Features

Add Reading
Add Reading with Clipboard Size
Reset Data
Save Data
Start DBTrace
DBTrace Options
Start Profiler
Show Graph
My Alerts
Alerts: During application processing, Process Commander writes to the performance alert log a sequence of text entries called alert messages that identify mainly performance-related issues or errors. The performance alert log is usually named PegaRULES-ALERT-YYYY-MMM-DD log.

AES: Exceptions are processed in a similar way as alerts. When a Process Commander server generates exceptions they are sent by SOAP to the AES system. The system parses the exceptions and stores the records in the pegaam_exception table in the AES database. Based upon how often an exception occurs and the system events that triggered those exceptions, AES aggregates these records into work objects called AES exception items. These items are written to the AES database in the pegaam_exception_work table.

For more interview questions, visit here