Google News
logo
Pega Interview Questions
Pega is a powerful low-code platform that builds agility into the world’s leading organizations so they can adapt to change. Clients use our AI-powered decisioning and workflow automation to solve their most pressing business challenges – from personalizing engagement to automating service to streamlining operations.
 
Pegasystems Inc. is an American software company based in Cambridge, Massachusetts. Founded in 1983, Pegasystems develops software for customer relationship management and business process management. The company has been publicly traded since 1996 as PEGA.
 
Pega is a popular BPM tool and a platform that allows users to develop apps, perform integration with the external system and implement mobility easily. It is mainly concerned with customer engagement and digital process automation.
 
Pega essentially offers four different types of studios  :
 
* Dev Studio
* App Studio
* Admin Studio
* Prediction Studio

Studios, also called workspaces, are used to speed-up application development and enable users to work with role-based capabilities. Role-based capabilities help different types of developers perform specific functions with the tool. 
Pega is a platform that facilitates users to develop applications, implement mobility, help in managing the case life cycle, extensive user interface design, managing the decisions and implementing the DevOps and Robotic Automation, extensive User Interface Design, and reporting etc. Pega is preferred over other tools that it eliminates coding, simplifies the process by using inbuilt functionalities and mainly stands for reusing the existing rules and modifying accordingly.
From the application development point of view, the following are some of the new features added in Pega 8.4 :
 
* In Pega 8.4, we can use role-based workspaces.
* The new version provides developers with the capability to review complete project highlights on a single page.
* It also provides effective management of reusable components.
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.
 
The Data Class : This class specifies the rules that govern the use of data types and objects. 

The Integration Class : This class comprises rules that spell out how the application interacts with external services and resources such as customer databases and 3rd party servers.

The Work Class : This class consists of data items, interfaces, and other resources that govern the processing of test cases.
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.
Edit Validate : Use the 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 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 need to write java code for this transformation.
The different types of standard classes available are.
 
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.

* 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.
Following is the list of main certifications available for developers in Pega :
 
CSA : CSA stands for Certified System Architect. It is the basic level of certification as the entry-level for a developer.

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.

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 thorough with all the functionalities and implement accordingly.
10 .
What are the different types of harnesses used in Pega?
There are several types of standard harnesses available in Pega, but the most commonly used harness is new, perform, review, conform, Tabbed, perform screen flow, Tree Navigation etc.
Following is the list of some different techniques that are used in the activities :
 
* Page- Remove
* Page- New
* Object - List
* Object -Open
* Object - Save
* RBD -Save
* RBD - List
* RBD - Delete
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.
 
We can create a work object in Pega in the following steps :
 
* Create a button that looks like a section or a header.
* Click the action tab after expanding the cell property within the button.
* Add an action set to the button.
* The button should have a focus class and a flow name.
* With “Param.prevRecordkey,” we can get the current work object ID.
* Open the case with "Obj-Open-By-Handle."
* Copy the data from pagers with Page-Copy.
Pega Work Flow
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."
work object

13 .
What do you understand by id DataPage and what is its scope?
DataPage is Single Page or a Page list where it stores the data that the system needs to populate work item properties for its calculation or other processes.
Differences between declare pages and regular pages :

Declare Pages :
 
* Declare pages are created using declarative rules.
* The declare keyword must be specified while creating a declare page.
* Declare pages are read-only pages, and these pages cannot be deleted or updated directly.

Regular pages :
 
* Regular pages or user pages are created using a page new method.
* These pages can be easily updated or deleted directly
* , and these pages are automatically deleted once logout from the system.
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.
 
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:
 
* DCO enables collaborative teams to model situations that must be addressed by the application's end users. The modelling and simulation tools allow users to take a critical interim step after documenting the application but before incurring the cost of development to see if the software is meeting our objectives. When we can think through and work out solutions as part of the software development life cycle, we are less likely to be blindsided in production.

* Organizations can use DCO to improve their efforts and use iterative processes. Issues and risks are not allowed to be discovered and mitigated at the conclusion of a project; they are detected and mitigated in real-time. The software development process is more visible, and it allows teams to learn and improve on a constant basis. DCO technologies and best practices give organisations several ways to deliver go-live, increasing their return on investment and allowing them to reliably accomplish their objectives.
16 .
What is a portal in Pega, and where it will be configured?
Portal is an interface that appears for the users (Developers or End Users). Portal can be configured in Access Group. For example, Developer portal, manager portal, user portal, admin portal etc.
Following are the different types of requestors in Pega :
 
