Understanding production ruleset configuration on access group
I would like to understand the differences between configuring production ruleset in access group vs application. Can someone help me understand the scenarios when we have go with adding production ruleset in access group
Below is the information I got it from Help. I hope you can understand the use of Production ruleset and reason for configured at Access Group level
Optional. 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. A ruleset with this purpose is sometimes called a local-only or production ruleset.
Leave blank except for developers and others who modify rules. While your profile includes the ruleset versions listed here, they are not considered part of the current application. Rules in the ruleset versions listed here might not be visible in the Application Explorer, Guardrails tool, or Document wizard facilities.
As a best practice for good security — and to avoid a warning when you save the Access Group form, select from the ruleset versions that appear in the Production RuleSets array on the Definition tab of the application rule.