Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Chiranjeet Mishra (ChiranjeetM5260)
Rabobank
Pega Consultant
Rabobank
NL
ChiranjeetM5260 Member since 2021 14 posts
Rabobank
Posted: Sep 24, 2023
Last activity: Sep 26, 2023
Posted: 24 Sep 2023 22:01 EDT
Last activity: 26 Sep 2023 3:00 EDT
Closed

Ops Manager Deployment Generating New Enterprise App Versions

Hi,

We are moving to 1:1 Ops Manager where business will do the action or treatment changes and deploy through business change pipeline. But what I have observed is that when the code is deployed through business pipeline to DEV, Pega generates a new enterprise app version on top of which the overlay app is built. For example, if current enterprise app version is 01.01.03, Pega will generate a new version 04, update it in the overlay app and deploy it to next environments.

My question is If we are parallelly working on some enterprise change in the enterprise app (built on app for overlay app) then how do we manage this change and keep it isolated from the business changes because the enterprise change will happen in enterprise layer which Pega updates automatically in overlay app and deploys to production? Do we need to manually update the overlay app to point it to the initial enterprise app version and then execute the business pipeline from DEV->Test->BOE->PROD?

Thanks, Chiranjeet 

To see attachments, please log in.
Pega Customer Decision Hub 8.7
Change and Revision Management
Pega Cloud
Decision Management
Enterprise Application Development
Decisioning Architect
Senior System Architect

Posted: 1 year ago
Posted: 25 Sep 2023 4:04 EDT
Neeraj Singh (Neeraj_Singh)
Bits in Glass
Software Engineer
Bits in Glass
IN

Hi @ChiranjeetM5260

the approach could be to manually update the overlay application to point to the initial enterprise application version before executing the business pipeline from DEV->Test->BOE->PROD1. This would ensure that your enterprise changes are kept separate from the business changes.

However, this approach might not be ideal in all situations, and it’s important to carefully consider the impact of your changes and how they will interact with the business change pipeline.

If you’re finding it difficult to manage these changes, it might be worth considering using a more robust version control system or application lifecycle management tool. These tools can provide more granular control over your versions and make it easier to manage parallel development efforts.

As always, it’s important to thoroughly test all changes in a non-production environment before deploying them to production. This will help you catch any issues early and ensure that your changes don’t have any unintended side effects.

 

 

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice