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

 Hans Bernving (HansBernving) Hans Bernving
Bernving
NL
HansBernving Member since 2016 11 posts
Bernving
Posted: Dec 7, 2018
Last activity: Dec 7, 2018
Posted: 7 Dec 2018 3:48 EST
Last activity: 7 Dec 2018 6:06 EST
Closed

Prevent overwrite existing Dynamic System Settings when deploy

I looking for two options:

1. Prevent overwriting existing Dynamic System Settings when deploying a new version of an application (prefered solution)but adding new ones

2. Exclude Dynamic System Settings in the Prodcut Rule.

Pega version 7.3.1 used

To see attachments, please log in.
Installation and Deployment

Posted: 7 years ago
Posted: 7 Dec 2018 6:06 EST
Michel Kraaij - van den Berg (Michel Kraaij)
Anamata
Pega Lead on Quality Awareness, Pega CSSA, Pega Trainer, Testconsultant
Anamata
NL
  1. Yes, you can 'prevent' overwriting existing Dynamic System Settings. However, this only works when you import rules manually. During the import you have the option to exclude aged updates. When these settings are newer on the target system, they get marked for aged updates.

    However, currently this ONLY works for manual imports. If you use the PRPCserviceUtils to import, aged updates always be overwritten. In my opinion this is a bug. 
     
  2. If 'included associated data' is checked in your product rule, you might consider removing the ruleset association on specific instances. This way you will exclude these specific instances from packaging.
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