DES/Current/Designer/ApplicationSettings - Revision history

WikiSysop at 16:00, December 5, 2022

2022-12-05T16:00:38Z

WikiSysop at 14:00, August 16, 2022

2022-08-16T14:00:51Z

WikiSysop at 13:45, August 16, 2022

2022-08-16T13:45:50Z

Brian.Marshall.IX: Published

2022-03-03T15:42:11Z

Published

Marudhu.pandian@genesys.com: Published

2021-09-20T15:40:53Z

Published

Brian.marshall@genesys.com: Published

2021-06-24T19:24:44Z

Published

Ed.jamer@genesys.com: Ed.jamer@genesys.com moved page PEC-ROU/Current/Designer/ApplicationSettings to DES/Current/Designer/ApplicationSettings: Text replacement - "PEC-ROU/Current/Designer/" to "DES/Current/Designer/"

2021-04-21T13:57:41Z

Ed.jamer@genesys.com moved page PEC-ROU/Current/Designer/ApplicationSettings to DES/Current/Designer/ApplicationSettings: Text replacement - "PEC-ROU/Current/Designer/" to "DES/Current/Designer/"

Brian.marshall@genesys.com: Published

2021-03-11T18:33:06Z

Published

Brian.marshall@genesys.com: Published

2021-03-11T14:50:49Z

Published

Brian.marshall@genesys.com: Published

