Professional Documents
Culture Documents
8. Where can i see the parameter values in the clipboard ( values ..) i am
passing one activity to other?
18. how can i store the instance of the class in the data base
19. default data table where the instance of the class are store (how it
will search ) pc_work
20.In Routing activity what is the default property used to route the
object
22. Notify
26. Different type of flows. Explain in scenario based where u used and
worked
27. work object ID.. how to create.. activites used to create, or methods
Work ID:
30. how to end the work object in the activity (method used to kill the
work object)
33. How can I pass page as the parameter to the activity using java,
JavaScript?
35. How to get a property value from clipboard using Java step?
37. List different functions used to call an activity from java script.
50. Differentiate Decision table, Decision tree, Map value and Map value
pair
7.
9. What is an Exposed P
Pega is built on Java. Its latest version is Pega 8.2, which stands for Build for Change.
o CSA: CSA stands for Certified System Architect. It is the basic level of
certification as the entry-level for a developer.
o CSSA: CSSA stands for Certified Senior System Architect. This is an advanced
level of certification for developers. The developers with this certification are
considered experts in building, judging, and leading a team with good
technical aspects.
o LSA: LSA stands for Lead System Architect. This is the most advanced level of
certification for developers. The developers with this certification are
considered leaders of development who are through with all the
functionalities and implement accordingly.
o App Studio
o Dev Studio
o Admin Studio
o Prediction Studio
o Base class: It is the ultimate base class, and its child classes are work-, Data-,
Rule-, Assign-, History-, etc. Pega always supports two types of classes which
are abstract classes and concrete classes.
o Abstract Classes: The Abstract Classes are the classes that end with '-' and
abstract classes cannot create any work object instances.
o Concrete Classes: The Concrete Classes do not end with '-', and they will
create work object instances.
o Page- Remove
o Page- New
o Object - List
o Object -Open
o Object - Save
o RBD -Save
o RBD - List
o RBD - Delete
o Page property: Page property refers to a particular class and is used to access
the property of that class.
o Page List property: Page List Property also refers to a particular class, but it is
a collection of individual pages of the same class which can be accessed
through numeric indexes.
Page-validate:
Property-validate:
Every work object has a unique ID (property pyID), an urgency value, and a status
(property pyStatusWork).
Following are the steps that we have to implement in creating a work object in Pega:
Declare Pages:
Regular pages:
o Regular pages or user pages are created using a page new method.
o These pages can be easily updated or deleted directly
o , and these pages are automatically deleted once logout from the system.
o Browser requestor: The browser requestor starts with the letter 'H'.
o Batch requestor: The batch requestor starts with the letter 'B'.
o Application requestor: The application requestor starts with the letter 'A'.
o Portal requestor: The portal requestor starts with the letter 'P'.
o Work Class: The work class includes the processes, data items, and user
interfaces. These are all part of the work class, which provides the rules that
govern how to process a case.
o Integration Class: The Integration class consists of the rules that specify how
the application interacts with other services, such as the integration resources
connecting to a customer database or a third-party web server.
o Data Class: The data class stores the rules that specify the data objects used
in the application, such as a customer data type or order items data type etc.
When a rule is added in the App Studio, it automatically selects the proper class. You
have to concentrate on what you want the rule to accomplish rather than how to
develop it. You can also write the rule in Dev Studio if you need control over the
class. The Dev Studio is preferred if you write a rule that you can reuse in another
app.
21) What do you understand by DCO in Pega?
In Pega, DCO stands for Direct Capture Object. It is an apple dev tool that includes
the following things in the application.
Obj-Open: In Obj-Open, you will get multiple records from a table according to the
criteria from the specified class. It also opens an instance of a given class.
"Finish Assignment".
33) What are work objects in Pega?
Work objects are the primary unit of the completed work in the application. It is a
collection of essential data in which a flow operates. All the work objects contain an
urgency value, unique ID, and status.
o Screen Layout: The screen layouts are only used within a harness and are
typically used to establish portals for an application.
o Dynamic Layout: The dynamic layout is a DIV-based layout, and it is used to
display content in a variety of ways.
o Column Layout: A Columns layout is used to allow us to show major content,
like a work item, alongside supporting stuff, like an attachment.
o Grid Layout: The grid layout is also called table layout. It makes obtaining and
comparing data easier for the users. In this layout, tables are used as a flexible
base for users to process vast volumes of data in your apps. An example of a
grid layout is "tables" in price comparison software, and it can assist
customers in quickly identifying the best deal.
o Tree Grid Layout: The tree layout is used to view, navigate and access the
properties in embedded pages. It facilitates users to swiftly extend and
collapse branches of the tree to identify entries of current interest.
In dynamic and column layouts, you can add content to a section, such as properties,
controls, and other sections. The format of the skin determines the positioning,
alignment, width, and arrangement of components in a layout.
35) What is the difference between Pega BPM and
Appian BPM?
A list of key differences between Pega BPM and Appian BPM:
Latest Version The latest version of Pega The latest version of Appian is Appian
BPM is Pega - 7.2. - 18.1.
Integrations Pega BPM supports Data Appian BPM supports only Compatible
Supported Collection Systems and Datasheets.
Various CRMs
Customer Types / Pega BPM is mainly used in Appian BPM is mainly used in small,
Mainly used in medium and large medium, and large businesses.
businesses.
The main advantage of declaring pages is that it can prevent multiple DB hits.
Suppose there are multiple requestors in a node, so whenever the first user login into
the application, then load activity will be fired and create a declare page and then
load the data on that page. The requestors on that node see this declare page and
use the data on that page.
The main disadvantage of this is its read-only to the requestors. It can't add the
additional data and can't delete the specific data.
o Declare Expressions
o Declare Constraints
o Declare On change
o Declare trigger
o Declare Index
o Clipboard
o Tracer
o SMA
o PLA
o Inner join
o Outer join
o Right Outer join
o Left Outer join
Access group is used to control the security based on the job functions. It is the
instance of Data-Admin-Operator-AccessGroup. Following are the various aspects
that can be controlled through an access group:
Generally, we only require the four requestor types that contain our system name. If
we want to modify the system name after installation, we have to go to Designer
Studio => System => Settings => System Name to get to a landing page tab where
we can make the change. When we change a system's name, new requestor
instances are created that correspond to the previous name's instances. If the prior
system name did not include all requestor types for some reason, the missing
requestors are also produced when the system is renamed.
A workspace is a place where you can use specialized tools and functionalities. You may
let team members focus on tasks that fit with their expertise by using different workspaces
to create and administer your application.
Pega Platform offers four studios, or role-based authoring workspaces and they are as
follows:
App Studio
Dev Studio
Prediction Studio
Admin Studio
Each studio speeds up application development and increases productivity by giving users
role-based capabilities.
Using role-based workspaces in the Pega Platform can help you increase productivity.
Users may see what they require when they require it. Front-end developers, for example,
can work in one workspace to create interface channels, while system administrators can
switch between workspaces to configure additional features and monitor run-time
outcomes.
Multiple workspaces are available to users. The system opens the default workspace when
users log in. Users have access to various workstations and can switch between studios.
Real-Life Problems
2. Explain about classes in Pega. What are the different types of classes
available in Pega?
The Pega Platform allows users to reuse rules across case types and applications.
Developers frequently reuse rules in their systems, ranging from single data pieces to
complete processes. Reusing rules increases the quality of an application while also cutting
down on development time. Pega Platform divides rules into classes based on their re-
usability inside an application. Each cluster is referred to as a class. Each application is
made up of three different class kinds.
Work Class: Processes, data items, and user interfaces are all part of the Work class, which
provides the rules that govern how to process a case or cases.
Integration Class: The Integration class holds the rules that specify how the application
interacts with other services, such as the integration resources that connect it to a customer
database or a third-party web server.
Data Class: The rules that specify the data objects used in the application, such as a
customer data type or order items data type, are stored in the Data class.
When we add a rule in App Studio, it automatically selects the proper class. We can
concentrate on what we want the rule to accomplish rather than how to develop it. We can
write the rule in Dev Studio if you need control over the class. Switching to Dev Studio is a
good idea if we want to write a rule that we can reuse in another app.
3. What do you mean by a work object in the context of Pega? How do you
create a work object in Pega?
A work object is the most basic unit of task completion in an application, as well as the
most basic collection of data on which a flow runs. Work objects are generated, updated,
and eventually closed when an application is used (resolved). A unique ID (property pyID),
an urgency value, and a status are all assigned to each work object (property
pyStatusWork). A work object is also known as a work item in some companies.
Work objects under specific application settings may have a traditional name from the pre-
automation era. Work objects in a help desk or service desk system, for example, are
frequently referred to as trouble tickets.
Also, a work object can be created from an activity. To create a workpage for the case type
we desire, we use the activity "createWorkPage." The data transform that will be used to
initialise properties might be specified. If it's a stand-alone work object, use "addWork,"
and if it's a covered work object, use "addCoveredWork."
You can download a PDF version of Pega Interview Questions.
4. What do you understand about DCO in Pega? What are the benefits of
DCO in the context of Pega?
DCO stands for Direct Capture of Objectives. It is the process of acquiring, organising,
and storing data by using Pega's integrated solution, the Pega Platform. Processes and tools
for gathering and organising application artefacts are included in DCO. More crucially, IT,
business, and testing teams, as well as other resources, employ this enabling technology. It
saves time, effort, and money while also improving the quality of projects and people's
lives.
DCO is not a methodology or a step in the methodology development process. It's not just
one tool. Instead, the goals and benefits are to centralise the data so that it may be used
continually across departments at the right time and at the right level. DCO eliminates
communication obstacles by providing a centralised repository for linked application
artefacts (objectives, requirements, specifications, and implementation rules). All resources
have real-time as-built documentation and a single view of the application.
5. What do you know about SLA in the context of Pega? What is its
importance?
SLA is an acronym for Service Level Agreement. It is one of the most useful features of the
Pega CRM platform. As part of the case management process, Service Level Agreements
allow us to set targets and timelines. The major goal of SLA is to assist the task force in
completing all tasks on time. Pega Rules Process Commander will keep track of each SLA
rule's performance of a specific event action that was configured for that rule. By increasing
the urgency number, also adjusts the urgency associated with that assignment. This may
draw attention to the item on the employee's to-do list because it necessitates attention. So
we can sort the work-list based on the task's urgency.
A Service Level Agreement (SLA) establishes time intervals as a goal and time frame for
standardizing how you solve work in your application. It establishes a time limit for
completing the work. Pega establishes an SLA when we set a goal and a deadline. Service
levels can be set for processes, steps, stages, and entire classes.
Start: This is the point at which the service level timer starts ticking. It all starts at the
zeroth hour.
Goal: Its purpose is to specify how long the assignments should take. This step is counted
from the start of the assignment or case.
Deadline: The term "deadline" refers to the amount of time a case or process can take
before it is considered late. It is calculated from the start of the assignment or case.
Passed Deadline: When the assignment or case has passed the deadline, the term "passed
deadline" is used to indicate when further action should be taken. It calculates the amount
of time that has elapsed since an assignment's deadline.
SLA ensures that your service provider and you are on the same page as far as standards
and services are concerned. Setting explicit and measurable rules is vital since it reduces the
possibility of client dissatisfaction and provides remedies if the commitments are not met.
SLAs mention recourse to be taken in case of service commitments failure. If your service
provider fails to meet their duties, it will have serious ramifications for your company's
reputation. As a result, if performance standards are not reached, we must incorporate
repercussions in the SLA.
Your clients will have peace of mind with SLA. They have a contract that they may refer to
in order to hold their service provider accountable and to specify the type of service they
anticipate. They can lessen some of the consequences if the agreed-upon conditions are not
reached by receiving financial compensation from their supplier.
Assignment SLA: Assignment SLA is an SLA that refers to an assignment. This SLA
begins with the creation of the assignment and ends with the completion of the assignment.
The assignment urgency is set in the attribute pxUrgencyAssignSLA on the newly Assigned
Page.
Case Level SLA: When an SLA is referred to at the case level, it is referred to as a Case
level SLA. This SLA is relevant throughout the lifecycle of a case. It begins when a case is
opened and concludes when the case is closed. The standard property pySLAName is used
to identify this SLA under the workpage. It's set in pyWorkPage's pxUrgencyWorkSLA
parameter. The pxUrgencyWorkSLA property under pyWorkPage controls the urgency of
case-level SLAs.
Stage Level SLA: When an SLA is referred to at the stage level, it is referred to as Stage
level SLA. It begins when a case enters a stage and ends when it exits the stage. The
pxUrgencyWorkStageSLA property under pyWorkPage controls the urgency at the Stage
level.
Step level/Flow level SLA: An SLA is considered a Step level or Flow level SLA when it
is referred to as a step or flow level. A step-level SLA begins when a process or step is
initiated and ends when it is completed. When a flow is begun, a flow level SLA is started,
and when a flow is stopped, it is stopped. If a step SLA is present, it takes precedence over
a flow SLA. Step SLA can be referenced in every step under the stage in the case type rule.
The process tab of the flow rule refers to a flow SLA. The pxUrgencyWorkStepSLA
property under pyWorkpage controls the flow or step level urgency.
Screen Layout: Screen layouts are only used within a harness and are typically used to
establish portals for an application.
Dynamic Layout: A dynamic layout is a DIV-based layout that allows content to be
displayed in a variety of ways.
Column Layout: A Columns layout allows you to show major content, like a work item,
alongside supporting stuff, like an attachment.
Grid Layout: Table layouts make it easier for users to obtain and compare data. Tables can
be used as a flexible base for users to process vast volumes of data in your apps. Tables in
price comparison software, for example, can assist customers in quickly identifying the best
deal.
Tree Grid Layout: The properties in pages in an embedded Page List property can be
viewed, navigated, and accessed using a tree layout. To identify entries of current interest,
the user can swiftly extend and collapse branches of the tree.
In sections, dynamic layouts and column layouts are employed. In a dynamic or column
layout, you can add content to a section, such as properties, controls, and other sections.
The format of the skin determines the positioning, alignment, width, and arrangement of
components in a layout.
Topic Buckets
Mock Assessments
Reading Material
Page-Validate: This method is used to check all of the properties on a page. If a page has
embedded pages, this method validates all of the attributes in a recursive manner. This
method is time-consuming and uses a lot of system resources. Use the Obj-Validate method
with the Rule-Obj-Validate rule to validate specified properties.
Property-Validate: This method is used to set limits on the value of a property. To
implement constraints, use the Edit validate rule in conjunction with the Property-Validate
method. The Property-Validate method can be used to validate multiple properties.
10. Explain about Access Groups and Access Roles. Differentiate between
them.
Access Group :
The Operator ID of a user is used to associate an access group with that user. When a user
logs in with more than one access group established, the application associated with the
principal access group is used. Privilege inheritance can also be used by security managers
to make the process of allowing the user access to a feature protected by privilege easier.
The Data-Admin-Operator-AccessGroup class defines access groups.
Access Roles :
Through the Access of Role to Object and Access Deny rule types, access roles determine
the classes that a user can see, alter, and delete.
To grant permissions (capabilities) to users, use an access role name. In requestor type and
access group instances, access roles can be mentioned. For a range of users, the Pega
Platform includes built-in access roles ( names that begin with PegaRULES: ):
Guests
Administrators
Developers
Authenticated work users
The Rule-Access-Role-Name rule type defines access roles.
Difference :
Authorizations are granted according to a user's access group rather than their role. The
degree of authorization for the access group is determined by the most permissive role in
the access group.
A list of Data-Admin-Operator-AccessGroup instances is displayed on the Access Groups
tab. The table shows the system's access groups and the number of operators assigned to
each group whereas for the present application, the Access Roles tab displays a list of Rule-
Access-Role-Name rules. You can examine, add, and remove roles from this tab.
11. Explain Requestor Type in Pega. What are the different types of
Requestor types in Pega?
Pega Platform comes with four requestor types for the system name we specify during
installation, as well as a reserved requestor type prpc.BROWSER for exceptional cases.
Typically, we only require the four requestor types that contain your system name. If we
want to modify the system name after installation, we go to Designer Studio => System =>
Settings => System Name to get to a landing page tab where we can do so. When we
change a system's name, new requestor instances are created that correspond to the previous
name's instances. If the prior system name did not include all requestor types for some
reason, the missing requestors are also produced when the system is renamed.
12. Explain Flow Action in the context of Pega. What are the different types
of Flow Actions available?
A flow action is a decision that users can make as an interim or final disposition for an
assignment they're working on. The Rule-Obj-FlowAction rule type is used to define each
flow action.
There are two sorts of flow actions:
Connector Flow Actions: On a Visio presentation, connector flow actions appear as lines
in the Diagram tab of a flow rule. A line emerges from an assignment shape and terminates
at the flow's next shape. Users select a connector flow action during runtime, complete the
assignment, and move the work item along the connection to the next form.
Local Flow Actions: When a local flow action is selected at runtime, the assignment
remains open and on the worklist of the current user. The Assignment Properties panel
records local flow actions that aren't displayed on the flow diagram.
Take, for example, an application that facilitates employee recruitment operations. When
completing an assignment that requires the employee to evaluate the quality of a candidate
(based on a résumé and application form), the employee enters his judgments and reasoning
in the application and then selects one of three flow actions: Advance, Reject, or MoreInfo.
These flow actions may employ distinct user form displays, such as in the action section of
a perform harness or in a modal dialogue, and may require different input fields.
Interview Process
13. Explain PRPC in the context of Pega. What are the benefits of PRPC?
PRPC stands for Pega Rules Process Commander. Pegasystems is built on the PRPC
foundation. It is totally model-driven, allowing the creation of dependable and efficient
applications without the use of any code, including SQL, Java, CSS, or HTML. PRPC is a
software platform that enables companies to combine all of their diverse, complex business
procedures and methods into a single platform. It allows you to combine multi-stream
processing into a single system by automating, documenting, and simplifying business
processes.
Businesses can use the PRPC platform to combine all of their independent, separate, and
multiple business procedures and rules into a single platform.
It enables corporate processes to be automated, documented, and streamlined.
Multi-stream methods can be combined into a single system.
Data can be transferred between frameworks and processed, segregated, and decoded.
The purpose of PEGA PRPC is to cut down on the costs of any adjustments.
14. Explain activities in the context of Pega. What are the best practices
while using activities?
Activities in Pega Platform automate processing. Activities are scripted in Dev Studio and
consist of a series of stages that must be completed in the order specified. When more
appropriate rule types are unavailable, usually due to more sophisticated computations or
procedures, or when a rule requires an activity to run, activity rules automate the system.
Declare On change, for example, necessitates the usage of an activity to start a process or
pause work when the value of a particular property changes. Control returns to the rule that
called the action after the activity is completed.
For example, an insurance firm is obligated to upload insurance claims to the Registry of
Motor Vehicles. To minimize the impact on users, automated uploads take place during off-
peak hours. An activity can be configured in Pega Platform to allow the system to automate
claim uploads without the need for user participation.
Following are some of the best practices that one should keep in mind while using activities
in Pega :
Keep activities to a minimum. Limit your actions to no more than 25 steps, and make sure
that each one is focused on achieving a single goal.
Use alternate rule types whenever possible, such as a data transform to set a property value.
Hand-coded Java should be kept to a minimum. When standard or custom rule types, library
functions, or activity methods are available, skip the Java stages in activities.
15. Explain the decision table and decision tree in the context of Pega. What
are the differences between them?
Decision Table:
In case of a decision table, the values in a column in a decision table evaluate against the
same property/operator pair, such as Gender =. When developers need to analyse several
different combinations of the same set of properties or conditions in order to produce a
single value or property, they can use a decision table. For example, a corporation
determines bonus eligibility based on the number of years spent at the company and ratings
on five employee assessment measures.
Decision Tree:
In a decision tree, each branch compares the property/operator pair to a single value in
order to take an action, such as returning a value or evaluating a nested condition. When
evaluating requirements on multiple attributes that are reliant on other conditions,
developers might employ a decision tree. In a decision tree, each branch is assessed, and
any branches that evaluate to true perform the action that follows, such as continuing the
evaluation to the nested condition. A language learning software, for example, is doing
significant A/B testing, with some users receiving hearts and others receiving stars for their
efforts. Hearts and stars have their own properties with their own worth. Based on the
number of hearts or stars linked with the account, a decision tree examines the various
prizes that users are qualified for.
When a comparison evaluates to true, both decision tables and decision trees analyze
characteristics or conditions to deliver outcomes. Decision trees evaluate against distinct
characteristics or conditions than decision tables, which evaluate against the same set of
qualities or conditions.
A business stakeholder or low-code developer can easily configure and change dependent
conditions that evaluate against distinct characteristics due to the decision tree's line-by-line
layout. When a decision table is used in a circumstance where several criteria evaluate
against the same property, the decision table will include empty boxes where a value is not
required for the conclusion. A business stakeholder or low-code developer can easily
configure and change a decision that evaluates against many of the same properties due to
the decision table's table structure.
16. Explain Rule Resolution in the context of Pega. What are its benefits?
The search technique used by the system to discover the best or most appropriate rule
instance to apply in a given is known as rule resolution.
Except for a few rule types — classes that inherit from the Rule- class — rule resolution
applies to all rule types. Instances of classes derived from the Work-, Data-, or any other
base class are not affected by rule resolution.
Despite the fact that the rule resolution process is fast and invisible, it is critical to
comprehend how it works. Make key component value selections based on how you want
rules to be found via rule resolution when you construct applications. The rule resolution
process can be speed up by using an in-memory rule cache. If the system discovers an
instance (or instances) of the rule in question in the cache, it accepts the candidate rules
from the cache and bypasses many steps in the resolution process.
Across apps and organizations, rules can be shared. Object-oriented software development
has many advantages, including sharing and reuse.
More explicit rules stated at a lower level can override rules defined at a higher level. While
this reduces the value of sharing, it gives much-needed flexibility while highlighting
exceptions.
Even inside a single rule-set, rules might have many versions, and security rules limit which
users view and execute which versions. This makes application development, testing, and
patching easier.
With little conflicts and interference, a single Pega Platform system can host many apps,
multiple organizations, and multiple versions of a single application.
Applications can be built independently of one another, but they can all be based on the
same set of rules that are locked (and hence will not change).
Most declarative rules are reevaluated after the following types of events:
When users upload an input form, it is evaluated at the end of the input processing.
During the execution of an activity, assessment takes place at each step, after the method
has completed but before the evaluation of a transition in that phase.
As control passes from one job (one shape on the Visio flow diagram) to the next during
flow execution.
When the work item progresses from one form to another and within connectors at the end
of a flow transition (if a relevant property is set).
When the value of any of the attributes involved in the rule changes, index rules are
activated.
When an object is saved to the database, trigger rules are activated.
Decision tree rules, decision table rules, and case match rules do not employ forward
chaining and are only assessed when explicitly requested.
18. What do you mean by an agent in the context of Pega? Explain.
An agent is a server's internal background process that performs actions on a regular basis.
Agents deliver email notifications about assignments and outgoing messages, generate
updated indexes for the full-text search feature, synchronize caches among nodes in a
multiple node system, and other system duties. Agents are self-contained and
asynchronous: the activities they invoke operate on their own timetables, and a second
activity execution can begin before the first one has finished.
Agents are defined by their own set of rules (Rule-Agent-Queue rule type). Agent Queue
data instances are used to enable and schedule agents (Data-Agent-Queue class). If
potential deadlock and other locking issues are appropriately managed by the activities in a
multi node cluster, an agent can execute on numerous nodes, even each node, to achieve
high throughput.
19. Explain data pages in the context of Pega.
A data page in a Pega Platform application retrieves data from a specified data source and
caches it in memory. The integration to the data source is managed by a data page, which
separates business activities from any integration details. This separation enables app
developers to use supplied data in their apps without having to know the data source or
connection specifics. Unlike most Pega Platform pages, applications seek to populate the
contents of a data page only when the page is requested, rather than through an explicit
action. Data pages are classified as declarative rules since their content is available on
demand. To distinguish a data page from other pages in memory, Pega Platform
automatically adds the characters D_ to the name.
A developer must give four crucial pieces of information when creating a data page. They
are as follows :
Case management is a software-based strategy to assist people with day-to-day tasks and
automating work from start to end. Case management entails visualising your business
process, encompassing people, data, and actions, in order to plan a flexible path that leads
to your goal. By addressing business cases from start to finish and combining human
activities with digital automations, we employ case management to produce goal-oriented
solutions.
For example, we can simulate the process of accepting candidates after examining job
applications, from gathering documentation from a candidate to conducting a job interview
to receiving final approval. In case management, you can dynamically alter your work to
respond to changing conditions, in addition to designing the most common path to
resolution. When this step is relevant to the current circumstance, your business procedure
can include an additional employment interview. You can successfully address business
procedures that follow an ambiguous or unexpected workflow with case management.
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:
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.
The record selection actions in list view and summary view rules are influenced by which
properties are exposed. Your database administrator can make a property that was
previously only saved inside the Storage Stream column into a distinct exposed column in
many circumstances.
Single Value properties at the top level can only be exposed. If your application requires a
column for embedded property values, the values can be transferred to the top level or
provided indirectly using Index-class instances.
4. What is the Declare Index in Pega? How can you set up a declare index?
In Pega, Declare Index is a rule type that exposes aggregate properties like Page/ List/
Group for reporting purposes.They are rule instances of the Rule-Declare-Index. When an
Insert/ Update/ Delete operation on the work object is followed by a commit, it helps to
populate the corresponding index table. They can be found under the SysAdmin Category
in Records explorer.
There are two ways to set up a declare index in Pega. They are as follows :
1. Prepare ahead of time to identify the RuleSet and Version that will contain the wizard's
rules.
2. Check existing Declare Index rules to see if the property has already been indexed. (Do not
try to index a property that has previously been indexed with this wizard.)
3. In the Application Explorer, look for the embedded property. A Page, Page List, or Page
Group property can contain the property.
4. To get to the Application Explorer context menu, right-click. From the menu, choose Index
Property.
5. Select a RuleSet and Version in the first pop-up window to store the rules generated by this
wizard. Submit the form.
6. The class, property, and Declare Index rule produced are identified on a confirmation form.
The indexing process has begun. To review the regulations, click the pencil symbol.
Determine which property(ies) on the source object will be used to create the index
instance.
Create a concrete class that extends the Index base class and holds the new index objects.
The key for concrete classes generated from the Index base class is made up of three
attributes in that order: pxInsIndexedKey, pxIndexCount, and pxIndexPurpose.
Determine which database table the new indexes will be stored in. If necessary, create a
database table and associate it with the class using a Database Table instance. The table's
three important characteristics must be visible columns.
In the new index class, define Single Value attributes to retain the values of the source
instance properties. Confirm that all of these characteristics are exposed columns in the
database with your database administrator, or change the database schema as needed.
Choose a name for the Declare Index rule.
Create a Declare Index rule, noting the source of each property value and the index property
name it corresponds to.
Following are the different ways by which we can measure the performance of our
application in Pega :
DBTrace: The Performance Analysis Tool (PAL) has a feature called DBrace that provides
a thorough log of calls to the PegaRULES database. DBTrace shows the time spent on each
operation as well as the SQL queries delivered to the database.
Performance Analyzer Tool: The Performance Analyzer (PAL) displays all of the
performance statistics collected by Pega PlatformTM. You can utilise PAL to figure out
how much system resources a single requestor session uses. The Performance landing page
(Dev Studio > System > Performance) and the Performance tool in the toolbar both have
PAL.
To add reading
To add reading with clipboard size
To reset data
To save data
To configure DBTrace options
To start profiler
To show alerts
Alerts: Process Commander inserts a succession of text entries called alert messages to the
performance alert log during application execution to identify mostly performance-related
issues or faults. PegaRULES-ALERT-YYYY-MMM-DD is the most common name for the
performance alert log.
Autonomic Event Services (AES): Exceptions are handled in the same way that alerts are.
Exceptions generated by a Process Commander server are sent to the AES system via
SOAP. The system parses the exceptions and registers them in the AES database's pegaam
exception table. AES aggregates these records into work objects called AES exception
items based on how frequently an exception occurs and the system events that produced
those exceptions. The pegaam exception work table in the AES database is used to store
these objects.
6. Explain Work List and Work Basket in the context of Pega.
Work List:
o A worklist is a list of open, unfinished assignments that are waiting for a user to
complete them. As a result, a worklist display reveals selected Assign-Worklist
instances.
A column that indicates a work item ID is commonly included in worklist
presentations, but a worklist is not a list of work items. One work item may have
two or more open tasks at any given moment. These assignments may appear on the
worklist of a single user or on the worklists of multiple users.
Assignments usually appear on a worklist because they were created by an
Assignment shape in a flow. Assignments are ordered by assignment urgency, with
the most urgent assignments appearing first and having the largest
pxAssignUrgency value. If the user is inactive or exclusively works in a workspace
other than Process Work, the information on the worklist display may become stale
(outdated). To refresh the contents of the worklist, click the refresh symbol or
interact with it.
Work Basket:
o A workbasket is a named list of open assignments that aren't assigned to a specific
operator. An instance of the Data-Admin-WorkBasket class defines a workbasket.
An organisation unit, a work group, and a calendar can all be linked to a
workbasket. During system installation, a default@pega.com workbasket is
generated as a last resort for assignment routing.
The system makes assignments as work items proceed through a flow execution.
Assignments can be linked to either human users (and display on their worklists) or
workbaskets. A workbasket's "contents" are a collection of unprocessed tasks
arranged in decreasing order of priority, comparable to a worklist's contents. The
work queue is a term used to describe these assignments.
There are three ways that assignments leave a workbasket:
Users who are qualified can process an assignment by removing it from the workbasket.
Based on work schedules, due dates, talents, workloads, and other parameters, an
application can automatically route assignments in a workbasket to users.
Managers can move assignments from a workbasket to the worklists of their employees.
7. Explain Declare Triggers in the context of Pega. How can you create a
Declare Trigger in Pega?
Declare Trigger Rules establish the relationships between events in your case types.
Declare Trigger rules, which conduct activities in response to a case's specified event. As a
result, you're able to develop adaptable apps that properly fit your company's requirements.
When your application creates, changes, or deletes a class in the database, declare Trigger
rules to start actions. Actions in a case, such as storing a case or modifying information in a
case, are related to operations on classes. Declare Trigger rules can also be used to track
property changes and for auditing.
Forward chaining:
Forward chaining is an internal mechanism that allows changes in one property value to be
automatically propagated to other property values or indexes. For example, if the area
property is dependent on the length and width properties, forward Chaining will cause the
area property to be recalculated if the length or width values change.
Backward Chaining:
Backward chaining allows for automatic property calculation by executing the declarative
rule when the value for the property is required rather than when the input changes. If the
area property is dependent on the length and width properties, for example, backward
chaining forces the area property to be computed each time it is needed. Except for the
Rule-Declare-Expression, almost all declarative rules only implement forward chaining.
We have the option of going forward or backward chaining in rule-Declare-Expression.
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.
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.
In this article, we discussed the most frequently asked interview questions on Pega. BPM is
a framework for managing an organization's working systems and processes. It is a top-
down, holistic governance concept that focuses on improving consumer loyalty through
developing market practises. BPM is a coupled and persistent trend that is continually
changing the best way to manage projects and partnerships all over the world, making them
much more adaptable, robotic, and, to a considerable extent, innovative. As a result, Pega
BPM provides the firm with remarkable business efficiencies.
1. What is the difference between Page -Validate and Property-Validate
methods?
The 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 a lot of system resources and takes more time. If
you want to validate specific properties use the Obj-Validate method with a Rule-
Obj-Validate rule.
A property-validate method is used to impose restrictions on property value. Use
Edit validate rule along with Property-Validate method to impose restrictions. You
can validate multiple properties using the Property-Validate method.
2. What is the difference between Edit validate and Edit Input rules?
Edit Validate: Use the edit validate rule to validate the property value using
Edit Input: Edit input rules convert user-entered data into the required
format. For example, if the user enters the date MM/DD/YYYY format, the edit
input rule covers this date into DD-MMM-YYYY (required format). Again we
Work Objects are stored in the 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 the 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.
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.
StepStatusGood is when the condition defined in @baseclass, this when the rule
checks whether the value of the pxMethodStatus property is “Good”.
StepStatusFail is a when the condition defined in @baseclass, this when rule checks
whether the value of the pxMethodStatus property is “Fail”.
No, it's not possible in the clipboard, but you can see it in tracer by clicking the page
name in the step method column.
Open the rule, from that pick the pzinskey, go to prdbutil, and using the pzinskey
export the rule Import that zips file where you want.
Obj-Open: we will get multiple records from a table based on the criteria from the
specified class. Or Opens an instance of a given class.
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.
12. Inheritance concept in the Pega (rules, class).
Rules: Rules inheritance that can maximize the 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: Class inheritance searches for rules from a concrete, lower class, up the class
hierarchy to find available rules.
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.
PAL Features
Add Reading
Add Reading with Clipboard Size
Reset Data
Save Data
Start DBTrace
DBTrace Options
Start Profiler
Show Graph
My Alerts
Creating the separate DB table for that working-class within the DB, or map to
external DB and further saves will go to that DB.
fields Obj-List
SQL instance.
Access: An indication of the database package used to access this table, from
ObjClass: The object Class to List. When used with the RuleObjList
Using log-message.
18. How can I store the instance of the class in the database?
Creating the separate DB table for that working-class within the DB, or map to
external DB and further saves will go to that DB.
19. Default data table where the instance of the class is a store (how it will
search ) pc_work
The Work- base class is mapped to the pc_work table, a table with columns
that represent all the work object properties that need to be exposed to flow
processing to function correctly. Map your work object classes to either the
The Database class is mapped to the pr_data table. Map your data classes to
either the pr_data table or another table that has the same columns.
all Rule related data will be stored in pr4_pegarules. The pr_other table is the
last resort or default destination for saved instances that belong to a class
21. Notify
When you want to configure your flow to automatically send notification messages
about assignments, connect a notify shape to the assignment. A notify shape
identifies a notify activity.
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 a flow,
much like a programming “GOTO” destination.
pc_data_workattach.
25. Different types of flows. Explain in scenario-based where you used and
worked
– Application Preflight tool to list each rule in an application that contains a warning
message. Warning messages suggest that the rule is at variance with guardrails and
other best practices. You can also check for browser compatibility of visual
elements.
you can extend the set of warnings with a custom activity named Rule-
ZZZZ.CheckForCustomWarnings, where Rule-ZZZZ is a rule type.
Warnings are maintained as instances of the Index-Warning class and saved in the
pr_index_warnings database table.
28. How to end the work object in the activity (a method used to kill the work
object)
Using javascript.
Using Java:
sHashStringMapactivityKeys = new HashStringMap();
activityKeys.putString(“pxObjClass”, “Rule-Obj-Activity”);
activityKeys.putString(“pyClassName”, workclass);
activityKeys.putString(“pyActivityName”, “HistoryAndAttachments” );
tools.doActivity(activityKeys , workpage, tools.getParameterPage() );
pyActivity=GHC-HPlan-CS-Work.ABC&CSR=” + CSR.
31. How can I pass the page as the parameter to the activity using Java, JavaScript?
Using Java you can, maybe using java scripts you can, I not sure
32. How to get a property value from the clipboard using the Java step?
ClipboardPageworkpage = tools.findPage(pagename);
String propername = workpage.getProperty(“.pxResults.Risk”).toString();
Or
String propertyname=
tools.findPage(“WorkListPage”).getProperty(“.pxResults.Risk”).toString();
window.open (urlToRun,”_self”);
openUrlInSpace (urlToRun,””);
When a work object advancing through a flow reaches the Spin-off shape, Process
Commander starts the execution of a different flow, using the current or a different
work object. Processing in the current flow rule continues in parallel, without
waiting for the other flow to complete.
Use the Split-Join shape to require that multiple subflows of your flow be completed
before the current flow continues execution. This allows subflows to execute
asynchronously, in parallel. For example, see the standard flow Work-.ParallelWork.
The Split-For Each task provides a form of searching or enumeration over the pages
in a property. Use a Split-For Each shape to iterate over the pages of a Page List or
Page Group property. For each page, you can conditionally start a flow execution for
the work object.
Decision:
Use the Decision task ( ) to reference a map value rule, decision table rule,
decision tree rule or a Boolean expression that when evaluated produces a
value that is the basis of branching in the flow.
At runtime, the system evaluates the decision rule based on inputs from the
flow and the work object and chooses one of the outgoing connectors based
on the result. No user interaction or input is required.
Fork: Use the fork shape ( ) to represent a point where the flow execution
chooses one of a few different paths (connectors) based on tests on the work
object. At runtime, the system evaluates the conditions on each outgoing
connector, starting with the connector assigned the highest likelihood
Pega vs Appian
Customer Types Medium and large business Small, medium, and large businesses.
1. What are the different types of classes in Pega?
Example: "There are three major classes in Pega. They are the data class,
integration class and work class. The data class specifies the rules for data types
and objects. The integration class contains the rules that oversee how the
application interacts with external resources and services. Finally, the work class
contains the interfaces, data items and other resources that govern the processing
of test cases."
This question tests your working knowledge in Pega. You can answer this
question by listing the various steps of creating a workbasket and explaining
each step briefly.
Example: "The first step to create a workbasket is to click on 'Record.' Next, choose
'Workbasket' under the organisation category. Right-click the 'Create' option and
then create a name for the workbasket instance. While naming the workbasket, it is
a good practice to choose a name that conveys its content and purpose to other
users."
This question helps the interviewer know more about your experience in Pega
and your passion for the role. You can answer by describing a situation or factor
that influenced you to pursue a career as a Pega developer. You can also
elaborate on the answer to include your expertise on the platform and your
future career goals.
This question helps the interviewer evaluate if you understand the advantages
of Pega and its role in enterprise application development. To answer this
question, you can list as many advantages as possible and explain each one
briefly. It also helps to be aware of the limitations of Pega, as that is another
common interview question.
Example: "Building software applications is risky, time-consuming and expensive.
Organisations look for ways to reduce risk during application development. Pega
makes it easy for businesses to achieve these objectives by focusing on developing a
Minimum Lovable Product (MLP) with a quick turnaround. Once you develop and
deliver the MLP, Pega allows for further iterations and improvements to the
application as the business needs change and evolve. It is a low-code alternative
with good community and platform support for businesses to develop custom
applications quickly."
The interviewer might ask tricky questions like these to try to confuse you. To
answer such questions, take a few seconds to decide which is the better option
and then explain why you think it is better.
Example: "Pega provides two types of rule inheritance, such as directed inheritance
and pattern inheritance. Pattern is automatic inheritance and uses the class name
structure to determine which rules to reuse. In direct inheritance, the developer
explicitly specifies the parent class. Unlike pattern inheritance, which is automatic,
direct inheritance is explicit. Both are important and you use them for different
scenarios based on the requirements. That said, you give preference to direct
inheritance as you cannot leave it blank."
This question tests your coding knowledge in Pega. The interviewer might ask
you to write code snippets during the interview to check your programming
expertise in the Pega platform. To answer this question, explain the syntax of
the corresponding function for passing parameters.
Example: "To pass parameters to a data page, we can use the D_AXASTATES
function. The format for this function is D_AXASTATES [Param1:Value1,
Param2:Value2]"."
8. How do you create a temporary object in Pega?
The interviewer might ask this question, especially if the role requires you to
work with temporary work objects. Temporary work objects are beneficial in
several business scenarios, as the system stores them in the database only
when certain conditions get met. They help in database maintenance by not
storing unnecessary data.
Example: "As the name implies, temporary work objects are impermanent and not
stored in the database. Rather, they remain on the clipboard. Temporary objects do
not have an associated case ID. Any history addition that you perform on a
temporary object does not impact the flow. You can create a temporary work object
by clicking on a case type, navigating to the 'settings' tab, selecting the 'general'
category and then choosing 'enable temporary case'."
Security is a significant concern for all businesses. The interviewer might ask
this question to assess your security knowledge and evaluate if you take data
security seriously. You can answer this question by explaining the different
security protocols available in Pega and how it helps in securing enterprise
applications.
This question tests your knowledge of Pega functionalities. You can expect the
interviewer to ask such in-depth questions to check if you have knowledge
about the various inbuilt functionalities of Pega.
Dev Studio
App Studio
Admin Studio
Prediction Studio
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.
Q3. What do you understand by DCO in Pega?
DCO in Pega stands for Direct Capture of Objectives. It consists of resources,
tools, application artifacts, and processes for acquiring, storing, and processing
data on the integrated Pega platform.
Q4. Which are the different types of layouts
available in Pega?
This, again, is one of the most common Pega interview questions asked at
technical interviews. The different types of layouts available in Pega are -
Dynamic Layout
Screen Layout
Column Layout
Grid Layout
Q5. What is the average salary of a Pega developer in the United States?
A1. In Pega, the term "workspace" or "studio" generally refers to the integrated development
environments (IDEs) where developers design and build applications. There are two main types of
workspace offered: "App Studio" and "Dev Studio". App Studio is primarily for business users who
want to design and build applications without deep technical knowledge. It offers a more
intuitive, drag-and-drop interface for creating applications. On the other hand, Dev Studio
provides a more detailed and complex environment for developers who need to delve into the
underlying architecture, build integrations, and manage the finer aspects of the system.
Q2. Can you describe classes in Pega and list the different types?
A2. Classes in Pega are similar to classes in object-oriented programming. They act as templates
or blueprints to create objects and define the properties and activities that an object can have.
Pega has three types of classes: Work, Data, and Integration. Work classes hold business process
or case-related data, Data classes manage data instances related to business rules, and
Integration classes are used to manage external data and integrations.
Q3. What is a work object in Pega and how would you create one?
A3. A work object in Pega represents a single instance of a business transaction or process. It
holds information related to the business case and its associated data. To create a work object,
you would typically use a process in the Work- class. The process starts with the 'Create' method,
which establishes a new work object, and then populates the object's properties with necessary
data.
Q4. Could you explain the concept of DCO in Pega and its benefits?
A4. DCO stands for Direct Capture of Objectives. It is a collaborative methodology used in Pega
to gather and implement business requirements directly into the application during the
development process. Benefits of DCO include improved communication between business and
technical teams, faster development cycle as requirements are implemented as they are gathered,
and less rework since the requirements directly inform the application design.
Q5. What is SLA in Pega and why is it important? Can you list and
describe different types of SLA?
A5. SLA, or Service Level Agreement, in Pega is used to ensure that a work object or assignment
meets certain performance expectations within a specified time period. They are important to
maintain business standards, drive urgency, and ensure service delivery. Three types of SLAs can
be defined in Pega: Goal, Deadline, and Passed Deadline. Goal is the desired time to resolve a
task, Deadline is the time limit by which the task should be completed, and Passed Deadline
occurs when the task exceeds the set deadline.
Q6. What are the different types of layouts in Pega and how would
you create a dynamic layout?
A6. Pega provides different layout types for user interfaces, including Standard (Column),
Dynamic, Smart, and Repeating layouts. To create a dynamic layout, go to the section rule form,
click on Design > Add a layout > Dynamic Layout. In the configuration panel, you can add the
necessary settings to make it dynamic, such as adding conditions to display or hide certain parts
based on the evaluation of an expression.
A7. Page-Validate and Property-Validate are both used to ensure data integrity in Pega. Property-
Validate validates a single property value based on predefined validation rules. Page-Validate, on
the other hand, validates an entire page of data, making it a broader check. It calls the Property-
Validate method for each property in the page.
Q8. How would you define Access Groups and Access Roles in Pega,
and what are their differences?
A8. Access Groups and Access Roles in Pega are part of the system's security model. Access Roles
define what operations a user can perform on a certain class and its instances, including creating,
reading, updating, deleting, and executing activities. On the other hand, Access Groups are
collections of Access Roles that are assigned to a user or a group of users. An Access Group can
also define the application that the user logs into, the default portal for the user, and other user-
specific settings.
Q9. What is a Requestor Type in Pega and what are the different types
available?
A9. Requestor Type in Pega defines the nature of the user or process that's interacting with the
Pega system. There are three main types of Requestor: Browser, App, and Batch. A 'Browser'
requestor is a human user accessing Pega via a web browser. An 'App' requestor is an external
application interacting with Pega through services and connectors. A 'Batch' requestor refers to
internal system processes, such as agents.
Q10. Can you explain the concept of Flow Action in Pega and list the
different types?
A10. Flow Action in Pega represents a task or an action that a user can perform within a business
process. Flow Actions determine the options available to a user at a particular stage in the flow,
driving the case towards resolution. The two main types of Flow Actions are "Connector" and
"Local". Connector Flow Actions drive the process forward by connecting to the next stage in the
process. Local Flow Actions, on the other hand, allow for actions like updating data or adding
notes that don't drive the process forward.
Q11. What is PRPC in Pega and what are its benefits?
A11. PRPC, or PegaRULES Process Commander, is the core component of the Pega platform. It is
a business process management (BPM) tool that provides a framework for developing
applications. The key benefits of PRPC are its capabilities for rapid application development and
deployment, its rule-based architecture that promotes reuse and modularity, and its ability to
encapsulate complex business logic in an easily managed format.
Q12. Could you explain activities in Pega and the best practices for
using them?
A12. Activities in Pega are sequences of steps that perform a specific action or task, much like
methods in object-oriented programming. They are one of the key building blocks for
implementing business logic in Pega. Some best practices for using activities include: use
activities only for procedural processing and data manipulation, avoid using activities for UI logic,
avoid excessive use of Java steps, use the correct method for each step, and always document
what each activity and step does.
Q13. Can you differentiate between a decision table and decision tree
in Pega?
A13. Both decision tables and decision trees in Pega are used to encapsulate and implement
decision logic. A decision table uses a tabular format to map inputs to outputs, suitable for
situations where there are clearly defined sets of input-output pairs. A decision tree, on the other
hand, uses a tree-like model of decisions, ideal for handling more complex, branching decision
logic.
A14. Rule Resolution in Pega is the process the system uses to find the best or most appropriate
rule instance to use at runtime, considering factors like the class hierarchy, rule set, date range,
and circumstance. The benefit of Rule Resolution is that it allows for rule reuse and versioning,
leading to more efficient development and easier maintenance of applications.
A15. A declarative rule in Pega represents a form of business rule that is evaluated automatically
by the system when certain conditions are met. They are essentially if-then logic statements that
are used to calculate values, define constraints, and enforce relationships between properties.
Examples of declarative rules include expressions, constraints, decision tables, decision trees, and
so on. Declarative rules help to automate business logic without requiring explicit triggering or
sequencing in a process or activity.
Q16. What is an agent in Pega and how does it function?
A16. An agent in Pega is a background process that performs automated tasks on a schedule or
based on certain conditions. It functions by waking up at scheduled intervals, checking if there
are any tasks that meet the criteria defined in the agent's activity, and then executing those tasks.
Examples of tasks an agent might handle include sending reminder emails, purging old data, or
executing batch processes.
A17. Data pages in Pega are used to load and hold data that's used in an application. They
provide a layer of abstraction between the application's data and its source, allowing you to
change the data source without affecting the rest of the application. Data pages can be scoped
to the requestor or a specific thread, and they can load data on startup or on-demand. They are a
critical component of Pega's data management capabilities, offering efficient, declarative data
access.
Q18. Can you explain Case Management in Pega and its benefits?
A18. Case Management in Pega is a systematic approach to manage the lifecycle of a business
process, also referred to as a 'case'. It provides an organized structure to define stages, steps, and
processes that need to be completed for the successful resolution of a case.
Enhanced Visibility: It provides a holistic view of the entire case lifecycle, enabling stakeholders to
monitor progress and make informed decisions.
Collaboration: It enables different stakeholders to work together effectively, as each one has a
clear understanding of their role in the process.
A19. "Locking" in Pega refers to the mechanism to prevent simultaneous updates to a case by
multiple operators. Locking prevents data conflicts and ensures data integrity.
Optimistic Locking: This allows multiple users to open a case but only the first one to save the
changes can do so successfully. Others will receive a notification that the case has been updated.
Pessimistic Locking: This prevents other users from opening a case when one user is working on
it. It guarantees that only one user can make updates at a given time.
A20. An exposed property in Pega is a property that can be directly accessed and used by the
database for sorting, retrieving, or filtering data. By default, not all properties are exposed.
Exposing a property allows it to be included in a database index, improving the performance of
database operations that involve that property.
Q21. What is Declare Index in Pega and how would you set it up?
A21. Declare Index in Pega is a rule that creates and maintains indexes for instances of one class
in properties of instances of another class. These indexes are used to speed up database queries.
Create a new Declare Index rule and specify the source class.
Specify the class of the index instances and map the properties of the source class to the
properties of the index class.
A22. Pega provides several tools to measure application performance. The Pega Predictive
Diagnostic Cloud (PDC) can be used to monitor the health of your application in real time. It
provides insights about system health, case processing, and team performance.
Alerts and logs in the PegaRULES Log Analyzer (PLA) tool can also be analyzed to measure
performance. PAL (Performance Analyzer) is another tool that helps developers understand the
resources consumed by their actions.
Q23. Could you explain the concepts of Work List and Work Basket in
Pega?
A23. Work List and Work Basket are two key concepts in Pega.
A Work Basket, on the other hand, is a shared pool of work. It contains assignments that are not
assigned to a specific individual but rather to a team or a group of operators. Users from the
same team can pick tasks from the work basket.
Q24. What is Declare Trigger in Pega and how would you create one?
A Declare Trigger in Pega is a rule that defines an automatic, asynchronous response to changes
in a database instance. It allows actions to be performed whenever instances are created,
updated, or deleted.
Create a new Declare Trigger rule, specifying the Applies To class and the trigger activity to be
performed.
Select the event that will fire the trigger. This could be 'Save', 'Delete', or 'Save as a new copy',
corresponding to instance creation, deletion, and modification respectively.
Specify the condition under which the trigger will fire. This could be an 'Always' condition or a
'When' condition based on a when-rule.
A25. Forward Chaining and Backward Chaining are inference techniques used in Pega's
declarative processing.
Forward Chaining: It is a data-driven approach, where a change in a property value triggers the
recalculation of other properties that depend on it. For example, if you have a property 'Total'
that sums 'Price' and 'Tax', a change in either 'Price' or 'Tax' would automatically update 'Total'.
Backward Chaining: It is a goal-driven approach, where a property value is calculated only when it
is needed. In the above example, 'Total' would be calculated only when it's accessed, not when
'Price' or 'Tax' changes.
Q26. What are Spinoff and Split join shapes in Pega and how are they
used?
A26. Spinoff and Split Join are flow shapes used in Pega to control the flow of work.
Spinoff: The Spinoff shape is used when we want to create a separate, parallel process that
doesn't need to complete for the main flow to proceed. For instance, in an online shopping
process, a Spinoff could be used to handle shipment, which is a separate process and doesn't
need to wait for the payment process to complete.
Split Join: The Split Join shape is used to divide a flow into multiple parallel processes, all of
which need to complete before the flow can proceed. For example, in a loan approval process,
multiple checks like credit score check, income verification might happen in parallel and only
after all checks pass, the flow proceeds to the next step.
1. What is the difference between SOAP and REST
protocols?
SOAP and REST are web service protocols used in the integration.
SOAP REST
It uses XML as the intermediate language for It uses JSON, XML, HTML, etc, but most of the
communication. time it uses JSON because of its readability
It uses Service Interface to expose the It uses Uniform service locators for accessing
functionality to its clients. the components.
SOAP stands for “Simple object access REST stands for “Representational state
protocol” transfer”
between Requestor and Provider. This uses XML as the intermediate language for
independent of Languages and Platforms it works fine with any operating system.
services space.
most commonly used because of its lightweight, Simple, highly scalable, and less
Eg: If we use SOAP as the protocol then we use the SOAP CONNECT rule and
(Service Provider).
Eg: When we use SOAP as the protocol then the SOAP SERVICE rule should be
created and the REST SERVICE rule when Rest is used as the protocol.
infrastructure like Clipboard data etc. then State full should be used.
Stateless: This is used when all the requests are treated as independent requests or
fresh requests.
8. How many types of processing modes can be
configured on the Service Package rule
There are 2 types of processing modes that can be configured on the Service
infrastructure like Clipboard data etc. then State full should be used.
Stateless: This is used when all the requests are treated as independent requests or
fresh requests
10. How did you handle authentication for the Service
Configured
Authentication is the process of validating incoming requests. There are 3 different
Basic: This is used to verify the incoming request has a valid operator ID and
web apps
system.
Let’s see OOTB flow used to handle errors i.e. ConnectionProblem flow which
takes care of handling the errors which are not detected in the Activity or DataPage.
The other way is when we invoke the Service from an Activity rule check for the
StepStatusFail when the rule for error detection and jump to a corresponding step to
handle the errors. We can write a DataTransform rule to handle the errors based on
The other way to invoke the connector rule is from the DataPage where we check
the errors from pxDataPageHasErrors when rule. If there are any errors we need to
SOAP service.
It also has the endpoint URL where the service is located Basically WSDL
and to convert data from Clipboard structure to XML and vice versa we use parse
rules as below
Class Structure: Input Class (To create input properties), Output Class(Output
Data pages are declarative in nature in the sense when we refer the data page
system executes the source and creates the data page in the clipboard for usage.
page system executes the source and get data from the source and places it in the
Thread: Data page is available only for this thread. E.g.: work object
access groups is required to build the rule-set hierarchy for the operators.
Editable: Data page content is used for reading and editing if required.
be satisfied to refresh the data page i.e. refresh condition and data page should be
referred.
9. Explain Different sources for DataPages
To source the Data from the Database table we have multiple options as below:
Report definition
Activity
Datatransform
Connector
LookUp
10. Can we have multiple source for a Single Data page
Yes, conditionally (via when rule) we can execute multiple sources for a data page.
11. Explain how the data pages are stored in the
Clipboard
All Read only data pages are stored in the “Data pages” category of the clipboard
Editable and Saveable data pages are stored under “User pages “
Data pages in the clipboard are fetched on demand from the source and have scope
Report Definition is also used to generate reports based on the selection criteria.
Inner Join
is to fetch the matching records from the source table with the target table.
7. What is Right Join Explain
Right join is used to get the data which matches the target table records matching
pyReportContentPage.
1. What is Data Transform rule and explain
Data transform rule is used to manipulate the data.
method is used to add data to a page and then add the page to the page list.
be executed and then current class data transform rule will be executed.
6. How to call Data transform rule from an activity rule
Apply-DataTransform is the method used to call the data transform rule from the
activity.
7. Can we call child Data transform from Parent
DataTransform rule?
Yes, Apply Datatransform is used to call.
rules are preferred over the Activity rules for manipulation of the data.
1. How many types of declarative rules are there in Pega?
Below are the declarative rules in pega.
1. Declare Expression
2. Declare OnChange
3. Declare Trigger
4. Declare Index
5. Declare Constraints
6. Declare Pages
chaining.
A1. In Pega, the term "workspace" or "studio" generally refers to the integrated development
environments (IDEs) where developers design and build applications. There are two main types of
workspace offered: "App Studio" and "Dev Studio". App Studio is primarily for business users who
want to design and build applications without deep technical knowledge. It offers a more
intuitive, drag-and-drop interface for creating applications. On the other hand, Dev Studio
provides a more detailed and complex environment for developers who need to delve into the
underlying architecture, build integrations, and manage the finer aspects of the system.
Q2. Can you describe classes in Pega and list the different types?
A2. Classes in Pega are similar to classes in object-oriented programming. They act as templates
or blueprints to create objects and define the properties and activities that an object can have.
Pega has three types of classes: Work, Data, and Integration. Work classes hold business process
or case-related data, Data classes manage data instances related to business rules, and
Integration classes are used to manage external data and integrations.
Q3. What is a work object in Pega and how would you create one?
A3. A work object in Pega represents a single instance of a business transaction or process. It
holds information related to the business case and its associated data. To create a work object,
you would typically v
use a process in the Work- class. The process starts with the 'Create' method, which establishes a
new work object, and then populates the object's properties with necessary data.
Q4. Could you explain the concept of DCO in Pega and its benefits?
A4. DCO stands for Direct Capture of Objectives. It is a collaborative methodology used in Pega
to gather and implement business requirements directly into the application during the
development process. Benefits of DCO include improved communication between business and
technical teams, faster development cycle as requirements are implemented as they are gathered,
and less rework since the requirements directly inform the application design.
Q5. What is SLA in Pega and why is it important? Can you list and
describe different types of SLA?
A5. SLA, or Service Level Agreement, in Pega is used to ensure that a work object or assignment
meets certain performance expectations within a specified time period. They are important to
maintain business standards, drive urgency, and ensure service delivery. Three types of SLAs can
be defined in Pega: Goal, Deadline, and Passed Deadline. Goal is the desired time to resolve a
task, Deadline is the time limit by which the task should be completed, and Passed Deadline
occurs when the task exceeds the set deadline.
Q6. What are the different types of layouts in Pega and how would
you create a dynamic layout?
A6. Pega provides different layout types for user interfaces, including Standard (Column),
Dynamic, Smart, and Repeating layouts. To create a dynamic layout, go to the section rule form,
click on Design > Add a layout > Dynamic Layout. In the configuration panel, you can add the
necessary settings to make it dynamic, such as adding conditions to display or hide certain parts
based on the evaluation of an expression.
A7. Page-Validate and Property-Validate are both used to ensure data integrity in Pega. Property-
Validate validates a single property value based on predefined validation rules. Page-Validate, on
the other hand, validates an entire page of data, making it a broader check. It calls the Property-
Validate method for each property in the page.
Q8. How would you define Access Groups and Access Roles in Pega,
and what are their differences?
A8. Access Groups and Access Roles in Pega are part of the system's security model. Access Roles
define what operations a user can perform on a certain class and its instances, including creating,
reading, updating, deleting, and executing activities. On the other hand, Access Groups are
collections of Access Roles that are assigned to a user or a group of users. An Access Group can
also define the application that the user logs into, the default portal for the user, and other user-
specific settings.
Q9. What is a Requestor Type in Pega and what are the different types
available?
A9. Requestor Type in Pega defines the nature of the user or process that's interacting with the
Pega system. There are three main types of Requestor: Browser, App, and Batch. A 'Browser'
requestor is a human user accessing Pega via a web browser. An 'App' requestor is an external
application interacting with Pega through services and connectors. A 'Batch' requestor refers to
internal system processes, such as agents.
Q10. Can you explain the concept of Flow Action in Pega and list the
different types?
A10. Flow Action in Pega represents a task or an action that a user can perform within a business
process. Flow Actions determine the options available to a user at a particular stage in the flow,
driving the case towards resolution. The two main types of Flow Actions are "Connector" and
"Local". Connector Flow Actions drive the process forward by connecting to the next stage in the
process. Local Flow Actions, on the other hand, allow for actions like updating data or adding
notes that don't drive the process forward.
A11. PRPC, or PegaRULES Process Commander, is the core component of the Pega platform. It is
a business process management (BPM) tool that provides a framework for developing
applications. The key benefits of PRPC are its capabilities for rapid application development and
deployment, its rule-based architecture that promotes reuse and modularity, and its ability to
encapsulate complex business logic in an easily managed format.
Q12. Could you explain activities in Pega and the best practices for
using them?
A12. Activities in Pega are sequences of steps that perform a specific action or task, much like
methods in object-oriented programming. They are one of the key building blocks for
implementing business logic in Pega. Some best practices for using activities include: use
activities only for procedural processing and data manipulation, avoid using activities for UI logic,
avoid excessive use of Java steps, use the correct method for each step, and always document
what each activity and step does.
Q13. Can you differentiate between a decision table and decision tree
in Pega?
A13. Both decision tables and decision trees in Pega are used to encapsulate and implement
decision logic. A decision table uses a tabular format to map inputs to outputs, suitable for
situations where there are clearly defined sets of input-output pairs. A decision tree, on the other
hand, uses a tree-like model of decisions, ideal for handling more complex, branching decision
logic.
A14. Rule Resolution in Pega is the process the system uses to find the best or most appropriate
rule instance to use at runtime, considering factors like the class hierarchy, rule set, date range,
and circumstance. The benefit of Rule Resolution is that it allows for rule reuse and versioning,
leading to more efficient development and easier maintenance of applications.
A15. A declarative rule in Pega represents a form of business rule that is evaluated automatically
by the system when certain conditions are met. They are essentially if-then logic statements that
are used to calculate values, define constraints, and enforce relationships between properties.
Examples of declarative rules include expressions, constraints, decision tables, decision trees, and
so on. Declarative rules help to automate business logic without requiring explicit triggering or
sequencing in a process or activity.
Q16. What is an agent in Pega and how does it function?
A16. An agent in Pega is a background process that performs automated tasks on a schedule or
based on certain conditions. It functions by waking up at scheduled intervals, checking if there
are any tasks that meet the criteria defined in the agent's activity, and then executing those tasks.
Examples of tasks an agent might handle include sending reminder emails, purging old data, or
executing batch processes.
A17. Data pages in Pega are used to load and hold data that's used in an application. They
provide a layer of abstraction between the application's data and its source, allowing you to
change the data source without affecting the rest of the application. Data pages can be scoped
to the requestor or a specific thread, and they can load data on startup or on-demand. They are a
critical component of Pega's data management capabilities, offering efficient, declarative data
access.
Q18. Can you explain Case Management in Pega and its benefits?
A18. Case Management in Pega is a systematic approach to manage the lifecycle of a business
process, also referred to as a 'case'. It provides an organized structure to define stages, steps, and
processes that need to be completed for the successful resolution of a case.
Enhanced Visibility: It provides a holistic view of the entire case lifecycle, enabling stakeholders to
monitor progress and make informed decisions.
Collaboration: It enables different stakeholders to work together effectively, as each one has a
clear understanding of their role in the process.
A19. "Locking" in Pega refers to the mechanism to prevent simultaneous updates to a case by
multiple operators. Locking prevents data conflicts and ensures data integrity.
Optimistic Locking: This allows multiple users to open a case but only the first one to save the
changes can do so successfully. Others will receive a notification that the case has been updated.
Pessimistic Locking: This prevents other users from opening a case when one user is working on
it. It guarantees that only one user can make updates at a given time.
A20. An exposed property in Pega is a property that can be directly accessed and used by the
database for sorting, retrieving, or filtering data. By default, not all properties are exposed.
Exposing a property allows it to be included in a database index, improving the performance of
database operations that involve that property.
Q21. What is Declare Index in Pega and how would you set it up?
A21. Declare Index in Pega is a rule that creates and maintains indexes for instances of one class
in properties of instances of another class. These indexes are used to speed up database queries.
Create a new Declare Index rule and specify the source class.
Specify the class of the index instances and map the properties of the source class to the
properties of the index class.
A22. Pega provides several tools to measure application performance. The Pega Predictive
Diagnostic Cloud (PDC) can be used to monitor the health of your application in real time. It
provides insights about system health, case processing, and team performance.
Alerts and logs in the PegaRULES Log Analyzer (PLA) tool can also be analyzed to measure
performance. PAL (Performance Analyzer) is another tool that helps developers understand the
resources consumed by their actions.
Q23. Could you explain the concepts of Work List and Work Basket in
Pega?
A23. Work List and Work Basket are two key concepts in Pega.
A Work Basket, on the other hand, is a shared pool of work. It contains assignments that are not
assigned to a specific individual but rather to a team or a group of operators. Users from the
same team can pick tasks from the work basket.
Q24. What is Declare Trigger in Pega and how would you create one?
A Declare Trigger in Pega is a rule that defines an automatic, asynchronous response to changes
in a database instance. It allows actions to be performed whenever instances are created,
updated, or deleted.
Create a new Declare Trigger rule, specifying the Applies To class and the trigger activity to be
performed.
Select the event that will fire the trigger. This could be 'Save', 'Delete', or 'Save as a new copy',
corresponding to instance creation, deletion, and modification respectively.
Specify the condition under which the trigger will fire. This could be an 'Always' condition or a
'When' condition based on a when-rule.
A25. Forward Chaining and Backward Chaining are inference techniques used in Pega's
declarative processing.
Forward Chaining: It is a data-driven approach, where a change in a property value triggers the
recalculation of other properties that depend on it. For example, if you have a property 'Total'
that sums 'Price' and 'Tax', a change in either 'Price' or 'Tax' would automatically update 'Total'.
Backward Chaining: It is a goal-driven approach, where a property value is calculated only when it
is needed. In the above example, 'Total' would be calculated only when it's accessed, not when
'Price' or 'Tax' changes.
Q26. What are Spinoff and Split join shapes in Pega and how are they
used?
A26. Spinoff and Split Join are flow shapes used in Pega to control the flow of work.
Spinoff: The Spinoff shape is used when we want to create a separate, parallel process that
doesn't need to complete for the main flow to proceed. For instance, in an online shopping
process, a Spinoff could be used to handle shipment, which is a separate process and doesn't
need to wait for the payment process to complete.
Split Join: The Split Join shape is used to divide a flow into multiple parallel processes, all of
which need to complete before the flow can proceed. For example, in a loan approval process,
multiple checks like credit score check, income verification might happen in parallel and only
1. What is Rule?
Rule Gets stored into a Table which are mapped to instance classes.
2. Any Rule in Pega that gets stored in Rule base Table will have unique primary Key
“pzInsKey”?
To Open any rule PRPC uses it’s pzInsKey , by performing Obj-Open-By-Handle and the
respective table.
Operator
Obj-Open-By-Handle
pxUpdateDateTime
pxCreateOperator
pxUpdateOperator
pxCreateDateTime.
6. Name any one of the OOTB properties in PEGA which should never be part of
Declare Expression?
pxCreateDateTime
7. How to restrict a property such that it should never be used in declarative rules?
Property advanced tab – Check the option “Con not be a declarative target”.
8. How to unlock a rule set version when you don’t have a password?
At a time a class having Direct + Pattern inheritance make the class to have multiple
inheritance. This is in PRPC is called dual inheritance.
10. If child work object saves in PC_Work (same as parent case) which column hold
child work object data is it pzPVStream going to have embedded pages?
Today – <Tag1>
<Tag2>
<Tag3>
Today – <Tag1>
<Tag2>
<NewTag>
<Tag4>
DSS are data entries, which can be update without check in check out. System setting –
associated rule set versions, we need to patch it and move to production every time you
want to update it.
Configuration tab of the dec tree, “Allow selection of call decision option”.
14. Spinoff will be useful when you want to initiate/start another flow parallelly
without stopping the current flow. The current flow or main flow which has spinoff as
sub process proceeds to the next assignment in the flow and spinoff flow will get
initiated to the work item?
Spinoff is available in sub process shape. Selecting spin off option make process flow
asynchronous i.e, process will not wait for the sub flow to get completed.
15. Importance of Lock option in Obj-open method?
Supports some instance of locking. Shouldn’t allow other people to update the case
16. In the Obj-Open or Obj-Open-By-Handle, I don’t want to choose lock check box.
But when I update the instance, we have to make sure the latest data is available on
the instance step page.
Select to indicate that this flow creates a temporary work item. A temporary work item is
created and resolved by a single operator or by straight-through processing and is never
saved as a database object.
Use this option only in appropriate situations, as reporting, history, and attachment
features are not available for temporary cases. The following restrictions apply:
1.
1.
1.
1.
1.
Yes. We can create an activity in the activity call OOTB activity “NewFromFlow” and pass the
parameters “Flow name and Flow class name”.
Obj for Internal Rule base tables. RDB for external tables.
Obj Can’t execute Stored procs. RDB can execute Stored procs.
Fumction callActivity();
22. What are editable modes in Data Pages? Can a node level data pages are
editable?
If you want to update data page it should be editable. These are not available at node level.
This option is available only for list type data pages. In the page list Pages , one or more
properties can be mentioned as keys. While we pass this keys the matching page data will
be retrieved.
These keys can be passed when the data page is called only at property level but not from
dropdown or repeating layout or activity.
D_AXAStates[Param1:Value1,Param2:value2]
@DecisionTable.ObtainValue(tools,myStepPage,”StageCode”,true)
27. When two users from diff countries triggers (both GMT and IST formats saves)
change both formats as one format as GMT(because DB people issuing some
problems) ?
FormatDateTime()
28. When user login the PRPC Portal, the credientials we are providing
Authentication or Authorization?
29. Tell any 3 rules (when we are configuring them) without class and rule set?
30. If suppose i have three different classes (A,B,C) mapped to 3 different tables,
now my question is,
I should not write any queries or I should not use any obj methods to save phone number
and addresses into Table B and C.
We need to create Indexes for Phone Number and address Page List.
PageListA
PageListA(1) (A-B-C)
PageListA(2) (A-B-C)
PageListA(3) (A-B-C)
PageListB
PageListB(1) (A-B-C)
PageListB(2) (A-B-C)
PageListB(3) (A-B-C)
Append to — Use this action to copy a page to the target. The source and target must be of
the same or compatible classes.
Append and Map to : Use the Append and Map to action to append a page to the target
Page List mode property and set the context to that page for subsequent child actions to
map properties on that page. The target and source can be of different Applies To classes.
32. How many ways we can check checkout rules in Pega platform?
· MyCheckedOutRules (Code-Pega-List)
o pxResults
§ pxResults(1)(Data-Rule-Summary)
§ pxResults(2)(Data-Rule-Summary)
§ pxResults(3)(Data-Rule-Summary)
§ pxResults(4)(Data-Rule-Summary)
§ pxResults(5)(Data-Rule-Summary)
§ pxResults(6)(Data-Rule-Summary)
33. You have an application for managing a simple workflow across two
categories of work; “new business sales” and “renewing sales”. Your business has
many areas that sell different kinds of the same product, which means the ‘flavour’ of
these worktypes will differ from area to area?
The process for both work types is basically identical, however we can’t discount that new
business might one day be drastically different to renewing business. The content of the
screens between each business area does change a lot. We may also need to be able to
formally restrict work access between the different areas of the business.
35. A parent case has the ability for a user to generate up to 5 parallel sub/child
cases, those child cases can update values on the parent case?
36. how will you manage, and what are the considerations of this data
propagation challenge?
B) Make sure by the time child is instantiated the respective source properties must
have values assigned.
Bus (Page)
Tier(List)
Seats(List)
Passengers(List)
38. two page list we have—need to move the data from one pagelist to other
pagelist based on some condition?
40. Need to copy data at one stage in child to parent how u will do?
41. Need to change from 1 stage of case to stage 5 and after that again come back
to stage1—How u will do?
Change state.
42. we have one parent and 2 children when the lock is there lock on parent case
then what is the functionality…?
With default options for locking, when parent is open by requestor1 no one else can work
on children.
With option “do not lock parent when child is open” selected on child cases , when parent
case is been worked on by requestor1 other requestors can work on Children.
43. how many types of sub flow callings shape are there?
Browse (pxCreateDateTime)
Loop
(Obj-Open-By-Handle)
Property-set
Obj-save
Commitwitherrorhandling.
45. scenario: Create a report to get all assignments from workbasket how u will
do?
pxrefObjInsKey
Differ Save means , the data saved into differ queue but not yet committed to DB Tables.
47. scenarion:property1 upadted with X,obj-save and then again same property
updsated with Y with commit what will be the final output?
DB value is “X”.
48. What is Organization class structure and Different types of layers?
At Org, Implementation, Framework we have Data and Integration Layers à Data- and Int-
Org , Div, Unit(Work) – Insurance (Work Type or Case Type) {Belongs to class group}
Org , Div, Unit(Work) – Loan(Work Type or Case Type) {Belongs to class group}
Org , Div, Unit(Work) – Banking(Work Type or Case Type) {Belongs to class group}
49. What are the different mechanisms to initiate case? (what are different
options will be given to users to create case at run time )?
Add, AddWork
New , NewFromFlow
50. Suppose in a Screen flow, you’re having 4 assignments, all the assignments
should be completed within 2hours. Can we implement this or not? If yes, how will
you design this?
In the screen flow/ sub flow on process tab we can call SLA.
51. How can we trace someone’s work in production Environment?
52. What is WSDL file? And difference between WSDL URL and End Point URL?
What is End Point URL, Methods, Request and Response Parameters and its XML Data
Structure.
WS Security, Security through Encrypted User Name and Password send in the
Headers of XML.
55. When we have an issue with service, let’s say you are not getting proper
response from service. How would you trouble shoot this?
Pega-ProCom Rule Set Agents Instance will have an agent “Service Level Events”.
57. There is a concept of soft locking, what it is?
58. In ECS, When do we use framework layer and when do we use Organization
layer?
Org Layer and FW both will be accessible at all the class group.
59. We have Data Page, it is getting populated from external table, then how do
we configure load mechanism?
How would you know when to refresh the data page i.e whenever the data in external tables
changes how come PRPC D Page gets refreshed.
pzFlushDataPage (D_Page)
61. Tell me the difference between Associations and join criteria in RD?
Association rule is a like a reusable rule that defines join of two classes with matching
columns. This gets populated on report rule automatically.
Using a Data transform we can run Obj methods (Tables), Connector and Service Methods.
64. What are the differences between Declare Trigger and Declare Onchange? In
what scenario you will chose what explain?
Trigger monitors a Table and gets fired when DB Insert, Update Delete operations being
performed by Obj- Methods.
On Change gets fired whenever the property values gets changed on clipboard.
66. How to move from 4th stage to 1st stage? What is the activity?
All condition related to other children or parent case (base on ther status)
Manual Instantiation
Keyed Page is available only to list type D Pages and it available to call only on
property.
Requestor : D Page can be share with in requestor session among multiple WOs.
Node : can be share among multiple requestors who logon to same node.
72. When D page will get created if we chose thread as scope in Data page?
Each time we create a case, for each case D Page gets loaded with latest data from
DB.
74. When the page will be removed if the data page scope is thread?
Editable D Pages gets created on clipboard under user pages where read only D Pages
under Data Pages.
Editable pages can be updated , deleted. These D Pages will not be available at node level.
77. When look up option will available as a source for data page?
Post Load Processing, we can call an activity and here we can handle any exceptions.
79. When will u go for standard and when will go for advanced agent?
When we are working agents, if we want process or execute agent activity multiple
times / wakeup then this is possible through queuing.
Here Queue means PR_SYS_QUEUE Table. For each queue Item in this table agent
activity will be executed once.
The Queue Items with status “Scheduled” will be picked. While Processing the Queue Item
status gets updated to “Now Processing”. If something fails during processing, Queue status
is “Broken Process”.
Broken process Items can be re queued. When we re queue the items the status gets
updated to scheduled.
81. What is the access group significance of access group in Agents rule form?
At what access level the agent activity should be executed will be decided by Agents access
group in case of advanced agents.
Standard agents runs on the access group of requestor who put the agent queue item.
For standard agent the access group of requestor overrides the access group in the agent
rule form
82. What will happen if you are not mentioning the access group in advanced
agent?
If no access group specified in Agent Rule form, then advanced agents runs on Guest access
group.
85. How performance is better when we use report definition compared with
Activities?
Activity when we create it’s a used defined one. It may have Bad Coding, It may not be
compatible with the PRPC Existing transaction model.
86. If we want to join 10 tables. How to implement this using RPT rule. It should
not impact application performance?
87. If we want share Data between two pega applications. Insurance and the
other is Claims?
Get most urgent is an OOTB functionality which brings the Urgent Assignment to work
on.
Here we can Query the DB records and onclude their pzInsKeys. Then Data Instance will be
moved.
There are rules associated with rule sets but not with versions. When we select this check
box these rules will not be included in the product packaging.
93. We have deployed an application and application is running. After some you
got a requirement to modify only one of the rule which we have already moved. How
to achieve this?
We need to get the pzInsKey of Rule Instance and include it in Product Rule, then package it.
When we deploy this only one instance will be deployed into production.
94. We have made some changes and successfully tested in Dev, QA, UAT and Prod
also after deployments?
But When the business starts the latest code changes giving a technical issues which has
broken application functionality and entire is stopped. How to handle this situation?
We have separate schema for Rule and Data Instance i.e, Pega Rule and Pega Data.
All the rule instances gets stored in Rules Schema whereas Data instances gets stored in
Data Schema.
96. In activity suppose i have existing 10000 customers have common salary now i
want to increase their salary dynamically at a time?
Property-Set
Obj-Save
Commit;
97. What is the order of Rule resolution? and can u tell some rule types don’t
undergo Rule resolution?
Rule Cache
If Cache Available
Pick the rule from cache, Verify not blocked, Verify user authorized, Process
and Present Rule.
Data Instances like OpID, Access Group, Work Group, Work Basket etc… will
not go through rule resolution process. Because these instance will not be associated with
Rule set versions, Availability and circumstance.
1.
1.
1.
1.
1.
Exit-Activity Ends the execution of current activity whereas Activity-End ends the execution
of All the chain of activities which are involved in the calling processes.
99. What are the process improvements that you have do/Care in the project?
9. Move to UAT
2. Standard used OOTB AQM. 3. Advanced agent will not use , we want to go Queuing we need to design custom
100. What is the main difference b/w Standard Agent & Advanced Agent?
101. What is AQM. ..? Is AQM supports Standard Agent only r Advanced agent as well?
If we apply AQM with advanced agent, we need to implement our own Queue Management.
Assignment level Sla is only for one particular assignment on which we apply it.
WO level SLA is applicable throughout the case processing till it gets resolved.
103. I have one work object based on some condition I want to route work object to
Worklist or workbasket…? How many ways we can achieve this…? If I want give the
condition in single assignment itself how it is possible…?
We need to write a custom route activity which calls toworklist or toworkbasket activities
based on precondition.
104. What Are the Rule Set Pre Requisite, What are Types of rule Sets, and What is
the Rule set hierarchy in PEGA?
All the Predefined rule Sets Should be Address as “Required Rule Sets” to our application
Rule set then any rules in the predefined rule sets can be used in our application.
1. Application Rule Sets (Which we add in Application Rule Form)
2. Production Rule Sets (Which we will add in the Application Rule Form and Also we
can in Access Group Under Advanced Tab.
The Rules in PRPC like Decision rules, Correspondence Rules etc… can be delegated to
business so that business users can modify the rule as per their requirements.
Rules can be delegated from the action Dropdown of the rule form. When delegating it can
be done to Single Operator OR to an Access Group.
Delegated rules will be available to be accessible through the Portals under the
Section “My Business Rules”.
The OOTB sections rule name “Delegated Rules” which is available in “@baseclass”.
These rules can be created in a separate rule set and we call this rule set under
“Production rule Sets” in the application rule form.
The rule sets which we regularly user for creating our rules are application rule
sets.
o
Production Rule Set :- refer above question.
Branch Rule Set:- It is a share rule set. This allows multiple developers
to perform parallel updates on the rules. After that we can merge the
branch rule sets into the original rule set with all changes. Branch
Rule Set can be added in the application rule Form.
Personal Rule Set :- This is virtual rule set created with the Operator ID
name.
When an Operator check out a rule PRPC copies the rule from
Original Rule Set to Personal Rule Set allowing the operator to make
changes. After the changes are done/check in the personal rule set
copy will be lost and latest changes will be saved into original rule set.
All the Checkout rules will be available in Personal Rule Set. The
Priority when accessing the rule goes to Personal Rule Set.
On Change Rule gets executed when the property value changes anywhere in your
application.
Trigger gets executed only where there is any update or insert or delete operations
performed on Data Tables.
111. How to make a local action available to be accessible at all the assignments in
the Flow?
We can call the flow action or local action in the Design tab of the flow. The local action
which are called in the assignment shape properties will be available only to that particular
assignment whereas the local actions which we call in the design of the flow will be available
to access at all the assignments in a flow.
Declare expression is an example of forward and Backward chaining .We have different
options available to choose those are
1.Whenever Inputs Change (Every time when source properties changing Declare
expression gets executed and assign the target prop value this is FWD chaining.)
2. Whenever Used :- Every time when we use target prop declare expression will be
executed to assign value to target prop. This is backward chaining.
113. What are the OUT-OF-BOX solutions you’ve used in your project?
An Operator Can have Multiple Access Groups Defined but one should be default.
Work Group Acts an Interface between Operator and Work Basket. Work Group and Work
Basket can be connected to each other.
Work pool :- Class Group when added in the access group (Under Advanced Tab) it is said to
be work pool. It Identifies which case types should be loaded for an operator to create work.
Below Diagram Explains the relation between Operator, Work Group and Work
Basket.
117. What is the diff bet Rule and a Rule set?
Anything in PRPC is called as a Rule. For Example Property, Activity, Data Transform
etc… Rule Set is a container to hold all the rules into it and which allows the versioning
of rules.
118. What are the Application Servers that PRPC supports and who maintains these
servers?
If we want to see the current assignment details we can see on clipboard on a predefined
page “NewAssign” Page (Assign-)”
By default screen flow cannot create a work object but we can call OOTB activity rules like
“New or NewFromFlow” and pass the screen flow class and name as parameters then it
creates a Work object.
123. What’s the difference between connector flow action and local flow action?
Flow action performs an action on Work object and it moves WO from one assignment to
another assignment.
Whereas local action also performs an action on WO, but it doesn’t move from
current assignment i.e, the Work Object will be still on same assignment.
List View will generate plain reports whereas summary generates reports using Aggregate
Functions
14. Explain the purpose and use of Pega’s Decision Rules and Predictive
Analytics.
— Decision Rules are used to automate decisions, while Predictive Analytics uses
machine learning for intelligent decision-making.
15. How do you implement dynamic UI changes based on user input in Pega?
— Use Declare Expression and Refresh Harness to update the UI dynamically.
17. How do you manage access control and security in Pega applications?
— Pega provides access roles, privileges, and ACLs to control user access and
security.
18. What are the different types of connectors available in Pega for integrating
with external systems?
— Pega supports various connectors like SOAP, REST, JDBC, JMS, etc., to
integrate with external systems.
19. How do you implement SLAs (Service Level Agreements) in Pega
applications?
— Use SLA rules to define and manage SLA deadlines for case processing.
22. What is Pega’s SmartShape, and how do you use it in case processing?
— SmartShape is a graphical shape that represents flow actions in case
processing.
23. How do you design and configure data models in Pega applications?
— Use Pega’s Class, Property, and Data Model rules to design data structures.
24. What is a Page List in Pega, and how do you work with it?
— Page List is a collection of pages of the same class. Use it to store and
manipulate multiple instances of data.
26. What is a User Portal in Pega, and how do you create one?
— A User Portal is a customized interface for users to interact with Pega
applications. Use App Studio to create one.
27. How do you manage and monitor application performance in Pega?
— Pega’s Application Performance Monitoring (APM) helps monitor and
optimize application performance.
28. What is the Pega Robotics Studio, and how does it support Robotic Process
Automation?
— Pega Robotics Studio is used to design and configure robotic automation
tasks.
29. How do you implement encryption and secure storage of sensitive data in
Pega?
— Pega provides encryption options and secure storage mechanisms for
sensitive data.
30. Explain the purpose and use of Pega’s Case Management features.
— Pega’s Case Management features allow users to manage and track case
processing efficiently.
31. What is the purpose of Pega’s Declarative Network, and how do you
configure it?
— Declarative Network manages the flow of cases based on dependencies
between case types.
35. What is the role of a Pega Business Architect, and what responsibilities do
they have?
— A Pega Business Architect collaborates with business stakeholders to gather
requirements and define solutions.
36. How do you optimize and improve the performance of Pega applications?
— Use performance analysis tools like PAL (Performance Analyzer) and DB
Trace to identify bottlenecks.
39. What are Decision Maps in Pega, and how do you use them?
— Decision Maps visualize decision trees and help in understanding decision
logic.
40. How do you create and manage Business Reports in Pega?
— Use Report Definitions and Report Browser to create and manage Business
Reports.
41. Explain the purpose and use of Pega’s Case Types and Subtypes.
— Case Types represent different types of work, and Subtypes represent
variations within a case type.
42. What is Pega’s Agile Workbench, and how does it support Agile development
practices?
— Pega’s Agile Workbench helps manage and track user stories, backlogs, and
sprints
43. How do you implement auto-numbering and sequence generation for cases
in Pega?
— Pega’s Data Transform rules can be used to generate unique sequence
numbers.
45. How do you use Decision Tables in Pega for rule resolution?
— Decision Tables help in determining rule resolution based on conditions and
parameters.
46. What is Pega’s Case Designer Studio, and how do you use it?
— Case Designer Studio is used to design and configure case types and case
processes visually.
48. Explain the purpose and use of Pega’s Automated Testing features.
— Automated Testing allows users to create test cases and execute them
automatically.
49. How do you use Pega’s Dynamic Layouts for responsive UI design?
— Dynamic Layouts automatically adjust UI components based on screen sizes
and resolutions.
50. What is the Pega Cosmos Design System, and how does it enhance user
experiences?
— Pega Cosmos Design System provides UI guidelines and patterns for
consistent and intuitive user experiences.
52. What are Service Levels in Pega, and how do you configure them?
— Service Levels define maximum timeframes for case processing. Configure
them using SLA rules.
53. How do you implement conditional validation and data transformation in
Pega?
— Use when rules and Declare Expression rules for conditional validation and
data transformation.
54. Explain the role of a Pega System Architect, and what are their
responsibilities?
— Pega System Architects are responsible for designing and implementing
technical solutions.
57. How do you configure Pega’s Security policies and Authentication services?
— Use Access Groups, Authentication services, and Security Policies for user
authentication and authorization.
58. Explain the use of Data Transform rules for data manipulation in Pega.
— Data Transform rules are used to convert, copy, and manipulate data between
properties and pages.
59. How do you manage and monitor system performance in Pega applications?
— Use Pega’s Performance Analyzer (PAL) and Application Monitoring to
analyze and optimize performance.
60. What is Pega’s Application Express, and how does it support rapid
application development?
— Pega’s App Studio, part of Application Express, enables rapid application
development with minimal coding.
61. How do you implement system alerts and notifications in Pega applications?
— Use Email, SLA, and System Alerts to notify users and administrators of
critical events.
63. How do you use Pega’s DCO (Direct Capture of Objectives) in application
development?
— DCO facilitates the capture of business requirements and automates the
creation of application artifacts.
64. What is Pega’s Case Management Portal, and how do you customize it?
— The Case Management Portal provides an interface for managing and
processing cases. Customize it using skin rules.
65. How do you use Pega’s Email Listener for email integration?
— Pega’s Email Listener allows the system to process incoming emails as cases
or tasks.
68. What is the purpose of Pega’s Case Designer Studio, and how do you use it?
— Case Designer Studio allows users to visually design and configure case types
and case processes.
70. Explain the use of Pega’s Pulse feature for social collaboration in
applications.
— Pulse allows users to collaborate, share updates, and comment on cases
within the application.
71. How do you implement Parallel Processing in Pega for case management?
— Use the Split-For-Each shape in Flows to process multiple items in parallel.
73. How do you configure Pega’s Email Integration for incoming and outgoing
emails?
— Use Email Accounts and Correspondence rules to set up email integration.
74. Explain the use of Pega’s Embedded Pages for data organization and
manipulation.
— Embedded Pages allow the nesting of data within a property, enabling
structured data organization.
75. How do you integrate Pega applications with external systems using REST
APIs?
— Pega provides REST Connectors to interact with RESTful APIs of external
systems.
76. What is Pega’s Pulse and how does it support collaboration in case
processing?
— Pulse is a social collaboration tool that allows users to communicate and
collaborate on case updates.
78. Explain the use of Pega’s SLA (Service Level Agreement) rules in case
management.
— SLA rules define timeframes for completing stages and processing cases
within specific deadlines.
79. How do you implement Custom User Interfaces using Pega’s User Interface
(UI) components?
— Use Sections, Harnesses, and UI rules to create custom user interfaces in Pega
applications.
80. What is Pega’s Integration Designer, and how does it support external
integrations?
— Integration Designer provides tools to configure and manage integrations
with external systems.
81. How do you use Pega’s Declarative Expressions for dynamic data
computation?
— Declare Expression rules automatically compute and update property values
based on defined expressions.
82. What is the purpose of Pega’s Application Profile and how do you use it?
— Application Profile manages and controls branching and merging in
application development.
83. How do you design and configure Data Models in Pega for data
representation?
— Use Class, Property, and Data Model rules to design and represent data
structures.
84. Explain the use of Pega’s Case Management features for efficient case
processing.
— Pega’s Case Management features enable users to manage and track case
processing efficiently.
86. What is the purpose of Pega’s Decision Management features for intelligent
decision-making?
— Pega’s Decision Management helps automate and optimize decision-making
processes.
Pega applications?
— Pega’s Performance Analyzer (PAL) and Application Monitoring tools help
analyze and optimize performance.
88. What is Pega’s Application Express, and how does it support rapid
application development?
— Pega’s App Studio, part of Application Express, enables rapid application
development with minimal coding.
89. How do you implement system alerts and notifications in Pega applications?
— Use Email, SLA, and System Alerts to notify users and administrators of
critical events.
91. How do you use Pega’s DCO (Direct Capture of Objectives) in application
development?
— DCO facilitates the capture of business requirements and automates the
creation of application artifacts.
92. What is Pega’s Case Management Portal, and how do you customize it?
— The Case Management Portal provides an interface for managing and
processing cases. Customize it using skin rules.
93. How do you use Pega’s Email Listener for email integration?
— Pega’s Email Listener allows the system to process incoming emails as cases
or tasks.
96. What is the purpose of Pega’s Case Designer Studio, and how do you use it?
— Case Designer Studio allows users to visually design and configure case types
and case processes.
98. Explain the use of Pega’s Pulse feature for social collaboration in
applications.
— Pulse allows users to collaborate, share updates, and comment on cases
within the application.
99. How do you implement Parallel Processing in Pega for case management?
— Use the Split-For-Each shape in Flows to process multiple items in parallel.
100. What is the purpose of Pega’s System Management Application (SMA)?
— SMA provides tools for monitoring, managing, and troubleshooting the Pega
system.
These questions cover a broad range of Pega topics and can help you prepare for
your Pega architect interview. Remember to study and practice in-depth to
demonstrate your knowledge and skills during the interview. Good luck!
Pega Interview Questions and Answers
Pega is a software development solution that eliminates the need for coding while creating BPM and CRM
systems. Because Java is based on Java and makes use of OOP and Java concepts, it heads it in the
backend and automates all the business processes involved in developing the applications. Pega is
primarily used for cost-cutting and enhancing corporate objectives. You can see the list of basic Pega
interview questions that the panel asks most commonly in this article. This will enable you to ace the
interview at prestigious IT companies. Explore the top 15 reasons why you must learn Pega.
What is Pega?
With the help of the Pega platform, users may create apps, integrate them with other systems, and quickly
implement mobility. In-depth UI design, decision-making, DevOps implementation, robotic process
automation, case life cycle management, and reporting are all aided by it. It is based on Java and is
currently on version 8.2, which is also known as Build for Change.
Dev Studio
App Studio
Admin Studio
Prediction Studio
Studios—also referred to as workspaces—allow users to work with role-based capabilities and expedite the
development of applications. Role-based features enable various developer types to use the tool for
particular tasks.
What does Pega mean when it refers to a workstation or studio?
In Pega, a workstation or studio is a designated area with particular equipment and amenities.
What new components have been added to the Pega 8.4 version for developing applications?
The following are some of the new features that Pega 8.4 has added from the perspective of application
development:
What makes the Property-Validate and Page-Validate methods different from one another?
Every property on a page is validated using the page-validate method. This function will validate all the
properties recursively if a page has embedded pages. This approach takes longer and consumes more
system resources. To validate specific properties, use the Obj-Validate method in conjunction with a Rule-
Obj-Validate rule.
A property’s value can be restricted by applying the property-validate method. Use the Edit validate rule
when combined with the Property-Validate method to implement constraints. You can validate many
properties at once with the property-validate function.
What is the distinction between the Page and Page List properties? How are they put into action?
The following is the distinction between the Page and Page List properties:
A page property refers to a certain class and is used to access that class’s properties.
Page List Property also refers to a specific class, but it is a collection of individual pages of the
same class that may be retrieved via numeric indexes.
Regular Pages:
The page-new technique is used to build regular pages, also known as user pages.
It is simple to edit or remove these pages immediately.
The moment you log out of the system, these pages are instantly removed.
In Pega, what is a portal exactly, and where will it be set up?
A user interface that is visible to users is called a portal (either for developers or end users). The Access
Group is where the portal can be configured. portals for developers, administrators, managers, users, and
so forth.
Explore a wide range of RPA career opportunities and prepare yourself for a promising future.
Browser requestor: The browser requestor begins with the letter ‘H’.
Batch requestor: The batch requestor has the letter ‘B’ in its name.
Application requestor: The letter ‘A’ stands for application requestor.
Portal requestor: The letter ‘P’ stands for portal requestor.
Choose the delayed requestor from the list of requestors, then click the tracer.
Within 60 seconds, forward this case to a specific assignment that includes the SLA.
Our UiPath training in Chennai is also a recommended course that creates wonderful job opportunities
globally.
When combined with comprehensive support, it can enhance case management procedures.
Additionally, it improves case flow’s effectiveness for dynamic and automatic answers.
Using context-based and real-time management guarantees consistency and eliminates errors.
It saves the time, money, and effort required to put case management into practice.
5. You can choose from the following options for when you want the dynamic layout to show up in the
visibility field:
What are the primary benefits and drawbacks of declaring pages in Pega?
Benefits of Pega’s Declare Pages:
Declaring pages has the primary benefit of avoiding numerous database hits. Assuming that a node has
several requestors, load activity will start at the initial user’s login, creating a declaration page before
loading the data onto it. The requestors on that node view and use this declaration page and its contents.
Know the differences between RPA and Selenium.
Limitations of Pega’s Declare Pages:
One drawback of Pega’s ‘Declare’ pages is that they have the primary drawback of being read-only for the
requestors. It is unable to both add new data and remove particular data.
As a Pega developer, you’ll be working with various rule types in the Pega
platform to build applications and integrations. Knowing the difference
between Rule-Obj-Activity and Rule-Connect-SOAP demonstrates your
understanding of Pega’s rule types and their respective use cases, which is
essential for creating efficient and well-designed solutions within the
platform.
While both rule types play a role in integrating Pega applications with
external systems, Rule-Obj-Activity provides a more general-purpose
approach, whereas Rule-Connect-SOAP focuses on SOAP-based web
service integrations.”
3. How do you create a new work object in Pega?
Example: “To create a new work object in Pega, you typically use the Obj-
Open method or the Create Work process. The Obj-Open method is used
when you want to instantiate an existing work object, while the Create
Work process is utilized for creating a new instance of a work object.
When using the Create Work process, you first need to ensure that your
flow has a starting point by adding a “Create” shape at the beginning of the
flow. Next, configure the properties of the “Create” shape by specifying the
class and flow name associated with the work object. Once this is done,
save and run the flow. As the flow executes, it will create a new work object
based on the specified class and initiate the defined process.
5. What are some best practices for designing efficient user interfaces in Pega applications?
Once you have created or selected a Data Type, you can define its
properties (fields) that will store specific pieces of information. For each
property, you need to specify its name, data type, and any constraints or
validations required. You can also configure how these properties are
displayed on forms and reports.
Example: “Decision tables and decision trees play a vital role in Pega
development as they help implement business rules and logic efficiently.
Both are used to define conditional processing, but they serve different
purposes based on the complexity of the conditions.
Decision tables are best suited for scenarios with multiple conditions that
result in specific outcomes. They present these conditions in a tabular
format, making it easy to visualize and manage complex rule sets. Decision
tables simplify maintenance by allowing developers to update or modify
rules without altering the application’s code directly.
On the other hand, decision trees are ideal for handling more intricate
situations where nested conditions need to be evaluated. They use a
hierarchical structure to represent branching decisions based on various
criteria. This allows developers to create sophisticated decision-making
processes while maintaining readability and modularity within the
application.
10. How do you implement security features, such as authentication and authorization, in Pega
applications?
For authorization, I utilize Access Groups and Access Roles within Pega.
Access Groups define the roles and privileges assigned to different user
groups, while Access Roles determine what actions users can perform on
specific objects. I carefully design these configurations based on the
principle of least privilege, granting users only the necessary permissions
for their job functions. Additionally, I make use of Data Access Control
policies to restrict data visibility and modification at the record level,
ensuring that sensitive information is protected. These combined measures
help create a secure environment within the Pega application,
safeguarding both user access and data integrity.”
11. What is the significance of harnesses and sections in Pega UI design?
Sections, on the other hand, are reusable building blocks that can be
embedded within harnesses or other sections. They enable developers to
create modular and maintainable UI components, such as input fields,
tables, or buttons. Sections promote reusability and reduce redundancy by
allowing common UI elements to be shared across multiple forms or
pages.
Example: “Page List and Page Group are both types of properties in Pega
that store multiple pages, but they differ in how they organize and access
the data.
Choosing between Page List and Page Group depends on the specific
requirements of your application and how you need to access and
manipulate the data stored within these properties.”
13. What are the various types of flows available in Pega? Provide examples of when to use each
type.
Example: “There are three main types of flows in Pega: Process Flows,
Screen Flows, and Subflows. Each type serves a specific purpose within
the application development process.
1. Process Flows: These are the primary flows used to define the
sequence of steps required to complete a business process. They consist
of shapes like assignments, decisions, and connectors that represent
tasks, branching conditions, and paths between tasks. An example use
case for a process flow is an insurance claim processing system, where
multiple stages such as claim registration, validation, approval, and
payment need to be executed sequentially with possible conditional
branches based on various factors.
Hiring managers want to ensure that you, as a Pega Developer, have the
technical knowledge and expertise to integrate Pega applications with
external systems. This is a key aspect of the job, as Pega applications
often need to interact with other tools and systems within an organization.
Your ability to describe this process demonstrates your understanding of
Pega’s integration capabilities and your experience in working with diverse
technologies.
The rule resolution engine follows a specific order while searching for the
best-suited rule instance. It starts by looking at the highest class in the
inheritance path and then moves down through subclasses until it finds an
applicable rule. If multiple instances are found within the same class, the
engine considers additional factors like rule versioning, date-time validity,
and security constraints to select the most relevant one. This ensures that
the system executes the most suitable rule according to the current
context, promoting modularity and reusability of rules across different
applications and scenarios.”
17. What are the different types of inheritance in Pega, and how do they impact application
development?
Example: “Pega offers two types of inheritance: pattern and directed. Both
play a significant role in application development by promoting reusability,
modularity, and maintainability.
Once the rule is created, you can start configuring the report using the
Query tab. Here, you’ll select the properties (columns) to be displayed in
the report, specify filter conditions, and set up sorting or grouping as
needed. Additionally, you can use the Join feature to include data from
other classes if required. After defining the query, move on to the Data
Access tab to set pagination options and optimize performance by limiting
the number of rows returned.
To finalize the report, customize its appearance using the Display Options
tab, where you can choose chart types, add summary functions, and
format columns. Once satisfied with the configuration, save the rule and
test it using the Run button. Finally, embed the report into a section or
harness within your application so that end-users can access and interact
with it.”
19. What is the purpose of using validation rules in Pega applications?
Implementing validation rules not only enhances the overall quality of the
data but also improves user experience by providing immediate feedback
on any issues with their input. This allows users to correct mistakes
promptly, reducing the likelihood of encountering problems later in the
workflow. In summary, validation rules contribute significantly to
maintaining a reliable and efficient Pega application by safeguarding data
accuracy and promoting seamless user interactions.”
Firstly, I make use of declarative error handling using Validate rules. These
rules help me define validation conditions for properties and pages,
ensuring that data entered into the system meets specific criteria before
proceeding through the workflow. This helps prevent potential issues
caused by incorrect or missing information.
When it comes to runtime exceptions, I utilize the Exception Handling
shape within the flow rule. This allows me to define how the system should
respond when an exception occurs during process execution. For instance,
I can configure the shape to route the case to a different user or work
queue, send notifications, or log the error details for further analysis.
Additionally, I always ensure proper documentation of these exception
handling mechanisms so that other team members can easily understand
and maintain the implemented solutions.”
23. What are the key performance indicators that you monitor during Pega application
development?
24. Describe your experience with Pega unit testing and debugging tools.
Interviewers ask this question to gauge your familiarity with Pega’s built-in
testing and debugging tools, which are essential for ensuring the quality
and functionality of applications you develop. Your experience with these
tools demonstrates your ability to identify, troubleshoot, and resolve issues
in a Pega development environment, ultimately leading to a more efficient
and effective development process.
29. What are some common challenges you have faced during Pega development projects, and how
did you overcome them?
Another challenge has been integrating Pega with external systems, such
as databases or APIs from other platforms. In these cases, I collaborate
closely with the teams responsible for those systems to ensure seamless
data exchange and compatibility. Additionally, I leverage Pega’s out-of-the-
box connectors and integration capabilities whenever possible, which helps
streamline the process and minimize custom coding efforts.”
30. Can you provide an example of a successful Pega implementation that you were involved in?
13. How can I see the values of the activity's local variables?
Ans: Log message is used to see the values of the activity’s local variables.
Define Rules: Create your logical rules using the functions provided by z3.
These rules describe constraints, equations, or logical relationships.
Check Satisfiability: Use z3 to check if your rules are satisfiable, meaning they
can be true under certain conditions.
Solve or Analyze: Depending on your use case, you can solve equations,
analyze constraints, or find valid solutions based on the rules you've defined.
19. What workspaces are supported in the most recent Pega
release?
Ans: Pega's most recent release supports the four workspace types listed below:
App Studio: Helps to build an application without any line of code, it is
multichannel and helps in UI development.
Prediction Studio: Its built-in AI power and Decisioning help to Pega find the
next best decision.
Admin Studio: It basically manages security, users, the runtime status, and
cloud performance for all your apps
20. What are the many classes that PRPC (Pega Rules
Proccess Commander) supports?
Ans: PRPC is a framework for developing and deploying business process
management, customer relationship management (CRM), decision management,
and case management systems. Pega PRPC is a Java-based automated backend
tool from Pega.
The following are the various classes that PRPC supports:
Base Class: It is the ultimate base class, and its child classes include work-, Data-,
Rule-, Assign-, History-, and so on. Pega only supports two kinds of classes:
abstract classes and concrete classes.
Abstract Classes: Abstract classes are those that terminate in '-,' and they
cannot create any work object instances.
Concrete Classes: Concrete Classes do not terminate in '-' and will generate
work object instances.
Batch requestor: Its name begins with the letter 'B.'This is utilized by
background processing listeners, services, agents, and daemons. For requestor
sessions that use this instance, the requestor ID starts with the letter B. When
the PRPC (Pega Rules Process Commander): Agents access group is first
implemented, all BATCH requestors have access to it. If you make a
modification to Data-Admin-Requestor. When you BATCH so that it no longer
has access to the PRPC: Agents access group and then upgrade the Pega
Platform, the system may fail to boot.
Application requestor: Its name begins with the letter ‘A’.Listeners and other
client systems use this to access the Pega Platform, such as through a service
request (other than JSR-168 requests using Rule-Service-Portlet rules). In
requestor sessions that use this requestor type instance, requestor IDs that
begin with the letter A are used.
PRPC: Unauthenticated access group is first implemented, all BROWSER
requestors have access to it.
Portal requestor: Its name begins with the letter 'P.'For HTTP access as a
portlet, this is used in conjunction with Service Portlet rules.
33. What is the name of the table that is used for adding a note
in Pega?
Ans: The table that is used for adding a note in Pega is pc_data_workattach.
Ans: It collect the highest version of the every rule in the ruleset and copies them into new
major version of that ruleset on the same system.
EX: If we are skimming loan appl:05-06-07, the only options like 06-01-01 and 07-01-01, but
we can not skim to 05-07-08 and so on.
Ans: We have different types of Standard Classes will be avaliable which are,
@baseclass is Ultimate base class, And Its Child Classes are work-, Data-, Rule-, Assign-,
History-, etc. Pega always Support 2 types of classe which are Abstract Classes And Concrete
Classes
Abstract Classes are ends with ‘-‘ and abstract Classes cannot create any work object
instances
Concrete Classes will Does not ends with -, And Abstract Classes will create Workobject
instances
Ans: A work object is the primary unit of work completion in an application, and the
primary collection of data that a flow operates on.
As an application is used, work objects are created, updated, and eventually closed
(resolved).
Every work object has a unique ID (property pyID), an urgency value, and a status (property
pyStatusWork).
Q6. Explain about Work Object ID?
Q7. Where we determine the prefix and suffix of of the Work Object ID?
Ans: The prefix and suffix are determined by a model rule pyDefault for the work type or the
class corresponding to the class group. The model is referenced on the Process tab of the flow
rule that creates the work object.
1. Call: If we call one activity to another activity by using call, it will execute the called activity
and return back to calling activity then execute the remaining steps in a calling activity.
2. Branch: If we call one activity to another activity by using Branch, it will execute the called
activity and calling activity then it will not execute the remaining steps after branch.
Ans: Each operator may have a list of workbaskets that they can view. Normally users can
fetch assignments directly from any workbasket defined for their own organizational unit.
However, if the roles are specified in the roles array on the workbasket tab of the workbasket
data instance, the operator must possess at least one access role that matches an access role in
the Roles array.
Ans: A summary view rule defines a two-level report display, presenting summary counts,
totals or averages to be displayed initially, and allowing users to click a row to drill down to
supporting detail for that row.
Summary view rules support interactive charts, trend reports, and the use of AJAX for pop-up
Smart Info windows.
A summary view rule is an instance of the Rule-Obj-SummaryView rule type. This rule type
is part of the Reports category.
A list view rule, an instance of the Rule-Obj-ListView rule type, defines a report. Users can
personalize list view reports easily and interact with them.
Use the Report wizard to define list view reports and link them to our portal.
Ans: To divide the ListView in to different pages and set the number of records to be
displayed in a page.
Q18. What is the activity responsible for getting the data in List View?
Ans:
Step1: Create Activity in Our Class and create the New page
Step2: write a query and store in variable.
Step3: call the listview as Call Rule-Obj-ListView
Step4: Write the another activity in Embed-ListParams
Step5: create the parameter. This parameter get the sql query from previous activity
Step6: write Java method The java code in this method is
Get the page from pyContentPage if page already exists. If page is not available it creates the
new ContentPage.
In this code get the sql query from the above parameter and pass this query and above created
ContentPage as parameters to this tools.getDatabase().executeRDB(query, pagename)
method.
Q19. What are SLAs used for? How do you configure an SLA?
Ans: SLAs are rules in PRPC that indicate the expected or targeted turnaround time for the
assignment, or time-to-resolve for the work object. Each service level rule defines one to
three-time intervals, known as goals, deadlines, and late intervals. Late intervals are repeated.
Service level rules can be associated with assignments in a flow and with the entire flow. For
example, we can set a goal of 2 hours to process an assignment and a deadline of 4 hours.
(The time interval starts when the assignment is created, not when a user begins processing
the assignment.)
For assignments, the service level rule is referenced in the Assignment Properties panel of the
assigned task.
For the overall work object, the service level rule is identified in the standard
property .pySLAName, typically set up through a model for the class. (The default value is
the Default service level.)
** The Pega-ProCom agent detects service levels not achieved — unmet goals or deadlines
— promptly. If an assignment is not completed before the time limit, the system can
automatically notify one or more parties, escalate the assignment, cancel the entire flow, and
so on.
Q21. What do you mean by Case Management in PEGA? When do you use folders?
Ans: Case Management involves managing work that, for processing and reporting purposes,
differs from classic BPM work objects. Cases may involve:
Service levels
Attachments Categories(and automatic attachments when work objects are created).
Automatic and conditional instantiation of covered items when a new cover(case) is created.
Mapping roles to object access for your various case and work types.
Q22. What do you mean by exposing a property? Did you use any SQL tools or does Pega provide
some means to expose columns?
Ans: A Single Value property that is visible as a column in a database table is said to be
exposed. Only exposed properties can be used for the record selection operations in list view
and summary view rules.
In PEGA we can use the ‘Modify Database Schema’ wizard to expose properties. Also, the
database administrator can cause a property previously stored only inside the Storage Stream
column to become a separate exposed column using SQL tools such as TOAD.
** Aggregate properties, properties within an embedded page, and properties that are not
exposed are contained in a specially formatted Storage Stream or BLOB column. Most Pega
Rules database tables contain a Storage Stream column named pzPVStream.
** Exposing too many properties in a table may speed reporting and searching operations, but
make the insert and update operations slower. The tradeoff and relative impact depend on
hardware and software and no general guidelines exist.
Ans:
Whenever we want to connect with external data base, first we need to create the data base.
Whenever we create the data base, we need to provide the JDBC url name, user name and
password.
Once we created the date base, we need to create the data base class. In a data base class , we
need to create the required properties.
After creation of data base class, we need to create the data base table. At the time of creating
data base table, we need to provide the data base name, data base table name and schema
name.
We need to create the connect sql. In a connect sql rule , if we want to fetch multiple records
then we need to write the query in browse tab.
If we want to fetch single record then we need to write query in open tab.
If we want to save the data in to data base then we need to write the query in save tab.
Create the activities by using RDB-Methods.
Q24. What is Access Group and Access roles and difference between them?
Ans: Access groups make a set of RuleSet versions available to requestors. Use an access
role name to convey permissions (capabilities) to a user or a group of users. Access roles can
be referenced in requestor instances, Operator ID instances, in access group instances, in
activities, and in queries.
What do you mean by workplace or studio in the context of Pega?
A workstation is a designated area with particular equipment and amenities. You can
facilitate teamwork by assigning tasks that correspond with individual skills and utilizing
distinct workspaces for the development and administration of your application.
The Pega platform offers four role-based authoring workspaces, or “studios.”
App Studio
Dev Studio
Prediction Studio
Admin Studio
What role does the Service Page rule play in the development of a service?
When Pega apps are acting as service providers and delivering the service, a Service Package
rule is produced. The service package rule has three key functionalities configured.
Processing Mode: Two varieties of processing modes exist.
State Full: We select state full processing mode in state-full mode when we wish to
use a requestor’s clipboard data for other or subsequent requests.
Stateless: In this case, each request will be treated as unique.
Access Group: The incoming requestor running the access group uses this to determine the
service rules.
Authentication: Incoming requests are authenticated using this.
Suggested article: RPA Tools Comparison
When will we be establishing the connector rule in Pega?
When we needed to use the service that the other applications were providing, we defined
the connection rule in Pega.
For example, if the protocol is SOAP, the REST CONNECT rule is used for restful services and
the SOAP CONNECT rule is used for SOAP.
Softlogic is the best online training platform, and they offer a course titled “Pega Training” if you’re
interested in advancing your career through Pega expertise. Insights gained from this course will aid in
your pursuit of professional distinction in this field. Enroll in the best software training institute in Chennai
to become successful in your career.
2. Where work objects will be stored ?
By default, the pc work table is where Work Objects are saved. However, if you’d rather keep track of
your project’s items in a custom table, read on!
Make a database structure that mirrors the pc work table. (It’s recommended that you duplicate the pc work
schema and then change the names of the tables and constraints, if necessary.)
To use the new table, update the class group mapping (Data-Admin-DB-Table).
3. What is the distinction between Edit validate and Edit Input rules ?
To check if a property’s value is correct in Java, use the update validate rule. Validation rules for
properties, objects, and rules can be edited with the help of the property-validate, Rule-Obj-Validate, and
Property rules operations.
The rules of edit input reformat the user’s input into the desired format. If a user submits a date in
MM/DD/YYYY format, the edit input rule will automatically convert it to DD-MMM-YYYY format
(required format). For this modification, java code writing is required once more.
4. What are the distinctions between the Page-Validate and Property-Validate
approaches ?
All of a page’s properties can be checked using the page-validate method. For recursive property checking,
this method is useful when a page contains other pages within it. This procedure uses up more time and
resources on the computer. Use the Obj-Validate method in conjunction with a Rule-Obj-Validate rule to
check the validity of individual properties.
Limits on property value are enforced through the use of a property-validate strategy. Put in place rules by
combining the Edit validate rule with the Property-Validate technique. The Property-Validate technique
allows for the simultaneous validation of several properties.
5. How can I divide up the data from my application into three tables if I have
three distinct types of work objects ?
Invoke the instance of Data-Admin-DB-Table for each class, specifying the table name. This will create
the new table in the Data-Admin-DB-Table instance where all of the work objects can be kept. If there are
too many instances of a certain class’s objects, this is a good strategy to employ. Enroll in the best software
training institute in Chennai and learn any software course with hands-on experience.
6. How to make any rule a favorite to your manage ?
Give the management the regulation to implement.
7. How to Import Rules in PZinsky 9 ?
When exporting a rule, you first need to open it, then choose the pzinskey, then head to prdbutil, and lastly
enter the pzinskey. Put that compressed folder wherever you like.
8. What are StepStatusGood, StepStatusFail rules ?
The rule determines whether the pxMethodStatus property has the value “Good” if the condition defined in
@baseclass evaluates to true.
In order to determine if the pxMethodStatus property has the value “Fail,” the stepStatusFail when rule
examines the @baseclass-defined condition.
9. obj-open vs. obj-open-by-handled: what's the difference ?
With Obj-Open, we may retrieve numerous rows from a table according to the criteria from a given class.
Or Launches a new instance of the specified class.
The pzInskey is being used as an instance handle in an OBJ call to open a single record at a time. Or A
pzInsKey value handle opens the object.
Only if you know the handle that permanently identifies the instance you want to open should you use the
Obj-Open-By-Handle function. If it doesn’t work, try Obj-Open.
10. When comparing activity and value, what is the key distinction ?
The Rule-Obj-Activity rule type is instantiated whenever there is an activity. The basic sequential
processing unit in Process Commander is an activity.
The Visio diagram’s form indicates a process that does not need user intervention but does update a work
object. The system comes preloaded with predefined routines for commonly performed utility chores, and
you have the option of adding your own.
All utility jobs must have an Activity reference to a specific task. While the utility shape can be called an
activity type, the inverse is not true. Learn the Pega course in Chennai and excel in your profession.
11. Where can I find the values of the parameters I copied from one activity to
another (values..) in the clipboard?
No, this is not feasible with the clipboard; however, you may view it in tracer by tapping the page name in
the step method column.
12. Explain The Pega Inheritance Theorem (rules, class) ?
Inheritance in rules can maximize the reusability of your rules and permit localized overrides where
necessary. Inheritance, sometimes referred to as polymorphism, is the ability to apply a rule defined for
one class (perhaps an abstract class) to all classes that inherit from that class.
The process of class inheritance involves looking up the class hierarchy from a specific, lower class for
applicable rules.
“PAL counters” or “PAL readings” are where this information is kept. An application developer can use
the data gathered by the requestor’s counters and timers (together known as the “PAL”) to investigate
performance issues.
Reset Data
Save Data
Start DBTrace
DBTrace Options
Start Profiler
Show Graph
My Alerts
Alerts: As the application runs, Process Commander creates a series of text entries called alert messages
that are logged in the performance alert log. These messages typically detail problems or errors with the
application’s performance. PegaRULES-ALERT-YYYY-MMM-DD log is the standard naming
convention for the performance alert log.
AES: As far as AES is concerned, exceptions are handled in the same way as notifications. Whenever an
exception is thrown by a Process Commander server, it is forwarded to the AES system using the Simple
Object Access Protocol (SOAP). AES database’s pegaam exception table is where the system’s interpreted
exceptions are kept. AES aggregates these logs into artifacts of labor known as AES exception items,
taking into account the frequency with which an exception occurs and the system events that produced
those exceptions. The AES pegaam exception work table receives these updates.
14. How do obj-list and rdb-list differ from one another ?
The obj-list command is used to get a list of an object’s properties back to a page for viewing. Essential
Research Areas Obj-List
RequestType is the browser’s type, which enables various forms of processing and the definition of a
variety of attributes. Standard is the default. Constituent piece of the Rule-RDB-SQL implementation.
Access: From the INI file, a hint as to which database package was used to access this table (currently
ODBC). Integral piece of the Rule-RDB-SQL system.
Creating a new table in the database specifically for that occupational group, or mapping the data to an
external database where it will be stored going forward. Enroll in the best software training institute in
Chennai.
18. Where should I put the class instance in the database ?
Creating a new table in the database specifically for that occupational group, or mapping the data to an
external database where it will be stored going forward. Pega Training in Chennai gives you all the
required training and information about Pega
19. Class instances that are stored use the table as their default data source
(how it will search ) pc work
The pr assign workbasket table is where all of your assigned tasks will be kept.
The pr assigns worklist table is where all of your worklist assignments will be kept.
When it comes to flow processing, all the properties of Work objects that must be made available to the
system must be stored in the pc work table, which is mapped to the Work-base class. Connect the classes
of your work objects to the pc work table or another table with the same columns.
The pr data table corresponds to the Database type in the database. Any table with the same column names
as pr data can serve as a mapping for your data classes.
The rule database (pr4 pegarules) will be used to hold all rule-related information. If a class does not have
a corresponding entry in any of the other tables, the stored instance will be placed in pr other as a fallback.
20. Which property is used by default in the routing activity ?
px RouteTo = Param.AssignTo =” workbasket name” for work basket .s
Studios, also known as workspaces, facilitating role-based capabilities and expediting the application
development process. Role-based features allow for specialized use of the tool by various categories of
programmers.
22. What are the many Pega class types ?
This is a standard Pega interview question that often comes up in technical job interviews. Among Pega’s
many class options are:
Rules for working with different data kinds and objects are laid out in detail in the Data Class.
This class specifies how the application communicates with external services and resources, such as
customer databases and third-party servers. The Work Class encapsulates the various resources (data items,
interfaces, etc.) that control how test cases are handled.
23. In Pega, what does DCO stand for?
Direct Capture of Objectives (DCO) is a Pega acronym. Data acquisition, storage, and processing on the
unified Pega platform are all included in this umbrella term.
24. Describe the many Pega layouts that can be used ?
Again, this is a standard Pega interview question for technical positions. Pega’s varied design options
include the following:
Fluid Layout Variable Layouts for Screens Grids and Tree Grids. Learn the Pega course in Chennai and
upgrade your profile.
25. Which types of assignments are there, and where do they live in the Pega
database?
Generally speaking, there are two kinds of tasks to be completed: those on a to-do list and those in a work
basket. Pega’s separate worklists are where these tasks are kept.
Certified System Architect: CSA stands for Certified System Architect. This certification is an entry-
level certification for developers.
CSSA: It is the abbreviation for Certified Senior System Architect. This is a high level of developer
certification. The developers holding this qualification are regarded as professionals in constructing,
evaluating, and leading teams with strong technical characteristics.
LSA: LSA is a short form of Lead System Architect. This is the most advanced level of developer
certification. The developers who hold this certification are regarded as development leaders who are well-
versed in all functionalities and implement them effectively.
34. What does the term workplace or studio mean in Pega?
In Pega, a workspace or studio is an environment that contains particular tools and functionalities.
35. How many distinct harness kinds does Pega support?
There are various sorts of standard harnesses available in Pega, with new, perform, conform, review,
Tabbed, perform screen flow, Tree Navigation, etc. are the most widely used.
36. What are the many class types supported by PRPC?
The following are the various classes that PRPC supports:
Base Class : It is the ultimate base class, and its descendant classes are work-, Data-, Rule-, Assign-, and
History-. Abstract classes and concrete classes are the only two types of classes supported by Pega.
Abstract Classes : They are classes that finish with a dash (-), and abstract classes cannot create
instances of work objects.
Concrete Classes : Concrete Classes do not terminate in ‘-‘, and they produce instances of work objects.
Join the best software training institute in Chennai.
37. What is your definition of a work object? How may a work item be created
in Pega?
A work object is the fundamental unit of work in an application. It is the fundamental data set upon which
a flow operates. During application use, a work object is created, modified, and ultimately closed
(resolved).
Every work object possesses a unique identifier (property pyID), an urgency value, and a status value
(property pyStatusWork).
The following actions must be taken in order to create a work item in Pega:
Click the action tab after expanding the cell property within the button.
Add a specified action to the button.
Add both the focus class and flow name to the button.
Capture the current work object ID using the “Param.prevRecordkey” parameter.
Utilize “Obj-OpenBy-Handle” to open the case.
Copy the information from pagers using the Page-Copy function.
38. Can a flow be initiated via activity? If yes, then what method is employed ?
Yes. It is possible to initiate a flow-through activity. Flow-New is the name of the approach utilized here.
Declare Pages: Declare pages are constructed via declarative rules. While creating a
declare page, the declare keyword must be given. Declare pages as read-only, so they
cannot be immediately deleted or modified.
Regular pages: The page new technique is used to generate regular pages or user pages.
These pages can be directly edited or deleted without difficulty and these pages are
immediately erased upon system logout.
40. What is a portal and where is it configured in Pega ?
A portal is a user interface that appears (Developers or End Users). Access Group allows Portal
configuration. For example, Developer portal, management portal, user portal, admin portal, etc. Enroll in
the best software training institute in Chennai and learn everything with hands-on experience.
41. What are the different types of Pega requestors ?
Following are the various types of Pega requestors :
Internet browser requestor: The requestor browser begins with the letter ‘H’.
The batch requestor’s name begins with the letter “B.”
The application requestor’s name begins with the letter A.
The portal requestor’s name begins with the letter “P.”
42. What are Pega classes ? What different types of classes does Pega
support ?
Pega is a platform that enables rule re-use across case kinds and applications. It enables developers to often
reuse rules in their systems, from single data elements to entire processes. Reusing the rules improves the
application’s quality and can have a favorable effect on development time. The Pega platform classifies
rules according to their reusability within an application. Every cluster is known as a class.
Work Group: Included in the labor class are processes, data items, and user interfaces. All
of them make up the work class, which gives the rules governing how to handle a case.
Integration Class: The Integration class contains the rules that govern how the application
interacts with other services, such as the integration resources connecting to a customer
database or an external web server.
Data Class: The data class maintains the rules that define the application’s data objects,
such as a customer data type or an order items data type, etc.
When a rule is added in App Studio, the appropriate class is automatically selected. You must concentrate
on the desired outcome of the rule rather than its development. You can also write the rule in Dev Studio if
you require class control. If you write a rule that can be reused in multiple apps, the Dev Studio is
suggested.
Appl Accelerator
Application profiler wizard
Appl use cases
Appl Doc Wizard
Appl requirements
44. What exactly is SLA? What purpose does it serve ?
The Service Level Agreement (SLA) is an instance of the Rule-Obj-Service Level Rule type, which may
be added to work and assignment objects. There are two time intervals for SLA, which are referred to as
the Goal and the Deadline, and it reflects the anticipated amount of time needed to complete the
assignment as well as the amount of time needed to resolve the work object. In the event that a given
assignment is not finished within the allotted amount of time, the system has the ability to automatically
raise the assignment and cancel the entire flow, and so on. Learn the Pega course in Chennai and proceed
ahead in your professional life.
45. What are the kinds of SLA that are available? Give a quick summary of
each ?
The following is a list of the several forms of SLA that are utilized in Pega:
Choose the requestor that was delayed and then click on the tracer in the requestors section.
Within the next sixty seconds, please forward this case to a specific assignment that includes the SLA.
47. When it comes to Pega, what exactly is the difference between activity
and Utility?
The following is a list of the primary distinctions in Pega between activities and utilities:
Within the Pega platform, the processing is automated through the use of activity. It is possible to set it up
so that the system may automatically upload claims without any intervention from the user.
An activity consists of a series of actions that are carried out in the order specified by the facilitator. Utility
is a shape in the Pega flow, and Activity is a rule that belongs to the Rule-Obj-Activity combination. This
shape relates to an activity whose usage type is set to Utility. The utility usage type was selected.
An activity can have multiple sorts of usage, such as Utility, Connect, Assign, or Notify, and Route is one
of those usage types. When you want to call activity within a flow, you will need to use Utility. Join t in
this sector.he Pega training in Chennai and become a Pro
48. In Pega, what exactly is the RuleSet ?
An instance of Pega is defined by its RuleSet, which is a collection of business rules. The ruleSet is an
essential subset of PegaRULES, and it is required in order to reference instances that are stored in the
database.
49 .What are some of the most significant benefits of utilizing case
management in Pega ?
The following is a list of the primary benefits of using case management in Pega:
By providing holistic support, it has the potential to improve the case management
processes.
Additionally, the effectiveness of case-flow for automatic and dynamic responses is
improved as a result of this.
Through management that is both context-based and in real-time, it guarantees
consistency and eliminates errors.
The amount of time, money, and effort required to implement case management is
reduced as a result of its time efficiency and cost-effectiveness. Enroll in the best software
training institute in Chennai to learn from basics to advanced levels in Pega.
50. What does DCO stand for in Pega? What are some of the advantages of
utilizing DCO within Pega ?
Direct Capture of Objectives is what DCO means when referring to Pega. Pega’s comprehensive solution,
the Pega Platform, is being utilized throughout the process of data acquisition, organization, and storage.
Gathering and arranging application artifacts is part of DCO, which covers the processes and technologies
used for this purpose. Teams working in information technology, business, and testing, as well as other
resources, make use of this technology so that they can save time, effort, and money while also enhancing
the overall quality of their projects and the impact they have on society.
DCO is neither a methodology nor a tool in and of itself. Instead, it is used to consolidate data so that it
may be utilized continuously across departments at the appropriate time and level. DCO also removes
barriers to communication by serving as a common repository for application artifacts that are linked to
one another (objectives, requirements, specifications, and implementation rules). All of the resources have
real-time documentation of their as-built state and a unified perspective of the application.
The Following Equipment Is Utilized By DCO In Order To Automate The Work :
Case Lifecycle Manager
Application profiler
Specification documents
Effort Estimation
New Application Wizard
Document generation
Advantages Of Utilizing DCO In Pega Are As Follows :
DCO is utilized to facilitate the modeling of scenarios that need to be addressed by the
application’s end users by collaborative teams.
Users are able to take a vital interim step after documenting the application but before
incurring the cost of development to determine whether or not the program satisfies our
objectives.
This is made possible by the modeling and simulation tools. When you solve problems as
part of the software development life cycle, there is a very small probability that those
solutions will fail when the software is put into production.
Additionally, organizations utilize iterative processes and DCO in order to better their
own efforts. It makes the process of developing software more apparent, which enables
teams to learn from their mistakes and continually get better.
DCO technologies provide businesses with a number of different delivery options for go-
live, which boosts their return on investment and makes it easier for them to achieve their
goals in a dependable manner.
Thus you have been presented with the most possible and frequently asked Pega interview questions with
answers. Hope it will be of great help to you to ace your interview and progress in your profession. Best
Wishes.
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.
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.
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.
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. 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.
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.
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.
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.
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.
1. Explain Pega briefly.
Ans:
Ans:
The “workplace” refers to the user interface where users interact with Pega
applications, managing tasks and cases.
The “studio” is the development environment where developers design and build
applications, creating the underlying processes and rules.
Ans:
In Pega, classes are blueprints for creating instances, representing data structures and
behaviors within an application. Classes define rules, properties, and relationships. There
are two primary types:
Rule Classes:
Data Classes:
Ans:
Ans:
A work item in Pega represents a unit of work or a specific task within a business
process.
It encapsulates data, processes, and rules related to a particular case or assignment.
Ans:
DCO is a methodology within Pega that facilitates the direct capture and documentation of
business requirements on the platform itself. This approach promotes collaboration
between business stakeholders and IT professionals, ensuring a shared understanding of
project objectives and requirements from the outset.
Ans:
Ans:
Ans:
Ans:
Ans:
A Decision Table in Pega is a rule type for defining complex business logic. It represents a
matrix where business rules can be expressed in a tabular format, making it easy to
visualize and manage conditions and corresponding actions. Decision Tables are commonly
used to automate decision-making processes in decision rules like Rule-Declare-
DecisionTable and Rule-Declare-DecisionTree.
12. What are the advantages of DCO in the context of Pega?
Ans:
Enhanced Collaboration
Faster Requirements Gathering
Better Project Outcomes
Reduced Development Time
Pega DCO
13. How does Pega handle case management, and what is a Case Type?
Ans:
Pega excels in case management through the concept of Case Types. A Case Type is a
blueprint that defines the structure, behavior, and processing of a specific type of case
within the application. It encompasses the data model, business rules, user interfaces, and
process flows associated with a particular business scenario.
Ans:
Ans:
A Harness acts as a container that holds and organizes Sections, Controls, and other UI
elements. It provides the structure for the layout and presentation of information on a
user’s screen. On the other hand, a Section represents a reusable and modular unit of UI
design that defines the layout and behavior of a specific part of a user interface.
16. What is the difference between a Rule and a Data class in Pega?
Ans:
Purpose Governs application behavior and processing Defines and organizes data structures.
Usage Used for implementing business logic Used for defining and managing data.
Examples Flow rules, decision rules, UI rules Data tables, data pages, data transforms
Inheritance Inherits from the Rule- base class hierarchy Inherits from the Data- base class hierarc
Ans:
Ans:
Ans:
Declarative Rules in Pega provide a mechanism for developers to define and express
business logic without specifying the exact procedural steps needed to achieve the desired
outcome. These rules declare the desired behavior, allowing Pega’s runtime engine to
generate and execute the necessary instructions automatically.
20. Explain the difference between a Declare Trigger and a Declare OnChange rule in
Pega.
Ans:
Ans:
The Pega Clipboard tool is a powerful debugging and diagnostic tool that provides real-time
visibility into the data associated with a case or rule execution. It allows developers and
administrators to inspect, modify, and analyze clipboard pages, which represent data
instances during runtime.
Ans:
Ans:
A Service Level Agreement (SLA) in Pega is a rule that defines the expected time to
complete a task or case.
Configuration involves specifying the SLA rule, defining the goal and deadline times,
and associating it with the relevant element in the application.
24. What is Pega’s App Studio, and how does it differ from Dev Studio?
Ans:
Pega’s App Studio is a low-code environment designed for business users to model and
modify applications. Dev Studio, on the other hand, is geared towards developers for in-
depth rule configuration and customization. App Studio offers a simplified interface for non-
technical users.
Ans:
26. What is the purpose of the Pega Business Intelligence Exchange (BIX)?
Ans:
The Pega Business Intelligence Exchange (BIX) is a specialized tool designed for extracting,
transforming, and loading (ETL) data from Pega applications into external data warehouses
or reporting systems. BIX enables organizations to leverage the data stored within Pega
applications for advanced reporting, analytics, and business intelligence purposes.
Ans:
A Decision Tree in Pega is a rule used to define branching logic based on a series of
questions and answers.
It is an effective tool for making decisions by systematically evaluating a set of
conditions and determining the appropriate outcome.
28. How does Pega support versioning of rules and applications?
Ans:
Pega has a powerful versioning mechanism for managing rules and apps throughout their
lifespan. Versioning helps developers to create, store, and maintain distinct versions of
rules, ensuring that changes can be traced and rolled back if required.
Ans:
Dynamic System Settings in Pega serve as a centralized repository for managing and
storing system-wide configuration settings.
These settings are stored as key-value pairs and can be accessed by various parts of
the application to retrieve configuration information during runtime.
Ans:
Pega Connectors serve as a bridge between Pega applications and external systems,
facilitating seamless integration. They enable the exchange of data and actions between
Pega and diverse systems, including databases, APIs, and enterprise applications.
31. What is a Data Page in Pega, and how is it different from a Clipboard Page?
Ans:
A Data Page is a reusable container for holding data fetched from an external source,
providing better performance and caching. It differs from a Clipboard Page, which is
temporary and holds data during runtime but is not inherently reusable.
32. What are Pega Activities, and how do they differ from Processes?
Ans:
Pega Activities are rules that define the specific steps and logic to be executed within
a business process.
While processes in Pega represent the overall flow and coordination of work,
activities focus on the granular details of what needs to happen within each step of
the process.
33. Describe Pega’s User Portal and its significance.
Ans:
Pega’s User Portal is a centralized and customizable interface that provides end-users with a
unified workspace to interact with Pega applications. It serves as the entry point for users to
access their tasks, cases, and relevant information.
The User Portal significantly enhances user experience by providing a single, intuitive
platform for users to view, manage, and complete their work. It consolidates relevant
information and tasks.
Ans:
Ans:
Support Mechanisms: Pega supports case resolution and closure through a combination of
predefined processes, business rules, and user interactions.
Automation: Automation rules, such as decision trees and decision tables, can be
employed to automate decision-making aspects of case resolution.
User Actions: Users interact with the system through the User Portal to perform actions
required for resolution.
Ans:
A Data Transform in Pega is a rule that defines the mapping and transformation of data
between different structures within the application. It is used to manipulate and convert
data from one format to another, facilitating seamless integration and efficient processing.
37. What is the purpose of Pega’s Pulse feature?
Ans:
Real-Time Collaboration
Contextual Communication
Transparent Work Environment
Audit Trail
Ans:
A Pega Flow Action is a rule representing a step within a business process or case in a Pega
application. It defines the user interface and processing logic for a specific task in a flow.
Flow Actions gather user input, make decisions, and update case data. They are crucial in
guiding users through a process and dynamically adapting the user interface based on the
case context.
Ans:
Try Shape: Encapsulates activities prone to errors within the Try shape.
Error Messages and Logging: Developers configure error messages and logging within the
Catch shape.
40. What is the purpose of Pega’s Declarative Network Viewer (DNV)?
Ans:
The Declarative Network Viewer (DNV) in Pega serves a critical role in enhancing the
development process by providing developers with a visual representation of the intricate
network of dependencies between rules. This tool allows for a comprehensive and intuitive
understanding of how various rules within the application interact with each other.
Ans:
The significance of Pega’s Guardrails lies in their role as guiding principles that steer
developers toward building high-quality, scalable, and maintainable applications.
Serving as a set of design standards and best practices, Guardrails act as a compass
throughout the development lifecycle.
Ans:
Pega Agents are integral components within the Pega platform designed to handle
background processing, offering a mechanism for executing tasks asynchronously. The
primary role of Pega Agents is to automate and optimize various background processes,
ensuring that tasks are performed efficiently without requiring immediate user interaction.
43. Describe Pega’s Integration Designer.
Ans:
Pega’s Integration Designer is a tool that allows developers to design, configure, and
manage integrations with external systems. It plays a crucial role in ensuring seamless
communication and data exchange between Pega applications and external services.
Ans:
Pega Express is a methodology within Pega that aims to accelerate application development
by emphasizing simplicity, speed, and collaboration. It provides a streamlined approach to
building Pega applications, catering to business users, citizen developers, and experienced
developers alike.
Ans:
Pega’s Change Sets are containers for packaging and deploying changes across
different environments.
They facilitate controlled and organized deployment of application changes, ensuring
consistency and minimizing risks associated with versioning.
46. What role does Pega’s Case Manager portal play in enhancing user productivity?
Ans:
Pega’s Case Manager portal is designed for users responsible for managing and overseeing
cases. It provides a consolidated view of cases, tasks, and relevant information, streamlining
the decision-making process and enhancing user productivity in overseeing case lifecycles.
47. What mechanisms are available for securing sensitive information?
Ans:
Ans:
Ans:
The Case Worker portal in Pega serves as a dedicated workspace designed to cater to users
actively involved in case management within an application. Its primary purpose is to
provide these users with a centralized and comprehensive interface where they can
efficiently handle, monitor, and resolve cases.
Ans:
Pega supports mobile application development through its specialized tool, Pega Mobile
Studio. This tool plays a pivotal role in creating responsive and adaptive mobile applications
within the Pega platform. Pega Mobile Studio provides developers with a set of intuitive and
visual tools to design, configure, and customize mobile interfaces.
51. How does Pega handle case linking between different cases?
Ans:
Pega facilitates case linking through the use of case references, offering a robust
mechanism for managing case dependencies and relationships.
The system allows developers and users to establish connections between different
cases based on predefined relationships.
Ans:
Ans:
Pega’s Customer Process Manager (CPM) is specifically designed to optimize and streamline
customer-centric processes within an application. The role of CPM is to provide tools and
features that empower businesses to deliver personalized and efficient customer
experiences across various touchpoints.
54. How does the Decision Data Store support data-driven decision-making?
Ans:
Decision data, such as outcomes from decision strategies or predictive models, can
be stored in DDS for later retrieval and analysis.
This centralized storage facilitates quick access to historical decision data, enabling
organizations to make informed decisions based on past outcomes.
55. Explain data pages within the context of Pega.
Ans:
Data pages in Pega are reusable containers for holding data from various sources. They
enhance performance by caching and sharing data across multiple users, reducing
redundant database queries. Data pages can be configured to load data on-demand or pre-
fetch, optimizing application responsiveness and ensuring efficient data management.
Ans:
Pega facilitates integration with external systems through the use of Connectors,
which are rule types designed to define communication channels.
The role of Connectors is to streamline data exchange and enhance interoperability
between Pega applications and external services or systems.
Ans:
Ans:
Ans:
Ans:
Declare Triggers in Pega are rules that automatically perform actions when specified
conditions are met or when the values of properties change. They are part of the declarative
processing framework, providing a way to trigger updates, calculations, or other actions in
response to changes in the system.
Ans:
Forward chaining involves evaluating conditions and executing actions proactively when
relevant data changes occur. In contrast, backward chaining occurs when the system
evaluates conditions and triggers actions only when needed, typically in response to user
queries or specific events.
Ans:
To construct a Declare Trigger in Pega, you define a Declare Trigger rule in the Pega
Designer Studio.
Specify the triggering conditions based on property changes and define the actions
or calculations to be executed when those conditions are met.
63. Explain the spinoff and split join shapes in the context of Pega.
Ans:
In Pega’s case management, the spinoff and split-join shapes are elements in the case life
cycle that define how processes branch or converge. The spinoff shape allows for the
creation of new, parallel processes, while the split-join shape manages the merging of
multiple parallel processes back into a single flow.
Ans:
Activity: In Pega, an Activity is a rule type used for defining sequences of instructions to
perform a specific task. It encapsulates business logic and is typically used in processes and
flows to automate tasks, invoke services, or manipulate data.
Utility: Utility rules in Pega serve as a container for shared functions or routines that are
reusable across the application. Unlike activities, utilities are not directly associated with a
specific task or process but provide a centralized location for commonly used functions,
promoting reusability and consistency.
65. Where will the assignments be kept in the Pega rules database?
Ans:
Assignments in Pega are stored in the ‘Assign-‘ class group within the Pega rules database.
This class group includes various classes like ‘Assign-Worklist,’ ‘Assign-WorkBasket,’ and
others, where different types of assignments are stored based on their states and locations.
Ans:
In Pega, work items are stored in the PegaRULES database—the PegaRULES relational
database stores various artifacts, including rules, data instances, and work items. Work
items represent cases or assignments in a Pega application and are managed within the
database for efficient retrieval and processing during the application lifecycle.
Ans:
StepStatusGood: This rule is used to define the success status of a step in a flow. It
determines the outcome when the step is executed successfully.
StepStatusFail: This rule defines the failure status of a step in a flow. It specifies the actions
to be taken if the step encounters an error or failure during execution.
Ans:
To send many correspondences at once in Pega, you can use the “Bulk Processing” feature.
This involves creating a Batch Request Processor (BRP) and configuring it to handle the bulk
processing of correspondence. The BRP can be scheduled to run at specified intervals and
process multiple correspondences efficiently.
69. What is the purpose of Pega’s UI Gallery, and how does it aid in UI development?
Ans:
Ans:
To make a rule or regulation a favorite for your manager in Pega, you can use the “Add to
Favorites” option available in the rule form. Managers can access their favorite rules easily
from their portal, improving accessibility to commonly used rules.
Ans:
Pega Express is a low-code approach in Pega for rapid application development. It differs
from traditional approaches by emphasizing visual design, drag-and-drop elements, and a
simplified development process, allowing business users to participate in application
creation actively.
Ans:
You can call a Pega Activity from JavaScript using the Pega JavaScript API. The
‘pega.api.doAction’ function can be utilized, passing the activity name and parameters as
arguments. This enables seamless integration between client-side interactions and server-
side processing.
Ans:
To import rules into Pega, you can use the Application Explorer in the Pega Designer
Studio.
Navigate to the “Application” menu, select “Distribution,” and then choose “Import.”
Follow the wizard to specify the source and details of the rules to be imported.
Ans:
The user’s ruleset list in Pega is generated based on the operator’s access roles, application
context, and rule resolution logic. Pega evaluates the operator’s access and privileges to
determine the applicable rulesets. The ruleset list defines the order in which rules are
searched during the rule resolution process, ensuring the correct rule versions are
accessed.
75. What are the critical components of Pega’s Integration Designer
Ans:
Connectors: Connectors in Pega’s Integration Designer are rule types designed to define
communication channels with external systems.
Service REST: Service REST rules enable the definition of Representational State Transfer
(REST) services within Pega.
Service SOAP: Service SOAP rules, on the other hand, define Simple Object Access Protocol
(SOAP) services.
Explore Pega Sample Resumes! Download & Edit, Get Noticed by Top Employers!
DOWNLOAD
Ans:
Pega Robotics, also known as Pega Robotic Process Automation (RPA), plays a pivotal role in
automating repetitive tasks across desktop applications. It leverages software robots or
“bots” to mimic human interactions with applications, performing tasks such as data entry,
form filling, and data extraction. This automation streamlines business processes, reduces
manual effort, and enhances operational efficiency.
77. What encryption mechanisms are available for protecting sensitive information?
Ans:
Field Value Encryption: Pega allows the encryption of specific fields within the database
using Field Value Encryption.
SSL/TLS Encryption: Pega supports the use of Secure Sockets Layer (SSL) and Transport
Layer Security (TLS) protocols for securing communication between clients and servers.
Ans:
Pega’s Predictive Analytics introduces advanced machine learning capabilities into Pega
applications, enhancing decision-making by leveraging predictive models. The primary
purpose of Predictive Analytics is to analyze historical data, identify patterns, and generate
predictions or insights that can be utilized to make informed decisions within the
application.
Ans:
Smart shapes in Pega’s case design are visual elements within a case life cycle that enables
dynamic and adaptive case management. These shapes represent nodes in the case
workflow, each serving a specific purpose and contributing to the overall flexibility and
responsiveness of the case.
Ans:
Pega provides a robust framework for data validation, ensuring the integrity and
consistency of data within the application. vv
Central to this framework are Declare Constraints, which play a crucial role in
defining and enforcing validation rules on properties.
Ans:
Ans:
Its purpose is to enable proactive monitoring, early detection of issues, and efficient
management of the Pega environment to ensure optimal performance and reliability.
Ans:
Pega’s Design Templates are pre-built, reusable design patterns that play a crucial role in
promoting consistency in application design. They provide a standardized approach to
designing user interfaces, ensuring a cohesive and professional look and feel across
different parts of the application.
84. List out the advantages of Pega’s Dynamic Case Management (DCM) approach.
Ans:
Ans:
Ans:
Pega’s ruleset and ruleset versioning features enable the implementation of user-specific
rules and configurations in a structured and controlled manner. A ruleset is a logical
container for rules, and ruleset versioning allows for the creation and management of
different versions of a ruleset.
Ans:
Pega’s Case Lifecycle represents the end-to-end journey of a work item, guiding its
progression through various stages from initiation to resolution. It is a visual representation
of the flow that work items follow as they move through the system. The Case Lifecycle in
Pega includes stages, steps, and processes, each defining specific actions, conditions, and
milestones.
88. How does Pega facilitate the implementation of user-specific rules?
Ans:
Pega’s ruleset and ruleset versioning features enable the implementation of user-
specific rules and configurations in a structured and controlled manner.
A ruleset is a logical container for rules, and ruleset versioning allows for the creation
and management of different versions of a ruleset.
Ans:
Optimistic Locking
Pessimistic Locking
Record Locking
Field-Level Locking
Ans:
Pega’s Declare Index is a feature that improves database query speed on the Pega platform.
It permits building indexes on certain class attributes, improving data retrieval and query
performance. Declare Index effectively organizes data by declaring indexed characteristics,
conditions, and refresh techniques, lowering the total database load.
1. Explain Pega briefly.
Ans:
Ans:
The “workplace” refers to the user interface where users interact with Pega
applications, managing tasks and cases.
The “studio” is the development environment where developers design and build
applications, creating the underlying processes and rules.
Ans:
In Pega, classes are blueprints for creating instances, representing data structures and
behaviors within an application. Classes define rules, properties, and relationships. There
are two primary types:
Rule Classes:
Data Classes:
Ans:
Ans:
A work item in Pega represents a unit of work or a specific task within a business
process.
It encapsulates data, processes, and rules related to a particular case or assignment.
Ans:
DCO is a methodology within Pega that facilitates the direct capture and documentation of
business requirements on the platform itself. This approach promotes collaboration
between business stakeholders and IT professionals, ensuring a shared understanding of
project objectives and requirements from the outset.
Ans:
Ans:
Ans:
Ans:
Ans:
A Decision Table in Pega is a rule type for defining complex business logic. It represents a
matrix where business rules can be expressed in a tabular format, making it easy to
visualize and manage conditions and corresponding actions. Decision Tables are commonly
used to automate decision-making processes in decision rules like Rule-Declare-
DecisionTable and Rule-Declare-DecisionTree.
12. What are the advantages of DCO in the context of Pega?
Ans:
Enhanced Collaboration
Faster Requirements Gathering
Better Project Outcomes
Reduced Development Time
Pega DCO
13. How does Pega handle case management, and what is a Case Type?
Ans:
Pega excels in case management through the concept of Case Types. A Case Type is a
blueprint that defines the structure, behavior, and processing of a specific type of case
within the application. It encompasses the data model, business rules, user interfaces, and
process flows associated with a particular business scenario.
Ans:
Ans:
A Harness acts as a container that holds and organizes Sections, Controls, and other UI
elements. It provides the structure for the layout and presentation of information on a
user’s screen. On the other hand, a Section represents a reusable and modular unit of UI
design that defines the layout and behavior of a specific part of a user interface.
16. What is the difference between a Rule and a Data class in Pega?
Ans:
Purpose Governs application behavior and processing Defines and organizes data structures.
Usage Used for implementing business logic Used for defining and managing data.
Examples Flow rules, decision rules, UI rules Data tables, data pages, data transforms
Inheritance Inherits from the Rule- base class hierarchy Inherits from the Data- base class hierarc
Ans:
Ans:
Ans:
Declarative Rules in Pega provide a mechanism for developers to define and express
business logic without specifying the exact procedural steps needed to achieve the desired
outcome. These rules declare the desired behavior, allowing Pega’s runtime engine to
generate and execute the necessary instructions automatically.
20. Explain the difference between a Declare Trigger and a Declare OnChange rule in
Pega.
Ans:
Ans:
The Pega Clipboard tool is a powerful debugging and diagnostic tool that provides real-time
visibility into the data associated with a case or rule execution. It allows developers and
administrators to inspect, modify, and analyze clipboard pages, which represent data
instances during runtime.
Ans:
Ans:
A Service Level Agreement (SLA) in Pega is a rule that defines the expected time to
complete a task or case.
Configuration involves specifying the SLA rule, defining the goal and deadline times,
and associating it with the relevant element in the application.
24. What is Pega’s App Studio, and how does it differ from Dev Studio?
Ans:
Pega’s App Studio is a low-code environment designed for business users to model and
modify applications. Dev Studio, on the other hand, is geared towards developers for in-
depth rule configuration and customization. App Studio offers a simplified interface for non-
technical users.
Ans:
26. What is the purpose of the Pega Business Intelligence Exchange (BIX)?
Ans:
The Pega Business Intelligence Exchange (BIX) is a specialized tool designed for extracting,
transforming, and loading (ETL) data from Pega applications into external data warehouses
or reporting systems. BIX enables organizations to leverage the data stored within Pega
applications for advanced reporting, analytics, and business intelligence purposes.
Ans:
A Decision Tree in Pega is a rule used to define branching logic based on a series of
questions and answers.
It is an effective tool for making decisions by systematically evaluating a set of
conditions and determining the appropriate outcome.
28. How does Pega support versioning of rules and applications?
Ans:
Pega has a powerful versioning mechanism for managing rules and apps throughout their
lifespan. Versioning helps developers to create, store, and maintain distinct versions of
rules, ensuring that changes can be traced and rolled back if required.
Ans:
Dynamic System Settings in Pega serve as a centralized repository for managing and
storing system-wide configuration settings.
These settings are stored as key-value pairs and can be accessed by various parts of
the application to retrieve configuration information during runtime.
Ans:
Pega Connectors serve as a bridge between Pega applications and external systems,
facilitating seamless integration. They enable the exchange of data and actions between
Pega and diverse systems, including databases, APIs, and enterprise applications.
31. What is a Data Page in Pega, and how is it different from a Clipboard Page?
Ans:
A Data Page is a reusable container for holding data fetched from an external source,
providing better performance and caching. It differs from a Clipboard Page, which is
temporary and holds data during runtime but is not inherently reusable.
32. What are Pega Activities, and how do they differ from Processes?
Ans:
Pega Activities are rules that define the specific steps and logic to be executed within
a business process.
While processes in Pega represent the overall flow and coordination of work,
activities focus on the granular details of what needs to happen within each step of
the process.
33. Describe Pega’s User Portal and its significance.
Ans:
Pega’s User Portal is a centralized and customizable interface that provides end-users with a
unified workspace to interact with Pega applications. It serves as the entry point for users to
access their tasks, cases, and relevant information.
The User Portal significantly enhances user experience by providing a single, intuitive
platform for users to view, manage, and complete their work. It consolidates relevant
information and tasks.
Ans:
Ans:
Support Mechanisms: Pega supports case resolution and closure through a combination of
predefined processes, business rules, and user interactions.
Automation: Automation rules, such as decision trees and decision tables, can be
employed to automate decision-making aspects of case resolution.
User Actions: Users interact with the system through the User Portal to perform actions
required for resolution.
Ans:
A Data Transform in Pega is a rule that defines the mapping and transformation of data
between different structures within the application. It is used to manipulate and convert
data from one format to another, facilitating seamless integration and efficient processing.
37. What is the purpose of Pega’s Pulse feature?
Ans:
Real-Time Collaboration
Contextual Communication
Transparent Work Environment
Audit Trail
Ans:
A Pega Flow Action is a rule representing a step within a business process or case in a Pega
application. It defines the user interface and processing logic for a specific task in a flow.
Flow Actions gather user input, make decisions, and update case data. They are crucial in
guiding users through a process and dynamically adapting the user interface based on the
case context.
Ans:
Try Shape: Encapsulates activities prone to errors within the Try shape.
Error Messages and Logging: Developers configure error messages and logging within the
Catch shape.
40. What is the purpose of Pega’s Declarative Network Viewer (DNV)?
Ans:
The Declarative Network Viewer (DNV) in Pega serves a critical role in enhancing the
development process by providing developers with a visual representation of the intricate
network of dependencies between rules. This tool allows for a comprehensive and intuitive
understanding of how various rules within the application interact with each other.
Ans:
The significance of Pega’s Guardrails lies in their role as guiding principles that steer
developers toward building high-quality, scalable, and maintainable applications.
Serving as a set of design standards and best practices, Guardrails act as a compass
throughout the development lifecycle.
Ans:
Pega Agents are integral components within the Pega platform designed to handle
background processing, offering a mechanism for executing tasks asynchronously. The
primary role of Pega Agents is to automate and optimize various background processes,
ensuring that tasks are performed efficiently without requiring immediate user interaction.
43. Describe Pega’s Integration Designer.
Ans:
Pega’s Integration Designer is a tool that allows developers to design, configure, and
manage integrations with external systems. It plays a crucial role in ensuring seamless
communication and data exchange between Pega applications and external services.
Ans:
Pega Express is a methodology within Pega that aims to accelerate application development
by emphasizing simplicity, speed, and collaboration. It provides a streamlined approach to
building Pega applications, catering to business users, citizen developers, and experienced
developers alike.
Ans:
Pega’s Change Sets are containers for packaging and deploying changes across
different environments.
They facilitate controlled and organized deployment of application changes, ensuring
consistency and minimizing risks associated with versioning.
46. What role does Pega’s Case Manager portal play in enhancing user productivity?
Ans:
Pega’s Case Manager portal is designed for users responsible for managing and overseeing
cases. It provides a consolidated view of cases, tasks, and relevant information, streamlining
the decision-making process and enhancing user productivity in overseeing case lifecycles.
Ans:
Ans:
Ans:
The Case Worker portal in Pega serves as a dedicated workspace designed to cater to users
actively involved in case management within an application. Its primary purpose is to
provide these users with a centralized and comprehensive interface where they can
efficiently handle, monitor, and resolve cases.
Ans:
Pega supports mobile application development through its specialized tool, Pega Mobile
Studio. This tool plays a pivotal role in creating responsive and adaptive mobile applications
within the Pega platform. Pega Mobile Studio provides developers with a set of intuitive and
visual tools to design, configure, and customize mobile interfaces.
51. How does Pega handle case linking between different cases?
Ans:
Pega facilitates case linking through the use of case references, offering a robust
mechanism for managing case dependencies and relationships.
The system allows developers and users to establish connections between different
cases based on predefined relationships.
Ans:
Ans:
Pega’s Customer Process Manager (CPM) is specifically designed to optimize and streamline
customer-centric processes within an application. The role of CPM is to provide tools and
features that empower businesses to deliver personalized and efficient customer
experiences across various touchpoints.
54. How does the Decision Data Store support data-driven decision-making?
Ans:
Decision data, such as outcomes from decision strategies or predictive models, can
be stored in DDS for later retrieval and analysis.
This centralized storage facilitates quick access to historical decision data, enabling
organizations to make informed decisions based on past outcomes.
Ans:
Data pages in Pega are reusable containers for holding data from various sources. They
enhance performance by caching and sharing data across multiple users, reducing
redundant database queries. Data pages can be configured to load data on-demand or pre-
fetch, optimizing application responsiveness and ensuring efficient data management.
Ans:
Pega facilitates integration with external systems through the use of Connectors,
which are rule types designed to define communication channels.
The role of Connectors is to streamline data exchange and enhance interoperability
between Pega applications and external services or systems.
Ans:
Ans:
Ans:
Ans:
Declare Triggers in Pega are rules that automatically perform actions when specified
conditions are met or when the values of properties change. They are part of the declarative
processing framework, providing a way to trigger updates, calculations, or other actions in
response to changes in the system.
Get Ce
Ans:
Forward chaining involves evaluating conditions and executing actions proactively when
relevant data changes occur. In contrast, backward chaining occurs when the system
evaluates conditions and triggers actions only when needed, typically in response to user
queries or specific events.
Ans:
To construct a Declare Trigger in Pega, you define a Declare Trigger rule in the Pega
Designer Studio.
Specify the triggering conditions based on property changes and define the actions
or calculations to be executed when those conditions are met.
63. Explain the spinoff and split join shapes in the context of Pega.
Ans:
In Pega’s case management, the spinoff and split-join shapes are elements in the case life
cycle that define how processes branch or converge. The spinoff shape allows for the
creation of new, parallel processes, while the split-join shape manages the merging of
multiple parallel processes back into a single flow.
Ans:
Activity: In Pega, an Activity is a rule type used for defining sequences of instructions to
perform a specific task. It encapsulates business logic and is typically used in processes and
flows to automate tasks, invoke services, or manipulate data.
Utility: Utility rules in Pega serve as a container for shared functions or routines that are
reusable across the application. Unlike activities, utilities are not directly associated with a
specific task or process but provide a centralized location for commonly used functions,
promoting reusability and consistency.
65. Where will the assignments be kept in the Pega rules database?
Ans:
Assignments in Pega are stored in the ‘Assign-‘ class group within the Pega rules database.
This class group includes various classes like ‘Assign-Worklist,’ ‘Assign-WorkBasket,’ and
others, where different types of assignments are stored based on their states and locations.
Ans:
In Pega, work items are stored in the PegaRULES database—the PegaRULES relational
database stores various artifacts, including rules, data instances, and work items. Work
items represent cases or assignments in a Pega application and are managed within the
database for efficient retrieval and processing during the application lifecycle.
Ans:
StepStatusGood: This rule is used to define the success status of a step in a flow. It
determines the outcome when the step is executed successfully.
StepStatusFail: This rule defines the failure status of a step in a flow. It specifies the actions
to be taken if the step encounters an error or failure during execution.
Ans:
To send many correspondences at once in Pega, you can use the “Bulk Processing” feature.
This involves creating a Batch Request Processor (BRP) and configuring it to handle the bulk
processing of correspondence. The BRP can be scheduled to run at specified intervals and
process multiple correspondences efficiently.
69. What is the purpose of Pega’s UI Gallery, and how does it aid in UI development?
Ans:
Ans:
To make a rule or regulation a favorite for your manager in Pega, you can use the “Add to
Favorites” option available in the rule form. Managers can access their favorite rules easily
from their portal, improving accessibility to commonly used rules.
Ans:
Pega Express is a low-code approach in Pega for rapid application development. It differs
from traditional approaches by emphasizing visual design, drag-and-drop elements, and a
simplified development process, allowing business users to participate in application
creation actively.
Ans:
You can call a Pega Activity from JavaScript using the Pega JavaScript API. The
‘pega.api.doAction’ function can be utilized, passing the activity name and parameters as
arguments. This enables seamless integration between client-side interactions and server-
side processing.
Ans:
To import rules into Pega, you can use the Application Explorer in the Pega Designer
Studio.
Navigate to the “Application” menu, select “Distribution,” and then choose “Import.”
Follow the wizard to specify the source and details of the rules to be imported.
Ans:
The user’s ruleset list in Pega is generated based on the operator’s access roles, application
context, and rule resolution logic. Pega evaluates the operator’s access and privileges to
determine the applicable rulesets. The ruleset list defines the order in which rules are
searched during the rule resolution process, ensuring the correct rule versions are
accessed.
75. What are the critical components of Pega’s Integration Designer
Ans:
Connectors: Connectors in Pega’s Integration Designer are rule types designed to define
communication channels with external systems.
Service REST: Service REST rules enable the definition of Representational State Transfer
(REST) services within Pega.
Service SOAP: Service SOAP rules, on the other hand, define Simple Object Access Protocol
(SOAP) services.
Explore Pega Sample Resumes! Download & Edit, Get Noticed by Top Employers!
DOWNLOAD
Ans:
Pega Robotics, also known as Pega Robotic Process Automation (RPA), plays a pivotal role in
automating repetitive tasks across desktop applications. It leverages software robots or
“bots” to mimic human interactions with applications, performing tasks such as data entry,
form filling, and data extraction. This automation streamlines business processes, reduces
manual effort, and enhances operational efficiency.
77. What encryption mechanisms are available for protecting sensitive information?
Ans:
Field Value Encryption: Pega allows the encryption of specific fields within the database
using Field Value Encryption.
SSL/TLS Encryption: Pega supports the use of Secure Sockets Layer (SSL) and Transport
Layer Security (TLS) protocols for securing communication between clients and servers.
78. Describe the purpose of Pega’s Predictive Analytics.
Ans:
Pega’s Predictive Analytics introduces advanced machine learning capabilities into Pega
applications, enhancing decision-making by leveraging predictive models. The primary
purpose of Predictive Analytics is to analyze historical data, identify patterns, and generate
predictions or insights that can be utilized to make informed decisions within the
application.
Ans:
Smart shapes in Pega’s case design are visual elements within a case life cycle that enables
dynamic and adaptive case management. These shapes represent nodes in the case
workflow, each serving a specific purpose and contributing to the overall flexibility and
responsiveness of the case.
Ans:
Pega provides a robust framework for data validation, ensuring the integrity and
consistency of data within the application. vv
Central to this framework are Declare Constraints, which play a crucial role in
defining and enforcing validation rules on properties.
Ans:
Ans:
Its purpose is to enable proactive monitoring, early detection of issues, and efficient
management of the Pega environment to ensure optimal performance and reliability.
Ans:
Pega’s Design Templates are pre-built, reusable design patterns that play a crucial role in
promoting consistency in application design. They provide a standardized approach to
designing user interfaces, ensuring a cohesive and professional look and feel across
different parts of the application.
84. List out the advantages of Pega’s Dynamic Case Management (DCM) approach.
Ans:
Ans:
Ans:
Pega’s ruleset and ruleset versioning features enable the implementation of user-specific
rules and configurations in a structured and controlled manner. A ruleset is a logical
container for rules, and ruleset versioning allows for the creation and management of
different versions of a ruleset.
Ans:
Pega’s Case Lifecycle represents the end-to-end journey of a work item, guiding its
progression through various stages from initiation to resolution. It is a visual representation
of the flow that work items follow as they move through the system. The Case Lifecycle in
Pega includes stages, steps, and processes, each defining specific actions, conditions, and
milestones.
Ans:
Pega’s ruleset and ruleset versioning features enable the implementation of user-
specific rules and configurations in a structured and controlled manner.
A ruleset is a logical container for rules, and ruleset versioning allows for the creation
and management of different versions of a ruleset.
Ans:
Optimistic Locking
Pessimistic Locking
Record Locking
Field-Level Locking
90. What does Pega’s Declare Index stand for?
Ans:
Pega’s Declare Index is a feature that improves database query speed on the Pega platform.
It permits building indexes on certain class attributes, improving data retrieval and query
performance. Declare Index effectively organizes data by declaring indexed characteristics,
conditions, and refresh techniques, lowering the total database load.
pr_operators table.
It will be used for provide the access for external users(end users) to
accessing the application. For example End-users will not direct accessing
to the pega application, Suppose they want to access to the pega
application through interfacing with third party tool.
Only one access group at a time , but one operator will have multiple
access group in their operator id instance.
@baseclass is Ultimate base class, And Its Child Classes are work-, Data-,
Rule-, Assign-, History-, etc.
Pega always Support 2 types of classe which are Abstract Classes And
Concrete Classes
Abstract Classes are ends with ‘-‘ and abstract Classes cannot create any
work object instances
Concrete Classes will Does not ends with -, And Abstract Classes will
create Workobject instances
7 steps
Defer load means, suppose u can use any tabbed Section in that situation
u want to load the data on each tab u can write one activity to retrieving
data, then large amount of data will be loaded in clipboard, Its an
performance hit load the more data in clipboard, So in that situation we can
use Defer load option it will prevent performance because while u Check
the Defer load option it will ask some activity on each tab Cell properties,
so when ever the particular tab is opened then relevant activity only will be
fired and load the related data…So it will Avoid the performance Yes we
can load the values in dropdown
9) How many types of portals does PRPC can provide? Where will you
specify the portals that u have created?
After creating a portal it will specified in the Access group Settings tab, then
it will access to the particular user.
we can specify the privileges or when conditions in Security tab of the flow
action
By using the modified Data base schema or optimise for reporting option
Optimise reporting means right click on the property and select the optimise
for reporting
Suppose u can specify the entry point checkbox in the assignment that
shape allows as a start point in the flow.. means for which assignment
shapes u can check this checkbox that assignments only display in the
output, then u can use the breadcrumbs and navigate any screen.
16) What are all the different types of scope that declare scope
provide ?
The main Advantage of the Declare pages is, It prevents the multiple DB
hits , Suppose is there multiple requestors in that node when ever first user
login into the application then load activity will be fired and create a declare
page and then loaded the data in that page, requestors who can on that
node will show this declare page and use the data on that page.
The Disadvantages are its read only to the requestors, and can not add the
additional data and cannt delete the specific data.
18) Diff b/w declare page and regular pages ?
User pages are created through page new method in an activity, these
pages can be updated, deleted directly, these pages automatically deleted
once logout from the system.
Summary view rules support interactive charts, trend reports, and the use
of AJAX for pop-up Smart Info windows.
Use the Report wizard to define list view reports and link them to our portal.
To divide the ListView in to different pages and set the number of records
to be displayed in a page.
5. The resulting List of Classes window displays the number of rows in the
table, the number of columns in the table and a list of the classes assigned
to that table. The Properties Set to Be Visible value counts the properties
for which the Column Inclusion value is Required or Recommended. This
Column Inclusion value is advisory, and does not indicate whether the
property is exposed — corresponds to a column. The Count column shows
the total count of properties in this class plus those its parent classes.
6. To see the columns currently defined in this table, click the numeric link
labeled Number of columns in this table.
7. The List of Database Columns window shows the column name, column
data type, and column width in bytes for each column in the table.
28. How to expose aggregate property?
2. Create Single Value properties in the new class to hold values of the
embedded values.
But we can’t refer the property without exposing in Critera fields of the
Content tab.
30. What is the activity responsible for getting the data in List View?
getContent Activity
Embed-ListParams class.
Yes
33. How to customize the getContent Activity?
Step1: Create Activity in Our Class and create the New page
Step5: create the parameter. This parameter get the sql query from
previous activity
Get the page from pyContentPage if page already exists. If page is not
available it creates the new ContentPage.
In this code get the sql query from the above parameter and pass this
query and above created ContentPage as parameters to this
tools.getDatabase().executeRDB(query, pagename) method.
34. How do we get the data from the two different tables?
35. How do we fetch the data from two different tables with out using
two different tables?
Write a database View. In this view logically combine the Two different
tables.
Write the List View. Applies to class is class of the Combined table. So we
can refer the properties of both the tables in list view.
36. What is the use of HTML property in ListView?
HTML Property rules appear in list view and summary view rules to define
the appearance of values in reports.
37. Consider this scenario: I need to generate a list view report of all
the work objects created on a particular date and then I need to
include this list view in a section. How this can be done?
List view is generally used for complex queries where sorting is required
and also we can retrieve less information using Paging.
39. Explain in brief the configuration of a list view?
- Applies to class of list view will be taken as the database table map for the
search criteria.
- Display fields tab is used to depict the fields that are displayed along with
category and to enable/disable sorting
- Format tab is used to depict the formatting of the list (like even/odd
coloring) and details on single click etc.
A list view can be used for complex retrievals from database by not
specifying the display, format and Organize tabl.
Summary views are used to create reports which are grouped by certain
criteria and can be later drilled down.
- Applies to class of summary view will be taken as the database table map
for the search criteria
- Category is used to know under which tab the report should come.
- Criteria is used in the where class (this can be asked to user by enabling
prompt user)
- Group by and field functions (like count) are used for initial display. If we
have more than one group by
- Drill down fields are used to display the fields when we click on the
assignment.
- Format is used to tell how to format the display and charts can also be
used.
By default, the Agent Manager checks for new or updated agents rule once
every ten minutes.
After we create an agents rule, the Agent Manager generates one Agent
Schedule instance for each node running on your Process Commander
system the next time it checks for new agents rules.
No
46. What are the Agent running time intervals?
Periodic — The agent runs the activity and then "sleeps" for the number of
seconds entered in the Interval column.
Queue mode indicates whether the agent uses the agent queue capability
to process items from the agent queue. This feature allows the agent to
temporarily skip over items that fail — for example, because a needed
resource is locked — and try again later to process the item later.
Legacy — specifies that this is an agent that was created in a version prior
to V5.4 and has not yet been updated. This option is not available for
agents created in V5.4 or later.
Agent activity calls another activity. This called activity may not appear in
agent rule set. So setup of the Rule set list and Roles by providing Access
group in security Tab.
Select the access group to use for the legacy and advanced agents listed
in this rule. This field is ignored for agents with a type of Standard.
49. How do we Troubleshoot or Trace an Agent?
Verify above tag in prconfig file. Value of the above tag is true or false.
2. In Agent Schedule, schedule tab verify the check box Enable this agent
is Checked or Not. And also verify the Enabled? Check box is checked or
Not.
Agent runs on different nodes, select the particular node and run the
Tracer.
The Agent Manager is a master agent that gathers and caches the agent
configuration information set for our system when Process Commander
starts. Then, at a regularly scheduled interval, it determines whether any
new agents rules were created during the last period. If there are new
agents rules, the Agent Manager adds them to its list of agents and
generates agent schedule data instances for them for each node.
our system includes three standard agents rules. Because these agents
rules are in locked RuleSets, we cannot modify them. To change the
configuration settings for the agents listed in these rules, update the agent
schedules generated from the agents rule.
Pega-IntSvcs,
System Cleaner
System Pulse
When you need to modify the behavior of an agent listed in an agents rule
in a locked RuleSet (any of the standard Process Commander agents
rules, for example) you do so by editing one or more of the generated
The goal time is the smallest time interval, the deadline time is a longer
interval, and the late interval defines post-deadline times. Each time
interval is in days, hours, minutes, and seconds.
54. What are the types of SLA? Where they can be defined?
For the overall work object, the service level rule is identified in the
standard property .pySLAName, typically set up through a model for the
class. (The default value is the Default service level.)
55. How do we do Escalation?
Escalation can occur through a service level rule associated with the flow
and through background processing by the Pega-ProCom agent.
56. What are SLA's, how are they different from Agents?
level can define a goal and a deadline times for processing an assignment,
and can
execute activities if the goal or the deadline is not met. This assignment-
level service
level is distinct from any service level associated with the entire flow.
against the goal and deadline times computed from the service level rule)
starts when the
SLA’s are always associated with an assignment. Just drag a SLA shape
and provide an instance of Rule-Obj-ServiceLevel.
Yes, SLA can be defined for the entire workobject by defining it in the
model.
By using privileges and when conditions under process tab of the flow
instance.
A flow action rule controls how users interact with work object forms to
complete assignments.
A local flow action permits users at runtime to update, but not complete, an
assignment. Local flow actions always are optional. Users may perform
none, one, or multiple local flow actions, or repeat a local flow action
multiple times.
At runtime, the system runs this activity before it does other processing for
this flow action. This activity is not visible on the Visio flow diagram. This
activity executes only once, the first time a user selects this flow action for
this assignment.
For screen flow rules By default, when this flow action appears as a step in
a screen flow rule, and the user at runtime clicks away to a different step in
the screen flow rule, this activity rule does not run. To cause this activity to
execute when the user clicks away to a different step, select the Post
Action on Click Away? check box on the Assignment shape properties
panel.
A local flow action permits users at runtime to update, but not complete, an
assignment. Like connector flow actions, local flow actions are referenced
inside an assignment task in a flow.
Local flow actions always are optional. Users may perform none, one, or
multiple local flow actions, or repeat a local flow action multiple times.
On the Action tab of the Flow Action form, we can mark a flow action rule
as local, or connector, or both.
62. How Rule-Edit-Validate is different from Rule-Obj-Validate?
Dynamic Select is a drop down from which we can only select a value.
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.
Use HTML Property rules to control how properties appear on work object
forms, correspondence, and other HTML forms, for both display and for
accepting user input.
HTML Property rules also may appear in list view and summary view rules
to define the appearance of values in reports, and in harness, section, and
flow action rules that define work object forms.
These three prefixes are reserved. We cannot create new properties with
such names. We can override these standard properties with a custom
property of the same name (without changing the mode or Type).
Px: Identifies properties that are special, meaning that the values cannot be
input by user input on an HTML form.
Py: Properties with names that start with py are not special, meaning that
values can be input by users on an HTML form.
Pz: Properties with names that start with pz support internal system
processing. Users cannot directly manipulate pz properties. our application
may examine these values, but do not set them. The meaning of values
may change with new product releases.
Validation rule is used to validate the value against the some other value.
Once the validation fails the system add error message to that field in
clipboard.
Note: I think Obj-Validate is used for Server Side Validation and Edit-
Validate is used for Client Side Validation.
71. How do you add custom message to the Property when it fails
the Validation.
Use the Activity-End method to cause the system to End the current activity
and all calling activities.
Ex:if Alpha calls Beta, which calls Gamma, which calls Delta, which
performs the Activity-End method, all four activities are ended.
The Exit-Activity method ends the current activity and returns control to the
calling activity.
The Page-New method is used to create a page on the clipboard. The new
page may be a top-level page or an embedded page.
We can identify a model to initialize the newly created page. The model can
set values for one or more properties.
77. Explain about Page-Remove method?
The Call instruction calls the another specified activity and execute it. When
that activity completes, control returns to the calling activity.
Use the Branch instruction to find another specified activity and branch to it
without a return.
When the branched activity ends, processing of the current activity also
ends.
This method creates one embedded page for each instance retrieved.
Obj-Browse method is used to search instances of one class and copy the
entire instances, or specified properties, to the clipboard as an array of
embedded pages.
The system uses rule resolution to find the list view rule and executes it,
but does not produce any HTML output display.
The system uses the specified class and key fields to find and open the
object and place its data into the specified step page. The system searches
up the class hierarchy as appropriate to find the instance. If it finds the
specified step page, the system clears any data that is on it and reuses the
page. If no existing page has a name matching the specified step page, the
system creates a new page.
The Obj-Delete method uses the class of the page to obtain the appropriate
Rule-Obj-Class instance. It uses the table name, key fields, and other
aspects of the class rule to mark the instance for deletion.
The Obj-Save method uses properties on the page to derive the internal
key under which it will be saved.
We cannot save a page that our session does not hold a lock on (if the
page belongs to a lockable class), unless the object is new, never yet
saved.
We cannot save pages of any class derived from the Code- base class or
the Embed- base class. Such pages exist only on the clipboard.
A validate rule (Rule-Obj-Validate rule type) can call edit validate rules
(Rule-Edit-Validate rule type).
97. Explain about Obj-Sort method?
Obj-Sort method is used to sort the clipboard pages that are the values of a
property of mode Page List.
We can specify one or more properties to sort on, and whether the sort
sequence is ascending or descending for each sort level.
Use Connect SQL rules and RDB methods only with an external database.
Do not use Connect SQL rules or RDB methods for the PegaRULES
database(s). Because not all properties in the PegaRULES databases are
distinct database columns, use the Obj-Open and Obj-Save methods, not
the RDB- methods, with the PegaRULES database to prevent loss of data.
This method references a Connect SQL rule instance, and executes SQL
statements stored in the Browse tab of that rule instance. The search can
do anything we can specify in a SQL statement, such as a SELECT
WHEREstatement. Any constraints on the returned data are in the SQL.
Use this method in conjunction with a Connect SQL rule that contains
SQLSELECT or EXECUTE statements in the Open tab. Define the SQL
statements so that the database returns exactly one row.
100. Explain about RDB-Save method?
This method operates in conjunction with a Connect SQL rule that contains
SQL statements such as INSERT, UPDATE, and CREATE statements on
the Save tab.
Can you explain key concepts of PRPC and how they work together to build a process-driven
application?
How do you design and implement business rules and decision tables in Pega?
In Pega’s PRPC framework, business rules and decision tables are used to define the behavior
of the application and automate decision-making.
Designing business rules in PRPC involves creating a rule hierarchy and defining the
conditions, actions, and exceptions for each rule. The rule hierarchy is a hierarchical structure
that organizes rules into a logical structure, with higher-level rules providing context for
lower-level rules.
To create a business rule in PRPC, you can use the Rule Designer, which is a visual tool that
allows you to create, edit, and manage rules. You can create different types of rules, such as
decision rules, data transform rules, and more.
Decision tables are used to define complex decision-making logic in a clear and easy-to-
understand format. In PRPC, decision tables are created using the Decision Table Rule form.
You can create a decision table by defining the conditions, actions, and exceptions in a
tabular format.
Can you walk me through a recent Pega project you led, including the challenges you faced and how
you overcame them?
the project was to build a process-driven application for a retail company to manage their
inventory and customer orders. The project would involve creating process flows, business
rules, and decision tables to automate the inventory management and customer order
processes.
Some of the challenges that may have been faced during the project include:
Complex business requirements: The retail company may have had complex business
requirements that required a large number of rules and decision tables to be created.
Integration with other systems: The application may have needed to integrate with other
systems such as a warehouse management system or a customer relationship management
system.
Data validation and security: The application may have needed to ensure that data was
validated and secure, to protect sensitive customer and inventory information.
To overcome these challenges, the following steps could have been taken:
Break down the complex business requirements into smaller, manageable tasks.
Use Pega’s integration capabilities to connect the application to other systems.
Use Pega’s built-in security features to validate and secure data.
Create a detailed test plan and conduct thorough testing to ensure that the application was
working as expected.
Continuously review and monitor the application’s performance and make any necessary
improvements.
By taking these steps, the project team could have successfully built a process-driven
application that automates the inventory management and customer order processes for the
retail company.
In Pega’s PRPC framework, data validation and error handling are achieved through the use
of rules and data transforms.
Data validation rules are used to ensure that the data entered into the application is in the
correct format and meets the business requirements. PRPC provides built-in data validation
capabilities, such as the use of regular expressions to validate data, as well as the ability to
create custom validation rules.
To handle data validation, you can create a data validation rule and map it to the field or
property that you want to validate. The validation rule will be triggered when the user
submits the form and will check the data against the validation criteria you have defined. If
the data is invalid, the rule will return an error message and prevent the form from being
submitted.
Error handling in PRPC is the process of catching and responding to exceptions or errors that
occur during the execution of the application. PRPC provides built-in error handling
capabilities, such as the ability to catch and handle exceptions, as well as the ability to create
custom error handlers.
To handle errors, you can create an error handler rule and map it to the process or flow where
you want to catch the error. The error handler rule will be triggered when an exception occurs
and will handle the exception based on the criteria you have defined. For example, you can
use the error handler to redirect the user to a different page, display an error message, or log
the error.
Overall, PRPC provides a flexible and powerful set of tools for data validation and error
handling, allowing developers to ensure that the application is functioning as expected and
providing a good user experience.
Can you explain how you use Pega’s built-in reporting and analytics features?
Pega’s PRPC framework provides built-in reporting and analytics features that allow you to
create, view, and analyze data within the application. Some of the key features include:
1. Reports: PRPC provides a built-in reporting engine that allows you to create and view reports
on various aspects of the application. Reports can be created using a drag-and-drop
interface, making it easy to create complex reports without any coding. Reports can be
viewed in different formats, such as tabular, chart, and map, and can be exported to different
formats, such as PDF, Excel, and CSV.
2. Dashboards: PRPC provides a dashboard feature that allows you to create customized
dashboards to view and analyze data. Dashboards can be created using a drag-and-drop
interface, making it easy to create and customize dashboards without any coding.
Dashboards can be shared and embedded in other applications, and can be viewed in
different formats, such as tabular, chart, and map.
3. Analytics: PRPC provides built-in analytics features that allow you to analyze data and create
insights. The analytics feature provides a set of pre-built data models, algorithms, and
visualizations that allow you to quickly and easily analyze data, without the need for complex
coding.
4. Pega Intelligence: Pega Intelligence is a built-in feature in Pega Platform that enables you to
create advanced analytics and predictive models, that can be embedded on the platform.
To use Pega’s built-in reporting and analytics features, you would first need to define the data
sources you want to use, such as case data, performance data, or external data sources. Once
the data sources are defined, you can use the reporting and analytics features to create and
view reports and dashboards, as well as analyze data and create insights.
It is worth mentioning that Pega also provides the ability to integrate with third-party
reporting and analytics tools like Tableau, Power BI and more, to gain more advanced
capabilities and flexibility.
How do you implement and manage security and access controls in Pega?
Implementing and managing security and access controls in Pega’s PRPC framework is
achieved through the use of access groups, access roles, and access roles with rules.
1. Access groups: Access groups are used to group users together based on their role or job
function. Each user is assigned to one or more access groups, and each access group is
assigned a set of access roles.
2. Access roles: Access roles are used to define the permissions that a user has within the
application. Access roles can be assigned to access groups, and a user’s permissions are
determined by the access roles that are assigned to the access groups to which they belong.
3. Access roles with rules: Access roles with rules allow you to define fine-grained access
controls that are based on the specific data or actions that a user is trying to access or
perform. Access roles with rules are used to define the conditions under which a user can
access or perform a specific action.
To implement security and access controls in Pega, you would first need to define the access
groups and access roles that are required for your application. Then, you would need to
assign the appropriate access roles to the access groups and assign users to the appropriate
access groups.
Once the access roles and access groups are defined and assigned, you can use the built-in
security features in PRPC, such as the Data-Admin-Security class, to define the data access
and security controls that are required for your application. Additionally, you can use the
built-in validation rules to ensure that users can only access or perform actions on data that
they are authorized to access or perform actions on.
Managing access controls in Pega can be done through the use of built-in tools, such as the
Access Group and Access Role editors, which allow you to view and manage access groups
and access roles, respectively. Additionally, you can use the built-in reporting features to
view and analyze access control data and detect any potential security issues.
Overall, Pega’s PRPC framework provides a robust set of tools for implementing and
managing security and access controls, allowing you to ensure that your application is secure
and that users can only access the data and perform the actions that they are authorized to
access and perform.
Can you explain your experience with Pega’s integration capabilities, such as SOAP and REST
services?
Pega’s PRPC framework provides built-in support for integrating with external systems using
SOAP and REST services. Some of the key features and capabilities include:
1. SOAP integration: PRPC provides built-in support for integrating with SOAP web services. You
can create a service rule that defines the SOAP web service and the operations that you want
to call. You can then use the service rule to invoke the web service and process the response.
2. REST integration: PRPC provides built-in support for integrating with RESTful web services.
You can create a service rule that defines the RESTful web service and the operations that
you want to call. You can then use the service rule to invoke the web service and process the
response.
3. Connectors: Pega provides connectors to integrate with different system, such as Salesforce,
SAP, and Oracle.
4. External system integration: Pega provides the ability to create custom connectors to
integrate with external systems that are not supported out of the box. You can use the
Connect-SOAP and Connect-REST classes to create custom connectors and invoke web
services.
5. Authentication: Pega supports different authentication methods, such as Basic
Authentication, OAuth, and SAML.
6. Event-Driven Architecture : Pega provides the ability to build event-driven architecture to
integrate with external systems.
7. Pega API : Pega provides the ability to access Pega’s functionality through an API.
To use Pega’s integration capabilities, you would first need to define the external systems
that you want to integrate with and the operations that you want to call. Then, you would
need to create the appropriate service rule for the type of integration you are using (SOAP or
REST) and configure the service rule with the appropriate settings. Once the service rule is
configured, you can use the service rule to invoke the external system and process the
response.
It is worth mentioning that Pega also provides the ability to integrate with different protocols,
such as MQ, JMS, and more, to gain more advanced capabilities and flexibility.
How do you handle performance tuning and optimization in Pega?
1. Database Optimization: One of the key areas to focus on when tuning Pega performance is
the database. This includes optimizing database queries, indexes, and the database schema
to improve performance.
2. Data Model Optimization: Reviewing the data model and simplifying it can help improve
performance by reducing the amount of data that needs to be loaded and processed.
3. Rule Optimization: Reviewing the rules and optimizing them can help improve performance.
This includes optimizing the rules that are called frequently and identifying and removing any
rules that are not being used.
4. Caching: Pega’s PRPC framework provides built-in caching mechanisms that can be used to
improve performance. This includes caching data and rules to reduce the number of calls to
the database and the number of rule evaluations.
5. Memory Management: Reviewing the amount of memory that Pega is using and optimizing
it can help improve performance by reducing the amount of memory that Pega needs to use.
6. Thread Management: Reviewing and optimizing the number of threads that Pega is using can
help improve performance by reducing the number of threads that Pega needs to use.
7. System Configuration: Reviewing and optimizing the system configuration settings can help
improve performance by configuring Pega to use the resources that are available on the
system more effectively.
8. Monitoring: Monitoring the performance of the Pega application and identifying any
bottlenecks can help identify areas that need to be optimized.
To implement performance tuning and optimization in Pega, you would first need to identify
the areas of the application that are causing performance issues. Once the areas have been
identified, you can then use the techniques and approaches mentioned above to optimize the
performance of the application. Additionally, Pega provides built-in performance monitoring
and diagnostic tools that can be used to identify performance issues and monitor the
performance of the application over time.
It’s worth mentioning that Pega 7.4 and above use the Intelligent Decisioning which helps the
performance of decisioning by caching and reuse of decisioning data.
Overall, performance tuning and optimization in Pega’s PRPC framework is a process that
requires a combination of different techniques and approaches, including database
optimization, data model optimization, rule optimization, caching, memory management,
thread management, system configuration and monitoring. By using these techniques and
approaches, you can improve the performance of your Pega application and ensure that it is
running as efficiently as possible.
Can you explain your experience with Pega’s mobile and offline capabilities?
My experience with Pega’s mobile and offline capabilities is that Pega provides several built-
in features and tools that can be used to create mobile applications that can function offline.
1. Pega Mobile App Studio: Pega’s Mobile App Studio is a visual development tool that enables
developers to create mobile applications using drag-and-drop functionality. It allows for the
creation of native mobile apps for iOS and Android.
2. Pega Offline: Pega offline allows users to continue working on their case when they are
disconnected from the internet. Pega offline stores the data locally and syncs it with the
server once the user reconnects to the internet.
3. Pega Mobile Push Notifications: Pega supports mobile push notifications to alert users of
new cases, assignments, and messages.
4. Pega Mobile Offline Forms: Pega’s offline forms allow users to complete forms and submit
them even when they are offline. The forms are automatically submitted once the user
reconnects to the internet.
5. Pega Mobile SDK: Pega provides a mobile software development kit (SDK) that can be used
to develop custom mobile applications that can interact with Pega’s PRPC framework.
6. Pega Mobile App Security: Pega provides built-in security features for mobile applications,
including support for single sign-on (SSO) and two-factor authentication (2FA).
To implement mobile and offline capabilities in Pega, you would use the tools and features
provided by Pega, such as the Mobile App Studio, Pega Offline, and Pega Mobile SDK.
Additionally, you would need to configure the application to work offline and ensure that the
data is synced correctly when the user reconnects to the internet.
Overall, Pega provides a robust set of tools and features for creating mobile applications that
can function offline, including the Mobile App Studio, Pega Offline, Pega Mobile Push
Notifications, Pega Mobile Offline Forms, Pega Mobile SDK, and Pega Mobile App
Security. These tools and features can be used to create mobile applications that provide users
with a seamless experience, even when they are offline.
Handling system upgrades and maintenance in Pega typically involves the following steps:
1. Planning: Before upgrading, it’s important to plan the upgrade process and identify any
potential issues or challenges that may arise. This includes identifying the version of Pega
that you are currently using, the version you want to upgrade to, and any dependencies or
customizations that may be affected.
2. Backup: It is important to take a backup of the current system before upgrading. This
includes taking a backup of the database, the application, and any other related files.
3. Testing: After the upgrade, it is important to test the system to ensure that it is working
correctly and that there are no issues or errors. This includes testing the system in a test
environment and then in a production environment.
4. Deployment: Once the system has been tested and any issues have been resolved, the
upgrade can be deployed to the production environment. This involves installing the new
version of Pega and updating any dependencies or customizations that may be affected.
5. Monitoring: After the upgrade, it is important to monitor the system to ensure that it is
working correctly and that there are no issues or errors. This includes monitoring the system
logs and performance metrics, and addressing any issues that may arise.
6. Maintenance: Once the upgrade is complete, it is important to maintain the system to
ensure that it continues to work correctly. This includes performing regular maintenance
tasks, such as database maintenance, and applying any necessary patches or updates.
Pega also provides several built-in features and tools to help with system upgrades and
maintenance, such as Pega Upgrade Manager, which automates the process of upgrading
Pega, and Pega System Management, which provides a single point of control for monitoring,
managing, and maintaining your Pega system.
Overall, handling system upgrades and maintenance in Pega requires a good understanding of
the Pega platform, the version of Pega that you are currently using, the version you want to
upgrade to, and any dependencies or customizations that may be affected. It is important to
plan the upgrade process, take a backup of the current system, test the system, deploy the
upgrade, monitor the system and maintain it to ensure that it continues to work correctly.
Pega also provides built-in features and tools to help with system upgrades and maintenance,
such as Pega Upgrade Manager and Pega System Management.
Can you explain your experience with Pega’s case management and workflow capabilities?
Pega’s case management and workflow capabilities allow you to create and manage complex
business processes within the Pega platform. This includes the ability to create and manage
cases, which are instances of a specific business process, and the ability to create and manage
workflows, which are the series of steps that make up a case.
The case management in Pega allows organizations to automate and streamline their business
processes, by providing a centralized location for managing and tracking cases. Cases can be
created, assigned, and tracked by users, and can be linked to other cases and workflows. This
allows for the efficient management of business processes, and allows organizations to easily
track and report on the status of cases.
Pega’s workflow capabilities allow you to define and manage the steps that make up a case.
Workflows can be created using a drag-and-drop interface, and can include a wide range of
activities such as data validation, decision making, and communication. Pega also provides a
built-in rule engine, which allows you to create and manage business rules within the
workflow. This allows you to define the logic that governs the flow of the case, and to
automate decision-making within the workflow.
Pega also provides tools for monitoring and reporting on workflows and cases, such as the
Case Explorer and the Work Manager. These tools allow you to view and track the status of
cases and workflows, and to generate reports on case and workflow performance.
Testing and quality assurance (QA) are critical components of any Pega project, as they help
ensure that the application is functioning as expected and meets the requirements of the
business.
Here are some ways that testing and QA can be handled in Pega projects:
1. Unit testing: Unit testing is the process of testing individual units of code, such as rules,
activities, and flows, to ensure that they function as expected. Pega provides tools for
creating and executing unit tests, such as the Unit Test harness, that allows developers to
create and execute unit tests for their code.
2. Functional testing: Functional testing is the process of testing the application as a whole to
ensure that it meets the requirements of the business. Pega provides tools for creating and
executing functional tests, such as the Test harness, that allows developers and QA testers to
create and execute functional tests for the application.
3. Performance testing: Performance testing is the process of testing the application to ensure
that it can handle the expected load and performance requirements. Pega provides tools for
creating and executing performance tests, such as the Performance Test harness, that allows
developers and QA testers to create and execute performance tests for the application.
4. Automated testing: Automated testing is the process of automating the execution of tests,
which can be done using tools like Selenium or Test Complete. Pega provides an integration
with these tools which allows creating automated test scripts that can run functional and
regression tests.
5. User Acceptance Testing (UAT): User acceptance testing is the process of testing the
application with real-world users to ensure that it meets their needs and expectations. UAT
can be done by creating test cases and scenarios that mimic real-world usage, and having
users test the application using these scenarios.
6. Data validation: Pega allows creating validation rules and constraints to ensure data integrity
and quality. These rules are enforced when the data is entered and are also used for data
migration and integration.
In summary, testing and QA in Pega projects can be handled by using a combination of unit
testing, functional testing, performance testing, automated testing, User Acceptance Testing
(UAT) and data validation, using the built-in tools and integration with other testing tools that
Pega provides.
Can you explain your experience with Pega’s deployment and version management process?
Deployment and version management are critical components of any Pega project, as they
help ensure that the application is deployed and versioned correctly, and that the appropriate
version of the application is running in each environment.
Here are some ways that deployment and version management can be handled in Pega
projects:
In summary, deployment and version management in Pega projects can be handled by using a
combination of environment management, version control, deployment, continuous
integration and delivery and disaster recovery, using the built-in tools and integration with
other tools that Pega provides.
Providing support and troubleshooting issues in Pega applications involves several steps and
processes to ensure that issues are identified, resolved, and prevented in the future. Here are
some ways that support and troubleshooting can be handled in Pega projects:
Can you explain your experience with Pega’s different tools and utilities like Tracer, Clipboard, and
so on?
Pega has a number of different tools and utilities that can be used to help develop, test, and
troubleshoot applications built on the PRPC framework. Here are a few examples of some of
the tools and utilities that I have experience with:
1. Tracer: Tracer is a debugging tool that allows developers to trace the execution of a process
and view the values of variables and properties at different points in the execution. This can
be useful for identifying and resolving issues related to process flow and data validation.
2. Clipboard: The Clipboard is a tool that allows developers to view and edit the values of
variables and properties at runtime. This can be useful for troubleshooting issues related to
data validation and process flow.
3. Work Object: Work Object is the central data structure in Pega and it can be used to store
and manage data throughout the life of a case. Developers can use the Work Object to view
and edit the data associated with a case and to create new cases as needed.
4. Rule Inspector: Rule Inspector is a tool that allows developers to view and manage the rules
that make up a Pega application. This can be useful for troubleshooting issues related to rule
execution and for making changes to the rules in an application.
5. System Management Application (SMA): SMA is a web-based tool that allows administrators
to manage and monitor the performance of a Pega system. This can be useful for
troubleshooting issues related to system performance and for making changes to the system
configuration.
6. Performance profiler: Performance profiler is a tool that allows developers to identify and
analyze performance bottlenecks in an application. This can be useful for troubleshooting
issues related to system performance and for making changes to improve the performance
of an application.
7. Trace Analyzer: Trace Analyzer is a tool that allows developers to analyze log files and trace
information generated by Pega applications. This can be useful for troubleshooting issues
related to system performance, process flow, and data validation.
8. Deployment Manager: Deployment Manager is a tool that allows developers to manage and
deploy changes to a Pega application. This can be useful for managing the lifecycle of an
application and for making changes to an application in a controlled and organized manner.
In summary, Pega provides a wide range of tools and utilities that can be used to develop,
test, and troubleshoot applications built on the PRPC framework. These tools and utilities can
be used to view and edit data and rules, troubleshoot performance issues, and manage the
deployment of changes to an application.
1. Explain the concept of classes in Pega. What are the many types of classes that Pega has to offer?
Users can reuse rules across case types and apps with the Pega Platform. Developers reuse
rules in their systems all the time, from single data points to entire processes. Reusing rules
improves an application’s quality while simultaneously reducing development time. Pega
Platform categorises rules into classes based on how easily they may be reuse inside an
application. A class is the name given to each cluster. Each application consists of three
different types of classes.
Work Class: The Work class contains processes, data objects, and user interfaces, as well as
the rules that govern how to process a case or cases.
The Integration class contains the rules that govern how the application interacts with
external services, such as the integration resources that link it to a customer database or a
third-party web server.
Data Class: The Data class stores the rules that specify the data objects used in the
application, such as a customer data type or order items data type.
When we add a rule in App Studio, it chooses the appropriate class for us. Instead of focusing
on how to build the rule, we might concentrate on what we want it to accomplish. If you
need control over the class, we can write the rule in Dev Studio.
2. In the context of Pega, what do you know about SLA in Pega Certified System Architect?
The abbreviation SLA stands for Service Level Agreement. It’s one of the Pega CRM
platform’s most useful features. Service Level Agreements allow us to set targets and
timetables as part of the case management process. SLA’s main objective is to help the task
force complete all jobs on time. Each SLA rule’s performance of a specific event action that
was set for that rule will be track by Pega Rules Process Commander. By increasing the
urgency number, the assignment’s urgency is adjusted as well. Because it necessitates
attention, this may call attention to the item on the employee’s to-do list. As a result, we can
order the to-do list by task urgency.
For the system name we select during installation, Pega Platform provides four requestor
types, as well as a reserved requestor type prpc.BROWSER for certain scenarios. We usually
only need the four requestor kinds that have your system name in them. After installation, we
head to Designer Studio => System => Settings => System Name to access a landing page
tab where we can change the system name. When a system’s name is change, new requestor
instances are create that correspond to the instances of the prior name. When a system is
rename, if the previous name did not include all requestor types for some reason, the missing
requestors are also produce.
4. In the context of Pega, explain PRPC in Pega Certified System Architect.
Pega Rules Process Commander (PRPC) is an acronym for Pega Rules Process Commander.
The PRPC foundation is use by Pegasystems. It is entirely model-driven, allowing the
development of reliable and efficient applications without the need for any code, including
SQL, Java, CSS, or HTML. PRPC is a software platform that allows businesses to
consolidate their many, complex business procedures and methodologies into a single
platform. You may merge multi-stream processing into a single system by automating,
documenting, and simplifying business operations.
5. Explain what you’re doing in the context of Pega in Pega Certified System Architect.
Pega Platform activities automate processes. In Dev Studio, activities are programmed as a
series of steps that must be complete in the order provided. Activity rules automate the
system when more appropriate rule types are unavailable, frequently due to more complex
computations or procedures, or when a rule requires an activity to run. Declare When the
value of a certain property changes, for example, using an activity to start a process or
suspend work is require. After the activity is performed, control returns to the rule that called
the action.
An insurance company, for example, is require to submit insurance claims to the Registry of
Motor Vehicles. Automated uploads take performed during off-peak hours to reduce the
impact on users. In Pega Platform, an activity can be design to allow the system to automate
claim uploads without requiring user input.
6. In the context of Pega, explain Rule Resolution in Pega Certified System Architect.
Rule resolution is the search process use by the system to find the best or most appropriate
rule instance to apply in a particular situation.
Rule resolution applies to all rule types, except a few rule types — classes that inherit from
the Rule- class. Further, rule resolution has no effect on instances of classes derived from the
Work-, Data-, or any other base class. Even though the rule resolution process is quick and
unobtrusive, it is crucial to understand how it works. When building applications, make
important component value selections base on how you want rules to be found via rule
resolution. An in-memory rule cache can help speed up the rule resolution process. If the
system finds an instance (or instances) of the rule in question in the cache, it accepts the
candidate rules and skips many steps in the resolution process.
7. In the context of Pega, explain data pages in Pega Certified System Architect.
A data page in a Pega Platform application retrieves and caches data from a given data
source. A data page manages the data source integration, separating business processes from
any integration details. App developers can use supplied data in their apps without needing to
know the data source or connection details because of this separation. Unlike the majority of
Pega Platform pages, applications attempt to populate the contents of a data page only when
the page is request, rather than through an explicit action. Since their content is provided on
demand, data pages are classed as declarative rules.
8. In the context of Pega, explain Case Management in Pega Certified System Architect.
Case management is a software-based technique for assisting people with day-to-day chores
and automating work processes from beginning to end. Case management comprises
visualising your business process, which includes people, data, and actions, in order to map
out a flexible path to your destination. We use case management to develop goal-oriented
solutions by addressing business cases from beginning to end and combining human activities
with digital automations.
We can, for example, mimic the process of accepting candidates after reviewing job
applications, from collecting documentation from candidates to conducting job interviews to
gaining final approval. You can dynamically adjust your work in case management to
respond to changing conditions, as well as construct the most typical path to resolution. Your
business procedure can incorporate an additional job interview if this phase is relevant to the
current situation. With case management, you may successfully address business procedures
that follow an ambiguous or unexpected workflow.
9. In the context of Pega, what do you mean by locking? What are the many types of locking
mechanisms?
When two or more actions attempt to update the same case at the same time, the more recent
action may overwrite the data written by the previous action. Data damage or loss might
happen from overwrites, creating delays in case processing and possibly inaccurate case
resolution. A case locking approach is essential for data integrity when an application
supports several users at the same time.
10. In Pega, what is the Declare Index in Pega Certified System Architect?
Declare Index is a rule type in Pega that exposes aggregate attributes such as Page, List, and
Group for reporting reasons. They are Rule-Declare-Index rule instances. It helps to populate
the correct index table when an Insert/Update/Delete operation on the work object is follow
by a commit. They can be discover in Records Explorer under the SysAdmin Category.
11. In Pega, how can you assess the performance of your application?
The numerous ways we can measure the performance of our application in Pega are as
follows:
DBTrace: DBrace is a feature of the Performance Analysis Tool (PAL) that provides a detailed
log of calls to the PegaRULES database. DBTrace displays both the time spent on each
operation and the SQL queries sent to the database.
Performance Analyzer Tool (PAL): The Performance Analyzer (PAL) displays all of Pega
PlatformTM’s performance statistics. You can utilise PAL to determine how much system
resources are consume by a single requestor session. PAL is available on the Performance
landing page (Dev Studio > System > Performance) as well as the Performance tool in the
toolbar.
12. How do you tell the difference between the Page-Validate and Property-Validate methods?
The page-validate method is use to ensure that all of the properties on a page are valid. If a
page has embedded pages, this method validates all of the attributes in a recursive manner.
This method is time-consuming and uses a lot of system resources. Use the Obj-Validate
method with a Rule-Obj-Validate rule to validate specified properties.
Property value constraints are imposed via the property-validate technique. To implement
constraints, use the Edit validate rule in conjunction with the Property-Validate method. The
Property-Validate method can be use to validate multiple properties.
13. What is the difference between Edit Input and Edit Validate rules?
Edit Validate: Use the edit validate rule to use java code to validate the property value.
Property-validate, Rule-Obj-Validate, and Property rules can all be use to edit validate rules.
Edit Input: Edit input rules transform user-entered data into the proper format. If a user
types a date in MM/DD/YYYYY format, the edit input rule converts it to DD-MM-YYYY
(required format). For this transformation, we’ll need to write java code once more.
14. Where will the work objects be kept in Pega Certified System Architect?
By default, work objects are kept in the pc work table. If you want to store the work objects
in a user-created table, however, follow the instructions following.
Make a schema that looks like the pc work table. (It’s advisable to duplicate the pc work
schema and change the table and constraint names if necessary.)
Change the Data-Admin-DB-Table class group mapping to the newly created table.
15. What are the rules for StepStatusGood and StepStatusFail?
StepStatusGood is when the rule checks whether the value of the pxMethodStatus property
is “Good” according to the condition defined in @baseclass.
StepStatusFail is a when rule that checks whether the value of the pxMethodStatus property
is “Fail” as defined in the @baseclass condition.
16. Where can I see the clipboard parameter values (values, etc.) while I’m sending one activity to
another?
No, you won’t be able to see it in the clipboard, but you can see it in tracer by clicking the
page name in the step method column.
Open the rule, select the pzinskey, go to prdbutil, and export the rule using the pzinskey.
Import the zips file to wherever you’d like.
Rules: inheritance that allows you to reuse your rules as much as possible while allowing for
localised overriding when necessary. Inheritance, often known as polymorphism, allows a
rule written for one class (perhaps an abstract class) to be applied to other classes that
inherit from that class.
To identify available rules, class inheritance searches for rules from a concrete, lower class up
the class hierarchy.
Directed inheritance and pattern inheritances are two types of class inheritance.
20. What is the distinction between the Page-Validate and Property-Validate methods?
The page-validate method ensures that all of the properties on a page are valid. If a page has
embedded pages, this method validates all of the attributes recursively. This method is time-
consuming and uses a lot of system resources. Use the Obj-Validate method with a Rule-Obj-
Validate rule to validate specified properties.
Property value constraints are impose via the property-validate technique. To implement
constraints, use the Edit validate rule in conjunction with the Property-Validate method. The
Property-Validate method can be use to validate multiple properties.
21. Where will the work objects be kept?
By default, work objects are kept in the pc work table. If you want to store the work objects
in a user-created table, however, follow the instructions following.
Make a schema that looks like the pc work table. (It’s advisable to duplicate the pc work
schema and change the table and constraint names if necessary.)
Change the Data-Admin-DB-Table class group mapping to the newly created table.
22. What are the rules for StepStatusGood and StepStatusFail?
StepStatusGood is when the rule checks whether the value of the pxMethodStatus property
is “Good” according to the condition defined in @baseclass.
StepStatusFail is a when rule that checks whether the value of the pxMethodStatus property
is “Fail” as defined in the @baseclass condition.
23. Is there a distinction between activity and utility?
24. How are the results of our work in the Pega measure?
DBTrace: The Performance Analysis Tool (PAL) has a function called DBrace that provides a
thorough log of calls to the PegaRULES database. DBTrace shows the time spent on each
operation as well as the SQL queries delivered to the database.
PAL: “PAL counters” or “PAL readings” are use to store this information. Performance
Analyzer (PAL) is a collection of counters and timer measurements saved in the requestor
that an application developer can utilise to assess system performance concerns.
25. What is the best way to save a class instance in a database?
Creating a distinct DB table for that working-class within the database, or mapping to an
external database and saving to that database.
Creating a distinct DB table for that working-class within the database, or mapping to an
external database and saving to that database.
In an application, a work object is the primary unit of work completion and the primary
collection of data on which a flow operates.
Work items are generated, updated, and eventually closed when an application is utilise
(resolve).
A unique ID (property pyID), an urgency value, and a status are all assigned to each task
object (property pyStatusWork).
28. What is the difference between an Access Group and an Access Role?
It’s an instance of the Rule-Obj-Flow Action rule type, to be precise. It is the only category in
the user interface that specifies the options available to the user when executing assigned
tasks.
12) What are SLAs used for? How do you configure an SLA?
Ans: SLAs are rules in PRPC that indicate the expected or targeted
turnaround time for the assignment, or time-to-resolve for the work
object. Each service level rule defines one to three-time intervals,
known as goals, deadlines, and late intervals. Late intervals are
repeated. Service level rules can be associated with assignments in a
flow and with the entire flow. For example, we can set a goal of 2
hours to process an assignment and a deadline of 4 hours. (The time
interval starts when the assignment is created, not when a user
begins processing the assignment.) For assignments, the service
level rule is referenced in the Assignment Properties panel of the
assigned task. For the overall work object, the service level rule is
identified in the standard property .pySLAName, typically set
up through a model for the class. (The default value is the Default
service level.) ** The Pega-ProCom agent detects service levels not
achieved — unmet goals or deadlines — promptly. If an assignment
is not completed before the time limit, the system can automatically
notify one or more parties, escalate the assignment, cancel the entire
flow, and so on.
14) Which harness would you use to present the work object to
the users only for viewing?
Ans: Review harness. Review harness is used to display the work
objects in display-only mode, with no fields changeable.
15) What are Work Parties? How do you send correspondence
to work parties?
Ans: Work party is a person, organization, or other actor identified
in a work object, who can be the recipient of the email or other
forms of correspondence. A work object may identify no work
parties, one, or many work parties. The work party role associated
with each work party identifies why a party is present and may
determine which properties are defined for that party. A Notify
activity, when referenced in a flow, sends out correspondence, such
as an email message, when a flow execution creates an assignment.
Typically, the system addresses correspondence to a work party
identified in the work object and reports progress to that party.
16) In the flow, what is the difference between local and
connector flow action?
Ans: Flow actions specify the choices that user has when performing
an assigned work object. Flow actions are mainly of two types i.e.,
connector actions and local actions. Connector flow actions advance
the flow. They are associated with the connector that exists at the
assignment, so selecting them causes the flow to advance along with
the path. Local actions allow the user to update the work item but
don’t advance the flow. After the assignment is committed, the flow
remains at the same assignment from which the local action was
performed.
17) Have you integrated any external systems with Pega? How
do you make a SOAP call? Briefly mention the steps to connect
to an external system using SOAP.
Ans: To make a SOAP call from PRPC we import the wsdl from the
external web service and create SOAP connector rules in PRPC to
invoke the external web service. We use the Connector and Metadata
Accelerator to generate the connector rules. The Connector and
Metadata Accelerator imports information about an external
application or system and generates rules and data objects that the
PRPC applications can use to communicate with that external
system. Before you use the Connector and Metadata Accelerator to
generate connector rules, follow these steps: Identify the RuleSet
and version to contain the generated rules — classes, properties,
connector rules, activities, and so on. Identify or create the following
class rules to use for the generated rules. An abstract class rule —
typically one that inherits from the Database class — for the
accelerator to use as the container or base for the generated items
with the exception of the connector activities. (If you do not create
this class before you begin, the accelerator can create one for you.) A
concrete class rule for the connector activities. If you plan to call the
connector from a flow, choose a class that inherits from the Work-
base class, so that the connector activities can be called directly from
an Integrator task. Next, start the Connector and Metadata
Accelerator and provide the URL to the WSDL document of the Web
service that you want to connect to. Complete all the steps on the
wizard to generate the connector rules and data mapping rules. **
Also, be familiar with Soap Service rules. You may also get
questions on that.
Only Single Value attributes at the top level are visible. However, it is possible
to convey embedded property values to the top level or offer them indirectly
via instances of the Index class.
21. How Do You Deal With
Escalation?
Escalation refers to any activity within a Process Commander application that
makes high-priority work objects visible to users and managers and causes
them to be rapidly processed. For example, a service level rule connected
with the flow and background processing by the Pega-ProCom agent can lead
to Escalation.
Even within a single rule set, rules may exist in several versions,
and security rules restrict which users can read and execute
which versions.
A single Pega Platform system may host numerous applications,
various organizations, and multiple versions of a single
application with little conflicts and interference.
Developers can develop applications independently of one
another, but they can all adhere to a fixed set of rules.
Apps and organizations can share rules between themselves.
Object-oriented software development provides numerous
benefits, including reuse and sharing.
Rules established at a lower level that are more specific can
supersede rules defined at a higher level. Even though this
decreases the value of sharing, it provides much-needed
flexibility and highlights exceptions.
Harnesses in Pega is used to define the look and processing of user forms
in any application that is necessary for the creation of work items and the
processing of assignments.
An assignment in Pega is a break in the flow and it denotes the need for
an external system or a person to act on a work object so that the flow
can resume.
Q.7) What is ruleset in Pega?
Click on Record
Select Workbasket under the Organization category.
Right-click on Create.
Indicate a name to identify the workbasket instance.
Assign a name to convey the purpose and content to the users.
You can open an exercise system in Pega using a to the Pega 7 designer
studio that opens in a new window.
A working pool in Pega is a collection of the work objects, both open and
resolved, as well as the work- classes that a user is able to enter in an
application, determined by the system from a list of class groups.
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.
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?
Delay it.
Delay it again.
In the requestors, select the delayed requestor and click on the tracer.
Column layout.
Grid layout.
Portal layout.
Dynamic layout.
7. What is the ruleset in Pega?
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
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?
Rule-Declare-Expressions.
Rule-Declare-Index.
Rule-Declare-Trigger.
Rule-Declare-OnChange.
Rule-Declare-Constraints.
10. What is the difference between Page-Validate and Property-Validate methods?
Ans:
Page-Validate:
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.
Property-Validate:
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.
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 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.
Ans:
Decision Table:
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.
Decision Tree:
In a decision tree, if the first condition is true or false, it will check all
conditions and it will return results.
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.
1) What is BPM?
Any business has to perform a series of steps to accomplish a task and this entire life cycle is
called a business process. A BPM tool is something that provides a simple yet systematic
approach to perform any given operation in an optimized way. The major goal of
implementing a BPM tool is to plan, design, implement and automate business operations
while minimizing errors, miscommunications, and inefficiencies.
Improved productivity
High flexibility
Minimized errors
Easy implementation of policies
Eliminated Micromanagement
Simplified data accessibility
Easy Data Migration between multiple systems
Supports digital transformation journey
System Centric
Human-Centric
Document Centric
Finance
Sales
Human resource
Marketing
5) Name a few well-known BPM tools?
There is a wide range of BPM tools available in the market and the following are some of the
widely used BPM tools are:
Pegasystems
BP Logix
Kofax
Tibco Software
Oracle
Appian
IBM
6) What is Pega?
Pega is a widely used BPM software built using java that helps in building modern enterprise
applications. It comes with advanced features to simplify the complex app building process
and saves a lot of time. Pega powers the digital transformation process of the business by
unifying leading technologies like artificial intelligence and customer engagement
capabilities.
Pega comes with many advanced in-built components and supports various internal as well as
external database integrations. Moreover, it also has a best-in-class configuration
management system. All together these features have made it possible to build web-based
apps compared to Java.
Dev Studio
App Studio
Admin Studio
Prediction Studio
Assignment SLA
Case Level SLA:
Stage Level SLA:
Step level/Flow level SLA
13) What is the Page -Validate method?
The Page – Validate method is used to validate all the properties available on a page. This
method requires a lot of system resources and time taking. If in case a page contains
embedded pages this method works repeatedly to validate overall properties. Whenever you
want to validate any particular property on a page you need to use the obj-validate method.
14) What is the Property -Validate method?
The core aim of using the Property-validate method is to impose restrictions on a property
value. In order to impose any restriction on a property value, you are required to use the Edit
validate rule along with the Property validate method.
15)What is meant by the page list property?
A Page list property is an embedded list of ordered pages and referenced by a numeric script.
This method is helpful for storing the lists of data.
16) What is a “Page Group” Property?
The Page Group property is quite opposite to the Page list property and contains an unordered
list of pages referenced by a string subscript. This is the best way to look into the pages
by unique identity number.
17) What is a Work Object in Pega?
A Work object in Pega is defined as a primary unit of task completion in an application and
also a collection of data. In general, whenever application functions, the work objects are
created, modified, and closed. In Pega, each work object is assigned with a unique ID,
urgency level, and final status.
18) What do you know about SLA?
In Pega, the Service Level Agreement (SLA) feature has been used to set a deadline for work
completion. This feature enables the organization in making the employees focus on the task
at hand and to gain on-time performance.
19) What is Pega DCO?
In Pega, DCO stands for Direct Capture of Objects and is considered an essential component
for the success of any object. It is a process to capture, organize and store business data by
using the Prga Integrated solution. The DCO consists of different components and tools
required to collect and organize application information.
20) Name a few tools used by DCO to automate work?
Case Lifecycle Manager
New Application Wizard
Application profiler
Document generation
Effort estimation
Specification documents
Dynamic Layout
Column Layout
Layout group
Dynamic Layout group
Repeating dynamic layout
Navigational tree layout
Screen layout
Table layout
A summary view rule defines a two-level report display, presenting summary counts, totals
or averages to be displayed initially, and allowing users to click a row to drill down to
Summary view rules support interactive charts, trend reports, and the use of AJAX for pop-
A summary view rule is an instance of the Rule-Obj-SummaryView rule type. This rule type is
A list view rule, an instance of the Rule-Obj-ListView rule type, defines a report. Users can
Use the Report wizard to define list view reports and link them to our portal.
To divide the ListView in to different pages and set the number of records to be displayed in
a page.
But we can’t refer the property without exposing in Critera fields of the Content tab.
Embed-ListParams class.
6) What is the activity responsible for getting the data in List View?
getContent Activity
Step1: Create Activity in Our Class and create the New page
Step5: create the parameter. This parameter get the sql query from previous activity
Get the page from pyContentPage if page already exists. If page is not available it creates
In this code get the sql query from the above parameter and pass this query and above
pagename) method.
8)How do we fetch the data from two different tables with out using two
different tables?
Write a database View. In this view logically combine the Two different tables.
Write the List View. Applies to class is class of the Combined table. So we can refer the
Use the Activity-End method to cause the system to End the current activity and all calling
activities.
Ex: if Alpha calls Beta, which calls Gamma, which calls Delta, which performs the Activity-End
The Exit-Activity method ends the current activity and returns control to the calling activity.
Page-Copy method is used to copy the contents of a source clipboard page to a new or
previously created destination clipboard page. The source page is not altered.
After this method completes, the destination page contains properties copied from the
The Page-New method is used to create a page on the clipboard. The new page may be a
We can identify a model to initialize the newly created page. The model can set values for
Page-Remove method is used to delete one or more pages from the clipboard. The contents
Use the Page-Set-Messages method to add a message to a clipboard page. Like a message
associated with a property, a message associated with a page normally prevents the page
page. The system reads the appropriate property and adds the message to the page. We
can provide the entire literal text of the message, or reference a message rule key that in
Use the Property-Map-DecisionTable method to evaluate a decision table rule and save the
Declare-DecisionTree rule type) and store the result as the value of a property.
MapValue rule type) defined in the parameter. The method sets the result as a value for a
values.
19) Explain about Property-Remove method?
Property-Remove method is used to delete a property or properties and its associated value
from the step page or another specified page. This does not affect the property rule, its
definition.
Property-Set method is used to set the value of one or more specified properties.
The Show-HTML method is used to cause the activity to process an HTML rule and send the
resulting HTML to a user for display by Internet Explorer. This may involve the interpretation
of JSP tags (or the older directives), which can access the clipboard to obtain property
The Show-Page method is used to send an XML representation of the step page to a user’s