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.

Difference between WHEN rule and Access WHEN in Pega

 When Rule is used to produce a conditional outcome or to decide when to run an activity or to make a decision. It can route documents to the different teams depending on the value in the document fields.

Access When Rule is used to restrict users from accessing a page rules and data. It specifies users who can access the pages and tasks by providing conditions. This rule is mostly used when a user has access to multiple pages.

Pega Access of Role to Object

 Pega Access is a powerful data security tool used in Pega Platforms to define access permissions for roles and objects. An object could be an application, report, service, clipboard page, rule set, etc. It can be used to control who can access what information and operations based on the roles assigned to them. Pega Access works by assigning permissions to objects or rules. These permissions can be set as public, private or privileged. This helps in managing user access to different objects based on roles, data visibility and various other security and compliance requirements.