Browser requestor : The browser requestor starts with the letter 'H'.

Batch requestor : The batch requestor starts with the letter 'B'.

Application requestor : The application requestor starts with the letter 'A'.

Portal requestor : The portal requestor starts with the letter 'P'.
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.
 
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.
SLA

Assignment SLA :
As the name suggests, the Assignment SLA 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 : The Case Level SLA is an SLA that is referred to at the case level. This SLA is relevant throughout the lifecycle of a case. It starts when a case is opened and is completed when the case is closed. The standard property pySLAName is used to identify this SLA under the work page, and it is set in pyWorkPage's pxUrgencyWorkSLA parameter. The pxUrgencyWorkSLA property under pyWorkPage is used to control the urgency of case-level SLAs.

Stage Level SLA : The Stage Level SLA is an SLA that is referred to at the stage level. It starts when a case enters a stage and ends when it exits the stage. The pxUrgencyWorkStageSLA property under pyWorkPage is used to control the urgency at the Stage level.

Step level/Flow level SLA : An SLA is called a Step level or Flow level SLA when referred to as a step or flow level. A step-level SLA starts when a process or step is initiated and ends when it is completed. A flow level SLA is started when a flow is begun and stopped when a flow 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.
We can use the following steps to trace SLA in Pega :
 
* By terminating the agent.
* By delaying it.
* By initiating the agent.
* Delay it again.
* In the requestors, select the delayed requestor and click on the tracer.
* Send this case to a particular assignment containing the SLA within 60 seconds.
Following are the key differences between activity and Utility in Pega :
 
* In the Pega platform, activity is used to automate processing. It can be configured to allow the system to automate claim uploads without user intervention.

* An activity contains a sequence of steps that perform in the instructed order.

* Activity is a rule of Rule-Obj-Activity, and Utility is a shape in the Pega flow. This shape refers to an activity with the usage type which is selected as a Utility.

* There are several usage types for an activity such as Utility, Connect, Assign, Notify, or Route.
The Utility is used when you want to call activity in a flow.
Following are the different types of layout available in Pega :
 
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.
Following steps must be followed to create a dynamic layout in Pega :
 
* Look for and open a Section form that already exists.

* Expand the Structural list on the Design tab, then drag the Dynamic layout onto the work area.

* Click the View properties icon in the Dynamic layout header.

* Set the layout format in the Properties window in either of the following ways:
* Choose one of the predefined formats.
* Select Other and then specify the custom layout format in the adjacent field to use a skin-defined custom layout format.

* Select when you want the Dynamic layout to appear in the Visibility field in either of the following ways:
* Choose one of the pre-defined options.
* Select Condition (expression) and then the Open condition builder icon to construct your own condition.

* Submit the form.
24 .
What is the RuleSet in Pega?
In Pega, the RuleSet is a collection of rules of business that defines an instance. The RuleSet is an essential subset of PegaRULES that is necessary to reference instances in the database.
Following are the key advantages of case management in Pega :
 
* It can improve the processes of case management with holistic support.
* It also increases the efficacy of case-flow for automatic and dynamic responses.
* It ensures consistency and removes errors with context-based and real-time management.
* It is time-efficient and saves time, costs and effort needed to implement case management.
The system adds entries it finds from the following sources in the order listed. The system adds entries it finds from these sources in the top of the list.
 
Requestor : (Data-Admin-Requestor class) — Usually this adds the RuleSets named Pega-RULES, and Pega-IntSvcs and a version or version prefix for these.
 
Division : As referenced in the Operator-ID instance.
 
Organization : As referenced in the Operator-ID instance.
 
Access Group :  As referenced in the Operator-ID instance.
 
Ruleset Versions : Prerequisite RuleSets and Versions to those already compiled.
 
Operator ID : If this user has the ability to check out rules, the personal RuleSet (named the same as the Operator ID key) is added last. It is also called a private ruleset.
The declarative rule is an instance of a class derived from Rule-Declared. 
 
* They allow for automatic processing of Property values.
* No need to be called explicitly.
* No need to run in a sequential fashion.
* The system manages re-evaluation when it detects a change.

The declarative rules in Pega are.
 
* Rule-Declare-Expressions. 
* Rule-Declare-Index.
* Rule-Declare-Trigger. 
* Rule-Declare-OnChange.
* Rule-Declare-Constraints.
Decision Table :
 
