Product Suites

>What Is a Product Suite?

>Prerequisites for Creating a Product Suite

>Lifecycle Stages of a Product Suite

>Product Suite Status

>Creating a Product Suite

>Actions for Product Suites

New to Sentinel EMS?
See How to Use Sentinel EMS?

What Is a Product Suite?

A product suite is a combination of products that are intended to be sold together according to your product packaging plan. The products included in a product suite may be functionally similar or complementary. A product suite can include one or more products from its namespace. Here are some typical scenarios in which a suite can be created:

>A number of your customers buy a specific group of products. You can combine these products into a suite and offer them a discount on the total cost.

>To increase the visibility of your new products, you may combine a free one-year subscription for these with your most popular products.

>Two or more of your products are interdependent or complementary. You may choose to bundle these products so that your customers do not have to order these separately.

NOTE   Product suites are not supported for Sentinel Fit. This means that although you can create product suites using Sentinel Fit products, these product suites cannot be included in entitlements.

Prerequisites for Creating a Product Suite

>A role that includes Catalog (Namespace) permissions for the relevant namespace. (You cannot move an entity from one namespace to another.) At minimum, the vendor user needs the Add permission. For details, see Roles.

> All features and products to be included must exist in the same namespace as the product suite.

Lifecycle Stages of a Product Suite

A product suite's lifecycle contains the following stages:

>Not Deployed: The product suite is not included in any entitlement.

>Deployed: The product suite is included in an entitlement.

Product Suite Status

The Status attribute available on the Product Suites page indicates the status of a product suite.

Possible values:

>Draft: When you first create a product suite, it is saved as draft. You can edit or delete a draft product suite. You cannot create entitlements for a draft product suite, however, you can create test entitlements for testing purposes.

>Complete: You can create entitlements for the product suite.

>End of Life (EOL): An obsolete product suite. You cannot edit or delete the product suite, and it is no longer available for inclusion in new entitlements. You can restore an EOL product suite by marking it as complete.

Creating a Product Suite

From the navigation pane, select Catalog > Product Suites to open the Product Suites page. Then click the Add Product Suite button to create a product suite.

The following table explains the product suite attributes:

Attribute Description Required/Optional Valid Values
Namespace Name of the namespace. Required

>Alphanumeric

>1 to 500 characters

Name Name of the product suite. Required

>Alphanumeric

>Special characters

>1 to 90 characters

>Must not be a duplicate "name + version" combination

Version

Version of the product.

Required

>Alphanumeric

>Special characters except for
% ^ & " [ ] < >

>1 to 20 characters

>Must not be a duplicate "name + version" combination

Fixed Quantity

For every activation, the identical number of licenses is consumed.

The Fixed Quantity must be a divisor of the total quantity, where: Fixed Quantity x Number of Activations = Total Quantity

Note: This field appears only when the Fixed activation method is selected in the Additional Attributes section.

Required

Number from 1 to the maximum quantity of activations

Default value: 1

Description Additional information about the product suite. Optional

>Alphanumeric

>0 to 500 characters

Additional Attributes

Activation Method

The method of defining and allocating the quantity of licenses available for the product suite in an entitlement.

Activation methods:

>Define in Entitlement: The quantity of licenses to activate is set during entitlement creation using one of the following activation methods.

>Fixed: The total number of licenses can be divided equally for consumption in multiple activations.

When you select Fixed, the Fixed Quantity field is added to the Define Attributes pane enabling you to specify the fixed amount to be consumed in each activation.

>Partial: The quantity can be consumed in multiple activations. Each activation reduces the total number of available activations by the quantity activated.

>Full: The entire quantity is activated in a single activation.

>Unlimited: An unlimited number of activations can be performed for the product suite.

Required

One of the following:

>Define in Entitlement

>Fixed

>Partial

>Full

>Unlimited

External ID External reference identifier that uniquely identifies the product suite in an external system. Optional

>Alphanumeric

>0 to 60 characters

>Must be unique

 
Ref ID 1 Reference identifier that identifies the product suite in an external system. Optional

>Alphanumeric

>0 to 100 characters

Ref ID 2 Reference identifier that identifies the product suite in an external system. Optional

>Alphanumeric

>0 to 100 characters

Associate Products

After providing the attribute details, use the Associate Products pane displayed below to associate products with the product suite you are creating.

The points to remember when you associate a product with a product suite:

>An empty product suite can be created without associating any products.

>Click for a product to remove it from the Associated Products list.

Actions for Product Suites

The following table lists the actions available for product suites:

Action Description
Edit button Edit

Updates information for an existing product suite.

Note:

>You can modify the Name, Version, External ID, Ref IDs, Activation Method, and Description of a product suite that is not deployed. You can also add or remove products if the product suite is not deployed.

>You can modify the External ID, Ref IDs, and Description for a deployed product suite.

Complete button Complete

Marks a product suite as "complete".

Note:

>A product suite can be marked as "complete" only if at least one product is associated with it.

>A product suite is available for an entitlement only after it is marked as "complete".

Delete button Delete

Deletes a non-deployed product suite.

Copy button Copy

Duplicates an existing product suite, enabling you to edit the copy and create a new product suite. Edit the details as required, and then click Save to create the new product suite.

End of Life button End of Life

Marks a product suite as End of Life (EOL) to make the product suite obsolete.

Note:

>You cannot add an EOL product suite to entitlements.

>You cannot edit or delete an EOL product suite.

>This action is only available after a product suite is marked as "complete".

>You can restore an EOL product suite by marking it as "complete". This makes the product suite available for entitlements.