Application Options Menu

Open the application and click the Application Options Menu button on the right to access the following options:

• Actions Menu

• Incoming Attached Data

• Voice Biometrics

• Global Fields

• Field Sensitivity

• Sensitive Terms Redaction

• Global TTS Configuration

• App as Flow

• Share Application

• Publish Application

• Delete Dialog Application

Actions Menu

The Actions Menu provides common actions such as copying, pasting, and deleting building blocks and nodes on the canvas, similar to Getting Started with Orchestrator | Orchestrator Keyboard Functions.

To access these actions:

1. Select the building block or node on the canvas.

2. Open the Application Options Menu.

3. Click Actions.

Incoming Attached Data

For more information about this feature, see the Configure Incoming Attached Data page.

Voice Biometrics

For more information about this feature, see the Voice Biometrics in Orchestrator page.

Global Fields

You can set specific fields as global. Global Fields are reusable across all miniApps and Flows within the Application. They can be used without repeatedly configuring them as inputs or outputs in each building block. Using Global Fields helps optimize the interaction between Orchestrator and external services.

To configure Global Fields:

1. Open the Application Options Menu and click Global Fields.
   

   

2. In the dialog, type the name of the Global Field and click + Add Global Field.
   

   

   • You can add multiple fields.

   • Click Save to finish.

3. Select a miniApp, open its Settings, and choose GlobalValue from the list of Input Fields.
   

   

Field Sensitivity

The Field Sensitivity feature in Orchestrator enables you to manage sensitive and non-sensitive data within a single application. It allows you to define which fields require protection so that sensitive data is stored and handled securely.

To configure field sensitivity:

1. In the Application tab, click the Options menu button and select Field Sensitivity.
   

   

2. In the Select Sensitive Fields drop-down, choose any field from the list.

3. In the Select Privacy menu, choose how the data in this field should be protected:

   • Irreversible Masking (***): the data is stored as masked text and becomes permanently inaccessible.

   • Envelope Encryption (AES 256): the data is stored in encrypted form; only administrators in the user’s organization can decrypt it.

   

4. Click Save.

5. Deploy the miniApp to apply the changes.

To verify the changes:

1. Access the DiaManT log file of the required dialog following the https://learn.ocp.ai/guides/ocp-monitor-user-guide#OCP%C2%AEMonitorUserGuide-DialogReviewdialog_review.

2. Locate the field you marked as sensitive. The value of this field will be masked with ***.

Sensitive Terms Redaction

Use the Sensitive Terms Redaction feature to specify words or phrases that must be masked in logs and transcripts during dialog execution. This helps ensure compliance with privacy policies by preventing storage of utterances and audio data that include user-defined sensitive terms.

Sensitive terms are managed per Application and behave similarly to Global Fields: once defined, they are automatically applied across all miniApps in the Application.

Terms marked as sensitive are masked (replaced with ***) in:

• DiaManT logs

• Call Detail Records (CDRs)

• Transcripts (if applicable)

To configure Sensitive Terms Redaction:

1. In the Application tab, click the Options Menu button and select Sensitive Terms Redaction.
   

   

2. In the pop-up modal, enter the terms you want to flag as sensitive.

   • Add each term in a separate input field.

   • Click + Add Sensitive Term to add more terms.
     

     

3. Click Save to apply the changes.

To configure Sensitive Terms Redaction:

Global TTS Configuration

The Global TTS Configuration feature allows you to configure the text-to-speech (TTS) engine that your Application uses. This configuration overrides any TTS settings defined within individual miniApps used in your Application.

To configure TTS globally:

1. In the Application tab, click the Options Menu button and select Global TTS Configuration.
   

   

2. Start typing a language name to find the corresponding locale, or choose it from the drop-down list. You can select multiple locales.
   

   

3. For each locale, you can add multiple profiles with different providers.

   • The first profile is set as the default.

   • To add another profile, click Add New Profile.

4. For each profile, configure:

   • Profile name

   • Provider

   • Voice

   • Volume

   • Speech rate
     Then click Save Changes to store your TTS configuration.

To switch from the default TTS profile to another one within your Application, use a Set Field building block:

• Field name: _TTSProfile_

• Field value: the name of the TTS profile you want to use

App as Flow

The App as Flow feature allows you to reuse Applications created by others, in the same way you reuse Flows. The Application can have configured Inputs and Outputs to receive or send values before or after the shared Application is executed as a sub-dialog.

Inputs and Outputs can be configured even before the Application is shared. For more details, see Configure Settings of miniApps and Flows.

The Application becomes visible as a Shared App after you set the groups in the Share dialog, even if no Inputs or Outputs are configured.

To use the App as Flow option:

1. In the Application tab, click the Options Menu button and select App as Flow.
   

   

2. Configure the Input Fields and Output Fields as described in the Configure Settings of miniApps and Flows section.
   

   

   • You can assign multiple values.

   • Optionally, toggle Report Flow and select the reporting type for this Application/Flow. For more details, see Manage Flows.

   • Click Save when finished.

3. A success message appears when the configuration is completed.
   

   

Share Application

The Share option allows you to share the Application with other groups so that users outside your group can still use it. You can select multiple groups.

Once shared, the Application becomes available in Shared Flows and can be used as a sub-flow within other Applications.

When working with Shared Flows, note the following:

• Certain elements and settings from the original Application are not transferred automatically.

• When a Shared Flow is integrated into a different Application, it adopts the Global Settings of the host Application rather than those of the original Application.

• This ensures each Application retains its own configuration, which may be required due to differing requirements or operational contexts.

To share the Application:

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

   

2. In the dialog, select one or more groups to share the Application with from the drop-down list.
   

   

3. Click Save.

After sharing:

1. The Application appears in the Shared Flows section.

2. You can drag and drop Shared Flows onto the canvas and manage them like regular Flows. For more details, see Manage Flows.

Publish Application

Publishing allows you to capture and preserve the current state of the Application by creating application instances called Application tags. When you create a new Application instance:

• The system also creates new instances of the miniApps and Flows used in the Application.

• Each of these is marked with a configuration tag that matches the Application tag.

• All Applications and Flows are compiled so that sub-dialogs can use a specific instance of a miniApp as needed.

Different application instances can be used to:

• Run tests on the Application

• Deploy the Application for live traffic

• Roll back to a previous instance by selecting an older tag

All application instances and their tags are stored in a database.

To create a new application instance for an already deployed Application:

1. In the Application Options Menu, click the Options menu button and select Publish App.
   

   

2. Enter a tag name to identify your Application.
   

   

3. Click Save.

For example:

1. Go to Shared Flows.

2. Select the Flow and place it onto the canvas.

3. Click the Options menu in the upper-right corner of the Flow.

4. Select the tag for the instance you want that Flow to use.

Delete Dialog Application

To permanently delete a Dialog Application:

1. Select the Dialog Application you want to delete, open the Application Options Menu, and choose Delete to open the confirmation window.
   

   

2. In the confirmation window, type CONFIRM DELETE in the confirmation field.
   

   

3. Click Delete to finish.