info@10duke.com

Create product packages

You can create product packages in 10Duke SysAdmin.

Before you start

Step 1: Create a product package

  1. In the left sidebar, go to PRODUCT CONFIGURATION > Product packages.

  2. Select Actions > Create. A dialog opens.

  3. In Name, define a name for the product package. The name must be unique in the system.

  4. In Description (optional), write a short description.

  5. In Type (optional), select a type that you can use to categorize and filter product packages.

    This field is only metadata for administrative purposes, it’s not used by the system.

    Select a type:

    • Default: You would typically use this for standard or generic products.

    • Mono: You would typically use this for product packages with a single product.

    • Bundle: You would typically use this for a group of products that you sell as a single unit with one price.

    • Define a custom type by entering the name in the field.

  6. In License Model, select a license model to control this product package’s licenses.

  7. Click Save to create the product package.

    Select the new product package in the table: on the Details tab that opens below, the Id field shows the unique ID of the product package. This product package ID must be included in the request path when calling some of the 10Duke Enterprise API endpoints.

By default, a new product package is active and valid indefinitely starting from the current date.

To change this:

  1. Click the product package in the table. Its details open below the table.

  2. Go to the Details tab:

    • To deactivate the product package, disable the Active toggle.

      You can only grant licenses with an active product package.

    • To change the validity time:

      • Valid from: Define the start date from which the product package is valid. Use the format YYYY-MM-DD.

      • Valid until (optional): Define the end date after which the product package is no longer valid. Use the format YYYY-MM-DD.

      You can only grant licenses while the product package is valid.

  3. Click Save.

Step 2: Add the licensed items to the package

Next, add the licensed items to the product package:

  1. Go to the Licensed Items tab.

  2. Add new or existing licensed items:

    • To add existing licensed items, select Actions > Add Item(s) to product. Search and select the items you want and click Save.

    • To create a new licensed item and add it to this product package, select Actions > Create a new Licensed Item. Define a name and (optionally) write a short description, and click Save.

To remove licensed items from the product package, select a licensed item in the table and select Actions > Remove Item(s). (This doesn’t delete the licensed item from the system.)

Step 3: Define advanced settings for licensed items (optional)

If needed, define advanced settings for each licensed item:

  1. On the Licensed Items tab, click the pen icon next to a licensed item.

    The settings section opens below.

  2. Define the advanced settings:

    • License Model: If you want to override the product package’s license model, select the model to be used for this licensed item.

      We recommend that all the license models used in a product package use the same type of credit: either seat count, use count, or use time.

    • Version range: Define the software versions that this licensed item applies to. The end user can only use the defined software versions.

      You can only use this option with a custom license model that defines a version constraint.

      For example, 1.0.0 - 1.0.7 allows versions within this range, and 1.0.7 or 1.0.7 - 1.0.7 only allows access to one version.

      You can change the version information later per granted license if needed.

    • Display name for version range: Define a user-friendly display name for the software version information.

      If defined, the display name is shown in the 10Duke OrgAdmin UI instead of the version range. You can also use the display name in any custom UIs you build.

    • Seat count: Define the multiplier used for the seat count when licenses are granted.

      For example, if you set this to 10, and you grant 2 seats when granting licenses with this product package, the license will have 20 seats.

      This can be useful, for example, if you’re selling a product that by default provides a certain number of seats.

      Let’s say you’re selling a product that provides 100 seats by default, and a customer orders two products. Rather than creating two separate licenses with 100 seats each, or implementing logic in your third-party licensing provisioning system to know that buying two products means that 200 seats need to be granted, you can use this Seat count multiplier to do the calculation. You set the multiplier to the product’s default seat count 100, and grant the license with 2 seats (matching the number of products bought): 200 seats are granted in the customer’s license.

      The minimum multiplier value is 1. If you set the value to zero, unlimited seats are granted.

    • Seat reservation count: If the product package (or licensed item) uses a custom license model that requires named seats and only allows seats to be reassigned for a limited number of times, define how many seat reservations altogether can be made for this licensed item’s seats (first-time assignments or reassignments).

      You do this by defining a multiplier for the license’s seat count.

      As an example, let’s say you grant 10 seats when granting a license with this product package. If this multiplier is set to 2, altogether 20 seat reservations can be made for this license. Now, if every seat is assigned to a user, each seat can be reassigned one more time to some other user.

      To allow unlimited seat reservations, leave the value empty or set it to zero (0). Use this option if the product package (or licensed item) uses either a floating license model or a named-seat custom license model that allows unlimited reassignments.

    • Use count: Define the multiplier used for the use count when licenses are granted. This works in the same way as the Seat count multiplier.

    • Use time: Define the multiplier used for the use time when licenses are granted. This works in the same way as the Seat count multiplier.

  3. Click the save icon in the corner of the section.

If you want to track the seat count, use count, or use time for the licenses, and you’re using a custom license model, make sure the custom license model has tracking enabled for that credit type.

Next steps

Now you can grant licenses to the product package.

You can either use SysAdmin or the 10Duke Entitlement Management REST API.

On this page