Question

2
Replies
45
Views
Nikhil Bhandari (NIKUBHAN)
PayPal
Pega Architect
PayPal
IN
NIKUBHAN Member since 2009 15 posts
PayPal
Posted: November 21, 2019
Last activity: November 22, 2019
Posted: 21 Nov 2019 23:37 EST
Last activity: 22 Nov 2019 5:20 EST
Closed

How can we manage the order of rules getting saved while copying rules from Higher RSV to lower RSV?

Hi all,


This is a query regarding a difficulty I am facing in moving rules in bulk from one RSV to another.


Scenario:


I have built a Rule Movement tool that will allow user to select the Ruleset & Rulesetversion (Ruleset can be specified as ALL) & then list all the rules based on the selection. I also provide filter options to allow developers to select rules updated by them or belonging to a specific user story, date updated etc


Once the developer makes his/her selection (by ticking checkboxes) then clicking on Copy rules button will loop over the selected results & call Rule-SaveToNewVersion.


Issue:


When we move rules from higher RSV (say 01-01-99) to lower RSV (say 01-01-51), sometimes the activity rule may get copied before a property rule that it is referencing. If the property rule is created newly in v99 then activity doesnt get copied to lower version due to the dependency.


Is there a workaround by which


1. We can ignore the validations done by Pega in order to not throw these dependency errors?


2. Is there an easy way we can sequence the rule copy so that all the child rules are saved first & then the parent rules?



How does Pega handle this scenario while importing rules / in Copy Ruleset option in Refactor Rulesets landing page?



Any help would be greatly appreciated.



Regards,


Nikhil


***Moderator Edit-Vidyaranjan: Updated SR details***

Hi all,

This is a query regarding a difficulty I am facing in moving rules in bulk from one RSV to another.

Scenario:

I have built a Rule Movement tool that will allow user to select the Ruleset & Rulesetversion (Ruleset can be specified as ALL) & then list all the rules based on the selection. I also provide filter options to allow developers to select rules updated by them or belonging to a specific user story, date updated etc

Once the developer makes his/her selection (by ticking checkboxes) then clicking on Copy rules button will loop over the selected results & call Rule-SaveToNewVersion.

Issue:

When we move rules from higher RSV (say 01-01-99) to lower RSV (say 01-01-51), sometimes the activity rule may get copied before a property rule that it is referencing. If the property rule is created newly in v99 then activity doesnt get copied to lower version due to the dependency.

Is there a workaround by which

1. We can ignore the validations done by Pega in order to not throw these dependency errors?

2. Is there an easy way we can sequence the rule copy so that all the child rules are saved first & then the parent rules?

How does Pega handle this scenario while importing rules / in Copy Ruleset option in Refactor Rulesets landing page?

Any help would be greatly appreciated.

Regards,

Nikhil

***Moderator Edit-Vidyaranjan: Updated SR details***

Low-Code App Development System Administration Installation and Deployment Support Case Exists
Moderation Team has archived post, 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.