- 1) What is Pega? …
- 2) What is a harness in Pega? …
- 3) How to create a work object in Pega? …
- 4) What is case management in Pega? …
- 5) What is PRPC in Pega? …
- 6) What is an assignment in Pega? …
- 7) What is ruleset in Pega? …
- 8) How to create workbasket in Pega?
1) What is a Work Group? What is the primary function of a Work Group from a business perspective?
Ans: A workgroup is a logical collection of operators having a common supervisor i,e. a workgroup can identify a user who is a supervisor and a set of workers and workbaskets that report to that supervisor.
Use – For the supervisor of a workgroup, the My Group area of the Process Workspace provides quick access to the work lists and workbaskets associated with the group (In the workbasket tab of workbasket data instances we enter the name of a workgroup that uses the workbasket. This field determines which workbaskets appear in the View Queue list on the My Group area of the Process Work workspace for managers). Also, workgroups facilitate for better monitoring and reporting of tasks on the Monitor Activity workspace.
assignment from the workbasket to process the assignment. The “contents” of a workbasket is a set of assignments awaiting processing, ordered in decreasing urgency, similar to the contents of a worklist.
Few other important things to keep in mind about workbaskets are (If only the specific question is asked then answer as below):
An application can automatically route assignments in a workbasket to users based on work schedules, due dates, skills, workloads, and other factors.
** During execution of a flow, a router task can choose which workbasket is most appropriate to receive a newly created assignment.
** The relationship between workgroups and workbaskets is one-to-many i.e. one workgroup can be associated with multiple workbaskets. (In the workbasket tab of workbasket data instances we enter the name of a workgroup that uses the workbasket. This field determines which workbaskets appear in the View Queue list on the My Group area of the Process Work workspace for managers).
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: The primary purpose of an access group is to make a set of RuleSet versions available to requestors.
The local customization RuleSet name and RuleSet version. These usually are defaulted when this user creates a new rule instance.
5) What is the difference between a Workpool and a Work Type? Can a workpool belong to another workpool? Can a worktype belong to a work pool?
Ans: Different work types (classes derived from the Work- base class) are grouped into one class group and when this class group is added to auser in his access group, the user can work on each work type of each class group added. Class groups so added are called as Work pools. A workpool cannot belong to another work pool. Multiple work types can belong to a work pool
** Class Group – A class group instance causes the system to store the instances corresponding to two or more concrete classes that share a common key format in a single database table. The name of the class group is a prefix of the names of the member classes. Class groups and work pools are basically the same things and class groups added to an access group are called work pools.
Ans: Case Management involves managing work that, for processing and reporting purposes, differs from classic BPM work objects. Cases may involve:
5. Case Management design is governed by the Case Type Definitions gadget, which is used to configure the following case type and work processing configurations. Using the gadget, you can:
7. Add entirely new case types: Creates Class and Case Type rules, provides standard starting flows for the new case type.
needed”. Declarative rules will be in force automatically and hence you need not call these rules explicitly. The primary benefit of declarative processing is that the system controls when computations are processed. Some examples are :
** Keep in mind the concept of forward chaining and backward chaining and out of the above rules only Declare Expressions can use both FW Chaining as well as BW chaining. Rest all use only forward chaining.
Ans: For Migration of rules from one environment to another we create a ZIP file containing rules from one or more RuleSets. For this, we use a product rule (Rule-Admin-Product rule type) or a product patch rule (Rule-Admin-Product-Patch rule type) and then import the zip file into the target environment. Also, we can use the export gadget to create the zip file for rulesets.
** The data instances (such as access groups, operator ids etc.) can be included in the product or patch rules.
10) 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.
11) What is the concept of database table mapping? Why do we do that? Do you do any additional table to class mapping (apart from the existing mappings) during development?
Ans: In database table mapping a database table instance associates a class with a relational database table or view, in the PegaRULES database or an external database. This is done to map a class to a database table and thus store the instances of the class in the table. Yes, we have done an additional table to class mappings for several application specific classes during development.
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.
Ans: Yes it is possible to call one section from another. A section rule can appear within another section, panels and containers within a harness rule, or within a layout cell.
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.
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.
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.
Identify the RuleSet and version to contain the generated rules — classes, properties, connector rules, activities, and so on.
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.
Ans: When your Process Commander application uses a SOAP connector to interact with a Web service, you set it up by using the Connector Accelerator. The Connector Accelerator imports the WSDL of the Web service and generates rules as follows:
19) What are Connect HTTP rules used for and how are they different from connect SOAP rules?
These rules are used when you want your PRPC application to send XML or string data (regular text) as messages to an external system without having to comply with standards messaging protocols such as SOAP.
The rules currently work very similar to the SOAP rules but, do not create or consume WSDLs, nor can they be generated using the integration wizard. Use these rules instead of custom Java code for making HTTP requests to external systems.
Purpose – The HTTP integration interface supports interactions between your Process Commander applications and other systems through HyperText Transport Protocol.
Use HTTP connector rules when you want your Process Commander application to send XML or string data (text) as messages to an external system without the need to comply with messaging standards or protocols like SOAP.
20) How can we achieve reusability in Pega? Typically what kind of rules go in at the enterprise level and what rules would you create at the implementation level?
Ans: We can achieve reusability in Pega by creating rules which are to be used by different applications within an organization at an enterprise level. Typically rules that are generic and are to be used by multiple applications such as connectors and services go in at the enterprise level and rules which are specific to an application such as flows and activities go in at the application level.
Ans: Many computer input procedures are most effectively handled by presenting a user with a series of simple forms that each require only one or a few questions to be answered. After submitting a form, a user receives with another simple form (with more questions) that may depend on previous answers. At any point, users can backtrack to review, or change, previous answers.
Three runtime presentations are available to allow users to navigate within a screen flow execution at runtime:
Completed tasks (that are designated as entry points) appear as blue rectangles in a breadcrumbs control. A user selects a rectangle to return to that task.
Tabs for both completed and future tasks (that are marked as entry points) appear at the top of the action area. Completed tasks contain with a check mark.
No breadcrumbs control or tabs appear. A user can return to a completed task that is marked as an entry point when the button appears.
Ans: No. However, if the application needs a column corresponding to embedded property values, the values can be copied to the top level or exposed indirectly through instances of an Index- class and then used as criteria of a report.
Ans: An agent is an internal background process operating on the server that runs activities on a periodic basis. Agents route work according to the rules in your application; they also perform system tasks such as sending email notifications about assignments and outgoing correspondence, generating updated indexes for the full-text search feature, synchronizing caches across nodes in a multiple node systems, and so on.
Agents are defined by Agents rules (Rule-Agent-Queue rule type). Agents are enabled and are scheduled through Agent Queue data instances (Data-Agent-Queue class). The pattern (periodic/recurring) and interval (amount of time, in seconds, that the agent waits before restarting) for the Agent rule is configured in the Agent Queue data instances.
Author Bonjour. A curious dreamer enchanted by various languages, I write towards making technology seem fun here at Asha24.
Pega interview Questions – Case Management and Flows
Most Frequently Asked Pega Interview Questions
Ans: 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 DevOps 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.
Want to Become a Master in Pega? Then visit here to Learn Pega Training
Ans: The different types of standard classes available are.
Ans:
Ans:
Ans: The following are the steps implemented in creating a work object in Pega.
Ans: Direct Capture Object is an apple dev tool that includes.
Ans: It is the instance of Rule-Obj-Service Level Rule type. It can be added to assignment and work objects.
Service level contains two intervals of time as Goal and Deadline. It indicates the expected time for the assignment and time to resolve the work object. If an assignment isn’t completed before the time limit, the system can automatically raise the assignment and cancel the entire flow, and so on.
If you want to Explore more about Pega? then read our updated article – pega Tutorial
Ans: The steps to trace SLA in Pega are:
Ans: The following are the different layouts types available.
Ans: A RuleSet in Pega 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.
Ans: Yes, commit is used to save the data permanent in the DB.
Ans:
Ans:
Ans: An access group in Pega is an example of a Data-Admin-Operator-Access Group class that creates a set of RuleSet for the requestors. The developer defines access groups and assigns them to different users.
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
Ans:
Ans: It is the instance of the Rule-Obj-Flow Action rule type. It is the one category in UI specifying the choices to the user performing assigned work objects.
Local FA: If action is finished, the work object returns to the same level.
Connector FA: If action is finished, the work object moves to the next level.
Ans: 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.
Ans: The declarative rule is an instance of a class derived from Rule-Declared.
The declarative rules in Pega are.
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 Obj-Validate method with Rule-Obj-Validate rule.
Property-Validate:
This method is used to impose restrictions on property value. Use the Edit validate rule along with 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 the future application.
Ans: The advantages of Pega case management are.
Ans:
Ans:
Decision Table:
Decision Tree:
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.
Explore Pega Sample Resumes! Download & Edit, Get Noticed by Top Employers!
Ans: It is an Interface that shows up for the client either developer or an end User and entry can be arranged in Access Group.
Example: Developer entry, chief gateway, client entryway, administrator entrance.
Ans: Locking is acquiring control over a work object before proceeding to perform any action on it and to ensure only a single user to perform actions on a work object at a time. There are two types of locking as stated below.
Ans:
Ans: Forward Chaining provides the automatic calculation of the property by executing the declarative rule when any one of the input property values is changed.
Example: If the Area property depends on the length and width property, then Forward Chaining causes the area property to be recalculated every time either length or width values change.
Ans: BackWard chaining provides the automatic calculation of the property by executing the declarative rule when the value is needed for the property, rather than when an input changes.
Example: If the area property depends on length and width property, the backward chaining causes the area property to be recalculated each time the area property is required.
Subscribe to our youtube channel to get new updates..!
Ans: The following are the steps that are implemented for declaring an index.
Ans: There are ten Pega guardrails as follows.
Ans: Agents are an internal background process operating on the server to run an activity. Agents are asynchronous and independent. They also perform system tasks such as sending email notifications and synchronizing caches across nodes. Activities they call run individually on their own schedule and one activity doesn’t have to finish another activity.
Ans:
Verify the above tag in the “prconfig” file. Verify if the value of the above tag is true or false.
Ans: A service level rule is an instance of the Rule-Obj-Service Level rule type. Each service level rule defines one or two time intervals, known as goals and deadlines that indicate the expected or targeted time for the assignment, or time-to-resolve for the work object.
If an assignment isnt completed before the time limit, the system can automatically raise the assignment, and cancel the entire flow, and so on
Ans:
Forward Chaining: It provides the automatic calculations of the property value by executing the declarative rule, when any one of the input property value is changed.
EX: If the Area property depends on the Length and Width property, then forward chaining causes the Area property recomputed each time either Length/Width value changes.
Backward Chaining: It provides the automatic calculations of a property value by executing the declarative rule, when a value is needed for property rather than whenever inputs change.
EX: If the Area property depends on the Length and Width property, then backward chaining causes the Area property recomputed each time the Area property is required.
Ans : Circumstance is the optional condition and enhancement of rule resolution alg. diff variations of the rules within the same version created for diff flavors suit for different situation. Circumstance works during the rule resolution, at run time system first find the rules based on class hierarchy then searches for a rules the requestors session needs, it compares the values of rule set, version, and availability to determine which rule executed.
Ans: Access Group controls the security basing on the job functions. It is instance of Data-Admin-Operator-Access Group. Various aspects that can be controlled through access group are default and available types of works (also called as work pools), Primary rule sets ( Access Control to rule sets), Assigned roles, Portal layout
Ans: Work list is an outstanding assignment waiting for a user to perform them. Work basket is an instance of Data-Admin-Workbasket class. Work object progress through a flow execution, the system creates assignment. Assignment may be created either with individual user or work basket
Ans: When action is finished work object returns to same assignment.
Ans: Rule-Declare-Expressions, Rule-Declare-Index, Rule-Declare-Trigger, Rule-Declare-On Change
Ans: ( obj-validate is we can do validations for multiple properties of a single work object) (Property-validate is only one property we can do validations for single work object) Mphasis
Ans: A workspace is an environment that provides particular features and tools.
Ans: One needed some tools to access Admin Studio; they are:
Ans:
In-app development, some cool new features are included :
Ans: A prediction studio is a dedicated workspace for data scientists to control the life cycle of advanced analytics models. The prediction studio consists of predictive models, self-learning or adaptive models, and text models.
Ans:
Ans: PRPC consists of four types of portals
Ans: The requestor type in Pega is the requestor that accesses the Pega platform like an external application, an internal background process, or a browser session.
Ans: In Pega, platform activities make process automation. In Dev Studio, activities contain a series of steps that perform in the given order to keep activities short.
Ans: A declarative rule is an instance of a subclass of the Rule-Declare class. They allow the automatic processing of values.
Ans:To resolve work objects using activity, we have to follow the steps they are:
First step: open the object.
Second step: set the correct ticket on your flow or click on Finish Assignment.
Ans:There are different ways to measure the performance of your application in Pega.
Performance analyser tool, DB trace, Autonomic Event Services (AES), and Alerts
Ans:By checking the Chain tracking tab, you can specify if an expression triggers f/w or b/w.
Ans:Pega applications typically use four standard harnesses to organise the content of user forms they are: new, perform, review, conform,
Ans: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.
Ans:Rule Resolution is a search algorithm the system uses to determine the most appropriate or the best rule to apply and complete the process. With automated rule resolution, one can save time and make sure you implement resources efficiently.
Ans:Yes, without exposing we can refer to the property in the display tab. We can’t refer to the property without exposing it in the criteria fields of the content tab.
Ans:No. we can not create Agent schedules manually.
The Agent Manager on our Process Commander system generates at least one agent schedule instance for each agent’s rule.
Ans:Escalation means any processing within a Process Commander application that causes high-priority work objects to become visible to users and managers and to be processed immediately. Escalation can occur through a service level rule associated with the flow and through background processing by the Pega-ProCom agent
Ans:RDB- Open method retrieves a single row of data from an externas database and then adds the retrieved data into a specified clipboard page as property values and names.
Ans:
The types of flow in Pega are
Ans: In the workspace, there are specialised functionalities and tools to work. With different workspaces, we can manage and develop our application. In the Pega platform, there are four role-based authoring workspaces called Studios
With the help of studios, we can enhance productivity and speed up the application process by providing role-based capabilities to users.
HTML Property rules appear in list view and summary view rules to define the appearance of values in reports.
List view is generally used for complex queries where sorting is required, and also, we can retrieve less information using Paging
To create agents or agencies, use the Create Agent and Create Agency
Collect Agent Information screen collects agent details
Rule Set name is the Agent name
An agent is an instance of Rule-Agent-Queue.
There are two types of validations are there they are
Pega – Case Management Interview Q&A
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.
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).
Explain about Work Object ID?
A work object ID is the permanent, external identifier of a work object.
If we do not specify a prefix (on the Details tab of the application rule), the Work-.GenerateID activity uses W- as the prefix and no suffix. The Work-Cover-.GenerateID activity uses C- as the default prefix. Conventionally, the F- prefix is used to identify folder work objects.
Where we determine the prefix and suffix of the Work Object ID?
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.
Cover:
Explain about Cover?
A cover is a work object in a concrete class derived from the Work-Cover- abstract class
A cover work the object is a parent to one or a few other related work objects.
Typically, one work party such as the customer party is present in the cover work object and present in all the covered work objects associated with it. The covered work objects are the children in a parent-child relationship.
A cover work object provides coordinate processing of related work objects. By default, the system prevents the resolution of a cover work object unless all of its “member” covered work objects are resolved.
How do we create the Cover Work Object from Activity?
In the activity, we are creating Work Object and Add to the Cover at a time by using the method AddCoveredWork.
AddCoveredWork Creates a new covered work object using the primary page data. This activity assumes the cover is already locked. Due to the above, Reason, we have locked the cover by using Activity Obj-Refresh-And-Lock.
This activity saves the newly covered work object on the deferred list.
How the Cover Work Objects are working?
For example, if a single customer request causes a user to create three separate work objects, these work objects may follow separate flows, be handled by separate departments, and not otherwise affect each other. The cover object provides a way to consolidate, view, and manage the outstanding service requests of this customer. After all, three covered work objects become resolved; the cover work object can be resolved.
Pegasystems Inc. is an American software company based in Cambridge, Massachusetts. Founded in 1983, Pegasystems develops software for customer relationship management (CRM) and business process management (BPM). Pegasystems specializes in the following industries: financial services, life sciences, healthcare, manufacturing, insurance, government, high tech, communications and media, energy, and utilities. The company announced in 1996 that it would be publicly traded on the NASDAQ stock exchange (PEGA). Since 2010, the company has acquired a number of companies including Antenna Software, Firefly, Open Span, MeshLab’s, and Chordiant.The Company’s core product is the Pega 7 software platform.
PEGA is a platform which provided a systematic approach to build and deploy process-oriented and rule-based solution and applications. Business Process Management, Customer relationship management, Decision management and case management solutions are some of the examples where process and rules are integral part of application development. What PEGA provides to a developer is a Designer studio which acts as an Integrated Development Environment (IDE) to build applications. The best part is this Designer studio is web based so a developer can work and create solutions from anywhere in the world.
Pega/PRPC is a popular rules engine and BPM tool from Pega systems that is gaining good market share among large corporations. Architects and developers build the Pega/PRPC instance while administrators and even select business analysts have the option of changing workflow rules during runtime. Infact, their motto itself is “Build for change”. The goal is to “eliminate software coding” and “automate manual work” to the minimum and build complex systems at the enterprise level with features right out-of-the-box.
That’s how it works in the utopia world. But in the real world, you need good developer support. So, the lesser the code, the closer you are to the goal of a true BPM tool. Software coding might be reduced drastically. But you still need people with a development background using inputs from Business Analysts to make changes or add functionality. Pega/PRPC is pretty expensive so they primarily target any corporation that can afford such a luxury.
FAQ
What are the important topics in PEGA?
Is PEGA Java-based?
- Describe a data object; group related data.
- Configure data types, create data objects.
- Identify and create calculated values.
- Make data available to an application; add data records to a data type.
- Integrate with external applications.
What is PEGA PRPC?
