Question

6
Replies
1185
Views
Close popover
Anita Li (LIJ011)
PEGA
Principal System Architect
Pegasystems Inc.
US
LIJ011 Member since 2013 2 posts
PEGA
Posted: December 6, 2016
Last activity: March 6, 2017
Closed

Does Pega recommend Production Pilot Application deployment( two rules schema and shared/separate data schema)?

Client business requirement to have a pilot application deployed in production to test with production data first, then application moved to production with all users. Two approaches below:

Production rule schema , Pilot rule schema, Shared data schema - challenge: to separate/recognize non versioned rules, application data, work object for get next work, batch jobs etc.

Production rule schema, Pilot rule schema; Production data schema, Pilot data schema - challenge: need to merge work objects related data to production?

Client is asking for official recommendation from Pega and if not currently supported, will product support it in future version?

Client requirement to create a pilot production environment (PRPC7.19 or higher). The purpose is to implement a phased deployment approach over the course from weeks to months depending on the size of the deployment. Limit the pilot user as 10% of user population. As Pilot proceeds and is considered successful, the application can be moved to Production and rolled out to the entire end user community.

Benefits:

  • Pilot represents lower risk, but allows for the ability to roll back to the previous version if needed.

  • Users typically have an expedited mechanism for receiving support from Dev team; reduce P1/P2 ticket from production.

Data Integration System Administration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.