Update licenses

You can update an organization’s or user’s licenses on the Transactions tab in 10Duke SysAdmin.

You update licenses through the transaction they were granted with.

Licenses are also automatically updated by some other actions, such as if you edit the license model, or the licensed items themselves.

What happens in a transaction update?

In addition to making changes to existing licenses, you can use a transaction update to grant and delete licenses.

Edit an existing transaction item’s settings to make changes to the licenses. All the licenses granted with that transaction item will be updated accordingly.

For example, you can extend the license validity, or change the product package quantity to update the granted credit in the licenses.
Add a new transaction item to grant new licenses, which will be associated with this existing transaction.
Delete a transaction item to delete the licenses that have been granted with that transaction item.

It’s important to understand that the update reprocesses the whole transaction.

This may result in additional license updates than just the ones you made, if there have been changes in the product packages used by the transaction:

The update always uses the latest credit settings of licensed items in the product packages, and this also affects the existing licenses associated with the transaction.

This means you may see changes in the granted credit amount (or even credit type) in licenses even if you didn’t change the product package quantity in the transaction item. For example, if a particular licensed item in a product package now grants more seats than before, the seat count in the corresponding license is updated accordingly.
If new licensed items have been added to a product package, new licenses are granted automatically.

However, licenses are not deleted even if the corresponding licensed item has been removed from the product package.

Because there are certain limitations to what license updates can be done, you may sometimes choose to delete a transaction item to delete the associated licenses, and add a new transaction item to grant new licenses with the applicable product package and the latest licensed item settings.

In that case, note the following if you’re updating an organization’s transaction:

This may affect users’ and device clients’ access to the licenses, if the deleted licenses were in some other entitlement than where you’re placing the new licenses.
Any seat reservations to the deleted licenses are also deleted. Similarly, if a user or device client has been blocked through OrgAdmin from using the deleted license, the blocking is removed.

You can also update a transaction while it’s suspended. The existing licenses and any new licenses granted in the update will remain suspended.

Limitations

You can only edit a transaction’s contract details through the 10Duke Entitlement Management REST API.
You cannot change the external ID of the transaction, nor the external IDs of any existing transaction items in it.
You cannot change the product package used by an existing transaction item.
You cannot change the entitlement in an existing transaction item. This means the existing licenses cannot be moved by an update operation, and any new licenses created by an update are also placed in the currently defined entitlement.
Even though existing licenses are updated using the latest license credit settings from the product package, they are not affected by changes made to other settings in the product package. This means that existing licenses continue to use, for example, the same license model and allowed versions as before.

Before you start

Make sure the product packages used in the transaction are ready for granting and updating licenses.

Every product package in the transaction must be active and valid, even those used in transaction items that you’re not making changes to. Otherwise reprocessing the transaction fails.
If you want to define custom license properties, the license property feature must be enabled in your deployment configuration. Contact the 10Duke Integration Support team if needed.

Update licenses in a transaction

To update the transaction of an organization or user:

In SysAdmin in the left sidebar, go to LICENSES > either Organization or Personal.
Search and select the organization or user, and click Confirm.
Go to the Transactions tab. The transactions table opens.
Select the transaction you want to update and select Actions > Update. A side panel opens.
In the Transaction details step, you can only edit the type of the transaction in Transaction type.
Click Next, and in the Transaction items step, make changes to the transaction items as needed.

You can edit existing transaction items, and add and delete transaction items, in the same way as when creating a new transaction.

Changes to an existing transaction item will apply to all the licenses granted with that transaction item. For example, changing the validity period updates the same validity period to all the licenses.
Click Next, and review the information in the Summary step.
Click Process transaction to save the changes and to reprocess the transaction.

Next steps

The changes to existing licenses take effect after the cache has been refreshed (within 5 minutes by default). If a user or a device client is currently consuming a license that is no longer accessible to them (for example, it’s no longer valid or was deleted), the user or device client is able to continue consuming the license until the license lease expires or the client application tries to refresh the lease, whichever comes first.

If a license is updated by reducing the number of seats, this may result in a situation where there are more seat reservations than seats available. In this case, the seat reservations are in practice ignored and the seats are used like with a license model that has floating seats.

If the update granted new licenses to an organization, update group access to licenses if needed. You can also move the new licenses to other entitlements if needed.