Pega Interview Concepts on Application Architecture
What is the class group?
- A class group is a configuration as part of the class definition that creates a dedicated database table.
What is the work pool?
- Work pool is nothing but a class group that is configured as part of the access group. It is the set of allowed work items or cases that you can work within an application. When you have multiple work pools, you can switch between the work pools from the application menu.
What happens if we don’t define the work pool at the accessgroup level?
- The logged-in operator with that corresponding access group cannot see the list of classes in the application explorer and cannot create cases from any of the portals.
How you will inherit two PEGA Frameworks into an application?
- From PEGA 7.2, we can add multiple built-on applications as part of the application definition. This concept can be used for the organisation framework application or to the direct implementation application.
- Previous to PEGA 7.2, the concept is single built-on with multiple application instances to inherit multiple frameworks.
How you will handle the versioning mechanism for the production ruleset?
- As the application users update the delegated rules, for the production rulesets — leave the “Use Checkout” checkbox to blank in the ruleset security definition
- The same concept applies to reporting production ruleset as well
How does the Locale work in PEGA?
- In the operator rule form, we need to define the operator locale. If the operator locale field is blank, then the system uses the browser locale.
- Locale is useful in displaying the dates, currencies, and the locale-specific field values in the application.
How is the estimation works as part of the PEGA Application?
- Sizing wizard provides the way to do the project estimations. It is navigated through Designer Studio -> Application -> Tools -> Sizing. Sizing is done at the application level with the respective project methodology. The project methodology includes “Scrum” and “Iterative Waterfall”.
- Scrum Methodology: Provides the list of tasks that are getting planned for each sprint.
How do you extend the class structure when you have multiple built-on applications?
- It is a bit tricky question. The implementation application layer is having multiple built-on applications. If we want to extend the framework or built-on application class functionality then it is to have via direct inheritance. It is not required to have all pre-defined case types for the built on application case types.
- For Example: Refer to the PEGA Learning Application: PEGACSSample is built on Customer Service Application.
- Any custom case types are only created in the PEGACSSample related rulesets. Other case types and functionalities are used as it is of the PEGA provided Customer Service Application.
Application stack usage
There are different scenarios of application stack usage:
Use case 1: Multiple applications using the same PegaRULES version
Each built-on application is processed by using a depth-first algorithm.
Use case 2: Multiple applications using different PegaRULES versions
The numerically highest available version of PegaRULES is used in the application stack list.
Use case 3: A duplicated application with different versions
Even though the application with the lowest position in the tree list is retained, the application stack list uses the numerically highest available version for the duplicated application.
Use case 4: A duplicated application with multiple branch points
Duplicate applications with the same version use the lowest positioned application in the tree list.
Use case 5: An application with branches
An application can branch its own ruleset or the rulesets for the built-on application at design time, but cannot branch the ruleset for the built-on application at run time.
