Arpita_D Member since 2013 29 posts
Posted: 3 years ago
Last activity: 3 years 3 months ago

Client Constraint during configuration of Pega 7 post the upgrade


The question is around the privileges of the user role using which Pega has been configured after the upgrade.

One of our Clients have upgraded by giving deployment user temporary admin access, but later during configuration following occured.

What is Client Constraint?

Client has security constraint of not providing a DB user with full admin access to both Rules and Data Schema.

What Client provided:

During upgrade, on a temporary mode full admin access was given to the deployment user using which the upgrade scripts have been run.

Now during configuration - they created a Base User role which is only having DML access on both Rules and Data schema and using that the Pega has been configured. All cross schema privileges generated during cross schema granting has been revoked as well.

Our Question:

As a result of the above-stated configuration, team is experiencing issues like table creation, framework installation from application end.

We mainly want to confirm, will the mentioned configuration also impact any product behavior/operation to support split schema mode. Also as cross schema grants have been removed, will those impact Pega running in split schema.



Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn