What Case locking in Pega?

 Case locking in Pega is a feature used to ensure data integrity and prevent conflicts between users when editing a particular case. It prevents users from editing a case at the same time by placing an exclusive ‘lock’ on the case. A single user can obtain a lock on a case and when another user attempts to work on the same case, they are notified that the case is locked.

Default locking and Optimistic locking in Pega

What is Synchonous and Asynchronous Processing in Pega?

 Synchronous processing occurs when a request has to be fulfilled before a response is generated. For example, when a user makes an API call or a database query, the request must be handled and a response generated before anything else can happen.

What are stateful and stateless processing modes in Service package

 Stateful processing mode is where a Service Package remembers data between two requests from a client. This data is stored in its memory and the next request from the client can use the stored data for faster processing.

Exception handling in Pega Connect-REST

 Error handling when using Pega Connect-REST involves catching response codes from the server and taking the appropriate action in the application.

By default, a GET or PUT request will return a 200 or 204 for success or a 404 for a note found. The other error codes, such as 401 and 500, should be handled in the application code.

Explain Connect-REST process in Pega

 Connect-REST is an advanced mechanism in Pega that provides developers with a way to interact with external REST services that return data in XML or JSON format. The process involves the following steps:

1. Creating a Connect-REST service: Using the Connect-REST rule wizard, developers can set up basic services that can be used to send and receive data from a REST web service. This includes specifying the HTTP verb, the request URI, the request parameters, the request headers and the response media type.

What is the difference between Pega inplace and out-of-place upgrade?

A Pega inplace upgrade is when your current version of Pega is upgraded within the same environment and codebase. An out-of-place upgrade is when you migrate from an earlier version of Pega to a newer version, but the upgrade occurs in a different environment than the original one. It may also involve a different codebase. In addition, an out-of-place upgrade may require manual data migration, while an inplace upgrade may not.

On-premises Pega upgrade

 The process of upgrading an existing on-premises Pega deployment generally consists of the following steps:

1. Preparing the Environment: Before starting the upgrade process, ensure that the environment is ready and any pre-requisite activities are met. 2. Backing Up Existing Data: As a good practice, it is important to take a backup of the existing Pega system, including the entire production and non-production databases, applications and files. 3. Performing the Upgrade: Download the latest version of the Pega software and install it in the existing environment. Update the schema for all the databases to bring it to the latest version.