Scribd
Upload
128 views

Interview Questions

The document provides explanations for various Pega concepts including advantages of Pega constellation, storing different work objects in separate tables, performance measurement using DBTrace and PAL, default routing properties, use of ticket shape, logic for forming a user's ruleset list, locking and its types, spinoff and split join shapes, classes in Pega and types of assignments and where they are stored.

Uploaded by

Vaishali Tupe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
128 views

Interview Questions

The document provides explanations for various Pega concepts including advantages of Pega constellation, storing different work objects in separate tables, performance measurement using DBTrace and PAL, default routing properties, use of ticket shape, logic for forming a user's ruleset list, locking and its types, spinoff and split join shapes, classes in Pega and types of assignments and where they are stored.

Uploaded by

Vaishali Tupe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Tell me abt urself

1. What are the specific advantages of Pega constellation?


It offers a complete presentation layer so that applications are more
appealing to users, allowing companies to deliver and iterate faster.
Since the presentation layer is available out-of-the-box, teams can focus on
business logic and data.

2. 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.

3. Performance of our work in the Pega is measured using?


DBTrace: DBrace 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.

4. In Routing activity what is the default property used to route the object
pxRouteTo=Param.AssignTo =” workbasket name” for work basket .s

For work list: pirouette =Param.Worklist=”true” &&Param.AssignTo =”


pxRequestor.pyUserIdentifier” for work list.

5. ticket: Explain any scenario you used


Use the Ticket shape ( ) to mark the starting point for exceptions that may
arise at any point in the flow, such as a cancellation. The ticket is a label for a
point in flow, much like a programming “GOTO” destination.

6. 34. How a user’s ruleset list is formed ( the logic )?

The system adds entries it finds from the following sources in the order
listed. The system adds entries it finds from these sources at the top of the list,

Requestor - (Data-Admin-Requestor class) — Usually this adds the RuleSets named


Pega-RULES, and Pega-IntSvcs and a version or version prefix for these
Division - As referenced in the Operator-ID instance
Organization - As referenced in the Operator-ID instance
Access Group: As referenced in the Operator-ID instance
Ruleset Versions - Prerequisite RuleSets and Versions to those already compiled
Operator ID - If this user has the ability to check out rules, the personal RuleSet
(named the same as the Operator ID key) is added last. Also called a private
ruleset.

7. What do you mean by Locking in the context of Pega? What are the different types
of locking? Explain them.
When two or more actions try to update a case at the same time, the most
recent action may overwrite data written by the prior action. Overwrites can cause
data corruption or loss, causing delays in case processing and possibly resulting
in an inaccurate case resolution. If an application supports several users at the
same time, a case locking strategy is critical for data integrity.
In Locking, we configure an appropriate locking technique for each case type to
avoid data corruption or loss due to overwrites. Pessimistic locking and optimistic
locking are two solutions that Pega Platform enables to balance the need for user
access with the necessity for data security.

Pessimistic Locking:
When an application uses a pessimistic locking approach to open an object, it
uses an exclusive lock. When a person or a system opens an object, they have
exclusive
access to it until the application unlocks it. Other users are unable to edit the
item while it is locked.

For example, an underwriter examines an open life insurance claim to determine the
amount of benefit that a claimant is entitled to. As the underwriter collects
evidence and
updates the case, a complex claim may necessitate extensive computations and
referrals to third parties,
and any additional modifications may override claim values and generate an
inaccurate payout to the claimant. Apply a pessimistic locking approach in this
situation to prevent
other users from overwriting data when the underwriter updates the claim and
changes the payout amount.

Optimistic Locking:
When an application uses an optimistic locking approach, it does not use an
exclusive lock when opening an object. Instead, the item can be opened and edited
at any moment by any user or the system itself. Before making any modifications to
the item, the program checks to see if it has changed.

A manager, for example, may need to evaluate the most recent data for a given
service request instance. A case worker may need to update the case at the same
time as
the manager does not need to update any information. Apply an optimistic locking
approach in this situation to prevent the manager from locking the case and
preventing a
case worker from completing an assignment that would push the case toward
resolution.

8. Explain Spinoff and Split join shape in the context of Pega.


Spinoff join shape:When one flow execution starts another flow execution that
runs asynchronously and independently of the first flow execution, this is known
as a spinoff. The first flow does not pause or wait for the second flow's results.
The second flow could work on the same or a different work item than the first
flow.
At the workflow level, spinoffs enable parallel processing of work. While one
department or business unit performs its functions for the work item at its own
pace and
according to its own flow, another department works on the same work item.
Increased parallelism can reduce end-to-end resolution times, allowing for more
efficient staffing
and better customer service.

Split Join Shape:This shape causes work item processing to divide into two or more
distinct flow executions that run asynchronously and then rejoin later at runtime.

At the business process level, this capability allows for multitasking or parallel
work processing. While one department or business unit performs its functions for
the work
item at its own pace and according to its own flow, another department works on the
same work item. Similarly, if the split creates six subflows, each of them could be
assigned
to and worked on by six separate users who are all working on their assignments at
the same time.

9. Which are the different types of classes in Pega?


The Data Class - This class specifies the rules that govern the use of data
types and objects.
The Integration Class - This class comprises rules that spell out how the
application interacts with external services and resources such as customer
databases
and 3rd party servers.
The Work Class - This class consists of data items, interfaces, and other
resources that govern the processing of test cases.

10. Which are the different types of assignments, and where are they stored in the
Pega database?
There are fundamentally two types of assignments - the Work-List assignment
and the Work-Basket assignment. These assignments are stored in individual
worklists in Pega.
-The pc_assign_worklist stores work-list assignments
-The w pc_assign_workbasket stores work-basket assignments

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy