Featured post

GetNextWork functionality in pega

What is GetNextWork in pega? Pega provided a functionality to get the most urgent assignment(task) for user to work on. This is configured o...

Pega - Real time Interview Q&A - 3

Define Flow and explain different types of flows available with an example?


Flow: Flow is graphical representation of business process that can be with Start Shape and ends at End Shape.

Created under: Process Category

Instance of- Rule-Obj-Flow

Call from activity with Flow-New Method

by using Sub Flow shape we can make call to the Sub Flow or Screen Flow

Types of Flows:

Process Flow

Sub Flow

Screen Flow

Process Flow:  Every Application Start form the Process Flow. Once the Flow started OW will be generate.  In addition, Generated WO is Travers through the Flow (every shape).

Sub Flow: Sub Flow well get started from Process flow.  Sub flow also creates the WO.

Ones the execution process of Sub Flow completed then the process control move on to Main flow.

Screen Flow: Used to present series of forms to user with Previous and Next options.  At any point of time user can go to previous form.

For Ex: Screen flow used to collect information from user with help Questioners

Screen Flow does not create WO.

We cannot start the work from Screen Flow because “Create New Object” option is disabled in the process tab of Flow.


Explain Inheritance in Pega

Pega Provides 2 types Inheritances to classes:

Pattern inheritance

Direct Inheritance

Pattern Inheritance:   In a class hierarchy lower level classes are, inherit the characteristic of high-level classes in a same hierarchy. This type of inheritance called as Pattern Inheritance.

By default pattern,Inheritance applied to every child class. We can disavow this inheritance also.

Directed Inheritance:  This is a Process of Inherit Characteristics of one class into another class by directly assign the class name in Direct Inheritance column.


Different Terms in PEGA:

Work list: Every operator has a Work list, which shows the assigned work to process.

Work Basket: Generally, Department will setup work Basket to pull the assignments by the users.

Work Group: is an organization structure and used when configure a Work Basket.

Workbasket and Work Group connected to each other.

Access Group: Operator ID pointed to an Access Group, which defines- Application, type of Portal and access role.

Work Parties: These people have interested to know the status of Work Object.

Classes: it defines the scope and applicability of rule, it does not hold/store the rule, and it can defines how the rules are stored in Ruleset.

Abstract Class: These are the generalize classes which cannot instanced, meant for reusability and end with “-”, Cannot connected with Table

Concrete Class: are specialized classed which can instantiated and connected to a Table

Business logic runs from the concrete class only.

Class Group: It is a combination of one or more Abstract classes and first concrete class in the application.

It inherits characteristics of classes: Work- and Work-Cover-


Explain Rule Availability:

1) Yes: If Rule Availability is equal to Yes, and then Rule is available to a particular set.

2) No/Draft Mode: If Rule Availability is equal to No/Draft Mode, and then Rule is not available to a particular set.

3) Final: If Rule Availability is equal to Final, and then Rule is not over write or change in a particular rule set.

4) Withdrawn: If rule availability is equal to Withdrawn, then Rule is not available to lower version and it is available in current and higher version.

5) Blocked: If Rule availability is equal to Blocked, and then Rule is not available to lower versions of that particular class and inheritance class.





No comments:

Post a comment