Question
GDPR Erase
Last activity: 7 Dec 2021 6:00 EST
Action Deployment Pega marketing
Hello,
We are updating some actions in the application ruleset. We have the decision data rule in artifacts ruleset as we have some revision manager releases as well.
When we deploy the new rulesets with the actions in the higher environments. The decision data rule in the artifact ruleset is not taking into account the new versions of the actions. Either we have to do a private edit and discard the actions manually to refresh the decision data rule or we have to save as those actions in artifacts ruleset post deployment.
We tried revalidate and save option to save the actions in bulk but it does not help. The only option we have today is to save each action manually after deployment.
Is there a better way to deploy actions?
Regards,
Gourav
Accepted Solution
Updated: 7 Dec 2021 6:00 EST
Pegasystems Inc.
IN
Managing Actions (Create new or edit an existing) is a Business change and we recommend to use 1:1 Operations manager application for this purpose.
For more details please see Business Agility in 1:1 Customer Engagement | Pega Academy
Note : DDR complexity is handled for you in 1:1 Operations manager.
Updated: 25 Nov 2021 5:36 EST
Pegasystems Inc.
IN
Hello @gdpr.erase185
A few questions before we attempt to solve this.
- How are you administering changes to or introducing new actions? Are you using revision management or OpsManager to do this?
- Are you administering changes to decision data rules and action rules separately? If yes, why?
Please note that changes to action rules also update the decision data rule for the group in the backend. Their lifecycle is interdependent. Based on what you've just described, I understand that you have the action rules and the associated decision data rules in two separate rulesets which I don't think is ideal.
@BURTA @MarioBatres thoughts?
-Thanks!
GDPR Erase
Hi,
We have two type release cycles. For outbound campaigns we use the revision manager to deploy the changes. For inbound campaigns the actions are more complex and it is developed in dt1 environment and deployed via regular deployment process using deployment manager. Most of actions in both of the scenario comes under the same heirarchy. So we have to keep the decision data rule in artifact ruleset to make sure the decision data takes into account both business changes deployed by revision manager and technical changes coming from the devs. As the decision data is not auto refreshed after the deployment, we are currently doing the manual post deployment steps for each action as mentioned in the question.
Is there a way to refresh the decision data using a utility or something to reduce the deployment time?
Accepted Solution
Updated: 7 Dec 2021 6:00 EST
Pegasystems Inc.
IN
Managing Actions (Create new or edit an existing) is a Business change and we recommend to use 1:1 Operations manager application for this purpose.
For more details please see Business Agility in 1:1 Customer Engagement | Pega Academy
Note : DDR complexity is handled for you in 1:1 Operations manager.