Posted: 19 Dec 2019 4:04 EST Last activity: 24 Dec 2019 1:47 EST
Production ruleset: application VS access group
Does anybody know what's the use to add a production ruleset in application rule? As far as I know it doesn't affect on runtime ruleset list. Only when you add production ruleset to the access group it will appear in the ruleset list. And my experiments confirm this.
And another question: is there any way to specify a production ruleset common for all access groups?
It is very strange if I have no ability to make production ruleset rules visible for everyone who use some application.
A production ruleset is a ruleset that contains rules that you can modify after the application is deployed
The one in application rule form is an optional field. If you specify your production ruleset here then the rulesets specified in this section needs also to be mentioned under the Access Group form's Layout tab
Whereas for the access group level you need to enter production rulesets and versions specific to this access group. For example, in a production setting, you can identify one ruleset and version that remains unlocked and holds only rules expected to be changed often. Such rules can be delegated to management. PFB link for more information.
When you specify the "Production Ruleset" in the access group it limits the usage or owner of that ruleset.When you create production ruleset you need to identify the corresponding owner or simple identify who can modify the rules as they are production ruleset. That is why you have to specify the "production rulset" in the access group as it limits the owner of the rules.
A production ruleset is a ruleset that contains rules that you can modify after the application is deployed, refer the below links for your reference.