* The logic implemented in the decision table is if, else if condition.
* In the decision table, if the first condition is true, it will not check the remaining conditions/if the first condition is false, then only it will check the next condition.
* For simple logic, we can go to the decision table.

Decision Tree :
 
* The logic implemented in Decision Tree is if, if condition.
* In a decision tree, if the first condition is true or false, it will check all conditions and it will return results.
* For simple logic, we can go for a decision tree.
Key differences between obj-open and obj-open-by-handled in Pega:
 
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.
 
OBJ-open-handle : In OBJ-open-handle, you have had to pass the pzInskey as an instance handle. This method opens only one record at a time, and it also opens the object by the handle to the pzInsKey value.
30 .
How can you save the instances of a class in a particular database?
We can save the instances of a class in a particular database by creating a separate database table to the working class within a DB or the external DB.
Comparing Feature Pega BPM Appian BPM
Application Pega BPM is used to develop applications without hard coding. Appian BPM requires work automation of enterprise with data management.
Latest Version The latest version of Pega BPM is Pega - 7.2. The latest version of Appian is Appian - 18.1.
Integrations Supported Pega BPM supports Data Collection Systems and Various CRMs Appian BPM supports only Compatible Datasheets.
Supported OS Pega BPM supports Windows, Linux, Mac, and Web-Based OS. Appian BPM supports Windows, Windows Mobile, Android, iPhone, Mac, and Web-Based OS.
Customer Types / Mainly used in Pega BPM is mainly used in medium and large businesses. Appian BPM is mainly used in small, medium, and large businesses.
Obj-list : Retrieve to a page, read-only, a selected set of properties Important fields Obj-List
 
RequestType : The Type of the browse; allows different processing or sets of properties to be defined.  Defaults to Standard.  Key-part to the Rule-RDB-SQL instance.
 
Access : An indication of the database package used to access this table, from the INI file (currently ODBC).  Key-part to the Rule-RDB-SQL instance.
 
ClassName : The object class on which the browser is performed.
 
Rdb-list : To Retrieve external Relational Database List.
 
Important fields in RDB-List
 
PageName : Page Name indicating where the results will be put
 
ObjClass : The object Class to List.  When used with the RuleObjList parameter, this is the class of the list to use.
33 .
In Routing activity what is the default property used to route the object
pxRouteTo=Param.AssignTo =” workbasket name” for work basket .s
 
For work list :
pirouette =Param.Worklist=”true”   &&Param.AssignTo =” pxRequestor.pyUserIdentifier”    for work list.
Preflight : Starts the Application Preflight tool, which reports warning conditions on the rules in your Application RuleSets. These may indicate guardrail compliance issues, potential performance issues, accessibility status, or other notable conditions.
 
– 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.
 
The standard decision tree rules Embed-Warning.pxWarningDetails controls whether warnings of a specific type are reported in the Application Preflight tool. By default, all are reported; you can override this decision tree rule to choose which to omit. This decision tree tests the property pxWarningType, which can have values indicating the source of the warning, such as:
 
* Java - an activity contains a Java step
 
* API 02 - an activity uses the Version 3 PublicAPI
 
* WriteNow - An activity step includes a method with an immediate database writes operation rather than a Commit method.
HashStringMapactivityKeys = new HashStringMap();
activityKeys.putString(“pxObjClass”, “Rule-Obj-Activity”);
activityKeys.putString(“pyClassName”, workclass);
activityKeys.putString(“pyActivityName”, “HistoryAndAttachments” );
tools.doActivity(activityKeys , workpage, tools.getParameterPage() );
Or you can use osafeURL to call an activity
 
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() );
Access Group :
 
Access Group is used to restrict access to our application’s functionality. To accomplish varying levels of access control, we can create multiple access groups for the same application.
 
An access group decides on the following :
 
* After logging in, users can access the portals.
* The roles, or privileges, that users have access to.
* Advanced parameters are applied to new rules, such as the default rule-set name and version.

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
 
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.
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.
ClipboardPageworkpage = tools.findPage(pagename);
String  propername = workpage.getProperty(“.pxResults.Risk”).toString();

Or

String  propertyname= tools.findPage(“WorkListPage”).getProperty(“.pxResults.Risk”).toString();
40 .
What are Declare Triggers in Pega?
Declare Triggers are used to run an activity when instances of a specific class are created, updated, or deleted in the DataBase. Declare Triggers are always Forward Chaining.
The most important debugging tools available in Pega are :
 
