Application Options Menu

Options Menu

When clicking the Application Options menu button, you can see the following options:

• Incoming Attached Data

• Voice Biometrics

• Global Fields

• App as Flow

• Share

• Publish App

• Delete

Navigate directly to Incoming Attached Data and Voice Biometrics pages to read more about these features.

App as Flow

Please note that this feature is not available to all environments yet.

The App as Flow feature allows users to re-use Applications developed by others in their own applications similarly to Flows. It is possible for the Application to have configured Inputs and Outputs in order to receive or send values before or after shared Application could be used in a sub-dialog.

Inputs and Outputs can be configured without having an Application shared. Read more about Configure settings of miniApps and Flows in the corresponding section.

The Application becomes visible as Shared App after setting the groups in Share dialog even with no Inputs or Outputs configured.

To use the App as Flow option, follow the steps below:

1. Click the Options menu button on the Application name tab, and select App as Flow.

2. Configure the Input and Output Fields as described Configure settings of miniApps and Flows section. It is possible to assign multiple values. Also, you can switch the Report Flow toggle and select the reporting type for this Application/Flow. Read more about reporting type in the Manage Flowssection. Click Save when finished.

3. The success message appears when completed.

Share Application

Please note that this feature is not available to all environments yet.

The Share option allows to share the Application with other groups so that the users who don’t belong to your group could still use it. Note that you can select multiple groups. Once shared, the Application will be available in the Shared Flows and could be used as a sub-flow of the Application.

When working with Shared Flows, it is important to understand that certain elements and settings from the original application are not automatically carried over. When a Shared Flow is integrated into a different Application, it adopts the Global Settings of the new host application rather than retaining those from the original. This ensures each application retains its unique configuration, which may be essential due to different requirements or operational contexts.

The complete list of settings that will not be transferred through sharing an application are the below:

• Global settings

  • Errors

  • Error Handlers

  • Dialog End Handlers

  • Incoming Attached Data

  • Voice Biometrics Configuration

  • Global Fields

When integrating a Shared Application that includes Transfer Actions into a new Application, it's essential to ensure that these Transfer Actions are effectively replicated within the new Application.

Recreating Transfer Actions with the same names is crucial for the correct functionality of the Shared Application within a new environment, maintaining the integrity of workflows and ensuring the desired application behavior.

To share the Application, proceed as follows:

1. Click the Options menu button on the Application name tab, and select Share.

2. In the opened window select the group you want to share the Application with from the dropdown list. Click Save when finished.

3. When shared, the Application will appear in the Shared Flows section.

4. Once appeared in the Shared Flows section, these Flows are available to be dragged and dropped onto the canvas and can be managed as regular Flows. Read more about Flows in the Manage Flows section.

Publish App

Please note that this feature is not available to all environments yet.

Publishing provides the capability to capture and preserve the current state of the Application by creating app instances called Application tags. When you create a new Application instance, the system also generates the new instances of its miniApps and Flows, each marked with a configuration tag, same as Application tag.

Also, the system compiles all Application and Flows so that the sub-dialog could use a particular instance on the miniApp as needed. Different app instances can be used for running tests on the Application, deploying it to accept live traffic, or rolling back to a previous instance if needed by selecting the prior app instance.

All the app instances with corresponding tags are stored in a database.

After creating an application and clicking the Deploy button, you can refer to this application as a draft version.

To create a new app instance of an already deployed application, follow the steps below:

1. Click the Options menu button on the Application Options menu and select Publish App.

2. Enter the tag name to identify your application and click Save when finished.

When you publish the application, all the Flows and miniApps you've used get marked with a tag, and it's the same tag you entered in the pop-up window.

However, Shared Flows operate a bit differently. Since they were previously created by someone else, they already have their own tags generated by the owners of Shared Flows and were published with those tags. When you add a Shared Flow to the canvas, you can only add the reference to the tags or draft version by picking a specific tag for a Shared Flow.

For example, navigate to Shared Flows, select the Flow and place it onto the canvas. Click the Options menu in the right upper corner of the Flow and select the tag of the instance you want this Flow to have.

In case a Shared Flow is added to the canvas and its configuration refers to the draft version (with no tags), the application cannot be published since it’s prohibited to use draft versions of Shared Flows when publishing the application. You should reconfigure all used Shared Apps to have tags before publishing.

In case when Shared App Inputs/Outputs (I/O) were reconfigured after its tag publishing, the configuration displayed in UI will not reflect these changes due to existing feature implementation. Developers are recommended to avoid updating I/O configurations of their Shared Apps.

Delete a Dialog Application

To permanently delete a Dialog Application, do the following:

1. Select the Dialog Application you want to delete, click the Options menu button on the Dialog Application panel and choose the Delete option to open the confirmation window.

2. In the confirmation window, type CONFIRM DELETE in the corresponding field and click the Delete button to finish.

Once deleted, the Dialog Application can't be restored.