2021-01-25T19:13:29Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Application Settings
|TocName=Application Settings
|Context=Learn how to configure the settings for your application.
|ComingSoon=No
|Platform=GenesysEngage-onpremises
|Role=Administrator
|Application=Designer
|Section={{Section
|sectionHeading=Managing the application settings
|anchor=manage
|alignment=Vertical
|structuredtext=When an application is open for editing, you can click [[file:des_gear_icon.png]] '''Settings''' to view and manage the settings for that application.
|Status=No
}}{{Section
|sectionHeading=General
|anchor=general
|alignment=Vertical
|structuredtext=*'''Application Reporting Title''' - Specify the name of this application that will be used in reporting.
*'''Application Version''' - Specify a version number for this application.
*'''Stage''' - Select an application stage. If {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=caching|display text=resource caching}} is enabled, the application stage also manages how often cached resources are checked for updates. By default, applications are in the '''Live''' stage.
|Status=No
}}{{Section
|sectionHeading=Media
|anchor=media
|alignment=Vertical
|structuredtext=*'''Media Resource Collection''' - Select the Media Collection that this application will use. See the {{Link-SomewhereInThisManual|topic=MediaResources|anchor=top|display text=Media Resources}} page for more information.
|Status=No
}}{{Section
|sectionHeading=Reporting
|anchor=reporting
|alignment=Vertical
|structuredtext=*'''Milestone Path Prefix''' - Specify a prefix to use with this application's {{Link-SomewhereInThisManual|topic=Milestone|anchor=top|display text=milestone}} paths.
|Status=No
}}{{Section
|sectionHeading=DTMF Options
|anchor=dtmf_options
|alignment=Vertical
|structuredtext=This tab enables you to set global DTMF commands for your application. These DTMF keys can be used at any time within the application to trigger a specified action.

A common use case for this feature is a global command for the DTMF key '''0''' that routes the caller directly to an agent. In this example, you can set '''0''' as a global DTMF command that routes directly to the '''Assisted Service''' phase. In your application, you can add a {{Link-SomewhereInThisManual|topic=PlayMessage|anchor=top|display text=Play Message block}} to announce that callers can press '''0''' at any time to speak to an agent.

Selecting '''Enable Global Commands''' enables global DTMF commands for the application.

To set a global DTMF command, select the drop-down menu beside the corresponding DTMF key that you want to use. In the drop-down menu, select a target block or phase for the DTMF key. Click '''OK''' when you are done setting global DTMF commands.

Global DTMF commands can target the '''Self Service''', '''Assisted Service''', or '''Finalize''' phase, or any block within the '''Self Service''' phase.{{NoteFormat|
*If the same DTMF key is also used by a block within your application, Designer first processes the command in the block.
*You can also use global DTMF commands with '''Self Service''' type {{Link-SomewhereInThisManual|topic=SharedModulesBar|anchor=top|display text=shared modules}}.}}
|Status=No
}}{{Section
|sectionHeading=Speech Recognition
|anchor=speech_recognition
|alignment=Vertical
|structuredtext=Configure settings for speech recognition (ASR). See the {{Link-SomewhereInThisManual|topic=UserInput|anchor=top|display text=User Input block}} page for more information.
|Status=No
}}{{Section
|sectionHeading=Global Retry
|anchor=global_retry
|alignment=Vertical
|structuredtext=This tab lets you specify a global retry prompt to play if a customer provides input that is not recognized. When '''Allow Retries''' is enabled, you can specify the following settings:

*'''Number of No Input retries allowed'''
*:Select the number of retries to allow for customers who do not provide any input. For each retry, you can specify whether a prompt is played by clicking the corresponding section beneath this field. For example, if you allow two no-input retries and you want to play a prompt after the first retry, select the '''No Input #1''' line and add a prompt. Enable the '''Play original menu prompt after this retry prompt''' check box to repeat the menu prompts for the caller.
*'''Number of No Match retries allowed'''
*:Select the number of retries to allow for customers who do not provide a match for a '''Menu Block'''. For each retry, you can specify whether a prompt is played by clicking the corresponding section beneath this field. For example, if you allow two no-input retries and you want to play a prompt after the first retry, select the '''No Match #1''' line and add a prompt. Enable the '''Play original menu prompt after this retry prompt''' check box to repeat the menu prompts for the caller.
*'''After Final No Input'''
*:Add the prompt to play after the maximum number of permitted '''No Input''' retries is reached. If this block is in the Self Service phase, you can also specify a target destination for the application to jump to, such as another block in the Self Service phase or to the Assisted Service or Finalize phase of the application.
*'''After Final No Match'''
*:Add the prompt to play after the maximum number of permitted '''No Match''' retries is reached. If this block is in the Self Service phase, you can also specify a target destination for the application to jump to, such as another block in the Self Service phase or to the Assisted Service or Finalize phase of the application.

[[File:des_app_settings_global_retry.png]]
|Status=No
}}{{Section
|sectionHeading=Digital
|anchor=digital
|alignment=Vertical
|structuredtext=To enable a Default application type for chat interactions, select '''Enable omni-channel support for Default applications'''.

Select '''Continue processing when the customer leaves''' if you want Designer to continue processing the application after the customer leaves the chat session (this option does not apply to voice interactions). This option is only available for Default application types if omni-channel support is enabled.{{NoteFormat|If '''Continue processing when the customer leaves''' is not enabled, Designer will terminate the chat session when the customer leaves and jump directly to the '''Finalize''' phase. This can interrupt any ongoing processing, including routing.}}[[File:des_application_settings_digital.png]]
|Status=No
}}{{Section
|sectionHeading=Predictive Routing
|anchor=predictive_routing
|alignment=Vertical
|structuredtext=Select this option to enable support for predictive routing (as required for the {{Link-SomewhereInThisVersion|manual=Designer|topic=PredictiveRouting|display text=Predictive Routing block}}).[[File:des_application_settings_predictive_routing.png]]
|Status=No
}}{{Section
|sectionHeading=Contextual Data
|anchor=contextual_data
|alignment=Vertical
|structuredtext=Select '''Enable Customer Profile''' to allow Designer to retrieve certain details about the customer, such as their name and contact information. When this option is enabled, you can also choose to select the amount of interaction history data that Designer should collect for the customer.

[[File:des_app_settings_contextual_data.png]]{{NoteFormat|This option must be enabled if you are using the '''Last Called Agent''' option in the {{Link-SomewhereInThisVersion|manual=Designer|topic=RouteAgent|display text=Route agent block}}.}}
|Status=No
}}{{Section
|sectionHeading=Caching
|anchor=caching
|alignment=Vertical
|structuredtext=Resource caching can improve overall system performance, but it can also cause a delay in how long it takes for changes in Designer to take effect (changes to Data Tables and Business Controls take effect immediately).

In most cases, it is best to leave '''Use workspace cache settings''' selected (it is already selected by default), as each application stage has optimized settings for how often a resource is checked. But you can disable it if you want the application to regularly check the cached resources for updates, and enter your own values for each resource.

The following resources are cached:

*Media Resources
*Speech Grammars
{{NoteFormat|Default values are set by Genesys for optimal performance. Although you can change these values, doing so might negatively impact application performance. Contact your Genesys representative for additional information that might apply to your environment.}}
|Status=No
}}{{Section
|sectionHeading=Misc
|anchor=misc
|alignment=Vertical
|structuredtext=From the '''Misc''' tab, you can enable the '''Parallel Test Environment''', '''Tracing''', and '''Wait Answering Machine''' options.[[File:des_application_settings_misc.png]]
{{AnchorDiv|pte}}
====PTE (Parallel Test Environment)====

Enable the '''PTE''' (Parallel Test Environment) option if you want non-production streams (DEV, QA, UAT) to use test versions of resources instead of the resources being used in the LIVE production environment.

For more information, see {{Link-SomewhereInThisManual|topic=AppStruc|anchor=pte|display text=Parallel Test Environment (PTE)}} on the {{Link-SomewhereInThisManual|topic=AppStruc|anchor=top|display text=Application Workflow}} page.

====Tracing====
Enabling the '''Tracing''' option enables additional data to be collected while the application runs, which can later be used for debugging.

{{NoteFormat|This option should only be enabled when required, as it impacts application performance.}}

====Wait Answering Machine====
This option tells Designer to wait for an answering machine beep (i.e. the tone that signals the caller to begin recording their message) during an outbound call. For example, if the customer does not answer the call, the application waits for an answering machine beep before playing a message.
|Status=No
}}
}}

