Manage Applications and Application Tags

In this section, you will find detailed instructions on how to import and export an Application or Application Tag between different groups or environments. Additionally, you will learn the steps to promote an Application effectively.

Export Application

To export the application, proceed as follows:

1. Select the application, click the options menu button on the right, and click the Export button.

2. In the opened form, you can select to export an Application or Application Tag.

• To export an Application, click Application. Here you may mark the Export with NLU box to also export NLU model references in the export files.
  

  

   

• To export an Application Tag, click Tag and select an Application Tag from the available ones in the dropdown menu.
  

  

   

• Click Export when completed. An EXPORT IN PROGRESS notification will appear, informing you that the export has been initiated. You can freely navigate away from the page while the export is processing - you do not need to remain on this screen.

• Once the export is complete, you will receive a notification. Click on it to open the Notifications panel.

• On the Export notification, click …more to expand, and then the Download app here link to download the exported file.

6. A notification will let you know of the download progress.

7. The exported application will be downloaded to the targeted folder as a ZIP file. Unpack the ZIP file to view the content. The ZIP file contains the Application with its agents, miniApps, Flows, global NLU configuration (found under nluConfig in the application's JSON file inside the app folder) and a Variables collection in JSON format.

Import an Application

You can import either an Application as is, or an Application Tag which is the application’s instance. You can read more about Application Tags.

Importing an Application

To import the application, follow the next steps:

1. Click the Import Application button.

2. In the Import Application form, select Application.

3. Choose the application you wish to import and place it onto the drop zone or click the Browse button to select the application manually.

4. Complete the fields as described below:

5. Group: Select the group in which the application will be available. You will see how many flows remain available in the selected group. This helps you determine whether you have sufficient capacity to complete the import, reducing failed imports due to quota limits. If the flow information is unavailable, it displays as N/A.

   • Rename App: To change the application's name, enter a new name. Note that renaming is only available for applications. Flows and miniApps cannot be renamed!

   • VB Profile: Select a Voice Biometric profile from the drop-down list.

     • If a VB profile already exists in the selected group, it will be utilized by the application.

     • If no VB profiles exist, a new one will be automatically created with a name based on the group name, such as mygroup_vb_profile.

     • If multiple profiles exist, you can choose from the available ones.

   • Import variables: If checked, the application’s variables will be imported along with the application. If unchecked, the variables collection will be excluded during the import.

   • Include imported NLU model references: This optional check-box allows you to reuse the NLU models within the same environment. For example, if you export an application, and then import it to the same environment under the new name, checking the Include imported NLU model references box allows to use already existing NLU models without creating new ones. If you import the application to the new environment, the new NLU models will be created automatically.

6. Select the NLU Deployment type:

   • Production (default) - this type complies with Production Grade SLAs. Use with your Production applications handling live traffic!

   • Testing - this type is cost efficient and used for Testing purposes only.

7. Click Import when finished.

8. A toast message will appear in the upper-right corner of the screen, indicating that the import is in progress.

9. Once the process is complete, you will receive a notification regarding the newly created variables, along with updates to existing variables.
   To view the service notification, simply click on the Bell icon and then select more to expand the notification text.

Importing an Application Tag

To import an Application Tag, follow the next steps:

1. Click the Import Application button.

2. In the Import Application form, click Tag.

3. Select an Application Tag you want to import, and place it onto the drop zone, or click the Browse button to manually select an Application Tag.

4. Fill in the fields as described below:

   • Application: Select the Application from the dropdown list of the available applications.

   • VB Profile: Select a Voice Biometric profile from the drop-down list.

     • If a VB profile already exists in the selected group, it will be utilized by the Application Tag.

     • If no VB profiles exist, a new one will be automatically created with a name based on the group name, such as mygroup_vb_profile.

     • If multiple profiles exist, you can choose from the available ones.

5. Choose the Deployment type:

   • Production (default) - this type complies with Production Grade SLAs. Use with your Production applications handling live traffic!

   • Testing - this type is cost efficient and used for Testing purposes only.

6. Click Import when finished.

7. A toast message will appear in the upper-right corner of the screen, indicating that the import is in progress.

8. Once the process is complete, you will receive a notification regarding the newly created variables, along with updates to existing variables.
   To view the service notification, simply click on the Bell icon and then select more to expand the notification text.

Importing a Large Application via the Chunked Upload API

The steps above use the Import Application form to send the whole archive in a single request. If your network path can't reliably complete one large upload (corporate firewall, proxy timeout, load balancer reset), use the chunked upload API instead. This API splits the archive into parts and uploads them one at a time.

To import a large application via the chunked upload API, proceed as follows:

1. Open a session and send a POST request to /api/v1/upload-sessions:

{
  "filename": "myapp.zip",
  "expected_size": 125829120,
  "total_parts": 3,
  "import_type": "app",
  "target_group": "my-group"
}

The response returns:

{
  "data": {
    "session_id": "5f1e...",
    "chunk_size": 8388608,
    "min_chunk_size": 5242880,
    "max_parts": 10000,
    "expires_at": "2026-09-04T12:00:00+00:00"
  }
}

2. Choose your part size and total_parts.

P_min = max(min_chunk_size, ceil(expected_size / max_parts))
P     = your chosen part size, P >= P_min
total_parts = ceil(expected_size / P)

3. Upload each part by sending a PUT request to /api/v1/upload-sessions/{session_id}/parts/{part_number}:

multipart/form-data: chunk=<bytes>, content_md5=<base64 md5>

Repeat for each part number up to total_parts. Re-uploading the same part number is safe.

4. Commit the upload by sending a POST request to /api/v1/upload-sessions/{session_id}/commit:

{ "parts": [...], "checksum_sha256": "<optional>" }

This always returns 202 with a result_id. A 422 response means parts are missing; retry only the part numbers listed in meta.missing_parts.

5. Poll the result by sending a GET request to /api/v1/results/{result_id}. This follows the same polling contract as the existing asynchronous /apps/import?async=true result.

Promote Application

Promoting an application allows to detach application traffic from different clusters.

Originally, if you want to deploy the application, it is deployed to the DiaManT Sandbox cluster (SND) where, for example, you can use the chat simulator to check the application. Promoting the application allows to create the copy of the deployed application which will be placed to the DiaManT Production cluster (PRD) with the real traffic, so that traffic for testing the application does not affect real calls.

To promote the application:

1. Select the application, open the Options menu on the right and click the Promote button.

2. You may select an Application Tag from the dropdown list of the available ones (optional). Otherwise, you can promote the application by not selecting any tag.

3. Confirm by clicking Promote.

4. A toast message will appear in the upper-right corner of the screen, indicating that promoting is in progress.

5. Once the process is complete, a service notification will display the import status. To see the service notification, click the Bell icon.

Navigate to Dashboard or miniApps in order to check the created clusters.

Application Tags

An Application Tag is an application’s instance. You can read more about Application Tags in Orchestrator User Guide. In the Environments Manager, you can find the list of all the Application Tags available for a particular Application.

List Application Tags

To find the list of Application Tags, click on a selected Application. This will open a page with SND (Sandbox) and PRD (Production) Application Tags available for the selected Application.

Delete an Application Tag

To delete an Application Tag, proceed as follows:

1. Click the Delete icon next to the selected Application Tag.

2. The following dialog box opens.

3. Type CONFIRM DELETE and confirm by clicking Delete. The Application Tag is deleted.