Temporary cases in pega

What is a Temporary case in Pega?

A temporary case is a case created in pega which doesn't have any ID and only be stored in a clipboard, not in the Pega database. Once it reaches the Persist Case shape it will be converted into a Permanent case and have pyID, case will be stored in the pega database.

Benefits of Temporary case?

Case locking in pega

What is the case locking mechanism in pega?

Pega case locking prevents conflicts when a user attempts to submit cases that are already updated, this is the "Default locking" strategy in pega. Allowing only one user to open the case and work while the second user tries to open the same case pega displays a locking message saying that the case is being locked by the first user. However, the second user still can open the case in read-only mode. When the first user opens the case, the case acquires the lock and by default, pega locks the case for 30 mins or until the user closes the case or submits the case whichever comes first.

Pega Activities complete understanding

To automate the process when there are no appropriate rule types available we can use activities. Activities contain sequential steps run one after another. Once all steps are completed control goes back to the rule that is called activity.

Global resource setting (GRS) in Pega

Global Resource Setting in Pega (GRS) allows referencing external system values, port numbers, addresses, and URLs.We can avoid using fixed text values in rule forms. Application moves to different environments before it goes live like Dev, QA, Staging, and Pre-prod.When we migrate an application from one environment to another environment, external system references such as End Point URLs, JNDI names typically changes depending on the environment. We cannot log into each environment and update the rules with correct values or settings by unlocking rule sets, especially in Production. Global Resource Settings allows us to set values for settings that can vary depending on the environment without requiring the update of data instances and integration rules.

Pega Keyed data page

Keyed page access in pega

Pre-loads the data from the original data source and returns matching instances by using one or more keys. The keyed data page is the best implementation when there are frequent unique queries before the information becomes stale. Keyed data page configuration is only applicable to List type data pages and "Read-Only" mode.

Pega remove duplicates from activity and data transform

How can we remove duplicates from a Page-List?

Byusing Pega functions like “RemoveDuplicatesInPageList”, pzRemoveDuplicatesFromListPage and pzRemoveDuplicatesFromListPage
We can use both the functions in Data Transform and Activity.

How to call a report definition in an activity? pega

Call Report definition in an activity

By using “Call Rule-Obj-Report-Definition.pxRetrieveReportData activity and passing Parameters Param.pyReportName, Param.pyReportClass, and Param.pyPageName in Property-Set method before calling the activity

Pega client and server side validation

What types of validations are there?
a.      Client Side Validations
If you want to validate properties before submitting the forms, those validations we can call client-side validations.
b.      Server Side Validations
If we want to validate properties after submitting the forms, those validations we can call a server-side validation.