13 Rules

Learn how to define, manage, and apply different types of rules to ensure your product offerings are validated, optimized, and aligned with business requirements.

Rules Overview

This section discusses the types of rules you can define in the Launch application when creating offerings or specifications.

Rules are different types of conditions that you can set for product offerings. 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 offering.

You can define rules from either the Rules landing page or through the guided flow for offering creation depending on your role. Creating rules using the guided flow for offering creation is available to both administrators and product managers. If you are 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 the REST API and also from the Launch application UI. See Use REST APIs to Create Catalog Entities in Launch Cloud Service Implementation Guide to create rules using the REST API and Creating Product Offer Using a Guided Flow to create rules using the Launch UI.
  2. Launch validates the rules to make sure they don't contradict each other.
  3. If desired, you can specify logical operators in rules. Set these operators carefully. These criteria include specifying whether a product requires another product or a product line excludes a product.
  4. You can't edit rules for an offer that has been retired.

Types of Rules

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

  • Eligibility rules: Defines the eligibility criteria of a user to buy a product offering or service. For more information, see Eligibility Rules.
  • Compatibility rules: Specifies the inclusion or exclusion of a combination of products in an offering. For more information, see Compatibility Rules.
  • Recommendation rules: Provides cross-sell and up-sell opportunities for offerings. For more information, see Recommendation Rules.
  • Upgrade and downgrade migration rules: Defines the permissible offerings 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 component selection for a Commercial or 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 supports at least 100 MBps.

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 two mobile phones the customer must purchase two each of voice and data plans.

Excludes

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

Requires

Use this template when a resource or an expression must include another resource or 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 together.

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 or attributes within the relationship.
  2. The constraint type, such as requires, requires (mutual), or excludes. Requires is the default setting.

If your configuration spans multiple nodes within the construct builder, you can refer to the textual construct of the configuration that appears simultaneously in the UI.

Eligibility Rules

You can set eligibility rules to specify whether a user is eligible for a product offering 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 the REST API and from the Launch application UI.

For more information on using the REST API to create catalog entities, see Use REST APIs to Create Catalog Entities in Launch Cloud Service Implementation Guide.

Create an Eligibility Rule

You can create an eligibility rule as part of the guided flow for creating offerings. If you are 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 offering 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

You use compatibility rules to define contextual dependencies or exclusions among catalog entities in both simple and bundle offerings. You can define compatibility rules for product offerings, 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. 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 the REST API and from the Launch application UI. See Use REST APIs to Create Catalog Entities.

Create a Compatibility Rule

You create a compatibility rule as part of the guided flow for creating offerings. If you are 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 offering aggregation constructs.
  • You can create a storefront experience of selecting a package and listing all compatible offerings and product lines or selecting a device and listing the compatible packages.

Related Topics

Recommendation Rules

Recommendation rules are a top-level resource in the Launch application. You can create recommendation rules as part of the offering 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 only for simple offerings. You can also edit, delete, or inactivate recommendation rules.

Create Recommendation Rules

To create a recommendation rule:

  1. During the offering 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 offering to which the recommendation is applicable.

  3. Specify the reason why a customer should 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 are 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.

June 1, 2025

Related Topics

Migration Rules

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

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

Note:

  • The migration rules are applicable between sellable bundles (commercial, service, or package).
  • When publishing the Initiative to a Siebel spoke system, it only supports the Product Offering of type Package.

Create an Upgrade or Downgrade Rule

To create an upgrade or downgrade rule:

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

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

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

  3. Specify other details including the penalty amount. A penalty amount is charged if the customer terminates the offering 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 offering before it ends.

Table 13-4 Example of Rule Upgrade

Upgrade Type offering Commitment Start Duration Penalty

Upgrade to

Wireless 2000 package

Now

12 months

$50

Related Topics