Working with Legacy Applications

This article explains how to create and deploy a Legacy Application.
A Legacy Application is a valid DiaManT® application, manually created and configured as a set of corresponding files, archived into a ZIP file according to DiaManT® naming conventions.

Create Legacy App

To create a Legacy App, follow the steps below:

1. Go to the Orchestrator page in your OCP Console® and click +Create.
   

   

   
   

2. In the Create new application form:

   • In App Type, select Legacy.

   • In Application Name, use only Latin letters, numbers, and underscores.

3. Click Save.

You can manage Legacy Applications from the Orchestrator landing page.
Click the three‑dots icon next to the Legacy App to access the following options:

• Edit Description & Labels

• App as Flow

• Share

• Deploy

• Audio Manager

• Delete

Legacy App in Orchestrator Board

For a Legacy Application:

• The left sidebar with miniApps, Flows, Shared Flows, and Dialog Controls is disabled.

• The Event Handlers drawer on the right side is disabled.

This means you cannot add new blocks to Canvas or edit existing ones for a Legacy App created from raw XML data.

The Application Options Menu for a Legacy App includes:

• App as Flow

• Share

• Audio Manager

• Delete

You can use the Orchestrator chat feature to test your application as usual by clicking the chat icon in the lower‑right corner.

It is also possible to deploy a Legacy App directly from the Orchestrator board, as described below.

Deploy Legacy App

Deploy from Orchestrator landing page

To deploy a Legacy Application from the Orchestrator landing page:

1. Click the three‑dots icon to the right of the Legacy App name and select Deploy.
   A pop‑up window appears, prompting you to upload a ZIP file (drag and drop or click Browse Files).
   

   

   

2. Prepare the ZIP file:

   • The ZIP file must contain a folder with the same name and group as the Orchestrator application.

   • The folder must follow this format:
     {your_group}@SND_{yourAppName}
     where your_group and yourAppName are the same group and application name you used when creating the Legacy App in the Orchestrator UI.

   • Before uploading the ZIP file, make sure you have incremented the application version inside the XML file.

3. After you add the file, click Deploy.

   • If you uploaded the wrong file, click the Trash icon above the Deploy button, or click Cancel to close the pop‑up.

4. If the Legacy App is deployed successfully:

   • The file is sent directly to DiaManT®.

   • A green Success message appears in the upper‑right corner of the screen.

5. If deployment fails:

   • A red Error message appears explaining why the deployment failed.
     Make the required changes to the file, upload it again, and redeploy.

Deploy from Orchestrator board

You can also deploy a Legacy App directly from the Orchestrator board.
The deployment flow is the same as when deploying from the Orchestrator landing page: you upload a ZIP file with the required structure and then click Deploy.

Audio Uploads for Legacy Apps

You can add audio files to Legacy Apps using the Audio Manager.

To open the Audio Manager:

• Open the Legacy App and click the Application Options Menu button, or

• Find your Legacy App in the Orchestrator app list and click the action menu button on the right.

In the Audio Manager:

1. In Select Locales, choose the language(s) for which you want to upload audio.
   You can select multiple locales and upload files separately for each.

2. Prepare and upload audio files:

   • Files must be in WAV format.

   • Compress the files into a ZIP archive.

   • You can include multiple files per locale in a single ZIP archive.

   • Once uploaded, files remain available for that locale indefinitely.

3. After upload:

   • Click Download System Audio List to download a TXT file with the list of audio files.

   • The next time you add locales, you can download the list of locales that already have uploaded audio.

4. Click Save Changes to apply the changes and exit Audio Manager.