Question
1
Replies
707
Views
Posted: September 8, 2016
Last activity: September 12, 2016
Closed
Solved
Tag Non version rules to a release
Hi,
In Recenet deployments we faced issue where developer forgot to add data rules (rules dont belong to ruleset version like WorkBasket, Class rule) in Product and encounterd issue post deployment.
My question is, we can tag CustomerFields to rules belings to rule- class, can this same feature be enable for rules which dont belong o rulesetversion.. so when ever developer create such rules they can tag to some name like release name "EnhancmentXYZ" so that when deploymnet Product is created we can easily identify those rules.
Please suggest is there already a best practice to handel such things which we are not aware ?
***Updated by moderator: Lochan to add Categories***
Moderation Team has archived post,
Close popover
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.
Hi,
Pega provides an "Associated Ruleset" field for all the data instances. Once you create any data instance add your application ruleset as associated ruleset and that links the data instance as assoiated data to the ruleset. When we create Rule-Admin-Product , in the Ruleset area we have "include associated data " check box against each ruleset listed. That takes care of all the data instances associated to that ruleset and migrates to other environment.