There are two ways to achieve rule delegation. Rule delegation by using favorites or simply delegating a rule. Paragraph, decision table, data type , map value, correspondence, service-level agreement , including circumstance types rules can be simply delegated and it is recommended not to use favorites approach to delegate them. Case match, Collection, Constraints, Decision tree, Declare Expression, Flow, Flow action, When rules are considered for delegating using the favorites approach.
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 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, Where as 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
When you model business policies in an application, you need to adopt a strategy to update these models as business conditions change. Doing so enables the business to be more agile. This approach also helps focus the workload for system architects. Rule delegation transfers the responsibility for maintaining low-risk business policies to business users. This allows system architects to concentrate on tasks suited to a longer, more rigorous development cycle.
If you allow business users to update business policies, the business application can be adapted to changes as they occur, rather than during the next update cycle. Designing the application so business policies are owned and modified by business users can help promote an agile response to ever changing business conditions. This design also empowers business users to make changes to business policies as those changes occur.
Using rule delegation, you put a set of policies under business control even while the application is in production. Business users view the policies in a familiar environment, and can make updates to the policies without knowing all the related, technical details.
Delegating business rules can promote an agile response to constantly changing business conditionsand provide a level of empowerment to business users
There are two ways to achieve rule delegation. Rule delegation by using favorites or simply delegating a rule.
Paragraph, decision table, data type , map value, correspondence, service-level agreement , including circumstance types rules can be simply delegated and it is recommended not to use favorites approach to delegate them.
Case match, Collection, Constraints, Decision tree, Declare Expression, Flow, Flow action, When rules are considered for delegating using the favorites approach.
Production rulesets have at least one unlocked ruleset version in the production environment.
Production rulesets include rules that are updated in the production environment. The most common use of production rulesets is for delegated rules. However, production rulesets can be used for any use case requiring rules to be updated in a production environment. Production rulesets are configured in the Advanced tab on the application record. In addition, the production ruleset needs to be specified in the access group.
A production ruleset is a ruleset containing rules that can be modified after the application is deployed. Using a production ruleset to organize and contain delegated rules insulates the rest of the application from frequent changes. Because the original version of the rule still exists in a locked ruleset, a system administrator can revert to the original copy if something happens to the delegated version of the rule.
Important: The ruleset containing the delegated rules must remain unlocked in production so business users can make changes to the delegated rules. Changes cannot be made to a rule in a locked ruleset.