* SMA
* PLA
* Tracer
* Clipboard
42 .
What is the prediction studio in Pega?
In Pega, the prediction studio is the studio used for building machine learning models for text analytics, predictive, and adaptive models.
Spin-off shape ( ) onto the flow : 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.
 
the Split/Join shape ( ) onto the flow : 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.
 
Split-ForEach shape ( ) to any locations : The Split-ForEach task provides a form of searching or enumeration over the pages in a property. Use a Split-ForEach 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.
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 :
 
* Structure of the page
* Object Type of the page’s content
* Edit Mode supported
* Scope of the data page
When two or more actions try to update a case at the same time, the most recent action may overwrite data written by the prior action. Overwrites can cause data corruption or loss, causing delays in case processing and possibly resulting in an inaccurate case resolution. If an application supports several users at the same time, a case locking strategy is critical for data integrity.
 
In Locking, we configure an appropriate locking technique for each case type to avoid data corruption or loss due to overwrites. Pessimistic locking and optimistic locking are two solutions that Pega Platform enables to balance the need for user access with the necessity for data security.
 
Pessimistic Locking :  When an application uses a pessimistic locking approach to open an object, it uses an exclusive lock. When a person or a system opens an object, they have exclusive access to it until the application unlocks it. Other users are unable to edit the item while it is locked.
 
For example, an underwriter examines an open life insurance claim to determine the amount of benefit that a claimant is entitled to. As the underwriter collects evidence and updates the case, a complex claim may necessitate extensive computations and referrals to third parties, and any additional modifications may override claim values and generate an inaccurate payout to the claimant. Apply a pessimistic locking approach in this situation to prevent other users from overwriting data when the underwriter updates the claim and changes the payout amount.
 
Optimistic Locking :  When an application uses an optimistic locking approach, it does not use an exclusive lock when opening an object. Instead, the item can be opened and edited at any moment by any user or the system itself. Before making any modifications to the item, the program checks to see if it has changed.
 
A manager, for example, may need to evaluate the most recent data for a given service request instance. A case worker may need to update the case at the same time as the manager does not need to update any information. Apply an optimistic locking approach in this situation to prevent the manager from locking the case and preventing a case worker from completing an assignment that would push the case toward resolution.
46 .
What is the Declare Index in Pega?
Declare index is a rule that exposes aggregate properties like List, page, or Group for reporting purposes. They are a part of the system admin category.
47 .
How to move code from development server to test server?
Create a new instance for product category, in that category we have to provide rule sets and rule set versions create zip file and moves to test server.
Constraint is a declarative rule which gets called automatically whenever invalid value entered by the user and show the error message according to ur logic, unlike constraint validation is not a declarative rule ad u need to call it from say flow actions/activity etc…it’s also used for validation.
Following are the different kinds of joins available in the reports in Pega :
 
* Inner join
* Outer join
* Right Outer join
* Left Outer join
50 .
What do you understand by a WSDL file?
WSDL stands for Web Service Description Language. This is a description language written in the XML format, and it is a standard for defining the functionality of a Web Service.
In Pega, a Data-Admin-Requestor instance defines a requestor type. The BROWSER requestor type indicates the characteristics of interactive user connections, such as guest connections, utilizing Internet Explorer or another web browser. Agents employ the BATCH requestor type for background processing. Pega Platform comes with four requestor types for the system name we specify during installation and a reserved requestor type prpc.BROWSER for exceptional cases.
 
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.
 
Following are the different requestor types in Pega :
 
Application : The application requestor type is used by listeners and external client systems to access the Pega Platform, such as through a service request (other than JSR-168 requests using Rule-Service-Portlet rules). Requestor IDs that begin with the letter A are used in requestor sessions that use this requestor type instance.

Batch : The batch requestor type is used by listeners, services, agents, and daemons executing background processing. The requestor ID for requestor sessions using this instance begins with the letter B. All BATCH requestors have access to the PRPC.

Browser : The browser requestor type is used for accessing the Pega Platform portal via a web browser via HTTP or HTTPS or from a browser displaying a Pega composite application. The requestor ID for requestor sessions utilizing this instance starts with the letter H.

Portal : The portal requestor type is used in conjunction with Service Portlet rules for HTTP access as a portlet. The requestor ID for requestor sessions utilizing this instance starts with the letter P.
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.
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 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.
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.
 
The features of PAL includes the following :
 
* 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.