@@ Line 25: / Line 25: @@
 |sectionHeading=Media
 |anchor=media
-|alignment=Vertical
+|alignment=Horizontal
-|structuredtext=*'''Media Resource Collection''' - Select the Media Collection that this application will use. See the {{Link-SomewhereInThisManual|topic=MediaResources|anchor=top|display text=Media Resources}} page for more information.
+|Media=Image
 |Status=No
 }}{{Section
@@ Line 70: / Line 97: @@
 |image=Des_app_settings_global_retry.png
 |AltText=Global Retry tab of the Application Settings
-|structuredtext=This tab lets you specify a global retry prompt to play if a customer provides input that is not recognized. When '''Allow Retries''' is enabled, you can specify the following settings:
+|structuredtext=This tab lets you specify a global retry prompt to play if a customer provides input that is not recognized. When '''Allow Retries''' is enabled, you can specify the '''No Input''' and '''No Match''' settings.
-*'''Number of No Input retries allowed'''
+These settings are described in more detail in the section below.
-*:Select the number of retries to allow for customers who do not provide any input. For each retry, you can specify whether a prompt is played by clicking the corresponding section beneath this field. For example, if you allow two no-input retries and you want to play a prompt after the first retry, select the '''No Input #1''' line and add a prompt. Enable the '''Play original menu prompt after this retry prompt''' check box to repeat the menu prompts for the caller.
+|structuredtextwide=====Number of No Input retries allowed====
-*'''Number of No Match retries allowed'''
-*:Select the number of retries to allow for customers who do not provide a match for a '''Menu Block'''. For each retry, you can specify whether a prompt is played by clicking the corresponding section beneath this field. For example, if you allow two no-input retries and you want to play a prompt after the first retry, select the '''No Match #1''' line and add a prompt. Enable the '''Play original menu prompt after this retry prompt''' check box to repeat the menu prompts for the caller.
+:Select the number of retries to allow for customers who do not provide any input. For each retry, you can specify whether a prompt is played by clicking the corresponding section beneath this field. For example, if you allow two no-input retries and you want to play a prompt after the first retry, select the '''No Input #1''' line and add a prompt. Enable the '''Play original menu prompt after this retry prompt''' check box to repeat the menu prompts for the caller.
-*'''After Final No Input'''
-*:Add the prompt to play after the maximum number of permitted '''No Input''' retries is reached. If this block is in the Self Service phase, you can also specify a target destination for the application to jump to, such as another block in the Self Service phase or to the Assisted Service or Finalize phase of the application.
+====Number of No Match retries allowed====
-*'''After Final No Match'''
-*:Add the prompt to play after the maximum number of permitted '''No Match''' retries is reached. If this block is in the Self Service phase, you can also specify a target destination for the application to jump to, such as another block in the Self Service phase or to the Assisted Service or Finalize phase of the application.
+:Select the number of retries to allow for customers who do not provide a match for a '''Menu Block'''. For each retry, you can specify whether a prompt is played by clicking the corresponding section beneath this field. For example, if you allow two no-input retries and you want to play a prompt after the first retry, select the '''No Match #1''' line and add a prompt. Enable the '''Play original menu prompt after this retry prompt''' check box to repeat the menu prompts for the caller.
 |Status=No
 }}{{Section
@@ Line 88: / Line 123: @@
 |image=Des_application_settings_digital_03.png
 |AltText=Application Settings - Digital tab
-|structuredtext=To enable a Default application type for chat interactions, select '''Enable omni-channel support for Default applications'''. This allows the application to service both voice and chat channels. For example, during chat sessions, the application displays voice prompts as chat messages.
+|structuredtext=The '''Digital''' tab of the application settings allows you to enable omni-channel support for Default applications. When enabled, it allows your application to handle both voice and chat interactions.
-In the '''Designer Application party name''' field, you can enter a name to use for the chat participant. This is the name that customers will see displayed in the chat widget when they join the chat session. If you don't specify a party name, the '''Application Reporting Title''' (as specified in the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=general|display text=General}} tab) is used.
+If you disable this option, Designer immediately terminates the chat session when the customer leaves and jumps directly to the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationPhases|anchor=finalize|display text=Finalize}} phase. Note that this can interrupt any on-going processing, including routing.
-Select '''Continue processing when the customer disconnects''' if you want Designer to continue processing the application after the customer leaves the chat session (this option does not apply to voice interactions). Otherwise, Designer terminates the chat session when the customer leaves and jumps directly to the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationPhases|anchor=finalize|display text=Finalize}} phase. This can interrupt any on-going processing, including routing. This option is only available for Default application types if omni-channel support is enabled.
+====Terminate the interaction when the customer disconnects====
-Select '''Terminate the interaction when the customer disconnects''' to terminate the interaction if the customer leaves the chat session.
+However, if both this option and the '''Continue processing when the customer disconnects''' option are enabled, Designer continues processing blocks that do not require any interaction or involvement with the customer, such as executing an HTTP request, while skipping any blocks that would require the customer to be present (such as sending a message or requesting input).
-Select '''Terminate the interaction when the interaction is stale''' to terminate the interaction if it is stale.
+Note that this can create a delay in closing the interaction that can cause Designer to sometimes report the interaction as Abandoned. If you want Designer to terminate the interaction immediately when the customer disconnects, enable this option but make sure that '''Continue processing when the customer disconnects''' is disabled.
-<br />
+====Terminate the interaction when the interaction is stale====
-|structuredtextwide={{NoteFormat|If both the '''Continue processing when the customer disconnects''' and '''Terminate the interaction when the customer disconnects''' options are enabled, Designer processes any subsequent blocks after the customer disconnects before executing a {{Link-SomewhereInThisVersion|manual=Designer|topic=TerminateCall|display text=Terminate Call}} block or ending the session (it does not jump automatically to the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationPhases|anchor=finalize|display text=Finalize}} phase). This delay in closing the interaction can cause Designer to report it as Abandoned.|}}
+This option is enabled by default and terminates the chat interaction if it has gone stale.
 {{NoteFormat|If your application is using the same TTS prompts and messages for both voice and chat channels, any {{Link-SomewhereInThisVersion|manual=Designer|topic=MediaResources|anchor=ssml|display text=SSML tags}} being used will be displayed in chats. To prevent this, set the '''removeSSMLInChat''' {{Link-SomewhereInThisVersion|manual=Designer|topic=Variables|anchor=SystemVariables|display text=system variable}} to <code>true</code>. |}}

@@ Line 119: / Line 119: @@
 |image=Des_app_settings_contextual_data.png
 |AltText=Contextual Data tab of the Application Settings
-|structuredtext=The '''Enable Customer Profile''' option enables Designer to retrieve certain details about the customer (such as their name, phone number, and email address) for the purpose of customer identification. For voice calls, Designer can identify the caller based on their phone number (ANI). For digital interactions, the contact's email address can be passed to Designer when the interaction starts. You can then choose how much {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=interaction_history_data|display text=interaction history data}} to collect for each customer.
+|structuredtext=The '''Enable Customer Profile''' option tells Designer to retrieve certain details about the customer associated with the incoming interaction (such as their name, phone number, and email address). For voice calls, Designer identifies the caller based on their phone number (ANI). For digital interactions, the contact's email address is used. You can then choose how much {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=interaction_history_data|display text=interaction history data}} to query for each customer.
 This contextual data can then be used in the application to provide a more personalized experience for the customer&mdash;for example, by playing announcements that are specifically designed for them or using the {{Link-SomewhereInThisVersion|manual=Designer|topic=RouteAgent|anchor=AgentRoutingtab|display text=Last Called Agent}} routing option to direct the customer to the last agent they spoke with.
@@ Line 126: / Line 126: @@
 |structuredtextwide={{AnchorDiv|interaction_history_data}}
 ===Interaction history data===
-When the '''Enable Customer Profile''' option is enabled, you can choose how much interaction history data to collect for each contact. By default, Designer collects 30-days of interaction history data, but you can adjust this to 1 hour, 24 hours, or choose to disable the interaction history entirely.
+When the '''Enable Customer Profile''' option is enabled, you can choose how much interaction history data to retrieve for the customer. By default, Designer retrieves 30-days of interaction history data, but you can adjust this to 1 hour, 24 hours, or choose to disable the interaction history entirely.
-Designer uses the following functions to retrieve the interaction history data:
+Designer provides the following functions to work with the interaction history data:
 *''getInteractionCount()'' &mdash; returns the number of interactions for the contact.

@@ Line 59: / Line 59: @@
 |sectionHeading=Global Retry
 |anchor=global_retry
-|alignment=Vertical
+|alignment=Horizontal
 |structuredtext=This tab lets you specify a global retry prompt to play if a customer provides input that is not recognized. When '''Allow Retries''' is enabled, you can specify the following settings:
@@ Line 70: / Line 73: @@
 *'''After Final No Match'''
 *:Add the prompt to play after the maximum number of permitted '''No Match''' retries is reached. If this block is in the Self Service phase, you can also specify a target destination for the application to jump to, such as another block in the Self Service phase or to the Assisted Service or Finalize phase of the application.
 |Status=No
 }}{{Section
@@ Line 78: / Line 79: @@
 |alignment=Horizontal
 |Media=Image
-|image=des_application_settings_digital_02.png
+|image=Des_application_settings_digital_03.png
 |structuredtext=To enable a Default application type for chat interactions, select '''Enable omni-channel support for Default applications'''. This allows the application to service both voice and chat channels. For example, during chat sessions, the application displays voice prompts as chat messages.
 In the '''Designer Application party name''' field, you can enter a name to use for the chat participant. This is the name that customers will see displayed in the chat widget when they join the chat session. If you don't specify a party name, the '''Application Reporting Title''' (as specified in the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=general|display text=General}} tab) is used.
-Select '''Continue processing when the customer disconnects''' if you want Designer to continue processing the application after the customer leaves the chat session (this option does not apply to voice interactions). This option is only available for Default application types if omni-channel support is enabled.
+Select '''Continue processing when the customer disconnects''' if you want Designer to continue processing the application after the customer leaves the chat session (this option does not apply to voice interactions). Otherwise, Designer terminates the chat session when the customer leaves and jumps directly to the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationPhases|anchor=finalize|display text=Finalize}} phase. This can interrupt any on-going processing, including routing. This option is only available for Default application types if omni-channel support is enabled.
-{{NoteFormat|If '''Continue processing when the customer disconnects''' is not enabled, Designer will terminate the chat session when the customer leaves and jump directly to the '''Finalize''' phase. This can interrupt any ongoing processing, including routing.}}
+Select '''Terminate the interaction when the customer disconnects''' to terminate the interaction if the customer leaves the chat session.
-Select '''Terminate the interaction when the customer disconnects''' to terminate the interaction if the customer leaves the chat session.
+Select '''Terminate the interaction when the interaction is stale''' to terminate the interaction if it is stale.
-Select '''Terminate the interaction when the interaction is stale''' to terminate the interaction if there does not appear to be any activity.
+{{NoteFormat|If your application is using the same TTS prompts and messages for both voice and chat channels, any {{Link-SomewhereInThisVersion|manual=Designer|topic=MediaResources|anchor=ssml|display text=SSML tags}} being used will be displayed in chats. To prevent this, set the '''removeSSMLInChat''' {{Link-SomewhereInThisVersion|manual=Designer|topic=Variables|anchor=SystemVariables|display text=system variable}} to <code>true</code>. |}}
 |Status=No
 }}{{Section
 |sectionHeading=Predictive Routing
 |anchor=predictive_routing
-|alignment=Vertical
+|alignment=Horizontal
-|structuredtext=Select this option to enable support for predictive routing (as required for the {{Link-SomewhereInThisVersion|manual=Designer|topic=PredictiveRouting|display text=Predictive Routing block}}).[[File:des_application_settings_predictive_routing.png]]
+|Media=Image
 |Status=No
 }}{{Section
 |sectionHeading=Contextual Data
 |anchor=contextual_data
-|alignment=Vertical
+|alignment=Horizontal
-|structuredtext=Select '''Enable Customer Profile''' to allow Designer to retrieve certain details about the customer, such as their name and contact information. When this option is enabled, you can also choose to select the amount of interaction history data that Designer should collect for the customer.
+|Media=Image
+|image=Des_app_settings_contextual_data.png
-[[File:des_app_settings_contextual_data.png]]{{NoteFormat|This option must be enabled if you are using the '''Last Called Agent''' option in the {{Link-SomewhereInThisVersion|manual=Designer|topic=RouteAgent|display text=Route agent block}}.}}
+|AltText=Contextual Data tab of the Application Settings
 |Status=No
 }}{{Section
@@ Line 122: / Line 131: @@
 |sectionHeading=Misc
 |anchor=misc
-|alignment=Vertical
+|alignment=Horizontal
-|structuredtext=From the '''Misc''' tab, you can enable the '''Parallel Test Environment''', '''Tracing''', and '''Wait Answering Machine''' options.[[File:des_application_settings_misc.png]]
+|Media=Image
 {{AnchorDiv|pte}}
 ====PTE (Parallel Test Environment)====
@@ Line 142: / Line 154: @@
 |sectionHeading=Language
 |anchor=language
-|alignment=Vertical
+|alignment=Horizontal
 |structuredtext=From the '''Language''' tab, you can select the languages to be used for playing {{Link-SomewhereInThisVersion|manual=Designer|topic=IntelligentPrompts|display text=intelligent prompts}}.
 You can select multiple languages, up to a maximum of eight. When playing intelligent prompts, Designer uses the overall language setting in the application (for example, the language specified by the '''Language''' {{Link-SomewhereInThisVersion|manual=Designer|topic=Variables|anchor=SystemVariables|display text=system variable}} or a {{Link-SomewhereInThisVersion|manual=Designer|topic=ChangeLang|display text=Change Language}} block) to determine which language to use.
 {{NoteFormat|Genesys recommends reviewing these selections regularly (for example, when publishing the application) and deselecting any languages that are not needed.|2}}<br />

@@ Line 79: / Line 79: @@
 |Media=Image
 |image=des_application_settings_digital_02.png
-|structuredtext=To enable a Default application type for chat interactions,  select '''Enable omni-channel support for Default applications'''.
+|structuredtext=To enable a Default application type for chat interactions, select '''Enable omni-channel support for Default applications'''. This allows the application to service both voice and chat channels. For example, during chat sessions, the application displays voice prompts as chat messages.
 In the '''Designer Application party name''' field, you can enter a name to use for the chat participant. This is the name that customers will see displayed in the chat widget when they join the chat session. If you don't specify a party name, the '''Application Reporting Title''' (as specified in the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=general|display text=General}} tab) is used.

@@ Line 138: / Line 138: @@
 ====Wait Answering Machine====
 This option tells Designer to wait for an answering machine beep (i.e. the tone that signals the caller to begin recording their message) during an outbound call. For example, if the customer does not answer the call, the application waits for an answering machine beep before playing a message.
 |Status=No
 }}
 }}

← Older revision	Revision as of 13:57, April 21, 2021
(No difference)

@@ Line 2: / Line 2: @@
 |Standalone=No
 |DisplayName=Application Settings
-|TocName=Application Settings
+|TocName=Application settings
 |Context=Learn how to configure the settings for your application.
 |ComingSoon=No

@@ Line 18: / Line 18: @@
 |anchor=general
 |alignment=Vertical
-|structuredtext=*'''Application Reporting Title''' - Specify the name of this application that will be used in reporting.
+|structuredtext=*'''Application Reporting Title''' - Specify the name to use for the application in reporting.
 *'''Application Version''' - Specify a version number for this application.
 *'''Stage''' - Select an application stage. If {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=caching|display text=resource caching}} is enabled, the application stage also manages how often cached resources are checked for updates. By default, applications are in the '''Live''' stage.
@@ Line 76: / Line 76: @@
 |sectionHeading=Digital
 |anchor=digital
-|alignment=Vertical
+|alignment=Horizontal
 |structuredtext=To enable a Default application type for chat interactions,  select '''Enable omni-channel support for Default applications'''.
-Select '''Continue processing when the customer leaves''' if you want Designer to continue processing the application after the customer leaves the chat session (this option does not apply to voice interactions). This option is only available for Default application types if omni-channel support is enabled.{{NoteFormat|If '''Continue processing when the customer leaves''' is not enabled, Designer will terminate the chat session when the customer leaves and jump directly to the '''Finalize''' phase. This can interrupt any ongoing processing, including routing.}}[[File:des_application_settings_digital.png]]
+In the '''Designer Application party name''' field, you can enter a name to use for the chat participant. This is the name that customers will see displayed in the chat widget when they join the chat session. If you don't specify a party name, the '''Application Reporting Title''' (as specified in the {{Link-SomewhereInThisVersion|manual=Designer|topic=ApplicationSettings|anchor=general|display text=General}} tab) is used.
 |Status=No
 }}{{Section