Yes, we should add.

Hello,

When working with Production ruleset, I was mainly doing it via the AccessGroup. So this ruleset becomes on top of everything else.

I never had to add it on Application ruleset stack.

The Production rulesets that we mention in the Application rule form is just tells that what all production rulesets we have in the application. And in order to be available to end user they need to added to access groups and usually delegated rules and reports will be kept in production so that special users can amend if required.

Thanks everyone.

Thats where i'm confused. I understand that the delegated rules will be amended by privileged users. However, what purpose does it serve when these rules are not available to other users for access. i mean since we dint add the product ruleset to application stack these rules will not be available to other users.

Yes we can add

For the delegated rules to be available to all access groups for execution, we need to add those in the application ruleset stack.

The production ruleset comes into picture when we want the operators to be able to create rules in production, mainly the customized reports. In this case, the operators with access groups having this ruleset in its production ruleset will only have access to this particular ruleset.

After reading this thread and all of the documentation I can find, the best practice on this is still very confusing.

Here's the scenario:

• An application has a production ruleset so that certain rules can be updated in production.
• Let's say we have a paragraph rule in the production ruleset that is delegated to the Managers AG so that Managers can update the content in production.
• We want all users of the application (regardless of what access group they are in) to execute the latest version of the rules in the production ruleset, everyone should see the latest version of that paragraph rule's content, regardless of what access group they are in.

What is the best option? Should we:

1. Add the production ruleset to the Application rulesets stack in the Application Definition?
2. OR Add the production ruleset to the Production Rulesets list (under Advanced > Run time configuration) in every Access Group

Option 1 seems like it would be easier to maintain and avoid the risk of having an Access Group that is missed. Are there any risks with option 1? Is there clear documentation to follow on this topic?

I could no where find any clear documentation as to what the best practice is.

I too agree with Option 1.

The production ruleset section of the application does not make any change to operators ruleset stack.
This field only allows the listed rulesets to be selectable in access group that are part of that application.
Always add the production ruleset to all the access groups so that changes will be reflected to all users.

Instead of adding it to all access group's I think adding it to the application ruleset stack is simple :)

Please find my toughts to the scenario.

EX: Rulesets in Application A,B,C,D,P (where P is the production ruleset).

Operator 1 is having A,B,C ruleset access

Operator 2 is having C,D,P ruleset access

If the Production ruleset P is in Application Stack then Operator 1 and 2 can access the Rules in Ruleset P and only operator 2 can edit the rules in the ruleset.

When I click on the knowledge base article link quoted above I get "You are not authorised to access this page". Seriously?