Interviewbit - Pega Interview Questions
Interviewbit - Pega Interview Questions
© Copyright by Interviewbit
Contents
Pega Platform offers four studios, or role-based authoring workspaces and they are
as follows:
App Studio
Dev Studio
Prediction Studio
Admin Studio
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.
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."
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.
The following tools are used by DCO to automate the work:
Case Lifecycle Manager
New Application Wizard
Application profiler
Document generation
Effort Estimation
Specification documents
Following are the benefits of DCO in Pega:
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.
There are four levels in SLA. They are as follows:
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.
Following are the benefits of SLA :
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 so ware, 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 swi ly 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.
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.
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 a er 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.
Following are the different requestor types in Pega:
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.
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.
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
so ware, 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.
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.
A developer must give four crucial pieces of information when creating a data page.
They are as follows :
Structure of the page
Object Type of the page’s content
Edit Mode supported
Scope of the data page
In Locking, we configure an appropriate locking technique for each case type to avoid
data corruption or loss due to overwrites. Pessimistic locking and optimistic
locking are two solutions that Pega Platform enables to balance the need for user
access with the necessity for data security.
Pessimistic Locking:
When an application uses 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.
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.
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.
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.
Work List:
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:
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 [email protected]
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.
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:
When one flow execution starts another flow execution that runs asynchronously and
independently of the first flow execution, this is known as a spinoff. The first flow
does not pause or wait for the second flow's results. The second flow could work on
the same or a different work item than the first flow.
At the workflow level, spinoffs enable parallel processing of work. While one
department or business unit performs its functions for the work item at its own pace
and according to its own flow, another department works on the same work item.
Increased parallelism can reduce end-to-end resolution times, allowing for more
efficient staffing and better customer service.
Split Join Shape:
On the Diagram tab of a flow rule, a Split Join shape can be found. This shape causes
work item processing to divide into two or more distinct flow executions that run
asynchronously and then rejoin later at runtime.
At the business process level, this capability allows for multitasking or parallel work
processing. While one department or business unit performs its functions for the
work item at its own pace and according to its own flow, another department works
on the same work item. Similarly, if the split creates six subflows, each of them could
be assigned to and worked on by six separate users who are all working on their
assignments at the same time.
Conclusion:
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.
To learn more about Pega, you can visit this link.
Css Interview Questions Laravel Interview Questions Asp Net Interview Questions