1. User's Guide
  2. Rules

13 Rules

Rules Overview

Use this topic to understand the types of rules you can define in the Launch application when creating offers or specifications.

What's a rule

Rules are different types of conditions that you can set for product offers. These conditions are applied during the ordering process to ensure that the validations and checks are in place.

You can view, confirm, edit, or revise rules based on the lifecycle status of the related offer.

How do I create rules

You can define rules from either the Rules landing page or through the guided flow for offer creation depending on your role. Creating rules using the guided flow for offer creation is available to both administrators and product managers. If you're an administrator, you can use the Rules card on the home page to navigate to the Rules landing page to create rules.

Considerations when creating rules:

  1. Rules are top-level resources in the Launch application. You can define these rules using REST APIs and also from the Launch application UI. See Use REST APIs to Create Catalog Entities to create rules using APIs and Product Offer Guided Flow to create rules using the Launch UI.
  2. Validations are in place to detect contradicting rules.
  3. Some of the rules may need logical operators to specify criteria that you must set carefully. These criteria include specifying whether a product requires another product, a product line excludes a product, and so on.
  4. You can't edit rules for an offer that's retired.

Types of Rules

You can set the following types of rules when creating product offers or product specifications:

  • Eligibility rules: Defines the eligibility criteria of a user to buy a product offer or service. For more information, see Eligibility Rules.
  • Compatibility rules: Specifies the inclusion or exclusion of a combination of products in an offer. For more information, see Compatibility Rules.
  • Recommendation rules: Provides cross-sell and up-sell opportunities for offers. For more information, see Recommendation Rules.
  • Upgrade and downgrade migration rules: Defines the permissible offers that the customers can migrate to or migrate from along with the terms. For more information, see Migration Rules.
  • Constraint rules: Defines the relationship between any two items in a product offering. For more information, see Constraint Rules.

Constraint Rules

Use constraint rules to enforce the components selection for a Commercial bundle and Service bundle. Defining these rules restricts the choices the users can make at runtime while configuring the cart.

Defining constraint rules lists or limits the choices the user can make when working with relationships, product offerings, or with attributes in product offerings.

For example, a constraint rule may prevent a user from selecting an attribute value, say a color or size, for a component that doesn’t support that color or size value.

You can access constraint rules from the Rules card in the administration menu.

To configure constraints, you must first select a template and then configure the constraint rule based on that template using a graphical builder.

Select a constraint rule template

The supported constraint templates that you can use to create a constraint rule are:

Table 13-1 Constraint Rules Template

Rules template When to use the template

Attribute expression

Use this template to create an expression where the value of an attribute requires or excludes a value of another attribute. For example, the attribute value of red isn’t available for attribute value of large.

Attribute value

Use this template where an attribute equals a value. For example, more than three OTT services would require a router that support at least 100Mbps.

Relationship quantity

Use this template to determine the number of entities that can be included in a relationship. For example, you can define that for 02 mobile phones the customer must purchase 02 quantities of both voice and data.

Excludes

Use this template when a resource or an expression must exclude another resource or an expression. For example, a premium service does not support 16 GB memory size.

Requires

Use this template when a resource or an expression must include another resource or an expression. For example, a premium service requires a 100 Mbps router.

Requires (Mutual)

Use this template when any two resources or expressions must mutually include each other. For example, when two interdependent products can’t be sold independently.

Model the rule using constraint rule Graphical builder

The constraint builder contains logical or comparison operators along with expressions to help you build your constraint rule.

A constraint may have the following:
  1. Selected product offering, relationship, an expression using the entities within the relationship, or attributes within a relationship.
  2. The constraint type as requires, requires (mutual), or excludes. Requires is the default setting.
  3. Selected product offering, relationship, an expression using the entities within the relationship, or attributes within a relationship.

If your configuration spans across multiple nodes within the construct builder, you can take help from the textual construct of the configuration that simultaneously appears on the UI.

Eligibility Rules

Use this topic to understand how you create and manage eligibility rules.

You can set eligibility rules to specify whether a user is eligible for a product offer or product service. You can set up different eligibility rules based on multiple conditions and specify whether all or some of the conditions are applicable. For example, you can make a product available to customers of a specific region.

Eligibility rule is a top-level resource in the Launch application. You can define these rules using both REST APIs and from the Launch application UI.

For more information on using REST APIs to create catalog entities, see Use REST APIs to Create Catalog Entities.

Create Eligibility Rule

