Create product packages

You can create product packages in 10Duke SysAdmin.

Before you start

Step 1: Create a product package

  1. In SysAdmin 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 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 date when the product package validity starts (at the start of the day in UTC time). Use the format YYYY-MM-DD.

      • Valid until (optional): Define the date when the product package validity ends (at the start of the day in UTC time). 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

With the default settings, each licensed item will grant a seat-based license that has one seat and uses the same license model as the product package.

You can change the credit and license model for each licensed item as needed, and define optional settings such as allowed software versions:

  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: Select a license model for this licensed item. By default, a licensed item uses the same license model as the product package.

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

      If you later change the license model of the product package, you can choose whether to apply the same license model to all the licensed items in the product package as well.

    • 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 number of seats included (the minimum value is 1).

      For example, if you’re selling a product that by default provides a certain number of seats, define the seat count here.

      To grant no seats, set the value to zero. To grant unlimited seats, leave the field empty.

    • Seat reservation count: If you defined a seat count, and the product package (or the 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 value that acts as a multiplier for the license’s (final) seat count, determining the total number of seat reservations that can be made.

      As an example, let’s say you grant a license with 10 seats using this product package. If this multiplier is set to 2, altogether 20 seat reservations can be made for this license. Now, if each of the 10 seats 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.

      Only affects licenses provisioned through the REST API. Licenses granted using SysAdmin have unlimited seat reassignments.

    • Use count: Define the use count included (the minimum value is 1).

      To grant no use count, set the value to zero.

      When you grant licenses using SysAdmin, the use count you define there overrides this value.

    • Use time: Define the use time included in milliseconds (the minimum value is 1).

      To grant no use time, set the value to zero.

      When you grant licenses using SysAdmin, the use count you define there overrides this value.

  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 using the product package.

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

On this page