Complex and Multi-SKU Applications
Some vendor agreements cover more than one application, or include many licenses (SKUs) for the same application. For example, one Atlassian contract can cover both Jira and Confluence, and a Microsoft Enterprise Agreement can include Microsoft 365, Visio, Power Apps, and GitHub licenses. In Zluri, you add these as a single contract linked to every application it covers, with one line item for each license.
How Zluri handles multi-app contracts
- One contract, many applications. A contract can be linked to more than one application. Each line item belongs to one application.
- Main application. When a contract is linked to several applications, the first application becomes the contract's main application. The main application doesn't change later.
- Licenses aren't split. A license belongs to one application and is counted the same way as on a single-app contract.
Add a contract that covers several applications
- When you create the contract, add every application it covers under What is this Contract for?.
- In Contract Line Items, add a line item for each license, and choose its application in Application Name.
- To add a license for an application you didn't select in step 1, search for or create the application from the Application Name list. Zluri adds it to the contract's applications.
For the full steps, see Create a Contract.
When a line item has no application
Every line item needs an application. If a contract covers more than one application and a line item doesn't name one, the line item shows Not set under Application Name, and Zluri asks you to Assign an application to every line item before you continue. Zluri doesn't choose an application for you.
To fix it, click the edit icon on each line item that shows Not set and choose its application. See Contract Upload and Contract Mapping Process.
Contracts synced from a file, SDK, or connector
When contracts come into Zluri through a CSV file, the SDK, or a connector, the same contract can appear in several rows with a different application in each row. Zluri combines these rows into one contract linked to all the applications.
| If a license line | Zluri |
|---|---|
| Names an application | Adds the license to that application. The license's application takes priority over the contract row's application. |
| Names no application, and the contract has one application | Adds the license to that application. |
| Names no application, and the contract has several applications | Skips the license and shows it in the error report. |
| Names an application the contract doesn't have | Adds that application to the contract, then adds the license to it. |
| Names an application that doesn't exist in Zluri | Creates the application, then links it to the contract. |
Check application names for typosIf an application name in the file doesn't match an existing application, Zluri creates a new application with that name. For example, a typo such as "Snowflke" creates a new application called Snowflke and links the contract to it. Small differences, such as "slack" for Slack, usually still match the existing application.
Applications are added, never removed
A sync can add an application to a contract but can't remove one. If someone links an application to a contract in Zluri, it stays linked even if the file never mentions it. To remove it, edit the contract in Zluri.
Changes made in Zluri take priority
| If someone in Zluri | The next sync |
|---|---|
| Hasn't edited the contract | Adds applications from the file as usual. |
| Edited the contract's application list | Doesn't add applications. The edited list stays. |
| Edited the application list, and a new license arrives for an application that isn't on it | Skips the license and reports it. |
| Deleted a license | Doesn't add the license back. |
Error report messages
Skipped rows appear in the sync error report:
| Message | What to do |
|---|---|
| The license named no application and its contract covers several | Add the application name to the license line. |
| No application of that name exists in this organisation | Check the spelling of the application name. |
| The contract's applications were edited manually in Zluri | The application list is managed in Zluri. The file can't change it. |
| The contract's licenses were edited manually in Zluri | Licenses were deleted in Zluri. The file can't add them back. |
Related articles
- Create a Contract
- Contract Upload and Contract Mapping Process
- Bulk Contract Upload
- License Mapping
Updated about 2 hours ago