What is pega ?
Pega is a BPM tool. With the help of pega we can create application much faster rather than traditional coding techniques.
What is Pega express?
Pega Express is an agile approach that uses design thinking practice to capture the customer journey and quickly deliver an (MLP) Minimum Loveable Product release.
What is Microjourneys,Personas,and channels?
Microjourneys-Microjourneys are a small piece of the overall customer journey & focus on accomplishing a specific goal.
Personas- Determine who interacts with the application.
Channels- Determines how a persona interacts with the application.
What is workspace and types of workspace with definition?
A pega provides 4 role based authoring workspace, reffered to as studios.
– App Studio – A low code workspace designed for business architects, citizen developers and System architects.
– Dev Studio – A low code workspace with advanced configuration options for Technical team members as well as system architects.
– Prediction Studio- Used by data scientists and business decision makers. e.g AI, NBA
– Admin Studio- Managed by IT staff and system administration. e.g- DevOps
What is case, case type , case life cycle, stage, process, steps ?
Case- Case is a specific instance of case type.
Case Type- Case type is an abstract model of business transaction.
Case Life Cycle- A case life cycle is a complete cycle of business transaction.
Stage- Stage contains series of processes and steps. A stage indicates a transition of work from one department to another.
Step – A Step is an action or task performed by the users or system.
What is SLA? Goal, Deadline and Passed deadline?
SLA- stand for Service Level Agreement. It establishes a work completion deadline.
Goal- It is ideal amount of time in which the work should be completed.
Deadline- Deadline is the maximum amount of time in which the work must be completed.
Passed Deadline- Passed deadline start when the deadline will be finsh.
What is Rule, and Ruleset ?
Rule- Rule is a set of instructions.
Ruleset- Ruleset is a container of rules. Pega provides default ruleset when we create an application.
What is Rule Type?
The rule type determines the type of behavior modeled by the rule.
Eg.- When we create a Section under the flowaction then flowaction is the rule type of that section.
What is Access Group?
It is a rule through which you will get access to the application and all the rules.
What is Access Roles?
Access Roles categorise user’s to work according to their job functions.
What is Validation type
Validate rule- It’s configured on data model, flowaction etc. Its a server side validation.
Edit validate rule- It is a client side validation.
What is Worklist, Workbasket, Sys-lock?
Worklist- Worklist is a container of tasks. It refers to a specific user.
Workbasket- Workbasket is a container of tasks. It refers to a set of users.
Sys-lock- Only one user can work on a particular assignment. If other want to work on it. It will give an error. eg- Someone is already working on it.
What is Routing?
When there are 2 or more users work on a case then we use routing to assign a particular work to a particular user.
Types 1. Current 2. Specific User (Worklist) 3. Workqueue (Set of Users) 4. Business Logic (If, Else) 5. Custom (Expression, Activity)
Decision table and tree difference?
In decision table use expression builder and In decision Tree we don’t have an option.
In decision table we have a Checkbox of Evaluate all rows. In tree don’t have.
If we have limited properties then we use Decision Table and If we have multiple properties or complex requirement then we use Decision Tree.
What is Map Value?
Map Value is a rule that converts one or two input values to calculated results values using a matrix to look up the result.
What automation shapes and advanced shapes?
Automation shapes- Automation Shapes automatically perform the task without user interaction.
1. Send Email
2. Change to a Specific Stage
3. Change to Next Stage
4. Create Case
5. Wait – Pause and resume the flow for a specific time.
Advanced Shapes-
1. Split Join- To define 2 or more sub-processes that can run independently but in parallel later they can rejoin.
2. Split for-each – Using a Split for each flow shape, we can call one sub-flow, and pass a pagelist parameter.
Basic Pega CSA Interview Questions
What is Data Type?
A Data type is set or related fields and its properties.
What is Data Object?
A data object is a template for describing an entity, such as a person or an item, by grouping a set of related fields.
What is Data model
The data model refers to a set of rules that work together to populate the data in your application.
What is Data Page?
Data Page is used to reteive the data from data source.
Optional Action
Optional actions are the actions which can perform additionally without interupt the primary path.
Local Action
The option local action allow you to update the assignment but doesn’t advance the flow.
Flow
It is a collection of pega shapes describing the process within a stage.
Flow Action
A flow action is that how user interact with the section to complete the form.
What is Locking?
Pega Platform locks the case to prevent other users from applying any changes.
1. Allow one user (Default) – Only one user can work at a time.
2. Allow multiple users (Optimistic) – Multiple users can work on the same time but Who will submit first their changes will reflect on the server and other users will get a popup screen and ask them to refresh the page and their changes maybe lost.
What is Clipboard?
Clipboard is a shared memory, shared the data from the data base.
What is Tracer?
Tracer help in troubleshooting.
What is Estimator tool?
We can estimate the development effort of one or more releases of your application.
What is Accessibility Inspector?
It allows us to identify & rectify accessibility issues within the application
What is Child Case?
Whenever we have a complex business scanerio then we use child case.
What is Duplicate Case?
Whenever the same data value in the case then it’s called duplicate case. There are 2 conditions basic and weighted conditions.
What is Page List and Page Group?
Page List – It’s an Order list. Page List Properties are useful for holding the list of data.
Page Group – It’s an Un-Order list. Page Group Properties referenced by a string subscript.
How many applications can be there in an access group in Pega?
In Pega, the number of applications that can be included in an access group is not limited. An access group is used to control access to applications and their associated content, such as cases, work items, and data instances. Access groups can contain one or more applications, and multiple access groups can be created to control access to different sets of applications and their content.
So, in theory, you can include as many applications as you want in an access group, but the actual number would depend on the specific requirements of your organization and the complexity of the access control rules.
What are the various decision rules?
In Pega, there are several types of decision rules that can be used to automate decision-making processes in applications. These include:
Decision Table – A tabular representation of a set of conditions and their corresponding actions.
Decision Tree – A graphical representation of a decision-making process, where each node represents a decision, and each branch represents a possible outcome of that decision.
Map Values – A type of decision rule that maps input values to output values, based on a set of conditions.
Scorecard – A type of decision rule that assigns scores to specific criteria or characteristics, and then calculates a total score to determine the outcome.
Decision Tree Wizard – A visual tool that allows users to create and manage decision trees, without the need for manual coding.
Method – A type of decision rule that defines a set of actions that are executed in a specific order.
If-Else – A type of decision rule that executes different sets of actions based on the evaluation of one or more conditions.
Switch-Case – A type of decision rule that executes different sets of actions based on the value of a single expression.
These are the most commonly used decision rules in Pega, and they can be used in combination to model complex decision-making processes within applications.
What are the validation rules?
In Pega, validation rules are used to enforce constraints on data inputs and to ensure the data entered into an application is complete, accurate, and consistent. Some of the common types of validation rules in Pega include:
Required field – Ensures that a specific field must have a value before the form can be submitted.
Length – Validates the length of a field’s value to ensure it falls within a specified range.
Format – Validates the format of a field’s value to ensure it matches a specific pattern, such as an email address or phone number.
Range – Validates that a field’s value falls within a specified range of values.
Compare – Validates that two fields have the same value.
Custom – A user-defined validation rule that can be created using a Java or JavaScript expression.
Regex – Validates a field’s value using a regular expression pattern.
Unique – Ensures that a field’s value is unique across all instances of the same data class.
These are the most commonly used validation rules in Pega, and they can be used to ensure data entered into an application is consistent and accurate. Validation rules can be defined at the field level or at the form level, and they are automatically executed when a user submits a form.
What are pre-processing actions in Pega?
In Pega, pre-processing actions are actions that are executed before the main flow of a process is executed. They can be used to set up the environment for a process, to prepare data for processing, or to perform any other necessary tasks that must be completed before the main flow of a process can begin.
Pre-processing actions can include:
Initialize Variables – Setting values for variables that will be used in the process.
Retrieve Data – Querying the database to retrieve data that will be used in the process.
Perform Calculations – Performing mathematical operations or other calculations that will be used in the process.
Validate Input – Validating input data to ensure it is complete and accurate before processing begins.
Run Rules – Running decision rules, such as Decision Tables or Decision Trees, to determine the path of the process.
These are some of the most common pre-processing actions in Pega, but any actions that need to be executed before the main flow of a process can be performed can be included as pre-processing actions. By executing these actions before the main flow of a process, it helps to ensure that the process is executed in the most efficient and accurate manner possible.
What are post-processing actions in Pega?
In Pega, post-processing actions are actions that are executed after the main flow of a process has been completed. They can be used to clean up the environment, to persist data to the database, or to perform any other necessary tasks that must be completed after the main flow of a process has been executed.
Post-processing actions can include:
Persist Data – Saving data to the database, such as updating a record or creating a new record.
Update Variables – Updating the values of variables used in the process.
Send Notifications – Sending notifications to stakeholders, such as emails or text messages.
Run Reports – Running reports to summarize or analyze the data processed by the process.
Log Process Information – Logging information about the process, such as the time it took to complete or any errors that occurred.
These are some of the most common post-processing actions in Pega, but any actions that need to be executed after the main flow of a process can be performed can be included as post-processing actions. By executing these actions after the main flow of a process, it helps to ensure that the process is executed in the most efficient and accurate manner possible, and that any necessary clean-up or follow-up tasks are performed.
Difference between Process Flow and Screen Flow?
| Process Flow | Screen Flow |
|---|---|
| 1. It can create a work object. | It can’t create a work object. |
| 2. For every assignment we see submit button, which means when an assignment is completed we can’t navigate back. | For every assignment, we get the next, back, and finish buttons available. We can navigate between assignments. |
| 3. Harness can be called on each assignment. | The harness can be called on start shape. |
| 4. Routing is available on assignment shape. | Routing is available on Start shape. |
| 5. Flow action can be called on assignment shape onward connector. Here we can call multiple flow-action per assignment. | Flow actions can be called on the assignment shape itself only one flow action per assignment is possible. |
Scenario Based Pega CSA Interview Questions and Answers
Where we configure SLA
We can configure SLA on Case, Stage, Process, Step (Flow).
Where we configure Decision Table, Decision Tree and Map Value?
On Decision Shape
Where we configure Access Group
First click on login button and select operator option and open the profile tab in right apply Access group.
Where we configure Roles
First go to access group then Click on Access group and access group is active one at the time then click on Target Icon and go to the Availability Roles then give the role which you want.
Where we configure Portals
First click on login button and select Access group option and open the Defination tab in add portal.
How many access group an operator can have?
Multiple and at a time he/she can access only one.
Company build a application for america and the same application want to build for the India, then which type of application layer will you use?
We will use implementation layer because we can use the ruleset which is required for the india application.
How to route a step to a specific person?
1. Create Persona in App Studio (Manager)
2. Create Channel and then delete existing channel (ManagerPortal)
3. Goto Dev Studio then on bottm left corner click on profile icon and then click on Operator
4. Click on Save as to copy the same operator and change the name of the Operator (ManagerOperator)
5. Go to the Newly created operator and Access Group section then choose the desired Persona (eg: KYCApp:Manager)
6. Then Click on the Target icon then choose the desired portal (e.g:ManagerPortal)
7. Then Go to Case Type then choose the step which you want to route
8. Choose Route to Specific
9. Enter Username (ManagerOperator) then Save
10. After that login with Newly Created operator (E.g: ManagerOperator) check their worklist (Task added there).
