It has been recommended to our organization to use deployment manager in such a way as to deploy the entire application instead of individual product rule by product mapping to individual stories.
I’m assuming that means that we need to version our application per release/build correct?
Assuming that is what is recommended that would mean that for each of our environments we need to suppose multiple lists of access groups that are pointed to particular versions of the application to support testing and use of those applications.
When we use deployment manager to deploy a version of the application to a particular environment that means that at least some of those access groups will need to be updated to point to that application version.
Is there anything in deployment manager that we can use to automate the updating of access groups upon deployment?
@TerranceK5260 you are right. My project also updates access groups to point to the latest application version deployed for a given release. This was quite a manual task that needed to be done for every release. I’m not sure if DM 6.x supports any automated way (we are using DM 5.x). Wish we have this enhancement in DM since this seems a common requirement for many projects. In my project, we created a custom DM task to automatically update the access groups in each env by calling Pega API in the respective candidate system.
@TerranceK5260 Deployment Manager does not directly automate the updating of access groups upon deployment. However, you can use a post-deployment step to run an activity that updates the necessary access groups. This activity can be created in your application and then referenced in the pipeline configuration in Deployment Manager.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
This is a GenAI-powered tool. All generated answers require validation against the provided references.