Configurable Grouping Rules for Subscriptions

You can now define grouping rules for subscription product lines from an upstream application. Using the grouping rules the incoming product lines can be grouped based on the conditions you specify. Additionally, you can also specify if they have to be added to an existing subscription.

The definition of a grouping rule is a new configuration under Subscription Management configuration available in Redwood.

Subscription Grouping Rule Set Listing

A Grouping rule set allows you to define rules to group subscription products from an upstream application into an existing subscription header or a new subscription header.

Every grouping rule set has a name, number and rank. The rank defines the order in which the grouping rule sets are evaluated for applying to an incoming subscription product line. A grouping rule set can be enabled or disabled. However, the grouping rule set has to be published before it can be used. The Publish Rule Sets action is used to publish the grouping rule sets.

A lower ranked grouping rule set is evaluated first. A grouping rule set is identified by matching the selecting rule criteria to the incoming subscription data.

Grouping Rule Set

The selection rule identifies which of the grouping rule set will be used for processing the incoming subscription. The selection rule can be created based on the attributes of the subscription header. The selection rule can help you segregate the rule sets by business units for example.

Selection Rule

The Segregation rule identifies the subscription products from the incoming transactions that have to me mandatorily created under a separate subscription header. In effect, the attributes from both subscription header and products which you think cannot have different values within a subscription header, must be identified as a segregation attribute. There are some mandatory segregation attributes which cannot be overridden.

Segregation Rule

The grouping rule determines the rules that will actually be applied to group the incoming order lines into a subscription header. The grouping rules can be ranked, and the rules will be processed in the order of increasing rank. Duplicate ranks are not allowed. The grouping rule can be created using attributes of subscription header and subscription products.

You can add as many grouping rules are required. If a grouping rule attribute is common across all the grouping rules, then it can be added in the Segregation rule.

Grouping Rule

Multiple Grouping Rules in a Grouping Rule Set

Once the grouping rules are created then the Grouping Rule Set has to be published for it to be usable.

Publishing Grouping Rule Set

The attributes of the sales order that are used for the selection rule, segregation rule and grouping rule can be mapped from Order attributes to the Subscription attributes using the Sales Order Subscription Mapping. The standard attributes are already mapped.

Sales Order Subscription Map

1. Group subscription products from upstream applications into different subscription headers based on different conditions.
2. Identify conditions to segregate subscription products based on attributes from upstream applications.
3. Set flexible rules to identify which set of rules should be applied to process incoming subscription products.
4. Add renewals and amendments to same source subscription header.
5. Specify the mapping between Fusion Order Management attributes and Subscription Management attributes.
6. View status of a subscription even as it is being fulfilled from Fusion Order Management. Your ecommerce customers can benefit by seeing what subscription products they have ordered and its fulfilment status.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

1. Always publish the grouping rule sets even if you have not created your own rule set. The default rule set will be published and used.
2. The service map used by the algorithm extension to map standard and custom Order attributes to Subscription attributes should match with the Sales Order Subscription Map.
3. Auto Mapped in the Sales Order Subscription Map indicates that the mapping for the said Subscription attribute is derived based on a predefined logic.
4. The attributes in the segregation rules should mandatorily have a value that is passed from the source application.