PEGA INTERVIEW QUESTION & ANSWERS

What is difference between default locking and optimistic locking?

Default locking stops two users working on the same case or two child cases of a Parent parallel by two users or  a Parent and child case by two users parallel at the same time.

Optimistic locking will allow two users to work on the same case or two child cases of a Parent parallel by two users in perform mode. But the recent updates commited to the case by the first user notifies the second user while he is submitting or commiting his changes to the case and ask him to refresh the case.

But in this two options we have the option to choose whether to lock the paren
t or not lock the parent while performing on the child case.

Q) Difference and relation between Work Class and data Class

Ans) A work class typically describes a Work Type, and pattern inherits from Work-. What this means is that all work classes inherits common Work- properties like pyStatusWork, pxUrgency, pyID etc. So, most often a class is created as a work class to describe some form of "work" to be instantiated and completed, e.g. New Purchase Order.

A data class is typically used to describe the data model, and can be used for interfacing with the data base. It pattern inherits from Data- and will contain properties common to this class. Data classes are also useful for describing the structure of your work classes' Page mode properties. These data classes may or may not interface directly with the database. If not, they can be created as an abstract data class

PRPC provides us different types of layouts as follows:

1     Dynamic Layout: Brand New layouts in Pega7

2    Smart Layout

3     Repeating Layout

4    Column Layout

Free form Layout

è Every section can have any number of layouts

è Every layout can accommodate sections in it

è Every section should have minimum one layout

è In Pega7 – HTML5 code is generated for UI, HTML code is generated earlier to Pega7

è Because of HTML code UI will not be compatible with other devices / browsers

Rule resolution

Rule resolution is the search algorithm that the system uses to find the best or most appropriate ruleinstance to apply in a situation.

Rule resolution applies to all but a few rule types — classes that inherit from the Rule- base class. Rule resolution does not apply to instances of classes derived from the Work-, Data-, or any other base class.

While the rule resolution algorithm is fast and invisible, it is important to understand how it operates. As you create applications, make your choices of values for key parts based on how you want rules to be found by rule resolution.

An in-memory rule cache helps the rule resolution process operate faster. If the system finds an instance (or instances) of the rule in question in the cache, it accepts what is in the cache as the candidate rules and skips many steps in the resolution process (see below).

The benefits of rule resolution include:

• Rules can be shared across applications and organizations. Sharing and reuse are major benefits of object oriented software development.

• Rules defined at a higher level can be overridden by more specific rules defined at a lower level. While this dilutes the sharing benefit, it provides often needed flexibility while bringing visibility to exceptions.

• Rules can have multiple versions, even within one ruleset, and security rules control which users see and execute which versions. This facilitates application evolution, testing, and patching.

• One Pega 7 Platform system can host multiple applications, multiple organizations, and multiple versions of one application with minimal concern for conflicts and interference.

• Applications can be developed independently from other applications, yet all can depend on common rules that are locked (and so won't change).

Overview

The inputs to the rule resolution process are:

• The key parts of a rule instance being sought, such as its Applies To class and name

• The user's ruleset list, assembled when the user logs in

• The class hierarchy — the structure of parent classes and subclasses below the ultimate base class

• The user's access roles and privileges held, determined by the access group

• Security and access control rules, such as Access of Role to Object rules and Privileges

• Rule availability — which rules are available rule, blocked, final, withdrawn, or not available

• Whether time and date limitations affect which rules are available for this session

• In some cases, the value of a circumstance property

The output of the resolution process is the first rule found that matches all the criteria. (Sometimes no rule instance is found, and execution stops.) The system then executes the selected rule. Often this causes one or more additional rules to become needed. These are also found by rule resolution.