Here are the quick steps to creating an eligibility rule as part of the guided flow for creating offers. If you're an administrator, you can also navigate to the Rules landing page directly from the application home page to create rules.

  1. On the Rules page, click Create Eligibility Rule.

  2. Specify details including the eligibility criteria and the effectivity dates. Specify additional criteria if needed and then click Create.

You can also edit, delete, or deactivate product eligibility rules.

Here's an example of an eligibility rule where an offer is eligible for customers residing in the United States.

Table 13-2 Example of Eligibility Rule

Parameter Operator Value

Country

Equals

United States
Related Topics

Compatibility Rules

Use this topic to understand how you create and manage compatibility rules.

You use compatibility rules to define contextual dependencies or exclusions among catalog entities in both simple and bundle offers. You can define compatibility rules for product offers, product lines, and product specifications.

As a product manager, you can specify the subject and the target for the compatibility rule. The subject defines the product that requires or excludes another product and a target defines the product that's required or excluded. This dependency can also be mutual where both the subject and the target require each other. You decide the rules for your entity when creating the compatibility rule. For example, a requires rule could be that a faster internet plan requires a router that supports the new bandwidth.

Compatibility rule is a top-level resource in the Launch application. You can define these rules using both REST APIs and from the Launch application UI. See Use REST APIs to Create Catalog Entities.

Create Compatibility Rule

Here are the quick steps to creating a compatibility rule as part of the guided flow for creating offers. If you're an administrator, you can also navigate to the Rules landing page directly from the application home page to create rules.

  1. On the Rules page, click Create Compatibility Rule.

  2. Specify the required details including entity type and rule type. Some of the rule types are: REQUIRES, REQUIRES (MUTUAL), EXCLUDES, and COMPATIBLE.

  3. Specify the search criteria as either product offering or product line and enter the effective start and end date for the rule.

  4. Click Create.

Note:

The COMPATIBLE operator provides design flexibility at runtime. For example:
  • You can allow device modeling outside the package.
  • You can reduce dependency on offer aggregation constructs.
  • You can create a storefront experience of selecting a package and listing all compatible offers and product lines or selecting a device and listing the compatible packages.

Related Topics

Recommendation Rules

Use this topic to understand what recommendation rules are and how you create them.

Recommendation rules are a top-level resource in the Launch application. You can create recommendation rules as part of the offer creation flow. You create these rules to provide sales representatives with cross-sell and up-sell opportunities for existing customers based on installed base products, demographics and other account-specific attributes. You can create recommendation rules for only simple offers. You can also edit, delete, or inactivate recommendation rules.

Create Recommendation Rules

Here are the quick steps to creating a recommendation rule:

  1. During the offer creation process, click Add Recommendation Rule on the Rules page.

  2. Specify whether it's an up-sell or cross-sell recommendation, and then specify the product offer to which the recommendation is applicable.

  3. Specify the reason why a customer must purchase the recommended product.

  4. Enter the score for the rule. This score determines the comparative value of a recommendation to other recommendations and it must be unique.

  5. Enter the effective start and end dates for the recommendation you're creating.

  6. Click Add.

Here's an example of a recommendation rule where the marketing administrator recommends a small memory card.

Table 13-3 Example of Recommendation Rule

Product Reason Effective Start Date

8 MB memory card that's compatible with the 2.0 MP camera.

An extra memory card is required to store more than 20 pictures.

1st June 2020

Related Topics

Migration Rules

Use this topic to understand migration rules and how you create these rules for bundle offers.

Migration rules is a top-level resource in the Launch application. You create these rules as part of the offer creation process for customers to upgrade or downgrade from one product offer to another.

These rules basically define the upgrade or downgrade path between marketable offers. You can create upgrade or downgrade rule for only bundle offers.

Note:

  • Migration rule is applicable between sellable bundles (commercial, service, or package).
  • When publishing the Initiative to Siebel spoke system, it will only support the Product Offering of type Package.

Create Upgrade or Downgrade Rule

Here are the quick steps to creating upgrade or downgrade rule:

  1. During the offer creation process, click Upgrade To or Upgrade From on the Rules page.

  2. Specify the details depending on whether you're creating an upgrade or a downgrade rule.

    A customer can either migrate from a source offer to the current offer, or from the current offer to another offer.

  3. Specify other details including the penalty amount. A penalty amount is charged if the customer terminates the offer before the specified end date.

  4. Click Add.

You can also edit, delete, or inactivate upgrade or downgrade rules.

Here's an example where a penalty is charged for terminating the current offer before it ends.

Table 13-4 Example of Rule Upgradation

Upgrade Type Offer Commitment Start Duration Penalty

Upgrade to

Wireless 2000 package

Now

New Duration

$50
Related Topics