Jump to: navigation, search
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=options 9.0.000.72=
+
=options 9.0.000.98=
 
<pre>{
 
<pre>{
 
"parameters": [
 
"parameters": [
Line 8: Line 8:
 
"default_value": "60000",
 
"default_value": "60000",
 
"description": "Specifies the duration, in milliseconds, before the session is considered closed when the connection with the server is lost.",
 
"description": "Specifies the duration, in milliseconds, before the session is considered closed when the connection with the server is lost.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 21: Line 22:
 
"default_value": "5",
 
"default_value": "5",
 
"description": "Specifies, in seconds, the timer blinking interval.",
 
"description": "Specifies, in seconds, the timer blinking interval.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 34: Line 36:
 
"default_value": "2000",
 
"default_value": "2000",
 
"description": "Specifies the delay in milliseconds before triggering the CometD 'unavailability' ('Connection lost, reconnecting') message toast. In case a CometD 'availability' event is received before this delay, 'unavailability' message toast is canceled.",
 
"description": "Specifies the delay in milliseconds before triggering the CometD 'unavailability' ('Connection lost, reconnecting') message toast. In case a CometD 'availability' event is received before this delay, 'unavailability' message toast is canceled.",
 +
"version": "9.0.000.36",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
 
"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
 
"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.notif.cometd.service-availability.show-on-user-action",
 +
"display_name": "CometD Availability Notification delay",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the CometD disconnection period. This option is independent from 'system.notif.cometd.service-availability-delay'.",
 +
"version": "9.0.000.76",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.disconnected.browser-notif.events",
 +
"display_name": "Disconnected Browser Notification Events",
 +
"type": "config",
 +
"default_value": "ReconnectFailure,DisasterRecoveryFailure,LoginRequired",
 +
"description": "Specifies which connection failure and connection recovery states should display a browser notification.",
 +
"version": "9.0.000.87",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of events associated with application disconnection and disaster recovery.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.notif.browser-unsupported.ie11",
 +
"display_name": "Show unsupported notification for IE11",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether a browser unsupported notification is to be shown for IE11 browser",
 +
"version": "9.0.000.98",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 47: Line 92:
 
"default_value": "10",
 
"default_value": "10",
 
"description": "Specifies the duration, in seconds, that contextual warning messages are displayed in the windows of the application.",
 
"description": "Specifies the duration, in seconds, that contextual warning messages are displayed in the windows of the application.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 60: Line 106:
 
"default_value": "(http:\\/\\/(www.)?{{!}}https:\\/\\/(www.)?{{!}}ftp:\\/\\/(www.){{!}}www.){1}([0-9A-Za-z+&@#\\/%?=~_{{!}}!:,.;-]+\\.+[0-9A-Za-z]{2,6})([0-9A-Za-z+&@#\\/%?=~_{{!}}!:,.;-]*)?",
 
"default_value": "(http:\\/\\/(www.)?{{!}}https:\\/\\/(www.)?{{!}}ftp:\\/\\/(www.){{!}}www.){1}([0-9A-Za-z+&@#\\/%?=~_{{!}}!:,.;-]+\\.+[0-9A-Za-z]{2,6})([0-9A-Za-z+&@#\\/%?=~_{{!}}!:,.;-]*)?",
 
"description": "Specifies the regular expression that identifies a URL in the Case Information area. This option can be overridden by a routing strategy as described in this [https://docs.genesys.com/Documentation/HTCC/Current/IWWDep/OverridingInteractionWorkspaceOptions Configuration Guide].",
 
"description": "Specifies the regular expression that identifies a URL in the Case Information area. This option can be overridden by a routing strategy as described in this [https://docs.genesys.com/Documentation/HTCC/Current/IWWDep/OverridingInteractionWorkspaceOptions Configuration Guide].",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 73: Line 120:
 
"default_value": "false",
 
"default_value": "false",
 
"description": "Specifies whether a Feedback button is displayed in the About window.",
 
"description": "Specifies whether a Feedback button is displayed in the About window.",
 +
"version": "9.0.000.25",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 86: Line 134:
 
"default_value": "10000",
 
"default_value": "10000",
 
"description": "Specifies the maximum number of characters in the feedback message.",
 
"description": "Specifies the maximum number of characters in the feedback message.",
 +
"version": "9.0.000.25",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 94: Line 143:
 
},
 
},
 
{
 
{
"id": "system.feedback.log-size",
+
"id": "system.feedback.submit-after-disconnect",
"display_name": "The feedback log size.",
+
"display_name": "Enabled feedback submit after disconnect.",
 
"type": "config",
 
"type": "config",
"default_value": "1000",
+
"default_value": "false",
"description": "Specifies the number of characters from the last Log to send with the feedback.",
+
"description": "Specifies whether a Feedback dialog box is displayed the next time the agent logs in after a session closed due to the Cometd defense. Managed by the system.cometd.timeout option.",
 +
"version": "9.0.000.25",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 107: Line 157:
 
},
 
},
 
{
 
{
"id": "system.feedback.auto.log-size",
+
"id": "system.log-level",
"display_name": "The automatic feedback log size.",
+
"display_name": "The global log level",
 
"type": "config",
 
"type": "config",
"default_value": "10000",
+
"default_value": "Trace",
"description": "Specifies the number of characters from the last log to send with the automatic feedback.",
+
"description": "Specifies the global log level.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 120: Line 171:
 
},
 
},
 
{
 
{
"id": "system.feedback.auto.publish-interval",
+
"id": "system.feedback.log-level",
"display_name": "The auto feedback publish interval.",
+
"display_name": "The Feedback log level",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "trace",
"description": "Specifies the duration, in seconds, between auto feedback submission. If the value is less than 30s, this feature will not be activated",
+
"description": "Specifies the feedback log level.",
 +
"version": "9.0.000.25",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 133: Line 185:
 
},
 
},
 
{
 
{
"id": "system.feedback.auto.publish-retry",
+
"id": "system.telemetry.log-level",
"display_name": "The auto feedback publish retry.",
+
"display_name": "The Telemetry log level",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "Info",
"description": "Specifies the count, in numbers, to retry auto feedback submission. If the publish failed to post.",
+
"description": "Specifies the telemetry log level.",
 +
"version": "9.0.000.65",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 146: Line 199:
 
},
 
},
 
{
 
{
"id": "system.feedback.submit-after-disconnect",
+
"id": "system.notif.open-media.service-availability-delay",
"display_name": "Enabled feedback submit after disconnect.",
+
"display_name": "OpenMedia Service Availability Notification delay",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "15000",
"description": "Specifies whether a Feedback dialog box is displayed the next time the agent logs in after a session closed due to the Cometd defense. Managed by the system.cometd.timeout option.",
+
"description": "Specifies the delay, in milliseconds, before triggering the OpenMedia (Interaction Server) unavailability notification to an agent. If an OpenMedia availability is received before the delay, unavailability notification is cancelled.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 159: Line 213:
 
},
 
},
 
{
 
{
"id": "system.log-level",
+
"id": "system.notif.open-media.service-availability.show-on-user-action",
"display_name": "The global log level",
+
"display_name": "OpenMedia Service Availability Notification",
 
"type": "config",
 
"type": "config",
"default_value": "Trace",
+
"default_value": "true",
"description": "Specifies the global log level.",
+
"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the OpenMedia (Interaction Server) disconnection period. This option is independent from 'system.notif.open-media.service-availability-delay'.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 172: Line 227:
 
},
 
},
 
{
 
{
"id": "system.feedback.log-level",
+
"id": "system.notif.contact.service-availability-delay",
"display_name": "The Feedback log level",
+
"display_name": "Contact Service Availability Notification delay",
 
"type": "config",
 
"type": "config",
"default_value": "trace",
+
"default_value": "15000",
"description": "Specifies the feedback log level.",
+
"description": "Specifies the delay, in milliseconds, before triggering the UCS (Contact Server) unavailability notification to an agent. If a UCS availability is received before the delay, unavailability notification is cancelled.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
+
"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 185: Line 241:
 
},
 
},
 
{
 
{
"id": "auth.session.invalidate-on-logout",
+
"id": "system.notif.contact.service-availability.show-on-user-action",
"display_name": "Invalidate Auth SSO session on Workspace logout",
+
"display_name": "Contact Service Availability Notification",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Specifies whether the Auth SSO session persists when an agent logs out.<br>If true, when an agent exits Workspace, both Workspace and the Auth session are removed and the gent is redirected to the Auth login view.<br>If false, when an agent exits Workspace, only the Workspace session is removed and agent is redirected to a Workspace session ended view.",
+
"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the Contact (UCS) disconnection period. This option is independent from 'system.notif.contact.service-availability-delay'.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 198: Line 255:
 
},
 
},
 
{
 
{
"id": "openmedia.workitem-channels",
+
"id": "system.notif.statistic.service-availability-delay",
"display_name": "Enabled Workitem Channels",
+
"display_name": "Statistic Service Availability Notification delay",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "-1",
"description": "Specifies the list of Workitem channels an agent may use.",
+
"description": "Specifies the delay, in milliseconds, before triggering the Statistic Server unavailability notification to an agent. If a Statistic server availability is received before the delay, unavailability notification is cancelled.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid Media Types.",
+
"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 211: Line 269:
 
},
 
},
 
{
 
{
"id": "<media-type>.ringing-bell",
+
"id": "system.notif.statistic.service-availability.show-on-user-action",
"display_name": "Ringing bell",
+
"display_name": "Statistic Service Availability Notification",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the path of the sound file that is played when the interaction is ringing. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the character '{{!}}'. The first is the sound file name (BELL, RING, CHORD or WARNING predefined aliases or an absolute url to a mp3 file). Then, a priority, the higher the integer the higher the priority. And a duration (-1 means plays and repeats until an explicit message stops it with an established event for instance, 0 means to play the whole sound one time, an integer > 0 means a time in milliseconds to play and repeat the sound).",
+
"description": "Specifies if a notification is displayed when an agent action involves a call to the back-end during the Statistic server disconnection period. This option is independent from 'system.notif.statistic.service-availability-delay'.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 224: Line 283:
 
},
 
},
 
{
 
{
"id": "<media-type>.auto-answer",
+
"id": "system.notif.voice.service-availability-delay",
"display_name": "Auto Accept Incoming Interaction",
+
"display_name": "Voice Service Availability Notification delay",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "15000",
"description": "Specifies whether an interaction is automatically accepted and joined when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the delay, in milliseconds, before triggering the Voice unavailability notification to an agent. If a Voice availability is received before the delay, unavailability notification is cancelled.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 237: Line 297:
 
},
 
},
 
{
 
{
"id": "<media-type>.auto-answer.timer",
+
"id": "system.notif.voice.service-availability.show-on-user-action",
"display_name": "Auto Accept Timer For Incoming Interaction",
+
"display_name": "Statistic Service Availability Notification",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "true",
"description": "Specifies the time, in seconds, after which the inbound interaction of the specified type is automatically answered. A value of 0 means call is auto-ansewered immediately. For outbound push-preview interactions, use the 'outbound.push-preview.auto-answer.timer' instead. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the Voice server disconnection period. This option is independent from 'system.notif.voice.service-availability-delay'.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 250: Line 311:
 
},
 
},
 
{
 
{
"id": "<media-type>.auto-answer.enable-reject",
+
"id": "auth.session.invalidate-on-logout",
"display_name": "Reject button for incoming interaction with auto accept timer",
+
"display_name": "Invalidate Auth SSO session on Workspace logout",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "When the option '<media-type>.auto-answer' with matching media type is set to true and '<media-type>.auto-answer.timer' is greater than 0, this option specifies whether the 'Reject' button is enabled when the corresponding privilige is granted. For outbound push-preview interactions, use the 'outbound.push-preview.auto-answer.enable-reject' option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the Auth SSO session persists when an agent logs out.<br>If true, when an agent exits Workspace, both Workspace and the Auth session are removed and the gent is redirected to the Auth login view.<br>If false, when an agent exits Workspace, only the Workspace session is removed and agent is redirected to a Workspace session ended view.",
 +
"version": "9.0.000.46",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 263: Line 325:
 
},
 
},
 
{
 
{
"id": "<media-type>.prompt-for-done",
+
"id": "openmedia.workitem-channels",
"display_name": "Prompt for done",
+
"display_name": "Enabled Workitem Channels",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies if the application prompts a confirmation message when a user clicks the 'Done' button. This option is only available for interaction open media. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the list of Workitem channels an agent may use.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of valid Media Types.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 276: Line 339:
 
},
 
},
 
{
 
{
"id": "intercommunication.<media-type>.queue",
+
"id": "<media-type>.ringing-bell",
"display_name": "Routing Based Queue for Workitem",
+
"display_name": "Ringing bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for a Workitem. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
+
"description": "Specifies the path of the sound file that is played when the interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Name of a valid Script object of type Interaction Queue",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 289: Line 353:
 
},
 
},
 
{
 
{
"id": "intercommunication.<media-type>.routing-based-actions",
+
"id": "<media-type>.auto-answer",
"display_name": "Routing based actions for Workitem",
+
"display_name": "Auto Accept Incoming Interaction",
 
"type": "config",
 
"type": "config",
"default_value": "OneStepTransfer",
+
"default_value": "false",
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
+
"description": "Specifies whether an interaction is automatically accepted and joined when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 302: Line 367:
 
},
 
},
 
{
 
{
"id": "intercommunication.<media-type>.routing-based-targets",
+
"id": "<media-type>.auto-answer.timer",
"display_name": "Routing based targets for Workitem",
+
"display_name": "Auto Accept Timer For Incoming Interaction",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "0",
"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.<media-type>.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
+
"description": "Specifies the time, in seconds, after which the inbound interaction of the specified type is automatically answered. A value of 0 means call is auto-ansewered immediately. For outbound push-preview interactions, use the 'outbound.push-preview.auto-answer.timer' instead. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.68",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
+
"data_type": "An integer value greater than or equal to 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 315: Line 381:
 
},
 
},
 
{
 
{
"id": "security.inactivity-timeout",
+
"id": "<media-type>.auto-answer.enable-reject",
"display_name": "Inactivity Timeout",
+
"display_name": "Reject button for incoming interaction with auto accept timer",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "false",
"description": "Specifies the amount of time, in minutes, of agent inactivity (no mouse or keyboard usage) that triggers the application to log out. If the agent has been inactive longer than the number of minutes that are specified by this inactivity timeout, the agent session is ended. A value of 0 disables this inactivity timeout.",
+
"description": "When the option '<media-type>.auto-answer' with matching media type is set to true and '<media-type>.auto-answer.timer' is greater than 0, this option specifies whether the 'Reject' button is enabled when the corresponding privilige is granted. For outbound push-preview interactions, use the 'outbound.push-preview.auto-answer.enable-reject' option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.68",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 328: Line 395:
 
},
 
},
 
{
 
{
"id": "security.inactivity-alert-dialog-before-timeout",
+
"id": "<media-type>.prompt-for-done",
"display_name": "Inactivity Alert Dialog before Timeout",
+
"display_name": "Prompt for done",
 
"type": "config",
 
"type": "config",
"default_value": "30",
+
"default_value": "false",
"description": "Specifies when Workspace displays an alert dialog to warn the agent of the upcoming inactivity timeout. The value of this option, in seconds, tells Workspace how soon to display the alert before the timeout occurs. You must set this option to a value less than the value of security.inactivity-timeout.",
+
"description": "Specifies if the application prompts a confirmation message when a user clicks the 'Done' button. This option is only available for interaction open media. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 341: Line 409:
 
},
 
},
 
{
 
{
"id": "security.login.inactivity-timeout",
+
"id": "intercommunication.<media-type>.queue",
"display_name": "Inactivity Timeout",
+
"display_name": "Routing Based Queue for Workitem",
 
"type": "config",
 
"type": "config",
"default_value": "60",
+
"default_value": "No default value",
"description": "Specifies the amount of time, in seconds, of agent inactivity (no mouse or keyboard usage) that triggers the application to log out for the second step of the login (place selection, queue selection, language selection, etc.). If the agent has been inactive longer than the number of seconds that are specified by this inactivity timeout, the agent session is ended. A value of 0 disables this inactivity timeout.",
+
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for a Workitem. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "Name of a valid Script object of type Interaction Queue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 354: Line 423:
 
},
 
},
 
{
 
{
"id": "security.login.inactivity-alert-dialog-before-timeout",
+
"id": "intercommunication.<media-type>.routing-based-actions",
"display_name": "Inactivity Alert Dialog before Timeout",
+
"display_name": "Routing based actions for Workitem",
 
"type": "config",
 
"type": "config",
"default_value": "20",
+
"default_value": "OneStepTransfer",
"description": "Specifies when Workspace displays an alert dialog to warn the agent of the upcoming inactivity timeout for the second step of the login (place selection, queue selection, language selection, etc.). The value of this option, in seconds, tells Workspace how soon to display the alert before the timeout occurs. You must set this option to a value less than the value of security.login.inactivity-timeout.",
+
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 367: Line 437:
 
},
 
},
 
{
 
{
"id": "workspace.web-content",
+
"id": "intercommunication.<media-type>.routing-based-targets",
"display_name": "Workspace web extension views",
+
"display_name": "Routing based targets for Workitem",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "The list of Web Applications that are configured to be displayed at the Workspace level. Refer to the [[Documentation:HTCC:IWWDep:SettingUpAgents:Current{{!}}Procedure: Enabling integration of web applications in the agent interface]] for information about creating web application objects in the configuration layer.",
+
"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.<media-type>.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of option section names that correspond to the extension views, for example: Extension1, Extension2, etc...",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 380: Line 451:
 
},
 
},
 
{
 
{
"id": "service-client-api.accepted-web-content-origins",
+
"id": "security.inactivity-timeout",
"display_name": "Workspace web service API granted origins and allowed API",
+
"display_name": "Inactivity Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "0",
"description": "Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self-explanatory keywords:\n* 'agent.get'\n* 'agent.getStateList'\n* 'agent.setState'\n* 'agent.getState'\n* 'interaction.getInteractions'\n* 'interaction.getByInteractionId'\n* 'interaction.getByBundleId'\n* 'interaction.getByCaseId'\n* 'interaction.setUserData'\n* 'interaction.deleteUserData'\n* 'system.closeToast'\n* 'system.popupToast'\n* 'system.updateToast'\n* 'voice.dial'\n* 'voice.startCallRecording'\n* 'voice.stopCallRecording'\n* 'voice.pauseCallRecording'\n* 'voice.resumeCallRecording'\n* 'email.create'.<br>For example, the value for of this option could now be: http://my-web-server0, http://my-web-server1 , http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*).<br><br>In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial'. For the http://my-web-server3 domain, only the following requests are allowed:\n* 'agent.get'\n* 'agent.getStateList'\n* 'agent.setState'\n* 'agent.getState'\n* 'interaction.getInteractions'\n* 'interaction.getByInteractionId'\n* 'interaction.getByBundleId'\n* 'interaction.getByCaseId'\n* 'interaction.setUserData'\n* 'interaction.deleteUserData'.<br>In addition to filtering by origin, you can filter by API with a wildcard in parentheses after the allowed origin. This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": "Specifies the amount of time, in minutes, of agent inactivity (no mouse or keyboard usage) that triggers the application to log out. If the agent has been inactive longer than the number of minutes that are specified by this inactivity timeout, the agent session is ended. A value of 0 disables this inactivity timeout.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of URL or '*', for example: 'http://my-web-server-1,http://my-web-server-2' or '*'.",
+
"data_type": "An integer value greater than or equal to 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 393: Line 465:
 
},
 
},
 
{
 
{
"id": "service-client-api.user-data.read-allowed",
+
"id": "security.inactivity-alert-dialog-before-timeout",
"display_name": "Service user data allowed to read",
+
"display_name": "Inactivity Alert Dialog before Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "*",
+
"default_value": "30",
"description": "Specifies the list of keys that can be read in the user data. This applies to the userData property of the Interaction object returned by a function or an event.",
+
"description": "Specifies when Workspace displays an alert dialog to warn the agent of the upcoming inactivity timeout. The value of this option, in seconds, tells Workspace how soon to display the alert before the timeout occurs. You must set this option to a value less than the value of security.inactivity-timeout.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of user data key to allow, or '*' to allow every keys, for example: Key1,Key2,Key3",
+
"data_type": "An integer value greater than or equal to 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 406: Line 479:
 
},
 
},
 
{
 
{
"id": "service-client-api.user-data.write-allowed",
+
"id": "security.login.inactivity-timeout",
"display_name": "Service user data allowed to write",
+
"display_name": "Inactivity Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "*",
+
"default_value": "60",
"description": "Specifies the list of keys that the [[Documentation:HTCC:Dev:InteractionNamespace:Current#setUserData{{!}}interaction.setUserData()]] and [[Documentation:HTCC:Dev:InteractionNamespace:Current#deleteUserData{{!}}interaction.deleteUserData()]] functions can write to in the user data.",
+
"description": "Specifies the amount of time, in seconds, of agent inactivity (no mouse or keyboard usage) that triggers the application to log out for the second step of the login (place selection, queue selection, language selection, etc.). If the agent has been inactive longer than the number of seconds that are specified by this inactivity timeout, the agent session is ended. A value of 0 disables this inactivity timeout.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of user data key to allow, or '*' to allow every keys, for example: Key1,Key2,Key3",
+
"data_type": "An integer value greater than or equal to 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 419: Line 493:
 
},
 
},
 
{
 
{
"id": "service-client-api.rate-limit",
+
"id": "security.login.inactivity-alert-dialog-before-timeout",
"display_name": "Service request global rate limit",
+
"display_name": "Inactivity Alert Dialog before Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "20",
"description": "Specifies the limit for the maximum number of requests per minute on the Service Client API. This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": "Specifies when Workspace displays an alert dialog to warn the agent of the upcoming inactivity timeout for the second step of the login (place selection, queue selection, language selection, etc.). The value of this option, in seconds, tells Workspace how soon to display the alert before the timeout occurs. You must set this option to a value less than the value of security.login.inactivity-timeout.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0. 0 for unlimited rate.",
+
"data_type": "An integer value greater than or equal to 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 432: Line 507:
 
},
 
},
 
{
 
{
"id": "service-client-api.rate-limit.<service-name>",
+
"id": "workspace.web-content",
"display_name": "Service request per API rate limit",
+
"display_name": "Workspace web extension views",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "No default value",
"description": "Specifies the limit for the maximum number of requests per minute on a specific API request on the Service Client API. The <service-name> can be one of the following: \n* agent.get\n* agent.getStateList\n* agent.setState\n* agent.getState\n* interaction.getInteractions\n* interaction.getByInteractionId\n* interaction.deleteUserData\n* interaction.setUserData\n* media.getMediaList\n* media.setState\n* system.closeToast\n* system.popupToast\n* system.updateToast\n* voice.dial\n* voice.startCallRecording\n* voice.stopCallRecording\n* voice.pauseCallRecording\n* voice.resumeCallRecording\n* email.create<br>This option cannot be overridden, it must be set in the WSA Cluster Application.",
+
"description": "The list of Web Applications that are configured to be displayed at the Workspace level. Refer to the [[Documentation:HTCC:IWWDep:SettingUpAgents:Current{{!}}Procedure: Enabling integration of web applications in the agent interface]] for information about creating web application objects in the configuration layer.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0. 0 for unlimited rate.",
+
"data_type": "A comma-separated value list of option section names that correspond to the extension views, for example: Extension1, Extension2, etc...",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 445: Line 521:
 
},
 
},
 
{
 
{
"id": "service-client-api.rate-limit-quarantine-delay",
+
"id": "workspace.web-content.url-encoding-defense-enabled",
"display_name": "Service request global quarantine delay once the rate limit reached",
+
"display_name": "Workspace web extension views URL Encoding",
 
"type": "config",
 
"type": "config",
"default_value": "30",
+
"default_value": "INTERNAL",
"description": "Specifies the quarantine delay, in seconds, during which requests are ignored once the rate limit is reached. This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": "Specifies the list of modes on which the url encoding defense is applied. If the '<mode>' is not set, the url is unmodified (not encoded). If the '<mode>' is set but no hexadecimal character (%XX, where X is a hexa) is found in the url, the url is encoded. If the '<mode>{{!}}FORCE' is set, the url is always encoded.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0. 0 for infinite quarantine delay.",
+
"data_type": "A comma-separated list of one or more modes and the optional FORCE modifier in this format: <mode>[{{!}}FORCE]. Valid modes: INTERNAL, BACKGROUND, HIDDEN, EXTERNAL.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 458: Line 535:
 
},
 
},
 
{
 
{
"id": "service-client-api.block-markdone-timeout",
+
"id": "service-client-api.accepted-web-content-origins",
"display_name": "Block MarkDone Timeout",
+
"display_name": "Workspace web service API granted origins and allowed API",
 
"type": "config",
 
"type": "config",
"default_value": "1000",
+
"default_value": "No default value",
"description": "Specifies the duration, in milliseconds, of the timeout started by the 'interaction.blockMarkdone()' service. If this option is set, when an agent marks an interaction as Done, the Mark Done operation is delayed until the specified timeout has elapsed. During this interval, Mark Done can be blocked by using the serviceClientAPI 'blockMarkdone' operation. If Mark Done is blocked by 'serviceClientAPI', the Mark Done operation is cancelled. If the Mark Done is not blocked, the Mark Done operation occurs after the specified duration has elapsed. If Mark Done has been blocked by the 'blockMarkDone' operation from the 'serviceClientAPI', it can be unblocked by using the 'unblockMarkDone' operation from the 'serviceClientAPI'.",
+
"description": "Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self-explanatory keywords:\n* 'agent.get'\n* 'agent.getStateList'\n* 'agent.setState'\n* 'agent.getState'\n* 'interaction.getInteractions'\n* 'interaction.getByInteractionId'\n* 'interaction.getByBundleId'\n* 'interaction.getByCaseId'\n* 'interaction.setUserData'\n* 'interaction.deleteUserData'\n* 'system.closeToast'\n* 'system.popupToast'\n* 'system.updateToast'\n* 'voice.dial'\n* 'voice.startCallRecording'\n* 'voice.stopCallRecording'\n* 'voice.pauseCallRecording'\n* 'voice.resumeCallRecording'\n* 'email.create'.<br>For example, the value for of this option could now be: http://my-web-server0, http://my-web-server1 , http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*).<br><br>In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial'. For the http://my-web-server3 domain, only the following requests are allowed:\n* 'agent.get'\n* 'agent.getStateList'\n* 'agent.setState'\n* 'agent.getState'\n* 'interaction.getInteractions'\n* 'interaction.getByInteractionId'\n* 'interaction.getByBundleId'\n* 'interaction.getByCaseId'\n* 'interaction.setUserData'\n* 'interaction.deleteUserData'.<br>In addition to filtering by origin, you can filter by API with a wildcard in parentheses after the allowed origin. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than 0.",
+
"data_type": "A comma-separated value list of URL or '*', for example: 'http://my-web-server-1,http://my-web-server-2' or '*'.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 471: Line 549:
 
},
 
},
 
{
 
{
"id": "service-client-api.option.read-allowed-web-content-origin",
+
"id": "service-client-api.user-data.read-allowed",
"display_name": "Workspace web service API granted origins and read allowed options permission",
+
"display_name": "Service user data allowed to read",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "*",
"description": "Specifies the list of granted origins and read allowed options that are used in the web extension views. You can filter access to provisioning with the following self-explanatory keywords:\n* 'voice.*'\n* 'sipendpoint.*'\n* '...'<br>For example, the value of this option could now be: http://my-web-server0, http://my-web-server1 (*) , http://my-web-server2 (voice.*, system.*), http://my-web-server3 (sipendpoint.*, CustomSection/*).<br><br>In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following access to provisioning are allowed: 'voice.*', 'system.*'. For the http://my-web-server3 domain, only the following access to provisioning are allowed:\n* 'sipendpoint.*'\n* 'CustomSection/*'<br>This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": "Specifies the list of keys that can be read in the user data. This applies to the userData property of the Interaction object returned by a function or an event.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of URL or '*', with patterns for example: 'http://my-web-server-1,http://my-web-server-2(*),http://my-web-server-3(voice.*)' or '*'.",
+
"data_type": "A comma-separated value list of user data key to allow, or '*' to allow every keys, for example: Key1,Key2,Key3",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 484: Line 563:
 
},
 
},
 
{
 
{
"id": "main-window.window-title",
+
"id": "service-client-api.user-data.write-allowed",
"display_name": "Window Title",
+
"display_name": "Service user data allowed to write",
 
"type": "config",
 
"type": "config",
"default_value": "&#36;Window.Title&#36;",
+
"default_value": "*",
"description": "Specifies the title of the browser window or tab. You can specify any string andor combination of valid field codes up to the maximum width of the browser window title bar or tab. If all field codes are empty, the following field codes are used: &#36;Window.Title&#36;.",
+
"description": "Specifies the list of keys that the [[Documentation:HTCC:Dev:InteractionNamespace:Current#setUserData{{!}}interaction.setUserData()]] and [[Documentation:HTCC:Dev:InteractionNamespace:Current#deleteUserData{{!}}interaction.deleteUserData()]] functions can write to in the user data.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "&#36;Window.Title&#36;,&#36;Application.Title&#36;,&#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.EmployeeId&#36;.",
+
"data_type": "A comma-separated value list of user data key to allow, or '*' to allow every keys, for example: Key1,Key2,Key3",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 497: Line 577:
 
},
 
},
 
{
 
{
"id": "login.workmode",
+
"id": "service-client-api.rate-limit",
"display_name": "Workmode",
+
"display_name": "Service request global rate limit",
 
"type": "config",
 
"type": "config",
"default_value": "unknown",
+
"default_value": "0",
"description": "Specifies the workmode that is applied when the voice DN logs in. To determine whether your switch supports the workmodem refer to the deployment guide of the relevant T-Server.",
+
"description": "Specifies the limit for the maximum number of requests per minute on the Service Client API. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: unknown, auto-in, manual-in.",
+
"data_type": "An integer value greater than or equal to 0. 0 for unlimited rate.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 510: Line 591:
 
},
 
},
 
{
 
{
"id": "agent-status.ready-workmode",
+
"id": "service-client-api.rate-limit.<service-name>",
"display_name": "Ready workmode",
+
"display_name": "Service request per API rate limit",
 
"type": "config",
 
"type": "config",
"default_value": "unknown",
+
"default_value": "0",
"description": "Specifies which workmode is applied on Ready operation done manually from the Global State menu and My Channels. This option is also applicable for the login.voice.is-auto-ready option. Supported workmodes are unknown, manual-in, auto-in.",
+
"description": "Specifies the limit for the maximum number of requests per minute on a specific API request on the Service Client API. The <service-name> can be one of the following: \n* agent.get\n* agent.getStateList\n* agent.setState\n* agent.getState\n* interaction.getInteractions\n* interaction.getByInteractionId\n* interaction.deleteUserData\n* interaction.setUserData\n* media.getMediaList\n* media.setState\n* system.closeToast\n* system.popupToast\n* system.updateToast\n* voice.dial\n* voice.startCallRecording\n* voice.stopCallRecording\n* voice.pauseCallRecording\n* voice.resumeCallRecording\n* email.create<br>This option cannot be overridden, it must be set in the WSA Cluster Application.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: unknown, manual-in, auto-in. Empty means no workmode specified.",
+
"data_type": "An integer value greater than or equal to 0. 0 for unlimited rate.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 523: Line 605:
 
},
 
},
 
{
 
{
"id": "keyboard.shortcut.interaction.previous",
+
"id": "service-client-api.rate-limit-quarantine-delay",
"display_name": "Jump to Previous Case Interaction",
+
"display_name": "Service request global quarantine delay once the rate limit reached",
 
"type": "config",
 
"type": "config",
"default_value": "Alt+B",
+
"default_value": "30",
"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump to the previous case interaction.",
+
"description": "Specifies the quarantine delay, in seconds, during which requests are ignored once the rate limit is reached. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
+
"data_type": "An integer value greater than or equal to 0. 0 for infinite quarantine delay.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 536: Line 619:
 
},
 
},
 
{
 
{
"id": "keyboard.shortcut.interaction.next",
+
"id": "service-client-api.block-markdone-timeout",
"display_name": "Jump to Next Case Interaction",
+
"display_name": "Block MarkDone Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "Alt+N",
+
"default_value": "1000",
"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump to the next case interaction.",
+
"description": "Specifies the duration, in milliseconds, of the timeout started by the 'interaction.blockMarkdone()' service. If this option is set, when an agent marks an interaction as Done, the Mark Done operation is delayed until the specified timeout has elapsed. During this interval, Mark Done can be blocked by using the serviceClientAPI 'blockMarkdone' operation. If Mark Done is blocked by 'serviceClientAPI', the Mark Done operation is cancelled. If the Mark Done is not blocked, the Mark Done operation occurs after the specified duration has elapsed. If Mark Done has been blocked by the 'blockMarkDone' operation from the 'serviceClientAPI', it can be unblocked by using the 'unblockMarkDone' operation from the 'serviceClientAPI'.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
+
"data_type": "An integer value greater than 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 549: Line 633:
 
},
 
},
 
{
 
{
"id": "keyboard.shortcut.jump-to-last-error",
+
"id": "service-client-api.option.read-allowed-web-content-origin",
"display_name": "Jump the focus to the last error.",
+
"display_name": "Workspace web service API granted origins and read allowed options permission",
 
"type": "config",
 
"type": "config",
"default_value": "Alt+L",
+
"default_value": "No default value",
"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump the focus to the last error.",
+
"description": "Specifies the list of granted origins and read allowed options that are used in the web extension views. You can filter access to provisioning with the following self-explanatory keywords:\n* 'voice.*'\n* 'sipendpoint.*'\n* '...'<br>For example, the value of this option could now be: http://my-web-server0, http://my-web-server1 (*) , http://my-web-server2 (voice.*, system.*), http://my-web-server3 (sipendpoint.*, CustomSection/*).<br><br>In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following access to provisioning are allowed: 'voice.*', 'system.*'. For the http://my-web-server3 domain, only the following access to provisioning are allowed:\n* 'sipendpoint.*'\n* 'CustomSection/*'<br>This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.38",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
+
"data_type": "A comma-separated value list of URL or '*', with patterns for example: 'http://my-web-server-1,http://my-web-server-2(*),http://my-web-server-3(voice.*)' or '*'.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 562: Line 647:
 
},
 
},
 
{
 
{
"id": "reporting.case.report-case-in-focus-duration",
+
"id": "main-window.window-title",
"display_name": "Report In Focus Duration",
+
"display_name": "Window Title",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "&#36;Window.Title&#36;",
"description": "Specifies whether the time that an interaction has been in the focus of the agent during its handling is reported to T-Server or Interaction Server at the end of its processing by the agent. When it is enabled, this notification allows Genesys Interaction Concentrator and Genesys Infomart to calculate some focus time metrics.",
+
"description": "Specifies the title of the browser window or tab. You can specify any string andor combination of valid field codes up to the maximum width of the browser window title bar or tab. If all field codes are empty, the following field codes are used: &#36;Window.Title&#36;.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "&#36;Window.Title&#36;,&#36;Application.Title&#36;,&#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.EmployeeId&#36;.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 575: Line 661:
 
},
 
},
 
{
 
{
"id": "views.SideBarRegion.order",
+
"id": "login.workmode",
"display_name": "Views order in Region SideBarRegion",
+
"display_name": "Workmode",
 
"type": "config",
 
"type": "config",
"default_value": "TeamCommunicatorView,NotificationsView,VoiceMailView,PerformanceTrackerView",
+
"default_value": "unknown",
"description": "Specifies the order (top to bottom) in which the views are displayed in the SideBar Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the workmode that is applied when the voice DN logs in. To determine whether your switch supports the workmodem refer to the deployment guide of the relevant T-Server.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): TeamCommunicatorView,NotificationsView,VoiceMailView,PerformanceTrackerView",
+
"data_type": "A value from the following list: unknown, auto-in, manual-in.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 588: Line 675:
 
},
 
},
 
{
 
{
"id": "views.NavigationBarRegion.activate-order",
+
"id": "agent-status.ready-workmode",
"display_name": "Views order in Region NavigationBarRegion",
+
"display_name": "Ready workmode",
 
"type": "config",
 
"type": "config",
"default_value": "ConnectRegion,MonitoringRegion",
+
"default_value": "unknown",
"description": "Specifies in precedence order the view selected by default in the Navigation Bar Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
+
"description": "Specifies which workmode is applied on Ready operation done manually from the Global State menu and My Channels. This option is also applicable for the login.voice.is-auto-ready option. Supported workmodes are unknown, manual-in, auto-in.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom subregion specified in a section): Connect, Monitoring.",
+
"data_type": "A value from the following list: unknown, manual-in, auto-in. Empty means no workmode specified.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 601: Line 689:
 
},
 
},
 
{
 
{
"id": "views.NavigationBarRegion.order",
+
"id": "keyboard.shortcut.interaction.previous",
"display_name": "Views order in Region NavigationBarRegion",
+
"display_name": "Jump to Previous Case Interaction",
 
"type": "config",
 
"type": "config",
"default_value": "ConnectRegion,MonitoringRegion",
+
"default_value": "Alt+B",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Navigation Bar Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump to the previous case interaction.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom subregion specified in a section): Connect, Monitoring.",
+
"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 614: Line 703:
 
},
 
},
 
{
 
{
"id": "views.NavigationBarRegion.ConnectRegion.activate-order",
+
"id": "keyboard.shortcut.interaction.next",
"display_name": "Views order in Region ConnectRegion",
+
"display_name": "Jump to Next Case Interaction",
 
"type": "config",
 
"type": "config",
"default_value": "MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
+
"default_value": "Alt+N",
"description": "Specifies in precedence order the view selected by default in the Connect Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
+
"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump to the next case interaction.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView.",
+
"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 627: Line 717:
 
},
 
},
 
{
 
{
"id": "views.NavigationBarRegion.ConnectRegion.order",
+
"id": "keyboard.shortcut.jump-to-last-error",
"display_name": "Views order in Region ConnectRegion",
+
"display_name": "Jump the focus to the last error.",
 
"type": "config",
 
"type": "config",
"default_value": "MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
+
"default_value": "Alt+L",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Connect Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump the focus to the last error.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
+
"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 640: Line 731:
 
},
 
},
 
{
 
{
"id": "views.NavigationBarRegion.MonitoringRegion.activate-order",
+
"id": "reporting.case.report-case-in-focus-duration",
"display_name": "Views order in Region MonitoringRegion",
+
"display_name": "Report In Focus Duration",
 
"type": "config",
 
"type": "config",
"default_value": "DashboardView,MyAgentsView",
+
"default_value": "false",
"description": "Specifies in precedence order the view selected by default in the Monitoring Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
+
"description": "Specifies whether the time that an interaction has been in the focus of the agent during its handling is reported to T-Server or Interaction Server at the end of its processing by the agent. When it is enabled, this notification allows Genesys Interaction Concentrator and Genesys Infomart to calculate some focus time metrics.",
 +
"version": "9.0.000.34",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): DashboardView,MyAgentsView",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 653: Line 745:
 
},
 
},
 
{
 
{
"id": "views.NavigationBarRegion.MonitoringRegion.order",
+
"id": "views.SideBarRegion.order",
"display_name": "Views order in Region MonitoringRegion",
+
"display_name": "Views order in Region SideBarRegion",
 
"type": "config",
 
"type": "config",
"default_value": "DashboardView,MyAgentsView",
+
"default_value": "TeamCommunicatorView,NotificationsView,VoiceMailView,PerformanceTrackerView",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Monitoring Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the order (top to bottom) in which the views are displayed in the SideBar Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): DashboardView,MyAgentsView",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): TeamCommunicatorView,NotificationsView,VoiceMailView,PerformanceTrackerView",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 666: Line 759:
 
},
 
},
 
{
 
{
"id": "views.ContactRegion.order",
+
"id": "side-bar.web-content.url-encoding-defense-enabled",
"display_name": "Views order in Region ContactRegion",
+
"display_name": "Custom Views URL Encoding in Region SideBarRegion",
 
"type": "config",
 
"type": "config",
"default_value": "ContactInformationView,ContactHistoryView",
+
"default_value": "No default value",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Contact Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the list of modes on which the url encoding defense is applied. If the '<mode>' is not set, the url is unmodified (not encoded). If the '<mode>' is set but no hexadecimal character (%XX, where X is a hexa) is found in the url, the url is encoded. If the '<mode>{{!}}FORCE' is set, the url is always encoded.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInformationView,ContactHistoryView.",
+
"data_type": "A comma-separated list of one or more modes and the optional FORCE modifier in this format: <mode>[{{!}}FORCE]. Valid modes: INTERNAL, BACKGROUND, HIDDEN, EXTERNAL.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 679: Line 773:
 
},
 
},
 
{
 
{
"id": "views.ContactRegion.activate-order",
+
"id": "views.NavigationBarRegion.activate-order",
"display_name": "Default View In Region ContactRegion",
+
"display_name": "Views order in Region NavigationBarRegion",
 
"type": "config",
 
"type": "config",
"default_value": "ContactInformationView,ContactHistoryView",
+
"default_value": "ConnectRegion,MonitoringRegion",
"description": "Specifies, in order of precedence, the view selected by default in the Contact region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
+
"description": "Specifies in precedence order the view selected by default in the Navigation Bar Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInformationView,ContactHistoryView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom subregion specified in a section): Connect, Monitoring.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 692: Line 787:
 
},
 
},
 
{
 
{
"id": "views.HistoryInteractionDetailsRegion.order",
+
"id": "views.NavigationBarRegion.order",
"display_name": "Views order in Region HistoryInteractionDetailsRegion",
+
"display_name": "Views order in Region NavigationBarRegion",
 
"type": "config",
 
"type": "config",
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
+
"default_value": "ConnectRegion,MonitoringRegion",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the History Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Navigation Bar Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom subregion specified in a section): Connect, Monitoring.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 705: Line 801:
 
},
 
},
 
{
 
{
"id": "views.HistoryInteractionDetailsRegion.activate-order",
+
"id": "views.NavigationBarRegion.ConnectRegion.activate-order",
"display_name": "Default view in Region HistoryInteractionDetailsRegion",
+
"display_name": "Views order in Region ConnectRegion",
 
"type": "config",
 
"type": "config",
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
+
"default_value": "MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
"description": "Specifies, in order of precedence, the view selected by default in the History Interaction Details Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
+
"description": "Specifies in precedence order the view selected by default in the Connect Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 718: Line 815:
 
},
 
},
 
{
 
{
"id": "views.WorkbinInteractionDetailsRegion.order",
+
"id": "views.NavigationBarRegion.ConnectRegion.order",
"display_name": "Views order in Region WorkbinInteractionDetailsRegion",
+
"display_name": "Views order in Region ConnectRegion",
 
"type": "config",
 
"type": "config",
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
+
"default_value": "MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Workbin Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Connect Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 731: Line 829:
 
},
 
},
 
{
 
{
"id": "views.WorkbinInteractionDetailsRegion.activate-order",
+
"id": "views.NavigationBarRegion.MonitoringRegion.activate-order",
"display_name": "Default view in Region WorkbinInteractionDetailsRegion",
+
"display_name": "Views order in Region MonitoringRegion",
 
"type": "config",
 
"type": "config",
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
+
"default_value": "DashboardView,MyAgentsView",
"description": "Specifies in precedence order the view selected by default in the Workbin Interaction Details Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
+
"description": "Specifies in precedence order the view selected by default in the Monitoring Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): DashboardView,MyAgentsView",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 744: Line 843:
 
},
 
},
 
{
 
{
"id": "views.InteractionDetailsRegion.order",
+
"id": "views.NavigationBarRegion.MonitoringRegion.order",
"display_name": "Views order in Region InteractionDetailsRegion",
+
"display_name": "Views order in Region MonitoringRegion",
 
"type": "config",
 
"type": "config",
"default_value": "DispositionView,ContactInteractionNotePadView",
+
"default_value": "DashboardView,MyAgentsView",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Monitoring Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): DispositionView,ContactInteractionNotePadView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): DashboardView,MyAgentsView",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 757: Line 857:
 
},
 
},
 
{
 
{
"id": "views.InteractionDetailsRegion.activate-order",
+
"id": "views.ContactRegion.order",
"display_name": "Default view in Region InteractionDetailsRegion",
+
"display_name": "Views order in Region ContactRegion",
 
"type": "config",
 
"type": "config",
"default_value": "ContactInteractionNotePadView,DispositionView",
+
"default_value": "ContactInformationView,ContactHistoryView",
"description": "Specifies, in order of precedence, the view selected by default in the Interaction Details Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Contact Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionNotePadView,DispositionView.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInformationView,ContactHistoryView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 770: Line 871:
 
},
 
},
 
{
 
{
"id": "views.CaseSideRegion.order",
+
"id": "views.ContactRegion.activate-order",
"display_name": "Views order in Region CaseSideRegion",
+
"display_name": "Default View In Region ContactRegion",
 
"type": "config",
 
"type": "config",
"default_value": "KnowledgeView,CoBrowseView,ContactView,SRLView",
+
"default_value": "ContactInformationView,ContactHistoryView",
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Case Side Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
+
"description": "Specifies, in order of precedence, the view selected by default in the Contact region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'interaction.web-content'): KnowledgeView,ExtensionSectionName,CoBrowseView,ContactView,SRLView. KnowledgeView and CoBrowseView are not supported for on-premises deployments.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInformationView,ContactHistoryView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 783: Line 885:
 
},
 
},
 
{
 
{
"id": "views.CaseSideRegion.activate-order",
+
"id": "views.HistoryInteractionDetailsRegion.order",
"display_name": "Default view in Region CaseSideRegion",
+
"display_name": "Views order in Region HistoryInteractionDetailsRegion",
 
"type": "config",
 
"type": "config",
"default_value": "ContactView,SRLView,KnowledgeView,CoBrowseView",
+
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
"description": "Specifies, in order of precedence, the view selected by default in the Case Side Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on.) If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the History Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'interaction.web-content'): ContactView,ExtensionSectionName,SRLView,KnowledgeView,CoBrowseView. KnowledgeView and CoBrowseView are not supported for on-premises deployments.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 796: Line 899:
 
},
 
},
 
{
 
{
"id": "expression.identify.phone-number",
+
"id": "views.HistoryInteractionDetailsRegion.activate-order",
"display_name": "Phone Number",
+
"display_name": "Default view in Region HistoryInteractionDetailsRegion",
 
"type": "config",
 
"type": "config",
"default_value": "(?:(?:[\\+]?([\\d]{1,3}(?:[ ]*{{!}}[\\-.])))?[(]?([\\d]{1,3})[\\-\\/)]?(?:[ ]+{{!}}[\\-.])?)?([\\d]{3,})",
+
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
"description": "Specifies the regular expression that identifies a phone number in the chat or email transcript. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies, in order of precedence, the view selected by default in the History Interaction Details Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 809: Line 913:
 
},
 
},
 
{
 
{
"id": "expression.phone-number.supported-characters",
+
"id": "views.WorkbinInteractionDetailsRegion.order",
"display_name": "Phone Number Supported Characters",
+
"display_name": "Views order in Region WorkbinInteractionDetailsRegion",
 
"type": "config",
 
"type": "config",
"default_value": "0123456789+",
+
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
"description": "Specifies the characters that are permitted when building a request to the T-Server that relies on a phone number. Any other characters from the original string coming from the User Interface are removed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Workbin Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.12",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Letters A to Z and a to z. Numbers 0 through 9. All special characters that are valid Windows file names.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 822: Line 927:
 
},
 
},
 
{
 
{
"id": "expression.validate.phone-number",
+
"id": "views.WorkbinInteractionDetailsRegion.activate-order",
"display_name": "Team Communicator Phone Number",
+
"display_name": "Default view in Region WorkbinInteractionDetailsRegion",
 
"type": "config",
 
"type": "config",
"default_value": "^[\\(\\)\\-\\.\\+\\d\\s\\*#]*[\\d]+[\\(\\)\\-\\.\\+\\d\\s\\*#/]*&#36;",
+
"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
"description": "Specifies the regular expression used to validate a phone number. It is used to recognize the phone number of a target entered in the Team Communicator when performing a call, a transfer, or a conference. If the number entered by the agent in the Team Communicator edit box matches this expression, the 'Call', 'Start Voice Consultation', 'Instant Transfer', or 'Instant Conference' action is enabled for this number. When the agent executes the action, the entered phone number is modified by the logic specified by the expression.phone-number.supported-characters option before the telephony operation is executed. This expression is also used to display a warning message if the phone number on the Contact Profile is incorrect.",
+
"description": "Specifies in precedence order the view selected by default in the Workbin Interaction Details Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
 +
"version": "9.0.000.12",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid regular expression.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 835: Line 941:
 
},
 
},
 
{
 
{
"id": "expression.validate.email-address",
+
"id": "views.InteractionDetailsRegion.order",
"display_name": "Team Communicator Email Address",
+
"display_name": "Views order in Region InteractionDetailsRegion",
 
"type": "config",
 
"type": "config",
"default_value": "^([A-Za-z0-9._-]+)@([A-Za-z0-9.-]+)\\.([A-Za-z]{2,6})&#36;",
+
"default_value": "DispositionView,ContactInteractionNotePadView",
"description": "Specifies the regular expression used to validate an email address. It is used to recognize an email address of a target entered in the Team Communicator, and also to display warning message if the email address on the Contact Profile is incorrect.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid regular expression.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): DispositionView,ContactInteractionNotePadView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 848: Line 955:
 
},
 
},
 
{
 
{
"id": "expression.identify.email-address",
+
"id": "views.InteractionDetailsRegion.activate-order",
"display_name": "Email Address",
+
"display_name": "Default view in Region InteractionDetailsRegion",
 
"type": "config",
 
"type": "config",
"default_value": "(\\w+([-+.]\\w+)*@\\w+([-.]\\w+)*\\.\\w+([-.]\\w+)*)",
+
"default_value": "ContactInteractionNotePadView,DispositionView",
"description": "Specifies the regular expression that identifies an email address in a chat.",
+
"description": "Specifies, in order of precedence, the view selected by default in the Interaction Details Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionNotePadView,DispositionView.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 861: Line 969:
 
},
 
},
 
{
 
{
"id": "expression.outbound-campaign-phone-number",
+
"id": "views.CaseSideRegion.order",
"display_name": "Outbound campaign phone number",
+
"display_name": "Views order in Region CaseSideRegion",
 
"type": "config",
 
"type": "config",
"default_value": "^[\\(\\)\\-\\.\\+\\d\\s\\*#]*[\\d]+[\\(\\)\\-\\.\\+\\d\\s\\*#/]*&#36;",
+
"default_value": "AgentAssistSuggestionsView,CoBrowseView,ContactView,SRLView,RelatedView",
"description": "Specifies the regular expression to validate a phone number in the 'New Phone Number' dialog to dial an Outbound Preview Record on a new phone number. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Case Side Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'interaction.web-content'): ExtensionSectionName,CoBrowseView,ContactView,SRLView,RelatedView. CoBrowseView is not supported for on-premises deployments.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 874: Line 983:
 
},
 
},
 
{
 
{
"id": "agent-status.enabled-actions-global",
+
"id": "views.CaseSideRegion.activate-order",
"display_name": "Enabled actions global",
+
"display_name": "Default view in Region CaseSideRegion",
 
"type": "config",
 
"type": "config",
"default_value": "Ready,NotReady,NotReadyReason,AfterCallWork,AfterCallWorkReason,LogOff",
+
"default_value": "AgentAssistSuggestionsView,ContactView,SRLView,RelatedView,CoBrowseView",
"description": "Specifies the available agent states in the global Status menu. The agent state commands are displayed in the order in which they appear in the list.",
+
"description": "Specifies, in order of precedence, the view selected by default in the Case Side Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on.) If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, Dnd, NotReadyReason, AfterCallWork, AfterCallWorkReason, LogOn, LogOff.",
+
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'interaction.web-content'): ContactView,ExtensionSectionName,SRLView,RelatedView,CoBrowseView. CoBrowseView is not supported for on-premises deployments.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 887: Line 997:
 
},
 
},
 
{
 
{
"id": "agent-status.enabled-actions-by-channel",
+
"id": "expression.identify.phone-number",
"display_name": "Enabled actions by channel",
+
"display_name": "Phone Number",
 
"type": "config",
 
"type": "config",
"default_value": "Ready,NotReady,NotReadyReason,AfterCallWork,AfterCallWorkReason,LogOff",
+
"default_value": "(?:(?:[\\+]?([\\d]{1,3}(?:[ ]*{{!}}[\\-.])))?[(]?([\\d]{1,3})[\\-\\/)]?(?:[ ]+{{!}}[\\-.])?)?([\\d]{3,})",
"description": "Specifies the available agent state actions in the My Channels contextual menu. The actions are displayed in the order in which they appear in the list.",
+
"description": "Specifies the regular expression that identifies a phone number in the chat or email transcript. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, NotReadyReason, AfterCallWork, AfterCallWorkReason, Dnd, LogOn, LogOff.",
+
"data_type": "A regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 900: Line 1,011:
 
},
 
},
 
{
 
{
"id": "agent-status.not-ready-reasons",
+
"id": "expression.phone-number.supported-characters",
"display_name": "Not ready reasons",
+
"display_name": "Phone Number Supported Characters",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "0123456789+",
"description": "Specifies the available reasons in the Agent Status menus (global and My Channels). The reason commands are displayed in the order in which they appear in the list.",
+
"description": "Specifies the characters that are permitted when building a request to the T-Server that relies on a phone number. Any other characters from the original string coming from the User Interface are removed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Action Code names of type Not Ready; empty means all not ready action codes are considered",
+
"data_type": "Letters A to Z and a to z. Numbers 0 through 9. All special characters that are valid Windows file names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 913: Line 1,025:
 
},
 
},
 
{
 
{
"id": "agent-status.after-call-work-reasons",
+
"id": "expression.validate.phone-number",
"display_name": "AfterCallWork reasons",
+
"display_name": "Team Communicator Phone Number",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "^[\\(\\)\\-\\.\\+\\d\\s\\*#]*[\\d]+[\\(\\)\\-\\.\\+\\d\\s\\*#/]*&#36;",
"description": "Specifies the available reasons in the Agent Status menus (global and My Channels). Workspace displays the reason commands in the order in which they appear in the list.",
+
"description": "Specifies the regular expression used to validate a phone number. It is used to recognize the phone number of a target entered in the Team Communicator when performing a call, a transfer, or a conference. If the number entered by the agent in the Team Communicator edit box matches this expression, the 'Call', 'Start Voice Consultation', 'Instant Transfer', or 'Instant Conference' action is enabled for this number. When the agent executes the action, the entered phone number is modified by the logic specified by the expression.phone-number.supported-characters option before the telephony operation is executed. This expression is also used to display a warning message if the phone number on the Contact Profile is incorrect.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Action Code names of type After Call Work; empty means all not ready action codes are considered",
+
"data_type": "A valid regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 926: Line 1,039:
 
},
 
},
 
{
 
{
"id": "accessibility.agent-state-change-bell",
+
"id": "expression.validate.email-address",
"display_name": "Agent-state change bell",
+
"display_name": "Team Communicator Email Address",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "^([A-Za-z0-9._-]+)@([A-Za-z0-9.-]+)\\.([A-Za-z]{2,6})&#36;",
"description": "Specifies the agent state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the regular expression used to validate an email address. It is used to recognize an email address of a target entered in the Team Communicator, and also to display warning message if the email address on the Contact Profile is incorrect.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "A valid regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 939: Line 1,053:
 
},
 
},
 
{
 
{
"id": "accessibility.interaction-state-change-bell",
+
"id": "expression.identify.email-address",
"display_name": "Interaction-state change bell",
+
"display_name": "Email Address",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "(\\w+([-+.]\\w+)*@\\w+([-.]\\w+)*\\.\\w+([-.]\\w+)*)",
"description": "Specifies the interaction state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the regular expression that identifies an email address in a chat.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "A regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 952: Line 1,067:
 
},
 
},
 
{
 
{
"id": "accessibility.supervision-state-change-bell",
+
"id": "expression.outbound-campaign-phone-number",
"display_name": "Supervision state change bell",
+
"display_name": "Outbound campaign phone number",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "^[\\(\\)\\-\\.\\+\\d\\s\\*#]*[\\d]+[\\(\\)\\-\\.\\+\\d\\s\\*#/]*&#36;",
"description": "Specifies the supervision state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the regular expression to validate a phone number in the 'New Phone Number' dialog to dial an Outbound Preview Record on a new phone number. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.68",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "A regular expression",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 965: Line 1,081:
 
},
 
},
 
{
 
{
"id": "accessibility.warning-message-bell",
+
"id": "agent-status.enabled-actions-global",
"display_name": "Warning message bell",
+
"display_name": "Enabled actions global",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Ready,NotReady,NotReadyReason,AfterCallWork,AfterCallWorkReason,LogOff",
"description": "Specifies the warning message sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the available agent states in the global Status menu. The agent state commands are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, Dnd, NotReadyReason, AfterCallWork, AfterCallWorkReason, LogOn, LogOff.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 978: Line 1,095:
 
},
 
},
 
{
 
{
"id": "accessibility.dialog-bell",
+
"id": "agent-status.enabled-actions-by-channel",
"display_name": "Dialog bell",
+
"display_name": "Enabled actions by channel",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Ready,NotReady,NotReadyReason,AfterCallWork,AfterCallWorkReason,LogOff",
"description": "Specifies the dialog sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the character '{{!}}'. The first is the sound file name (BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the available agent state actions in the My Channels contextual menu. The actions are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, NotReadyReason, AfterCallWork, AfterCallWorkReason, Dnd, LogOn, LogOff.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 991: Line 1,109:
 
},
 
},
 
{
 
{
"id": "accessibility.dialog-error-bell",
+
"id": "agent-status.not-ready-reasons",
"display_name": "Error dialog bell",
+
"display_name": "Not ready reasons",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the error alert sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the character '{{!}}'. The first is the sound file name (BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the available reasons in the Agent Status menus (global and My Channels). The reason commands are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "Comma-separated list of Action Code names of type Not Ready; empty means all not ready action codes are considered",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,004: Line 1,123:
 
},
 
},
 
{
 
{
"id": "accessibility.outbound-campaign-state-change-bell",
+
"id": "agent-status.after-call-work-reasons",
"display_name": "Outbound campaign state change bell",
+
"display_name": "AfterCallWork reasons",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the outbound campaign state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the character '{{!}}'. The first is the sound file name (BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the available reasons in the Agent Status menus (global and My Channels). Workspace displays the reason commands in the order in which they appear in the list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
+
"data_type": "Comma-separated list of Action Code names of type After Call Work; empty means all not ready action codes are considered",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,017: Line 1,137:
 
},
 
},
 
{
 
{
"id": "accessibility.voicemail-message-change-bell",
+
"id": "accessibility.agent-state-change-bell",
"display_name": "VoiceMail Message change bell",
+
"display_name": "Agent-state change bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the Voice Mail counter change sound-configuration string for new or old messages. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe character '{{!}}'. \n* Sound file name (BELL, RING, CHORD or WARNING, predefined aliases, or an absolute URL to a mp3 file). \n* Priority level. The higher the integer, the higher the priority.\n* Duration. 0 means to play the whole sound one time. An integer greater than 0 means a time in milliseconds to play and repeat the sound.",
+
"description": "Specifies the agent state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,030: Line 1,151:
 
},
 
},
 
{
 
{
"id": "outbound-callback.ringing-bell",
+
"id": "accessibility.permanent-statistics-change-bell",
"display_name": "Outbound campaign callback ringing-bell",
+
"display_name": "Permanent-statistics change bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the outbound callback ringing sound configuration string of a scheduled callback pushed to the agent as a preview. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the permanent statistics change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.89",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,043: Line 1,165:
 
},
 
},
 
{
 
{
"id": "chat.new-message-bell",
+
"id": "accessibility.interaction-state-change-bell",
"display_name": "New Message Bell",
+
"display_name": "Interaction-state change bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the path of the sound file Workspace plays when a new chat message arrives. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the interaction state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,056: Line 1,179:
 
},
 
},
 
{
 
{
"id": "chat.ringing-bell",
+
"id": "accessibility.supervision-state-change-bell",
"display_name": "Ringing bell",
+
"display_name": "Supervision state change bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the path of the sound file Workspace plays when a chat interaction is ringing. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the supervision state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,069: Line 1,193:
 
},
 
},
 
{
 
{
"id": "email.ringing-bell",
+
"id": "accessibility.warning-message-bell",
"display_name": "Ringing bell",
+
"display_name": "Warning message bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the path of the sound file Workspace plays when an email interaction is ringing. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the warning message sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,082: Line 1,207:
 
},
 
},
 
{
 
{
"id": "voice.notification.on-party-update.enabled",
+
"id": "accessibility.dialog-bell",
"display_name": "Call Release Tracking Enabling",
+
"display_name": "Dialog bell",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether the agent is notified when a participant leaves or joins an interaction they are handling. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the dialog sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,095: Line 1,221:
 
},
 
},
 
{
 
{
"id": "voice.notification.on-party-update.tooltip-history-ttl",
+
"id": "accessibility.dialog-error-bell",
"display_name": "Call Release Tracking Tooltip TTL",
+
"display_name": "Error dialog bell",
 
"type": "config",
 
"type": "config",
"default_value": "2000",
+
"default_value": "No default value",
"description": "Specifies the duration in microseconds that the participant status notification is displayed.",
+
"description": "Specifies the error alert sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "From 0 to MAXINT.",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,108: Line 1,235:
 
},
 
},
 
{
 
{
"id": "voice.notification.on-party-update.blink-interaction",
+
"id": "accessibility.outbound-campaign-state-change-bell",
"display_name": "Call Release Tracking blinking enabling",
+
"display_name": "Outbound campaign state change bell",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether interactions that do not have the focus blink when the status of a participant changes.",
+
"description": "Specifies the outbound campaign state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,121: Line 1,249:
 
},
 
},
 
{
 
{
"id": "voice.ringing-bell",
+
"id": "accessibility.voicemail-message-change-bell",
"display_name": "Ringing bell",
+
"display_name": "VoiceMail Message change bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the path of the sound file Workspace plays when a voice interaction is ringing. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the pipe ('{{!}}') character. The first is the sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file). The second is a priority: the higher the integer, the higher the priority. The last is the duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop.\n* 0: play the whole sound once\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.",
+
"description": "Specifies the Voice Mail counter change sound-configuration string for new or old messages. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,134: Line 1,263:
 
},
 
},
 
{
 
{
"id": "voice.sip-preview.ringing-bell",
+
"id": "outbound-callback.ringing-bell",
"display_name": "Ringing bell",
+
"display_name": "Outbound campaign callback ringing-bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the path of the sound file that is played when the SIP Preview is ringing. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the character '{{!}}'. The first is the sound file name (BELL, RING, CHORD or WARNING predefined aliases or an absolute url to a mp3 file). Then, a priority, the higher the integer the higher the priority. And a duration (-1 means plays and repeats until an explicit message stops it with an established event for instance, 0 means to play the whole sound one time, an integer > 0 means a time in milliseconds to play and repeat the sound).",
+
"description": "Specifies the outbound callback ringing sound configuration string of a scheduled callback pushed to the agent as a preview. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,147: Line 1,277:
 
},
 
},
 
{
 
{
"id": "voice.dialing-bell",
+
"id": "chat.new-message-bell",
"display_name": "Dialing bell",
+
"display_name": "New Message Bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the voice channel dialing sound-configuration string. For example: 'BELL{{!}}7{{!}}0'. The value has three components that are separated by the character '{{!}}'. The first is the sound file name (BELL, RING, CHORD or WARNING predefined aliases or an absolute url to a mp3 file). Then, a priority, the higher the integer the higher the priority. And a duration (-1 means plays and repeats until an explicit message stops it with an established event for instance, 0 means to play the whole sound one time, an integer > 0 means a time in milliseconds to play and repeat the sound).",
+
"description": "Specifies the path of the sound file Workspace plays when a new chat message arrives. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,160: Line 1,291:
 
},
 
},
 
{
 
{
"id": "interaction.reject-route",
+
"id": "chat.ringing-bell",
"display_name": "Reject Route",
+
"display_name": "Ringing bell",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Workspace enables the Reject voice call operation in SIP Server environments that use multi-site routing. The reject route mechanism has been extended to accommodate different types of 'reject' implementations, depending on the context. Use this option to enable the reject route mechanism by specifying a string as a key to be used at run-time to retrieve the behavior description from the interaction user data. It is the responsibility of the administrator to define the multi-site reject criteria. The reject route is specified in the interaction user data in the following format: <reject-method>:<dn>@<switch>. When reject-method is specified, ensure that the following characters are also specified: :, @, and the switch field. The following are possible values for the reject-method attribute:<br><br>sst: Reject applies the following action: SingleStepTransfer(OtherDN=<dn>,Location=<switch>).<br>release: Reject applies the following action: releaseCall. This value must be applied when the value of the TServer/divert-on-ringing SIP Server configuration option is set to false.<br><br>Warning: If the value of dn@switch corresponds to the same routing point as the one that is handling the call that is being delivered to the agent, the action will succeed only if the value of the TServer/divert-on-ringing SIP Server configuration option is set to true.",
+
"description": "Specifies the path of the sound file Workspace plays when a chat interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A string that represents an attached data key.",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,173: Line 1,305:
 
},
 
},
 
{
 
{
"id": "interaction.disposition.is-expanded-on-display",
+
"id": "email.ringing-bell",
"display_name": "Auto expand all disposition",
+
"display_name": "Ringing bell",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether the disposition tree is expanded rather than collapsed when displayed:\n* true: Expand all dispositions\n* false: Collapse all dispositions",
+
"description": "Specifies the path of the sound file Workspace plays when an email interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,186: Line 1,319:
 
},
 
},
 
{
 
{
"id": "<media-type>.detail-region.default-display-mode",
+
"id": "voice.notification.on-party-update.enabled",
"display_name": "Detail Region Default Display Mode",
+
"display_name": "Call Release Tracking Enabling",
 
"type": "config",
 
"type": "config",
"default_value": "Medium",
+
"default_value": "true",
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px, and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the agent is notified when a participant leaves or joins an interaction they are handling. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.61",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,199: Line 1,333:
 
},
 
},
 
{
 
{
"id": "voice.detail-region.default-display-mode",
+
"id": "voice.notification.on-party-update.tooltip-history-ttl",
"display_name": "Detail Region Default Display Mode",
+
"display_name": "Call Release Tracking Tooltip TTL",
 
"type": "config",
 
"type": "config",
"default_value": "Medium",
+
"default_value": "2000",
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the duration in microseconds that the participant status notification is displayed.",
 +
"version": "9.0.000.61",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
+
"data_type": "From 0 to MAXINT.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,212: Line 1,347:
 
},
 
},
 
{
 
{
"id": "chat.detail-region.default-display-mode",
+
"id": "voice.notification.on-party-update.blink-interaction",
"display_name": "Detail Region Default Display Mode",
+
"display_name": "Call Release Tracking blinking enabling",
 
"type": "config",
 
"type": "config",
"default_value": "Medium",
+
"default_value": "true",
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether interactions that do not have the focus blink when the status of a participant changes.",
 +
"version": "9.0.000.61",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,225: Line 1,361:
 
},
 
},
 
{
 
{
"id": "email.detail-region.default-display-mode",
+
"id": "voice.ringing-bell",
"display_name": "Detail Region Default Display Mode",
+
"display_name": "Ringing bell",
 
"type": "config",
 
"type": "config",
"default_value": "Medium",
+
"default_value": "No default value",
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the path of the sound file Workspace plays when a voice interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,238: Line 1,375:
 
},
 
},
 
{
 
{
"id": "interaction-bar.quick-access-modes",
+
"id": "voice.sip-preview.ringing-bell",
"display_name": "Quick Access Modes",
+
"display_name": "Ringing bell",
 
"type": "config",
 
"type": "config",
"default_value": "Pinned,Floating",
+
"default_value": "No default value",
"description": "Specifies the list of modes that are available to present interactions. The available modes are:\n* Pinned: the interaction view occupies the full available size, shared with Supporting Views like Contact and Responses.\n* Floating: the interaction view is presented in a floating window that is painted above any other kind of content and that fits the visual material to display. This view cannot display content displayed on the right part, such as Contact Profile or Responses.    <br>When more than one mode is specified, by default the first mode in the configured list is used. The end user can switch from one mode to the other using a dedicated control. For a given media type, this option can be overridden by option interaction-bar.quick-access-modes.<media-type>.",
+
"description": "Specifies the path of the sound file that is played when the SIP Preview is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.70",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,251: Line 1,389:
 
},
 
},
 
{
 
{
"id": "interaction-bar.quick-access-modes.<media-type>",
+
"id": "voice.dialing-bell",
"display_name": "Quick Access Modes <media-type>",
+
"display_name": "Dialing bell",
 
"type": "config",
 
"type": "config",
"default_value": "Pinned,Floating",
+
"default_value": "No default value",
"description": "Use this option as a template to specify the list of modes available to present interactions of the given media type. The available modes are: \n* Pinned: the interaction view occupies the full available size, shared with Supporting Views like Contact and Responses.\n* Floating: the interaction view is presented in a floating window that is painted above any other kind of content and that fits the visual material to display. This view cannot display content displayed on the right part, such as Contact Profile or Responses. <br>When more than one mode is specified, by default the first mode in the configured list is used. The end user can switch from one mode to the other using a dedicated control. When it is defined for a media type, this option overwrites the definition of the generic option interaction-bar.quick-access-modes.",
+
"description": "Specifies the voice channel dialing sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "",
+
"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,264: Line 1,403:
 
},
 
},
 
{
 
{
"id": "interaction.override-option-key",
+
"id": "interaction.reject-route",
"display_name": "Override option key",
+
"display_name": "Reject Route",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies that certain application options can be overridden by using a transaction object. The value of this option provides the key name of the attached data that contains the list of transaction objects.",
+
"description": "Workspace enables the Reject voice call operation in SIP Server environments that use multi-site routing. The reject route mechanism has been extended to accommodate different types of 'reject' implementations, depending on the context. Use this option to enable the reject route mechanism by specifying a string as a key to be used at run-time to retrieve the behavior description from the interaction user data. It is the responsibility of the administrator to define the multi-site reject criteria. The reject route is specified in the interaction user data in the following format: <reject-method>:<dn>@<switch>. When reject-method is specified, ensure that the following characters are also specified: :, @, and the switch field. The following are possible values for the reject-method attribute:<br><br>sst: Reject applies the following action: SingleStepTransfer(OtherDN=<dn>,Location=<switch>).<br>release: Reject applies the following action: releaseCall. This value must be applied when the value of the TServer/divert-on-ringing SIP Server configuration option is set to false.<br>redirect: Reject applies the following action: redirectCall<br><br>Warning: If the value of dn@switch corresponds to the same routing point as the one that is handling the call that is being delivered to the agent, the action will succeed only if the value of the TServer/divert-on-ringing SIP Server configuration option is set to true.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An attached data key name (string). The list is provided in the Attached Data in the strategy.",
+
"data_type": "A string that represents an attached data key.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,277: Line 1,417:
 
},
 
},
 
{
 
{
"id": "interaction.disposition.is-mandatory",
+
"id": "interaction.reject-route.default-method",
"display_name": "Disposition is mandatory",
+
"display_name": "Default operation for Reject voice call",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "redirect",
"description": "Specifies whether it is mandatory for the agent to set a disposition code before Marking Done an interaction. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the default operation for a rejected voice call for environments where the mechanism specified by the interaction.reject-route option is not used for routing. This option supports the SIP Server Hunt Groups reject route mechanism. Refer to the SIP Server Deployment Guide. Specify one of the following values:\n*  redirect - Reject applies the following action: redirectCall\n*  release - Reject applies the following action: releaseCall. This value must be applied when the value of the TServer/divert-on-ringing SIP Server configuration option is set to false or for calls distributed from a Hunt Group.",
 +
"version": "9.0.000.86",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "Specify a value from the following list: Redirect, Release.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,290: Line 1,431:
 
},
 
},
 
{
 
{
"id": "interaction.disposition.value-business-attribute",
+
"id": "interaction.disposition.is-expanded-on-display",
"display_name": "Disposition values Business Attribute",
+
"display_name": "Auto expand all disposition",
 
"type": "config",
 
"type": "config",
"default_value": "DispositionCode",
+
"default_value": "true",
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the disposition tree is expanded rather than collapsed when displayed:\n*  true: Expand all dispositions\n*  false: Collapse all dispositions",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid Business Attribute name.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,303: Line 1,445:
 
},
 
},
 
{
 
{
"id": "interaction.disposition.key-name",
+
"id": "<media-type>.detail-region.default-display-mode",
"display_name": "Disposition key name",
+
"display_name": "Detail Region Default Display Mode",
 
"type": "config",
 
"type": "config",
"default_value": "DispositionCode",
+
"default_value": "Medium",
"description": "Specifies the key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px, and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.59",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid key name.",
+
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,316: Line 1,459:
 
},
 
},
 
{
 
{
"id": "interaction.disposition.folder-name-depth-<n>",
+
"id": "voice.detail-region.default-display-mode",
"display_name": "Disposition folder name at depth n",
+
"display_name": "Detail Region Default Display Mode",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Medium",
"description": "Specifies the key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.59",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Valid key name associated with a disposition.",
+
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,329: Line 1,473:
 
},
 
},
 
{
 
{
"id": "interaction.disposition.cache-timeout-delay",
+
"id": "chat.detail-region.default-display-mode",
"display_name": "Cache timeout delay for disposition",
+
"display_name": "Detail Region Default Display Mode",
 
"type": "config",
 
"type": "config",
"default_value": "-1",
+
"default_value": "Medium",
"description": "Specifies the delay, in seconds, before the cache of a disposition request result is cleared. If set to -1, the dispositions are kept in cache until the browser page is refreshed, or until the agent logs out and logs back in.",
+
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.59",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "From -1 to MAXINT.",
+
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,342: Line 1,487:
 
},
 
},
 
{
 
{
"id": "interaction.web-content",
+
"id": "email.detail-region.default-display-mode",
"display_name": "Web extension views",
+
"display_name": "Detail Region Default Display Mode",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Medium",
"description": "Specifies the list of Web Applications that are configured to be displayed at the Interaction level. Refer to 'Enabling integration of web applications in the agent interface in the Configuration Guide for information about creating web application objects in the configuration layer. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.59",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of option section names that correspond to web extension views. For example: Extension1, Extension2",
+
"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,355: Line 1,501:
 
},
 
},
 
{
 
{
"id": "interaction.auto-focus",
+
"id": "interaction-bar.quick-access-modes",
"display_name": "Interaction auto focus",
+
"display_name": "Quick Access Modes",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Pinned,Floating",
"description": "Specifies whether the inbound interaction is in focus automatically when it is accepted. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the list of modes that are available to present interactions. The available modes are:\n*  Pinned: the interaction view occupies the full available size, shared with Supporting Views like Contact and Responses.\n*  Floating: the interaction view is presented in a floating window that is painted above any other kind of content and that fits the visual material to display. This view cannot display content displayed on the right part, such as Contact Profile or Responses.    <br>When more than one mode is specified, by default the first mode in the configured list is used. The end user can switch from one mode to the other using a dedicated control. For a given media type, this option can be overridden by option interaction-bar.quick-access-modes.<media-type>.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,368: Line 1,515:
 
},
 
},
 
{
 
{
"id": "interaction.auto-focus.<media-type>",
+
"id": "interaction-bar.quick-access-modes.<media-type>",
"display_name": "Interaction auto focus per media",
+
"display_name": "Quick Access Modes for open media interactions",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Pinned,Floating",
"description": "Specifies whether the inbound interaction of the specfied media type is in focus automatically when is accepted. This option overrides the 'interaction.auto-focus' option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Use this option as a template to specify the list of modes available to present interactions of the given media type. The available modes are: \n*  Pinned: the interaction view occupies the full available size, shared with Supporting Views like Contact and Responses.\n*  Floating: the interaction view is presented in a floating window that is painted above any other kind of content and that fits the visual material to display. This view cannot display content displayed on the right part, such as Contact Profile or Responses. <br>When more than one mode is specified, by default the first mode in the configured list is used. The end user can switch from one mode to the other using a dedicated control. When it is defined for a media type, this option overwrites the definition of the generic option interaction-bar.quick-access-modes.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,381: Line 1,529:
 
},
 
},
 
{
 
{
"id": "interaction.case-data.enable-hyperlink",
+
"id": "interaction.override-option-key",
"display_name": "Case Data Enable hyperlink",
+
"display_name": "Override option key",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether a hyperlink that is part of the case information may be displayed. See also the expression.url option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies that certain application options can be overridden by using a transaction object. The value of this option provides the key name of the attached data that contains the list of transaction objects.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "An attached data key name (string). The list is provided in the Attached Data in the strategy.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,394: Line 1,543:
 
},
 
},
 
{
 
{
"id": "interaction.case-data.format-business-attribute",
+
"id": "interaction.disposition.is-mandatory",
"display_name": "Case Data format Business Attribute",
+
"display_name": "Disposition is mandatory",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the name of the Business Attribute that contains the Business Attribute values that are used to filter and render attached data in the interaction. This option can be overridden by a routing strategy as described in the Configuration Guide. You can define the display order of Business Attribute Values by creating an interaction-workspace section in the annex of the Business Attribute, then add the interaction.case-data.order option. This option is a comma-separated list of Business Attributes Value Names that specifies the order of  the Business Attribute Values. The Attributes Values that are not listed in interaction.case-data.order option are put at the bottom of the list.",
+
"description": "Specifies whether it is mandatory for the agent to set a disposition code before Marking Done an interaction. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Business Attribute.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,407: Line 1,557:
 
},
 
},
 
{
 
{
"id": "interaction.case-data.frame-color",
+
"id": "interaction.disposition.value-business-attribute",
"display_name": "Case Data frame color",
+
"display_name": "Disposition values Business Attribute",
 
"type": "config",
 
"type": "config",
"default_value": "#17849D",
+
"default_value": "DispositionCode",
"description": "Specifies the color of the border of the Case Data view frame. Examples: #FFFFBA00 for a Gold color, #FF6F7074 for a Silver color, #FFB8400B for a Bronze color. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Valid Hexadecimal (HTML) color code.",
+
"data_type": "A valid Business Attribute name.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,420: Line 1,571:
 
},
 
},
 
{
 
{
"id": "toast.case-data.format-business-attribute",
+
"id": "interaction.related.disposition.value-business-attribute",
"display_name": "Case Data format Business Attribute",
+
"display_name": "Disposition values Business Attribute for related interactions.",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "&#36;Default&#36;",
"description": "Specifies the name of the Business Attribute that contains the Business Attribute Values that are used to filter and render attached data in the toast interaction preview.<br><br>You can define the display order of Business Attribute Values by creating an interaction-workspace section in the annex of the Business Attribute, then add the toast.case-data.order option. Use this option to specify a comma-separated list of Business Attributes Value Names that define the order of  the Business Attribute Values. The Attributes Values that are not listed in option toast.case-data.order are put at the bottom of the list.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code displayed in the Related tab. The value &#36;Default&#36; specifies that the value of the interaction.disposition.value-business-attribute option is used.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The valid name of a Business Attribute.",
+
"data_type": "A valid Business Attribute name or &#36;Default&#36;.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,433: Line 1,585:
 
},
 
},
 
{
 
{
"id": "toast.window-title",
+
"id": "interaction.related.disposition.key-name",
"display_name": "Window Title",
+
"display_name": "Disposition key name for related interactions.",
 
"type": "config",
 
"type": "config",
"default_value": "(&#36;Contact.FirstName&#36; &#36;Contact.LastName&#36;{{!}}&#36;Interaction.MainParty&#36;)",
+
"default_value": "&#36;Default&#36;",
"description": "Specifies the title of the Toast window by defining a string that contains the following field codes:&#36;Window.Title&#36;,&#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.EmployeeId&#36;,&#36;Interaction.CaseId&#36;,&#36;Interaction.MainParty&#36;,&#36;Contact.X&#36;,&#36;AttachedData.Y&#36; (X: name of contact attribute, Y: attached data key name). If all field codes are empty, the following field codes are used: '&#36;Window.Title&#36; - &#36;Interaction.MainParty&#36;'.",
+
"description": "Specifies the key that is used to populate the attached data or a user event when a disposition code is submitted from the Related tab to the back-end system, such as T-Server, Interaction Server, or Contact Server. The value &#36;Default&#36; specifies that the value of the interaction.disposition.key-name option is used.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "&#36;Window.Title&#36;,&#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.EmployeeId&#36;,&#36;Interaction.CaseId&#36;,&#36;Interaction.MainParty&#36;,&#36;Contact.X&#36;,&#36;AttachedData.Y&#36; (X: name of contact attribute, Y: attached data key name).",
+
"data_type": "A valid key name or &#36;Default&#36;.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,446: Line 1,599:
 
},
 
},
 
{
 
{
"id": "case-data.float-separator",
+
"id": "interaction.disposition.key-name",
"display_name": "Float Separator",
+
"display_name": "Disposition key name",
 
"type": "config",
 
"type": "config",
"default_value": ".",
+
"default_value": "DispositionCode",
"description": "Specifies the float separator that is used for Case data. This option should be used when the decimal symbol in the regional settings of the agent workstation is different from the one provided by the database.",
+
"description": "Specifies the key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid float separator. Typical float separators are: '.' ',' '\\'",
+
"data_type": "A valid key name.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,459: Line 1,613:
 
},
 
},
 
{
 
{
"id": "interaction.case-data.content",
+
"id": "interaction.disposition.folder-name-depth-<n>",
"display_name": "Case Data Content",
+
"display_name": "Disposition folder name at depth n",
 
"type": "config",
 
"type": "config",
"default_value": "History,CaseData",
+
"default_value": "No default value",
"description": "Specifies the content of the Case Information area in the interaction. The CaseData key enables the display of the attached data that is defined by the interaction.case-data.format-business-attribute option. The History key enables the display of interaction history information like the Origin field. The order in which the values are specified defines the order of the Case Data and History information in the Case Information area. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "History, CaseData",
+
"data_type": "Valid key name associated with a disposition.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,472: Line 1,627:
 
},
 
},
 
{
 
{
"id": "toast.case-data.content",
+
"id": "interaction.disposition.cache-timeout-delay",
"display_name": "Case Data Content",
+
"display_name": "Cache timeout delay for disposition",
 
"type": "config",
 
"type": "config",
"default_value": "History,CaseData",
+
"default_value": "-1",
"description": "Specifies the content of the Case Information area in the toast interaction preview. The CaseData key enables the display of the attached data that is defined by the toast.case-data.format-business-attribute option. The History key enables the display of interaction history information. The order in which the values are specified defines the order of the Case Data and History information in the Case Information area. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the delay, in seconds, before the cache of a disposition request result is cleared. If set to -1, the dispositions are kept in cache until the browser page is refreshed, or until the agent logs out and logs back in.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "History, CaseData",
+
"data_type": "From -1 to MAXINT.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,485: Line 1,641:
 
},
 
},
 
{
 
{
"id": "login.voice.is-auto-ready",
+
"id": "interaction.web-content",
"display_name": "Is Auto Ready",
+
"display_name": "Web extension views",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether the voice channels are in the Ready state at login.",
+
"description": "Specifies the list of Web Applications that are configured to be displayed at the Interaction level. Refer to 'Enabling integration of web applications in the agent interface in the Configuration Guide for information about creating web application objects in the configuration layer. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of option section names that correspond to web extension views. For example: Extension1, Extension2",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,498: Line 1,655:
 
},
 
},
 
{
 
{
"id": "login.voice.auto-not-ready-reason",
+
"id": "interation.web-content.url-encoding-defense-enabled",
"display_name": "Is Auto Not Ready Reason",
+
"display_name": "Web extension views URL Encoding",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "INTERNAL,BACKGROUND,HIDDEN{{!}}FORCE",
"description": "Specifies the NotReady Reason code if the Voice channel is automatically set to NotReady when the agent logs in.",
+
"description": "Specifies the list of modes on which the url encoding defense is applied. If the '<mode>' is not set, the url is unmodified (not encoded). If the '<mode>' is set but no hexadecimal character (%XX, where X is a hexa) is found in the url, the url is encoded. If the '<mode>{{!}}FORCE' is set, the url is always encoded. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid not ready reason.",
+
"data_type": "A comma-separated list of one or more modes and the optional FORCE modifier in this format: <mode>[{{!}}FORCE]. Valid modes: INTERNAL, BACKGROUND, HIDDEN, EXTERNAL.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,511: Line 1,669:
 
},
 
},
 
{
 
{
"id": "login.voice.prompt-dn-less-phone-number",
+
"id": "interaction.auto-focus",
"display_name": "Prompt DN Less Phone Number",
+
"display_name": "Interaction auto focus",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies whether a new page is displayed during the login phase to show the current phone number assigned to the agent and also permits the agent to update it. This option is specific to SIP Server environment with no Config Server proxy connected to GWS.",
+
"description": "Specifies whether the inbound interaction is in focus automatically when it is accepted. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.38",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,524: Line 1,683:
 
},
 
},
 
{
 
{
"id": "login.voice.nb-dn-less-phone-number-stored",
+
"id": "interaction.auto-focus.<media-type>",
"display_name": "Nb Dn Less Phone Number stored",
+
"display_name": "Interaction auto focus per media",
 
"type": "config",
 
"type": "config",
"default_value": "1",
+
"default_value": "true",
"description": "Specifies the number of phone numbers which are stored for the agent. For this option to apply, the value of login.voice.prompt-dn-less-phone-number.enable-dynamic-dn must be true.<br>0: no phone number is pre-filled in the second login screen.<br>1: the last entered phone number is displayed in the second login screen.<br>A number greater than 1 specifies the maximum number of phone numbers that can be displayed in the second login screen.",
+
"description": "Specifies whether the inbound interaction of the specfied media type is in focus automatically when is accepted. This option overrides the 'interaction.auto-focus' option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.38",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 0 through 10.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,537: Line 1,697:
 
},
 
},
 
{
 
{
"id": "login.voice.expression.dn-less-phone-number",
+
"id": "interaction.group-recovered-interactions.enable",
"display_name": "Expression for the DN Less Phone Number",
+
"display_name": "Allow grouping the recovered interactions",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the valid format for a new phone number. A regular expression can be used to check the DN-less phone number format in the login window.",
+
"description": "Specifies whether the recovered interactions are grouped at the start of the session.",
 +
"version": "9.0.000.85",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,550: Line 1,711:
 
},
 
},
 
{
 
{
"id": "login.voice.dn-less-phone-number.valid-format",
+
"id": "interaction.group-recovered-interactions.activate-threshold",
"display_name": "DN Less Phone Number Valid Format",
+
"display_name": "Threshold to group the recovered interactions",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "15",
"description": "Specifies the correct format information to be displayed to the agent when the DN less phone number format is not correct.",
+
"description": "When the option 'interaction.group-recovered-interactions.enable' is true, specifies the threshold to start grouping all the recovered interactions.",
 +
"version": "9.0.000.85",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A string",
+
"data_type": "An integer value greater than or equal to 5.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,563: Line 1,725:
 
},
 
},
 
{
 
{
"id": "login.voice.list-available-queues",
+
"id": "interaction.case-data.enable-hyperlink",
"display_name": "Prompt Queue",
+
"display_name": "Case Data Enable hyperlink",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the ACD Queues that are displayed in the login window. If the option value is left blank, no queue is displayed to the agent; the agent can enter any valid login queue name. If a single queue is specified and the value of the login.voice.prompt-queue no queue information is displayed during login.",
+
"description": "Specifies whether a hyperlink that is part of the case information may be displayed. See also the expression.url option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of queues.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,576: Line 1,739:
 
},
 
},
 
{
 
{
"id": "login.voice.prompt-queue",
+
"id": "interaction.case-data.format-business-attribute",
"display_name": "Prompt Queue",
+
"display_name": "Case Data format Business Attribute",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether the agent must enter the ACD Queue for the voice channel in the login window.",
+
"description": "Specifies the name of the Business Attribute that contains the Business Attribute values that are used to filter and render attached data in the interaction. This option can be overridden by a routing strategy as described in the Configuration Guide. You can define the display order of Business Attribute Values by creating an interaction-workspace section in the annex of the Business Attribute, then add the interaction.case-data.order option. This option is a comma-separated list of Business Attributes Value Names that specifies the order of  the Business Attribute Values. The Attributes Values that are not listed in interaction.case-data.order option are put at the bottom of the list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Business Attribute.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,589: Line 1,753:
 
},
 
},
 
{
 
{
"id": "login.prompt-place",
+
"id": "interaction.case-data.frame-color",
"display_name": "Prompt Place",
+
"display_name": "Case Data frame color",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "#17849D",
"description": "Specifies whether the agent must enter his place in the login window. When this option is set to true, a new page is displayed during the login phase to specify a place. Enabling this option disables login.voice.prompt-dn-less-phone-number. Do not enable this option if the privilege.sipendpoint.can-use privilege is granted.",
+
"description": "Specifies the color of the border of the Case Data view frame. Examples: #FFFFBA00 for a Gold color, #FF6F7074 for a Silver color, #FFB8400B for a Bronze color. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Valid Hexadecimal (HTML) color code.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,602: Line 1,767:
 
},
 
},
 
{
 
{
"id": "login.store-recent-place",
+
"id": "toast.case-data.format-business-attribute",
"display_name": "Store recent place",
+
"display_name": "Case Data format Business Attribute",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether the most recently used Place is stored. This option is available if the login.prompt-place option is set to true.",
+
"description": "Specifies the name of the Business Attribute that contains the Business Attribute Values that are used to filter and render attached data in the toast interaction preview.<br><br>You can define the display order of Business Attribute Values by creating an interaction-workspace section in the annex of the Business Attribute, then add the toast.case-data.order option. Use this option to specify a comma-separated list of Business Attributes Value Names that define the order of  the Business Attribute Values. The Attributes Values that are not listed in option toast.case-data.order are put at the bottom of the list.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "The valid name of a Business Attribute.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,615: Line 1,781:
 
},
 
},
 
{
 
{
"id": "login.list-available-locales",
+
"id": "toast.window-title",
"display_name": "List of available languages",
+
"display_name": "Window Title",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "(&#36;Contact.FirstName&#36; &#36;Contact.LastName&#36;{{!}}&#36;Interaction.MainParty&#36;)",
"description": "Specifies the language that the agent can select at login time.<BR>Either, set this option empty to prevent the agent from selecting the language or set this option to &#36;All&#36; to get all the languages available, or set this option to a list of languages (possible values are Brazilian (pt-BR), French (fr-FR), French Canadian (fr-CA), German (de-DE), Japanese (ja), Spanish (es), Korean(ko), Italian(it), Dutch(nl) and Polish(pl)). English is the default language, and will always be available.",
+
"description": "Specifies the title of the Toast window by defining a string that contains the following field codes:&#36;Window.Title&#36;,&#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.EmployeeId&#36;,&#36;Interaction.CaseId&#36;,&#36;Interaction.MainParty&#36;,&#36;Contact.X&#36;,&#36;AttachedData.Y&#36; (X: name of contact attribute, Y: attached data key name). If all field codes are empty, the following field codes are used: '&#36;Window.Title&#36; - &#36;Interaction.MainParty&#36;'.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of valid locale names based on format LanguageCode-CountryCode from the following list: &#36;All&#36;, en-US, pt-BR, fr-FR, fr-CA, de-DE, ja, es, ko, it, nl, pl.",
+
"data_type": "&#36;Window.Title&#36;,&#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.EmployeeId&#36;,&#36;Interaction.CaseId&#36;,&#36;Interaction.MainParty&#36;,&#36;Contact.X&#36;,&#36;AttachedData.Y&#36; (X: name of contact attribute, Y: attached data key name).",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,628: Line 1,795:
 
},
 
},
 
{
 
{
"id": "voice.floating-interaction-mode.auto-collapse",
+
"id": "service-client-api.toast.width",
"display_name": "Auto collapse Dropdown Interaction",
+
"display_name": "Toast Width for SCAPI",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "400",
"description": "Specifies whether new floating voice interactions are displayed collapsed automatically.",
+
"description": "Specifies a custom toast width in pixel for the API system.popupToast()",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value greater than or equal to 140.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,641: Line 1,809:
 
},
 
},
 
{
 
{
"id": "voice.consultation.merge-attached-data-to-main",
+
"id": "case-data.float-separator",
"display_name": "Merge consultation attached data to the main interaction",
+
"display_name": "Float Separator",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": ".",
"description": "Specifies whether any attached data specific to the consultation (for example those defined in a corporate favorite) is merged to the main interaction.",
+
"description": "Specifies the float separator that is used for Case data. This option should be used when the decimal symbol in the regional settings of the agent workstation is different from the one provided by the database.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid float separator. Typical float separators are: '.' ',' '\\'",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,654: Line 1,823:
 
},
 
},
 
{
 
{
"id": "voice.hold-active-call-on-make-call",
+
"id": "interaction.case-data.content",
"display_name": "Hold active call on Make Call",
+
"display_name": "Case Data Content",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "History,CaseData",
"description": "Specifies whether the active call is turned to hold before placing an independent call. When disabled, the make call operation isn't available when there is a call on hold.",
+
"description": "Specifies the content of the Case Information area in the interaction. The CaseData key enables the display of the attached data that is defined by the interaction.case-data.format-business-attribute option. The History key enables the display of interaction history information like the Origin field. The order in which the values are specified defines the order of the Case Data and History information in the Case Information area. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "History, CaseData",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,667: Line 1,837:
 
},
 
},
 
{
 
{
"id": "voice.enable-dtmf-tone",
+
"id": "toast.case-data.content",
"display_name": "Play dtmf locally",
+
"display_name": "Case Data Content",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "History,CaseData",
"description": "Specifies whether a tone is played when an agent clicks a DTMF key.",
+
"description": "Specifies the content of the Case Information area in the toast interaction preview. The CaseData key enables the display of the attached data that is defined by the toast.case-data.format-business-attribute option. The History key enables the display of interaction history information. The order in which the values are specified defines the order of the Case Data and History information in the Case Information area. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "History, CaseData",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,680: Line 1,851:
 
},
 
},
 
{
 
{
"id": "voice.auto-answer",
+
"id": "login.voice.is-auto-ready",
"display_name": "Auto answer incoming phone call",
+
"display_name": "Is Auto Ready",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies whether a voice interaction is automatically answered when a EventRinging message is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the voice channels are in the Ready state at login.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,693: Line 1,865:
 
},
 
},
 
{
 
{
"id": "voice.auto-answer.is-enabled-on-already-in-call",
+
"id": "login.voice.auto-not-ready-reason",
"display_name": "Auto answer only if there is no other active call",
+
"display_name": "Is Auto Not Ready Reason",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether a voice interaction is automatically answered if there is other active call(s) (used only with voice.auto-answer set to true). This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the NotReady Reason code if the Voice channel is automatically set to NotReady when the agent logs in.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid not ready reason.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,706: Line 1,879:
 
},
 
},
 
{
 
{
"id": "voice.prompt-for-end",
+
"id": "login.voice.prompt-dn-less-phone-number",
"display_name": "Prompt for end",
+
"display_name": "Prompt DN Less Phone Number",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies whether Workspace displays a confirmation message when the agent clicks End. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether a new page is displayed during the login phase to show the current phone number assigned to the agent and also permits the agent to update it. This option is specific to SIP Server environment with no Config Server proxy connected to GWS.",
 +
"version": "9.0.000.09",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,719: Line 1,893:
 
},
 
},
 
{
 
{
"id": "voice.mark-done-on-release",
+
"id": "login.voice.nb-dn-less-phone-number-stored",
"display_name": "Mark done on release",
+
"display_name": "Nb Dn Less Phone Number stored",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "1",
"description": "Specifies if an interaction should be closed automatically if a Release message is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the number of phone numbers which are stored for the agent. For this option to apply, the value of login.voice.prompt-dn-less-phone-number.enable-dynamic-dn must be true.<br>0: no phone number is pre-filled in the second login screen.<br>1: the last entered phone number is displayed in the second login screen.<br>A number greater than 1 specifies the maximum number of phone numbers that can be displayed in the second login screen.",
 +
"version": "9.0.000.09",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value from 0 through 10.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,732: Line 1,907:
 
},
 
},
 
{
 
{
"id": "voice.reject.counter-key-name",
+
"id": "login.voice.expression.dn-less-phone-number",
"display_name": "Reject counter key name",
+
"display_name": "Expression for the DN Less Phone Number",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the key that is used to populate a counter in attached data when a call is rejected. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the valid format for a new phone number. A regular expression can be used to check the DN-less phone number format in the login window.",
 +
"version": "9.0.000.09",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid key name.",
+
"data_type": "A regular expression",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,745: Line 1,921:
 
},
 
},
 
{
 
{
"id": "voice.cancel-after-call-work-on-done",
+
"id": "login.voice.dn-less-phone-number.valid-format",
"display_name": "Cancel After Call Work On Done",
+
"display_name": "DN Less Phone Number Valid Format",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies if the voice channel should be forced to its former status when the agent marks the voice interaction as 'Done' while his voice channel is in After Call Work status.",
+
"description": "Specifies the correct format information to be displayed to the agent when the DN less phone number format is not correct.",
 +
"version": "9.0.000.09",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": " true, false",
+
"data_type": "A string",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,758: Line 1,935:
 
},
 
},
 
{
 
{
"id": "voice.cancel-after-call-work-on-business-call",
+
"id": "login.voice.dn-less-phone-number.sample",
"display_name": "Cancel After Call On Business Call",
+
"display_name": "DN Less Phone Number Sample",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies if the voice channel should be canceled its After Call Work status when the agents switches from After Call Work to Ready or Not Ready during a business call. This option is specific to SIP Server environment.",
+
"description": "Specifies a sample of a DN-less phone number to be displayed in the second step of the login procedure.",
 +
"version": "9.0.000.84",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": " true, false",
+
"data_type": "A string",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,771: Line 1,949:
 
},
 
},
 
{
 
{
"id": "voice.clear-conference-on-release",
+
"id": "login.voice.list-available-queues",
"display_name": "Clear Conference On Release",
+
"display_name": "Prompt Queue",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether the conference call is cleared (all the parties in the conference are released) when the last agent leaves the conference.",
+
"description": "Specifies the ACD Queues that are displayed in the login window. If the option value is left blank, no queue is displayed to the agent; the agent can enter any valid login queue name. If a single queue is specified and the value of the login.voice.prompt-queue no queue information is displayed during login.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "Comma-separated list of queues.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,784: Line 1,963:
 
},
 
},
 
{
 
{
"id": "voice.user-data.send-only-updated-data-on-complete",
+
"id": "login.voice.prompt-queue",
"display_name": "Send Only Updated User Data On Complete",
+
"display_name": "Prompt Queue",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether only the updated user data is sent for reporting purposes when a call is completed. Otherwise, all the user data is sent when a call is completed.",
+
"description": "Specifies whether the agent must enter the ACD Queue for the voice channel in the login window.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,797: Line 1,977:
 
},
 
},
 
{
 
{
"id": "chat.auto-answer",
+
"id": "login.prompt-place",
"display_name": "Auto Accept Incoming Chat",
+
"display_name": "Prompt Place",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies whether a chat interaction is automatically accepted and joined when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the agent must enter his place in the login window. When this option is set to true, a new page is displayed during the login phase to specify a place. Enabling this option disables login.voice.prompt-dn-less-phone-number.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 1,810: Line 1,991:
 
},
 
},
 
{
 
{
"id": "chat.nickname",
+
"id": "login.store-recent-place",
"display_name": "Agent Nickname",
+
"display_name": "Store recent place",
 
"type": "config",
 
"type": "config",
"default_value": "&#36;Agent.UserName&#36;",
+
"default_value": "true",
"description": "Specifies the agent's nickname that is displayed to contacts during chat sessions. The nickname string may contain regular characters and field codes. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the most recently used Place is stored. This option is available if the login.prompt-place option is set to true.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A string that contains a compilation of characters and field codes from the following list: &#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.FullName&#36;,&#36;Agent.EmployeeId&#36;,&#36;FirstNameLastInitial&#36;..",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,823: Line 2,005:
 
},
 
},
 
{
 
{
"id": "chat.enable-auto-disconnect",
+
"id": "login.list-available-locales",
"display_name": "Enable Auto Disconnect",
+
"display_name": "List of available languages",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether the chat session is automatically disconnected if the agent is the last party remaining in the chat session.",
+
"description": "Specifies the language that the agent can select at login time.<BR>Either, set this option empty to prevent the agent from selecting the language or set this option to &#36;All&#36; to get all the languages available, or set this option to a list of languages (possible values are Brazilian (pt-BR), French (fr-FR), French Canadian (fr-CA), German (de-DE), Japanese (ja), Spanish (es), Korean (ko), Italian (it), Dutch (nl), Polish (pl), Simplified Chinese (zh-CN) and Traditional Chinese (zh-CHT)). English is the default language, and is always available.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "Comma-separated list of valid locale names based on format LanguageCode-CountryCode from the following list: &#36;All&#36;, en-US, pt-BR, fr-FR, fr-CA, de-DE, ja, es, ko, it, nl, pl, zh-CN, zh-CHT.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,836: Line 2,019:
 
},
 
},
 
{
 
{
"id": "chat.prompt-for-done",
+
"id": "voice.floating-interaction-mode.auto-collapse",
"display_name": "Prompt for done",
+
"display_name": "Auto collapse Dropdown Interaction",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies whether the application prompts a confirmation message when a user clicks Done. This option is only available for open media interactions. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether new floating voice interactions are displayed collapsed automatically.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,849: Line 2,033:
 
},
 
},
 
{
 
{
"id": "chat.prompt-for-end",
+
"id": "voice.consultation.merge-attached-data-to-main",
"display_name": "Prompt for end",
+
"display_name": "Merge consultation attached data to the main interaction",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies Whether the application displays a confirmation message when an agent clicks End. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether any attached data specific to the consultation (for example those defined in a corporate favorite) is merged to the main interaction.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,862: Line 2,047:
 
},
 
},
 
{
 
{
"id": "chat.pending-response-to-customer",
+
"id": "voice.hold-active-call-on-make-call",
"display_name": "Pending Customer Message Timer",
+
"display_name": "Hold active call on Make Call",
 
"type": "config",
 
"type": "config",
"default_value": "30,50",
+
"default_value": "true",
"description": "Specifies two alarm thresholds, in seconds, that warn agents that they have a pending response to a chat from a customer. Three levels are displayed: before the warning time, between the warning time and the maximum time, and after the maximum time.",
+
"description": "Specifies whether the active call is turned to hold before placing an independent call. When disabled, the make call operation isn't available when there is a call on hold.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list value: warning time, maximum time",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,875: Line 2,061:
 
},
 
},
 
{
 
{
"id": "chat.typing-is-enabled",
+
"id": "voice.enable-dtmf-tone",
"display_name": "Typing is enabled",
+
"display_name": "Play dtmf locally",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether typing notification is sent to the contact during a chat interaction. It should be disabled for Chat Server lower than 8.0.1.",
+
"description": "Specifies whether a tone is played when an agent clicks a DTMF key.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,888: Line 2,075:
 
},
 
},
 
{
 
{
"id": "chat.typing-timeout",
+
"id": "voice.auto-answer",
"display_name": "Typing timeout",
+
"display_name": "Auto answer incoming phone call",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "false",
"description": "Specifies the duration, in seconds, that the typing notification is displayed after the last keystroke and before the agent or contact sends their message.",
+
"description": "Specifies whether a voice interaction is automatically answered when a EventRinging message is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A positive integer value.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,901: Line 2,089:
 
},
 
},
 
{
 
{
"id": "chat.time-stamp",
+
"id": "voice.auto-answer.is-enabled-on-already-in-call",
"display_name": "Show Message Time Stamp",
+
"display_name": "Auto answer only if there is no other active call",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Specifies whether the time stamp is displayed in the Chat transcript area.",
+
"description": "Specifies whether a voice interaction is automatically answered if there is other active call(s) (used only with voice.auto-answer set to true). This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,914: Line 2,103:
 
},
 
},
 
{
 
{
"id": "chat.push-url.max-records",
+
"id": "voice.prompt-for-end",
"display_name": "Maximum size of pushed URL list",
+
"display_name": "Prompt for end",
 
"type": "config",
 
"type": "config",
"default_value": "20",
+
"default_value": "false",
"description": "Specifies maximum size of pushed URL list.",
+
"description": "Specifies whether Workspace displays a confirmation message when the agent clicks End. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any positive integer value.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,927: Line 2,117:
 
},
 
},
 
{
 
{
"id": "chat.on-hold-queue",
+
"id": "voice.mark-done-on-release",
"display_name": "On hold queue",
+
"display_name": "Mark done on release",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the Interaction Queue where the chat interaction is placed when the agent clicks Place chat on hold. This option can be overridden by a routing strategy, as described in Overriding Options by Using a Routing Strategy in the Configuration Guide.",
+
"description": "Specifies if an interaction should be closed automatically if a Release message is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid name of a Script of type Interaction Queue.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,940: Line 2,131:
 
},
 
},
 
{
 
{
"id": "email.print.print-content",
+
"id": "voice.reject.counter-key-name",
"display_name": "Email interaction fields to print.",
+
"display_name": "Reject counter key name",
 
"type": "config",
 
"type": "config",
"default_value": "From,To,Cc,Subject,Body,Date,Attachment,InteractionType",
+
"default_value": "No default value",
"description": "Specifies the list of fields to print for an email interaction. Supported fields are: From, To, Cc, Subject, Body, Date, Attachment, InteractionType, CaseData, Note.",
+
"description": "Specifies the key that is used to populate a counter in attached data when a call is rejected. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of one or valid more email interaction fields.",
+
"data_type": "A valid key name.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,953: Line 2,145:
 
},
 
},
 
{
 
{
"id": "email.auto-answer",
+
"id": "voice.cancel-after-call-work-on-done",
"display_name": "Auto Accept Incoming E-Mail",
+
"display_name": "Cancel After Call Work On Done",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies whether an email interaction is automatically accepted when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies if the voice channel should be forced to its former status when the agent marks the voice interaction as 'Done' while his voice channel is in After Call Work status.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": " true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,966: Line 2,159:
 
},
 
},
 
{
 
{
"id": "email.default-queue",
+
"id": "voice.cancel-after-call-work-on-business-call",
"display_name": "Default Submission Queue",
+
"display_name": "Cancel After Call On Business Call",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the Interaction queue in which new or reply outgoing emails are submitted.",
+
"description": "Specifies if the voice channel should be canceled its After Call Work status when the agents switches from After Call Work to Ready or Not Ready during a business call. This option is specific to SIP Server environment.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid name of a Script of type Interaction Queue.",
+
"data_type": " true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,979: Line 2,173:
 
},
 
},
 
{
 
{
"id": "email.outbound-queue",
+
"id": "voice.clear-conference-on-release",
"display_name": "Default Outbound Queue",
+
"display_name": "Clear Conference On Release",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the Interaction Queue in which outgoing emails are placed when agents click Send or Send Interim. This options is used only when Interaction Workflow does not set Queue for New Interactions when it is routing inbound email interactions to agents.",
+
"description": "Specifies whether the conference call is cleared (all the parties in the conference are released) when the last agent leaves the conference.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid name of a Script of type Interaction Queue.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 1,992: Line 2,187:
 
},
 
},
 
{
 
{
"id": "email.inline-forward-queue",
+
"id": "voice.user-data.send-only-updated-data-on-complete",
"display_name": "In-line Forward Queue",
+
"display_name": "Send Only Updated User Data On Complete",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the Interaction queue in which in-line forwarded inbound emails are submitted.",
+
"description": "Specifies whether only the updated user data is sent for reporting purposes when a call is completed. Otherwise, all the user data is sent when a call is completed.",
 +
"version": "9.0.000.68",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid name of a Script of type Interaction Queue.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,005: Line 2,201:
 
},
 
},
 
{
 
{
"id": "email.from-addresses",
+
"id": "voice.enable-agent-reservation",
"display_name": "Default From addresses",
+
"display_name": "Support agent reservation on voice media",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies a character string that specifies the name of the Business Attribute which contains the Attribute Values that are used as available addresses. These come from the addresses of email interactions. You can set a default value by using the flag from the Business Attribute value. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether Workspace should prevent an agent from manually setting the voice channel to Not Ready, Do Not Disturb, After Call Work, or Logged Off status, or from exiting the application if the agent has been marked as Reserved by the Router or any other server that can reserve an Agent for call distribution.",
 +
"version": "9.0.000.90",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Business Attribute.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,018: Line 2,215:
 
},
 
},
 
{
 
{
"id": "email.allowed-image-extensions",
+
"id": "voice.display-name.key-name",
"display_name": "Allowed image extensions",
+
"display_name": "Attached data key for display name",
 
"type": "config",
 
"type": "config",
"default_value": "jpg,gif,png",
+
"default_value": "No default value",
"description": "Specifies the list of image extensions that agents can attach to an email interaction. The attachment is refused by the system and an error message is displayed to the agent if the image extension is not in the list of allowed image extensions.",
+
"description": "Specifies the attached data key name of inbound voice interactions that contains the 'From' information of the inbound call, if the interaction does not have a contact set or the contact does not have a firstname or lastname property set. This information is displayed in the Interaction notification title and in the Recents list of Team Communicator. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.91",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated values of list of image extensions.",
+
"data_type": "Any valid attached data key name.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,031: Line 2,229:
 
},
 
},
 
{
 
{
"id": "email.max-attachment-size",
+
"id": "login.<media-type>.is-auto-ready",
"display_name": "Max attachment size",
+
"display_name": "Is Media Openmedia Auto Ready",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "false",
"description": "Specifies the maximum number of megabytes of one file that agents can attach to an external email interaction. The attachment is refused by the system and an error message is displayed to the agent if the size in megabytes of the attached file exceeds this value. The value 0 means that there is no restriction.",
+
"description": "Specifies whether the channel for the specified media-type (open media) is in the Ready state at login.",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A positive integer.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,044: Line 2,243:
 
},
 
},
 
{
 
{
"id": "email.max-attachments-size",
+
"id": "login.chat.is-auto-ready",
"display_name": "Max attachments size",
+
"display_name": "Is Media Chat Auto Ready",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "false",
"description": "Specifies the maximum number of total megabytes of files that agents can attach to an external email interaction. An error message is displayed to the agent if the total number of megabytes for all attached files exceeds this value. The value 0 means that there is no restriction.",
+
"description": "Specifies whether the chat channel is in the Ready state at login. This option also applies to social media channels (Facebook, Twitter, SMS, and WhatsApp) which are handled in the Chat interaction view.",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A positive integer.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,057: Line 2,257:
 
},
 
},
 
{
 
{
"id": "email.prompt-for-done",
+
"id": "login.email.is-auto-ready",
"display_name": "Prompt for done",
+
"display_name": "Is Media Email Auto Ready",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies if the application prompts a confirmation message when the user clicks Done. This option is only available for interaction open media. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the email channel is in the Ready state at login.",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,070: Line 2,271:
 
},
 
},
 
{
 
{
"id": "email.reply-prefix",
+
"id": "chat.auto-answer",
"display_name": "Reply prefix",
+
"display_name": "Auto Accept Incoming Chat",
 
"type": "config",
 
"type": "config",
"default_value": "Re: ",
+
"default_value": "false",
"description": "Specifies the reply prefix that is added to subject of the inbound email interaction.",
+
"description": "Specifies whether a chat interaction is automatically accepted and joined when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,083: Line 2,285:
 
},
 
},
 
{
 
{
"id": "email.inline-forward-prefix",
+
"id": "chat.nickname",
"display_name": "In-line forward prefix",
+
"display_name": "Agent Nickname",
 
"type": "config",
 
"type": "config",
"default_value": "Fwd: ",
+
"default_value": "&#36;Agent.UserName&#36;",
"description": "Specifies the inline forward prefix that is added to subject of the forwarded inbound email interaction.",
+
"description": "Specifies the agent's nickname that is displayed to contacts during chat sessions. The nickname string may contain regular characters and field codes. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "A string that contains a compilation of characters and field codes from the following list: &#36;Agent.UserName&#36;,&#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.FullName&#36;,&#36;Agent.EmployeeId&#36;,&#36;FirstNameLastInitial&#36;..",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,096: Line 2,299:
 
},
 
},
 
{
 
{
"id": "email.quote-char",
+
"id": "chat.enable-auto-disconnect",
"display_name": "Quote Char",
+
"display_name": "Enable Auto Disconnect",
 
"type": "config",
 
"type": "config",
"default_value": ">",
+
"default_value": "true",
"description": "For outgoing email that is formatted as plain text, specifies the characters that are used to quote the contents of the inbound email interaction in the outgoing email interaction body.",
+
"description": "Specifies whether the chat session is automatically disconnected if the agent is the last party remaining in the chat session.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,109: Line 2,313:
 
},
 
},
 
{
 
{
"id": "email.include-original-text-in-reply",
+
"id": "chat.prompt-for-done",
"display_name": "Include Original text in reply",
+
"display_name": "Prompt for done",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether the text of the original inbound email interaction is included in the outgoing reply email. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether the application prompts a confirmation message when a user clicks Done. This option is only available for open media interactions. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,122: Line 2,327:
 
},
 
},
 
{
 
{
"id": "email.reply-format",
+
"id": "chat.prompt-for-end",
"display_name": "Reply Format",
+
"display_name": "Prompt for end",
 
"type": "config",
 
"type": "config",
"default_value": "auto",
+
"default_value": "false",
"description": "Specifies the format of an outgoing email reply:\n* auto: outgoing email reply format is the same as corresponding inbound email.\n* html: outgoing email reply format is forced to html.\n* plain-text: outgoing email reply format is forced to plain text.",
+
"description": "Specifies Whether the application displays a confirmation message when an agent clicks End. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select a value from the following list: auto, html, plain-text.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,135: Line 2,341:
 
},
 
},
 
{
 
{
"id": "email.html-format",
+
"id": "chat.pending-response-to-customer",
"display_name": "HTML format",
+
"display_name": "Pending Customer Message Timer",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "30,50",
"description": "Specifies the format of a new outgoing email. When set to true, new email is formatted in HTML.",
+
"description": "Specifies two alarm thresholds, in seconds, that warn agents that they have a pending response to a chat from a customer. Three levels are displayed: before the warning time, between the warning time and the maximum time, and after the maximum time.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list value: warning time, maximum time",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,148: Line 2,355:
 
},
 
},
 
{
 
{
"id": "email.enable-toggle-format",
+
"id": "chat.typing-is-enabled",
"display_name": "Enable to toggle format",
+
"display_name": "Typing is enabled",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies whether the agent is permitted to switch between text and html in the email editor. Depends on 'E-Mail - Can Use E-mail Channel'. This option can be overridden by a routing strategy as described in Configuration Guide.",
+
"description": "Specifies whether typing notification is sent to the contact during a chat interaction. It should be disabled for Chat Server lower than 8.0.1.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,161: Line 2,369:
 
},
 
},
 
{
 
{
"id": "email.quote-header",
+
"id": "chat.typing-timeout",
"display_name": "Quote Header",
+
"display_name": "Typing timeout",
 
"type": "config",
 
"type": "config",
"default_value": "On <date>, <contact> wrote:",
+
"default_value": "10",
"description": "Specifies the character string that is used to introduce the quoted inbound email interaction content in the body of the outgoing email. The value &#36;FullHeader&#36; inserts the entire header of the inbound email into the outgoing email. You can also choose to include any other text. The following tags are supported: <contact>, <date>. This enables you to create a custom header, such as: 'On <date>, <contact> wrote:'.",
+
"description": "Specifies the duration, in seconds, that the typing notification is displayed after the last keystroke and before the agent or contact sends their message.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "A positive integer value.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,174: Line 2,383:
 
},
 
},
 
{
 
{
"id": "email.inline-forward-header",
+
"id": "chat.time-stamp",
"display_name": "Inline Forward Header",
+
"display_name": "Show Message Time Stamp",
 
"type": "config",
 
"type": "config",
"default_value": "&#36;FullHeader&#36;",
+
"default_value": "true",
"description": "Specifies the character string that is used to introduce the inbound email content in the body of the inline forward email. The value &#36;FullHeader&#36; inserts the entire header of the inbound email interaction into the inline forwarded email. You can also choose to include any other text. The following tags are supported: <contact>, <date>. This enables you to create a custom header, such as: 'On <date>, <contact> wrote:'.",
+
"description": "Specifies whether the time stamp is displayed in the Chat transcript area.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,187: Line 2,397:
 
},
 
},
 
{
 
{
"id": "email.signature.line-<n>",
+
"id": "chat.push-url.max-records",
"display_name": "signature",
+
"display_name": "Maximum size of pushed URL list",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "20",
"description": "Specifies the row number of the signature by a string that can contain regular characters and the following field codes: &#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.FullName&#36;. <n> is starting at 0. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies maximum size of pushed URL list.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "Any positive integer value.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,200: Line 2,411:
 
},
 
},
 
{
 
{
"id": "email.signature",
+
"id": "chat.on-hold-queue",
"display_name": "Signature using a standard response",
+
"display_name": "On hold queue",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the type and location of the signature template that Workspace should add to outgoing emails. The value has two components that are separated by a colon:<br>1. 'response'<br>2. The standard response name and the full path of the parent category in the Standard Response Library.<br>For example, 'response:Signatures\\Classic'.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the Interaction Queue where the chat interaction is placed when the agent clicks Place chat on hold. This option can be overridden by a routing strategy, as described in Overriding Options by Using a Routing Strategy in the Configuration Guide.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "\\\"response:\\\" followed by the response path to the standard response",
+
"data_type": "A valid name of a Script of type Interaction Queue.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,213: Line 2,425:
 
},
 
},
 
{
 
{
"id": "email.qa-review-dispositions-business-attribute",
+
"id": "email.print.print-content",
"display_name": "QA review disposition business attributes",
+
"display_name": "Email interaction fields to print.",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "From,To,Cc,Subject,Body,Date,Attachment,InteractionType",
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for qa-review-dispositions code. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the list of fields to print for an email interaction. Supported fields are: From, To, Cc, Subject, Body, Date, Attachment, InteractionType, CaseData, Note.",
 +
"version": "9.0.000.48",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid character string.",
+
"data_type": "A comma-separated list of one or valid more email interaction fields.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,226: Line 2,439:
 
},
 
},
 
{
 
{
"id": "email.enable-email-address-validation",
+
"id": "email.auto-answer",
"display_name": "Enable email address validation",
+
"display_name": "Auto Accept Incoming E-Mail",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies that the To, Cc, and Bcc addresses are validated when completing sending and forwarding.",
+
"description": "Specifies whether an email interaction is automatically accepted when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,239: Line 2,453:
 
},
 
},
 
{
 
{
"id": "email.outbound.editable-to-addresses",
+
"id": "email.default-queue",
"display_name": "Add To addresses",
+
"display_name": "Default Submission Queue",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether an agent can add To addresses to a new or reply outgoing email. This option can be overridden by a routing strategy, as described in the Configuiration Guide.",
+
"description": "Specifies the Interaction queue in which new or reply outgoing emails are submitted.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid name of a Script of type Interaction Queue.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,252: Line 2,467:
 
},
 
},
 
{
 
{
"id": "email.outbound.editable-cc-addresses",
+
"id": "email.outbound-queue",
"display_name": "Add Cc addresses",
+
"display_name": "Default Outbound Queue",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether an agent can add Cc addresses to a new, reply, or forward outgoing email. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
+
"description": "Specifies the Interaction Queue in which outgoing emails are placed when agents click Send or Send Interim. This options is used only when Interaction Workflow does not set Queue for New Interactions when it is routing inbound email interactions to agents.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid name of a Script of type Interaction Queue.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,265: Line 2,481:
 
},
 
},
 
{
 
{
"id": "email.outbound.editable-bcc-addresses",
+
"id": "email.inline-forward-queue",
"display_name": "Add Bcc addresses",
+
"display_name": "In-line Forward Queue",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether an agent can add Bcc addresses to a new, reply, or forward outgoing email. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
+
"description": "Specifies the Interaction queue in which in-line forwarded inbound emails are submitted.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid name of a Script of type Interaction Queue.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,278: Line 2,495:
 
},
 
},
 
{
 
{
"id": "email.mandatory-subject",
+
"id": "email.from-addresses",
"display_name": "Mandatory subject",
+
"display_name": "Default From addresses",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether the subject of an outgoing email must be specified to enable the Send operation:<ul><li>false: No control is applied on the content of the subject field.</li><li>true: Email sending cannot be completed until the subject field is not empty. An error message is displayed.</li><li>prompt: If the subject is empty, a confirmation box is displayed to prompt the agent to add a subject or proceed with sending without a subject.</li></ul>",
+
"description": "Specifies a character string that specifies the name of the Business Attribute which contains the Attribute Values that are used as available addresses. These come from the addresses of email interactions. You can set a default value by using the flag from the Business Attribute value. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Business Attribute.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,291: Line 2,509:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-print",
+
"id": "email.allowed-image-extensions",
"display_name": "Can print email",
+
"display_name": "Allowed image extensions",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "jpg,gif,png",
"description": "Enables agents to print email interactions from the My history and My Workbin views, and from the Contact History tabs of the Contact Directory, Interaction Search, and Interaction Detail views.",
+
"description": "Specifies the list of image extensions that agents can attach to an email interaction. The attachment is refused by the system and an error message is displayed to the agent if the image extension is not in the list of allowed image extensions.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated values of list of image extensions.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,304: Line 2,523:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-move-to-workbin",
+
"id": "email.max-attachment-size",
"display_name": "Can move to workbin",
+
"display_name": "Max attachment size",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "0",
"description": "Enables an agent to move email interactions to workbins.",
+
"description": "Specifies the maximum number of megabytes of one file that agents can attach to an external email interaction. The attachment is refused by the system and an error message is displayed to the agent if the size in megabytes of the attached file exceeds this value. The value 0 means that there is no restriction.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A positive integer.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,317: Line 2,537:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-reply",
+
"id": "email.max-attachments-size",
"display_name": "Can use reply",
+
"display_name": "Max attachments size",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "0",
"description": "Enables an agent to reply to inbound email interactions.",
+
"description": "Specifies the maximum number of total megabytes of files that agents can attach to an external email interaction. An error message is displayed to the agent if the total number of megabytes for all attached files exceeds this value. The value 0 means that there is no restriction.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A positive integer.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,330: Line 2,551:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-reply-all",
+
"id": "email.prompt-for-done",
"display_name": "Can  reply all",
+
"display_name": "Prompt for done",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to reply to all parties included in the distribution of inbound email interactions.",
+
"description": "Specifies if the application prompts a confirmation message when the user clicks Done. This option is only available for interaction open media. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,343: Line 2,565:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-send",
+
"id": "email.reply-prefix",
"display_name": "Can  send",
+
"display_name": "Reply prefix",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Re: ",
"description": "Enables an agent to send outgoing email interactions.",
+
"description": "Specifies the reply prefix that is added to subject of the inbound email interaction.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,356: Line 2,579:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-interim-send",
+
"id": "email.inline-forward-prefix",
"display_name": "Can Interim send",
+
"display_name": "In-line forward prefix",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "Fwd: ",
"description": "Enables an agent to send interim outgoing email interactions.",
+
"description": "Specifies the inline forward prefix that is added to subject of the forwarded inbound email interaction.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,369: Line 2,593:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-save",
+
"id": "email.quote-char",
"display_name": "Can  save",
+
"display_name": "Quote Char",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": ">",
"description": "Enables an agent to save in-progress outgoing email interactions.",
+
"description": "For outgoing email that is formatted as plain text, specifies the characters that are used to quote the contents of the inbound email interaction in the outgoing email interaction body.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,382: Line 2,607:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-add-attachment",
+
"id": "email.include-original-text-in-reply",
"display_name": "Can add attachment ",
+
"display_name": "Include Original text in reply",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables an agent to add attached files to outgoing emails.",
+
"description": "Specifies whether the text of the original inbound email interaction is included in the outgoing reply email. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,395: Line 2,621:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-delete",
+
"id": "email.reply-format",
"display_name": "Can delete",
+
"display_name": "Reply Format",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "auto",
"description": "Enables an agent to delete outgoing email interactions.",
+
"description": "Specifies the format of an outgoing email reply:\n* auto: outgoing email reply format is the same as corresponding inbound email.\n* html: outgoing email reply format is forced to html.\n* plain-text: outgoing email reply format is forced to plain text.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Select a value from the following list: auto, html, plain-text.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,408: Line 2,635:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-one-step-transfer",
+
"id": "email.html-format",
"display_name": "Can use one step transfer",
+
"display_name": "HTML format",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables an agent to one-step transfer email interactions.",
+
"description": "Specifies the format of a new outgoing email. When set to true, new email is formatted in HTML.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,421: Line 2,649:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-inline-forward",
+
"id": "email.enable-toggle-format",
"display_name": "Can use inline forward",
+
"display_name": "Enable to toggle format",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to forward an email inline instead of as an attachment.",
+
"description": "Specifies whether the agent is permitted to switch between text and html in the email editor. Depends on 'E-Mail - Can Use E-mail Channel'. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,434: Line 2,663:
 
},
 
},
 
{
 
{
"id": "privilege.email.embedded-images.can-use",
+
"id": "email.quote-header",
"display_name": "Can show embedded image",
+
"display_name": "Quote Header",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "On <date>, <contact> wrote:",
"description": "Enables agents to view embedded images in email interactions.",
+
"description": "Specifies the character string that is used to introduce the quoted inbound email interaction content in the body of the outgoing email. The value &#36;FullHeader&#36; inserts the entire header of the inbound email into the outgoing email. You can also choose to include any other text. The following tags are supported: <contact>, <date>. This enables you to create a custom header, such as: 'On <date>, <contact> wrote:'.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,447: Line 2,677:
 
},
 
},
 
{
 
{
"id": "privilege.email.embedded-images.can-add",
+
"id": "email.inline-forward-header",
"display_name": "Can add embedded image",
+
"display_name": "Inline Forward Header",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "&#36;FullHeader&#36;",
"description": "Enables agents to add embedded images in outgoing email interactions. Depends on the option privilege.email.embedded-images.can-use.",
+
"description": "Specifies the character string that is used to introduce the inbound email content in the body of the inline forward email. The value &#36;FullHeader&#36; inserts the entire header of the inbound email interaction into the inline forwarded email. You can also choose to include any other text. The following tags are supported: <contact>, <date>. This enables you to create a custom header, such as: 'On <date>, <contact> wrote:'.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,460: Line 2,691:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.routing-points",
+
"id": "email.signature.line-<n>",
"display_name": "Routing Points for voice",
+
"display_name": "signature",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the call number that is used by the Routing Base feature. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
+
"description": "Specifies the row number of the signature by a string that can contain regular characters and the following field codes: &#36;Agent.LastName&#36;,&#36;Agent.FirstName&#36;,&#36;Agent.FullName&#36;. <n> is starting at 0. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of call number names in the following format: &#36;dn_name@switch&#36;",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,473: Line 2,705:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.routing-based-actions",
+
"id": "email.signature",
"display_name": "Routing based actions for voice",
+
"display_name": "Signature using a standard response",
 
"type": "config",
 
"type": "config",
"default_value": "MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer",
+
"default_value": "No default value",
"description": "Specifies the list of Routing Based Actions that an agent may perform.",
+
"description": "Specifies the type and location of the signature template that Workspace should add to outgoing emails. The value has two components that are separated by a colon:<br>1. 'response'<br>2. The standard response name and the full path of the parent category in the Standard Response Library.<br>For example, 'response:Signatures\\Classic'.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid operation names from the following list: MakeCall, OneStepTransfer, InitTransfer, InitConference, OneStepConference.",
+
"data_type": "\\\"response:\\\" followed by the response path to the standard response",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,486: Line 2,719:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.routing-based-targets",
+
"id": "email.signature.attachments.enable",
"display_name": "Routing based targets for voice",
+
"display_name": "Enable attachments for email signature",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the list of targets that are contacted through the routing based mechanism for the requests that are defined by the intercommunication.voice.routing-based-actions option. Note: The targets AgentGroup and Skill are always addressed through routing; therefore, they are not affected by this option.",
+
"description": "Specifies whether the attachments from a standard response, set in the email.signature option, are included in the related email interaction.",
 +
"version": "9.0.000.95",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, RoutingPoint, TypeDestination, OutboundRecord, Contact",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,499: Line 2,733:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.make-call-caller-id-business-attribute",
+
"id": "email.qa-review-dispositions-business-attribute",
"display_name": "Make call caller-id business attribute",
+
"display_name": "QA review disposition business attributes",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as outbound caller IDs. This option is only applicable for external calls.",
+
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for qa-review-dispositions code. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.",
+
"data_type": "Any valid character string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,512: Line 2,747:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.make-call-caller-id-enable-anonymous",
+
"id": "email.enable-email-address-validation",
"display_name": "Enable Anonymous on Make Call Caller-ID",
+
"display_name": "Enable email address validation",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies whether anonymous is enabled on make call with caller id. This option is only applicable for external calls. This functionality can currently only be used in conjunction with the SIP Server TServer\\/enforce-p-asserted-identity option configured on the outbound PSTN Trunk DN. This must be configured in the environment where the PSTN Provider (Carrier) implements Calling Line Identification Restriction (CLIR) and allows masking the displayed number (Caller ID) only if privacy SIP headers are correctly constructed and 'anonymous@anonymous.invalid' is specified in the From field.",
+
"description": "Specifies that the To, Cc, and Bcc addresses are validated when completing sending and forwarding.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 2,525: Line 2,761:
 
},
 
},
 
{
 
{
"id": "voice.caller-id.key-name",
+
"id": "email.outbound.editable-to-addresses",
"display_name": "Attached Data Key for Caller Id",
+
"display_name": "Add To addresses",
 
"type": "config",
 
"type": "config",
"default_value": "IW_SelectedCallerId",
+
"default_value": "true",
"description": "Specifies the key name of the attached data that contains the selected caller id information.",
+
"description": "Specifies whether an agent can add To addresses to a new or reply outgoing email. This option can be overridden by a routing strategy, as described in the Configuiration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An attached data key name (string)",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,538: Line 2,775:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.single-step-conference-enabled",
+
"id": "email.outbound.editable-cc-addresses",
"display_name": "Single Step Conference enabled for voice",
+
"display_name": "Add Cc addresses",
 
"type": "config",
 
"type": "config",
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
+
"default_value": "true",
"description": "Specifies the list of targets enabled in Team Communication for a single step conference.",
+
"description": "Specifies whether an agent can add Cc addresses to a new, reply, or forward outgoing email. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,551: Line 2,789:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.single-step-transfer-enabled",
+
"id": "email.outbound.editable-bcc-addresses",
"display_name": "Single Step Transfer enabled for voice",
+
"display_name": "Add Bcc addresses",
 
"type": "config",
 
"type": "config",
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
+
"default_value": "true",
"description": "Specifies the list of targets enabled in Team Communication for a single step transfer.",
+
"description": "Specifies whether an agent can add Bcc addresses to a new, reply, or forward outgoing email. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,564: Line 2,803:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.consultation-enabled",
+
"id": "email.mandatory-subject",
"display_name": "Consultation enabled for voice",
+
"display_name": "Mandatory subject",
 
"type": "config",
 
"type": "config",
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
+
"default_value": "true",
"description": "Specifies the list of targets enabled in Team Communication for a consultation.",
+
"description": "Specifies whether the subject of an outgoing email must be specified to enable the Send operation:<ul><li>false: No control is applied on the content of the subject field.</li><li>true: Email sending cannot be completed until the subject field is not empty. An error message is displayed.</li><li>prompt: If the subject is empty, a confirmation box is displayed to prompt the agent to add a subject or proceed with sending without a subject.</li></ul>",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,577: Line 2,817:
 
},
 
},
 
{
 
{
"id": "intercommunication.voice.make-call-enabled",
+
"id": "email.insert-url.max-records",
"display_name": "Make Call enabled",
+
"display_name": "Maximum size of modified URL list",
 
"type": "config",
 
"type": "config",
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
+
"default_value": "20",
"description": "Specifies the list of targets enabled in Team Communication for making call.",
+
"description": "Specifies the maximum number of modified URLs in the menu in the Insert Link and Edit Link dialog boxes.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
+
"data_type": "Any positive integer value.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,590: Line 2,831:
 
},
 
},
 
{
 
{
"id": "intercommunication.chat.queue",
+
"id": "email.inline-forward.exclude-case-data-keys",
"display_name": "Routing Based Queue for chat",
+
"display_name": "List of attached data keys to be excluded in email inline forward for Case Data",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "ContactId,EmailAddress,FirstName,LastName,PhoneNumber,toAddresses",
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Chat. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
+
"description": "Specifies the list of attached data keys to be excluded in a email inline forward when the agent makes email inline forward.",
 +
"version": "9.0.000.98",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Name of a valid Script object of type Interaction Queue",
+
"data_type": "Comma-separated list of attached data keys.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,603: Line 2,845:
 
},
 
},
 
{
 
{
"id": "intercommunication.chat.routing-based-actions",
+
"id": "privilege.email.can-print",
"display_name": "Routing based actions for chat",
+
"display_name": "Can print email",
 
"type": "config",
 
"type": "config",
"default_value": "InitTransfer,OneStepTransfer",
+
"default_value": "false",
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
+
"description": "Enables agents to print email interactions from the My history and My Workbin views, and from the Contact History tabs of the Contact Directory, Interaction Search, and Interaction Detail views.",
 +
"version": "9.0.000.48",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid operation names from the following list: InitTransfer, OneStepTransfer, OneStepConference.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,616: Line 2,859:
 
},
 
},
 
{
 
{
"id": "intercommunication.chat.routing-based-targets",
+
"id": "privilege.email.can-move-to-workbin",
"display_name": "Routing based targets for chat",
+
"display_name": "Can move to workbin",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Defines the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.chat.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
+
"description": "Enables an agent to move email interactions to workbins.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,629: Line 2,873:
 
},
 
},
 
{
 
{
"id": "intercommunication.email.queue",
+
"id": "privilege.email.can-reply",
"display_name": "Routing Based Queue for email",
+
"display_name": "Can use reply",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for email. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
+
"description": "Enables an agent to reply to inbound email interactions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Name of a valid Script object of type Interaction Queue",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,642: Line 2,887:
 
},
 
},
 
{
 
{
"id": "intercommunication.email.routing-based-actions",
+
"id": "privilege.email.can-reply-all",
"display_name": "Routing based actions for email",
+
"display_name": "Can  reply all",
 
"type": "config",
 
"type": "config",
"default_value": "OneStepTransfer",
+
"default_value": "true",
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
+
"description": "Enables an agent to reply to all parties included in the distribution of inbound email interactions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,655: Line 2,901:
 
},
 
},
 
{
 
{
"id": "intercommunication.email.routing-based-targets",
+
"id": "privilege.email.can-send",
"display_name": "Routing based targets for email",
+
"display_name": "Can  send",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are specified in the 'intercommunication.email.routing-based-actions' option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
+
"description": "Enables an agent to send outgoing email interactions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,668: Line 2,915:
 
},
 
},
 
{
 
{
"id": "intercommunication.workitem.queue",
+
"id": "privilege.email.can-interim-send",
"display_name": "Routing Based Queue for workitem",
+
"display_name": "Can Interim send",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Workitem. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
+
"description": "Enables an agent to send interim outgoing email interactions.",
 +
"version": "9.0.000.34",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Name of a valid Script object of type Interaction Queue",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,681: Line 2,929:
 
},
 
},
 
{
 
{
"id": "intercommunication.workitem.routing-based-actions",
+
"id": "privilege.email.can-save",
"display_name": "Routing based actions for workitem",
+
"display_name": "Can  save",
 
"type": "config",
 
"type": "config",
"default_value": "OneStepTransfer",
+
"default_value": "true",
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
+
"description": "Enables an agent to save in-progress outgoing email interactions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,694: Line 2,943:
 
},
 
},
 
{
 
{
"id": "intercommunication.workitem.routing-based-targets",
+
"id": "privilege.email.can-add-attachment",
"display_name": "Routing based targets for workitem",
+
"display_name": "Can add attachment ",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are specified in the 'intercommunication.workitem.routing-based-actions' option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
+
"description": "Enables an agent to add attached files to outgoing emails.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,707: Line 2,957:
 
},
 
},
 
{
 
{
"id": "outbound.call-result-values",
+
"id": "privilege.email.can-delete",
"display_name": "Call result values",
+
"display_name": "Can delete",
 
"type": "config",
 
"type": "config",
"default_value": "Answered,AnsweringMachine,Busy,NoAnswer,WrongNumber",
+
"default_value": "true",
"description": "Specifies the list of call results that are available for the agent to use for an outbound interaction. The call results are displayed in the order in which they appear in the list.",
+
"description": "Enables an agent to delete outgoing email interactions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select at least one item from the list.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,720: Line 2,971:
 
},
 
},
 
{
 
{
"id": "outbound.call-result-automatically-selected",
+
"id": "privilege.email.can-one-step-transfer",
"display_name": "Call Result automatically selected",
+
"display_name": "Can use one step transfer",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the call result to be selected by default for outbound records. The specified call result must be defined by the values that are specified for the outbound.call-result-values option. If set to an empty value, the current call result of the outbound record is selected, or unknown is selected if there is no current value.",
+
"description": "Enables an agent to one-step transfer email interactions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any available call result value.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,733: Line 2,985:
 
},
 
},
 
{
 
{
"id": "outbound.preview.max-simultaneous-preview-record",
+
"id": "privilege.email.can-inline-forward",
"display_name": "Maximum number of simultaneous preview record",
+
"display_name": "Can use inline forward",
 
"type": "config",
 
"type": "config",
"default_value": "-1",
+
"default_value": "false",
"description": "Specifies the maximum number of simultaneous Outbound Preview records an agent can view in the interaction window. A 0 or a negative value indicates no limit.",
+
"description": "Enables agents to forward an email inline instead of as an attachment.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,746: Line 2,999:
 
},
 
},
 
{
 
{
"id": "outbound.treatment-mode",
+
"id": "privilege.email.can-delete-attachment-from-inbound",
"display_name": "Treatment Mode",
+
"display_name": "Can delete attachment for inbound email",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the type of treatment to be applied for the outbound record after it is marked as processed. If not set or set to 'none', no treatment is applied for the outbound record. This option can be overridden by a routing strategy as described in Configuration Guide.",
+
"description": "Enables agents to delete attachments from an inbound email interaction.",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "personal, campaign",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,759: Line 3,013:
 
},
 
},
 
{
 
{
"id": "outbound.negotiate-logout-on-exit",
+
"id": "privilege.email.embedded-images.can-use",
"display_name": "Negotiate Logout",
+
"display_name": "Can show embedded image",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Specifies whether negotiated logout with Outbound Server is enabled for Outbound campaigns. In negotiated logout, agents cannot log out of Workspace if they are the target of an outbound record or have an unclosed record. This option can be overridden by a routing strategy as described in Configuration Guide.",
+
"description": "Enables agents to view embedded images in email interactions.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,772: Line 3,027:
 
},
 
},
 
{
 
{
"id": "outbound.timed-preview-auto-dial",
+
"id": "privilege.email.embedded-images.can-add",
"display_name": "Outbound Timed Preview Auto Dial",
+
"display_name": "Can add embedded image",
 
"type": "config",
 
"type": "config",
"default_value": "-1",
+
"default_value": "false",
"description": "Specifies whether agents in Preview, Push preview, and Reschedule preview campaigns can manually dial a record, have the call auto-dialed as soon as the record is accepted, or have the call auto-dialed after a specified number of seconds. If set to 0, the interaction is dialed as soon as it is accepted. A value of -1 disables automatic dialing. This option can be overridden by a routing strategy as described in Configuration Guide.",
+
"description": "Enables agents to add embedded images in outgoing email interactions. Depends on the option privilege.email.embedded-images.can-use.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any integer greater than or equal to -1",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,785: Line 3,041:
 
},
 
},
 
{
 
{
"id": "outbound.callback-types",
+
"id": "privilege.email.can-insert-link",
"display_name": "Outbound Callback Types",
+
"display_name": "Can insert link",
 
"type": "config",
 
"type": "config",
"default_value": "Personal,Campaign",
+
"default_value": "true",
"description": "Specifies the list of callback types (Personal,Campaign) from which an agent can select when rescheduling an outbound record. This option can be overridden by a routing strategy as described in Configuration Guide.",
+
"description": "Enables agents to insert links in outgoing email interactions.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Personal,Campaign",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,798: Line 3,055:
 
},
 
},
 
{
 
{
"id": "outbound.call-result-is-mandatory",
+
"id": "intercommunication.voice.routing-points",
"display_name": "Outbound Call Result",
+
"display_name": "Routing Points for voice",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether it is mandatory for an agent to seelct a call result other than 'Unknown' before marking the interaction as done.",
+
"description": "Specifies the call number that is used by the Routing Base feature. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of call number names in the following format: &#36;dn_name@switch&#36;",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,811: Line 3,069:
 
},
 
},
 
{
 
{
"id": "outbound.agent-preview-mode",
+
"id": "intercommunication.voice.routing-based-actions",
"display_name": "Outbound Agent Preview Mode",
+
"display_name": "Routing based actions for voice",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer",
"description": "Specifies if Workspace sends PreviewDialingModeStart and PreviewDialingModeStop events to OCS for every campaign running in Preview mode.",
+
"description": "Specifies the list of Routing Based Actions that an agent may perform.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of valid operation names from the following list: MakeCall, OneStepTransfer, InitTransfer, InitConference, OneStepConference.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,824: Line 3,083:
 
},
 
},
 
{
 
{
"id": "outbound.direct-push-preview-toast.timeout",
+
"id": "intercommunication.voice.routing-based-targets",
"display_name": "Outbound Direct Push Preview Toast",
+
"display_name": "Routing based targets for voice",
 
"type": "config",
 
"type": "config",
"default_value": "20",
+
"default_value": "No default value",
"description": "Specifies the time duration in seconds for which Workspace waits for the agent to accept/reject a toast for a Direct Push Preview interaction before automatically removing the toast and rejecting the record and telling OCS to send a new one.",
+
"description": "Specifies the list of targets that are contacted through the routing based mechanism for the requests that are defined by the intercommunication.voice.routing-based-actions option. Note: The targets AgentGroup and Skill are always addressed through routing; therefore, they are not affected by this option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A integer from 5 through 60",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, RoutingPoint, ACDQueue, TypeDestination, OutboundRecord, Contact",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,837: Line 3,097:
 
},
 
},
 
{
 
{
"id": "outbound.direct-push-preview.no-record-timeout",
+
"id": "intercommunication.voice.make-call-caller-id-business-attribute",
"display_name": "Outbound Direct Push Preview Timeout",
+
"display_name": "Make call caller-id business attribute",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "No default value",
"description": "Specifies the duration, in seconds, for which Workspace, after having sent a Preview Mode Start request, waits for OCS to send a Direct Push Preview record before displaying a toast to the agent informing them that there are no more records in the current campaign.",
+
"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as outbound caller IDs. This option is only applicable for external calls.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A integer from 10 through 60",
+
"data_type": "Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,850: Line 3,111:
 
},
 
},
 
{
 
{
"id": "outbound.push-preview-mode",
+
"id": "intercommunication.voice.make-call-caller-id-enable-anonymous",
"display_name": "Outbound Push Preview Mode",
+
"display_name": "Enable Anonymous on Make Call Caller-ID",
 
"type": "config",
 
"type": "config",
"default_value": "regular",
+
"default_value": "false",
"description": "Specifies whether Outbound Push Preview camapigns are running in regular or direct mode. In direct mode, OCS communicates directly with Workspace instead of utilizing Interaction Server to handle interactions. This means that there is no automatic agent state control.",
+
"description": "Specifies whether anonymous is enabled on make call with caller id. This option is only applicable for external calls. This functionality can currently only be used in conjunction with the SIP Server TServer\\/enforce-p-asserted-identity option configured on the outbound PSTN Trunk DN. This must be configured in the environment where the PSTN Provider (Carrier) implements Calling Line Identification Restriction (CLIR) and allows masking the displayed number (Caller ID) only if privacy SIP headers are correctly constructed and 'anonymous@anonymous.invalid' is specified in the From field.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "One of either regular or direct",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,863: Line 3,125:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-use",
+
"id": "voice.caller-id.key-name",
"display_name": "Can use",
+
"display_name": "Attached Data Key for Caller Id",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "IW_SelectedCallerId",
"description": "Enables access to the Outbound Campaign functions.",
+
"description": "Specifies the key name of the attached data that contains the selected caller id information.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An attached data key name (string)",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,876: Line 3,139:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.push-preview.can-use",
+
"id": "intercommunication.voice.single-step-conference-enabled",
"display_name": "Push Preview can use",
+
"display_name": "Single Step Conference enabled for voice",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
"description": "Enables access to the Push Preview Outbound Campaign functions.",
+
"description": "Specifies the list of targets enabled in Team Communication for a single step conference.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,889: Line 3,153:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-mark-do-not-call",
+
"id": "intercommunication.voice.single-step-transfer-enabled",
"display_name": "Can Mark Do Not Call",
+
"display_name": "Single Step Transfer enabled for voice",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
"description": "Enables an agent to mark a contact as Do Not Call.",
+
"description": "Specifies the list of targets enabled in Team Communication for a single step transfer.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,902: Line 3,167:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-set-call-result",
+
"id": "intercommunication.voice.consultation-enabled",
"display_name": "Can Set Call Result",
+
"display_name": "Consultation enabled for voice",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
"description": "Enables an agent to set a call result to the outbound record.",
+
"description": "Specifies the list of targets enabled in Team Communication for a consultation.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,915: Line 3,181:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-reject-record",
+
"id": "intercommunication.voice.make-call-enabled",
"display_name": "Can Reject Record",
+
"display_name": "Make Call enabled",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
"description": "Enables an agent to decline a preview record. If an agent declines a preview record, it can be processed by another agent in the campaign.",
+
"description": "Specifies the list of targets enabled in Team Communication for making call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,928: Line 3,195:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-cancel-record",
+
"id": "intercommunication.chat.queue",
"display_name": "Can Cancel Record",
+
"display_name": "Routing Based Queue for chat",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to cancel a preview record. If an agent cancels a preview record, it is not processed again during the current campaign.",
+
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Chat. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Name of a valid Script object of type Interaction Queue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,941: Line 3,209:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-dial-on-new-number",
+
"id": "intercommunication.chat.routing-based-actions",
"display_name": "an Dial On New Number for outbound",
+
"display_name": "Routing based actions for chat",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "InitTransfer,OneStepTransfer",
"description": "Enables agents to dial an outbound contact on a new number, resulting in a new record added to the chain. Depends on 'Outbound - Can Use' and 'Can Dial Alternative Chained Record'.",
+
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of valid operation names from the following list: InitTransfer, OneStepTransfer, OneStepConference.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,954: Line 3,223:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-dial-alternative-chained-record",
+
"id": "intercommunication.chat.routing-based-targets",
"display_name": "Can Dial Alternative Chained Record",
+
"display_name": "Routing based targets for chat",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to dial a number from the preview record chain that is different than the number selected by the system.",
+
"description": "Defines the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.chat.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,967: Line 3,237:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-get-next-preview-record",
+
"id": "intercommunication.email.queue",
"display_name": "Get Next Preview Record",
+
"display_name": "Routing Based Queue for email",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to request a new preview record while processing of the previous preview record terminates.",
+
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for email. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Name of a valid Script object of type Interaction Queue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,980: Line 3,251:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-reschedule",
+
"id": "intercommunication.email.routing-based-actions",
"display_name": "Can Reschedule",
+
"display_name": "Routing based actions for email",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "OneStepTransfer",
"description": "Enables an agent to reschedule an outbound record for an active call. Use the privilege.outbound.can-reschedule-before-call privilege to allow rescheduling before the call is dialed.",
+
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 2,993: Line 3,265:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-reschedule-before-call",
+
"id": "intercommunication.email.routing-based-targets",
"display_name": "Can Reschedule Before Call",
+
"display_name": "Routing based targets for email",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to reschedule an outbound record before calling the contact.",
+
"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are specified in the 'intercommunication.email.routing-based-actions' option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,006: Line 3,279:
 
},
 
},
 
{
 
{
"id": "privilege.outbound.can-reschedule-on-new-number",
+
"id": "intercommunication.workitem.queue",
"display_name": "Can Reschedule On New Number",
+
"display_name": "Routing Based Queue for workitem",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to reschedule an outbound record on a new number (which adds a new record to the chain).",
+
"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Workitem. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Name of a valid Script object of type Interaction Queue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,019: Line 3,293:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-make-call",
+
"id": "intercommunication.workitem.routing-based-actions",
"display_name": "Can Make Call",
+
"display_name": "Routing based actions for workitem",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "OneStepTransfer",
"description": "Enables an agent to make a new voice call from any area enabling voice calls.",
+
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,032: Line 3,307:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-answer-call",
+
"id": "intercommunication.workitem.routing-based-targets",
"display_name": "Can Answer Call",
+
"display_name": "Routing based targets for workitem",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to manually answer an incoming voice call. Setting this option to false hides the Accept button in the Interaction notification pop-up.",
+
"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are specified in the 'intercommunication.workitem.routing-based-actions' option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,045: Line 3,321:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-release-call",
+
"id": "outbound.call-result-values",
"display_name": "Can Release Call",
+
"display_name": "Call result values",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Answered,AnsweringMachine,Busy,NoAnswer,WrongNumber",
"description": "Enables agents to manually end voice calls.",
+
"description": "Specifies the list of call results that are available for the agent to use for an outbound interaction. The call results are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Select at least one item from the list.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,058: Line 3,335:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-release-a-held-call",
+
"id": "outbound.call-result-automatically-selected",
"display_name": "Can Release Held Call",
+
"display_name": "Call Result automatically selected",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables agents to manually end voice calls in held state.",
+
"description": "Specifies the call result to be selected by default for outbound records. The specified call result must be defined by the values that are specified for the outbound.call-result-values option. If set to an empty value, the current call result of the outbound record is selected, or unknown is selected if there is no current value.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any available call result value.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,071: Line 3,349:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-hold-retrieve-call",
+
"id": "outbound.preview.max-simultaneous-preview-record",
"display_name": "Can Hold/Retrieve Call",
+
"display_name": "Maximum number of simultaneous preview record",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "-1",
"description": "Enables and agent to hold or retrieve a voice call.",
+
"description": "Specifies the maximum number of simultaneous Outbound Preview records an agent can view in the interaction window. A 0 or a negative value indicates no limit.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,084: Line 3,363:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-one-step-conference",
+
"id": "outbound.treatment-mode",
"display_name": "Can One Step Conference",
+
"display_name": "Treatment Mode",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables instant conferencing of a voice call.",
+
"description": "Specifies the type of treatment to be applied for the outbound record after it is marked as processed. If not set or set to 'none', no treatment is applied for the outbound record. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "personal, campaign",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,097: Line 3,377:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-one-step-transfer",
+
"id": "outbound.negotiate-logout-on-exit",
"display_name": "Can One Step Transfer",
+
"display_name": "Negotiate Logout",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables instant conferencing of a voice call.",
+
"description": "Specifies whether negotiated logout with Outbound Server is enabled for Outbound campaigns. In negotiated logout, agents cannot log out of Workspace if they are the target of an outbound record or have an unclosed record. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.38",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,110: Line 3,391:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-two-step-conference",
+
"id": "outbound.timed-preview-auto-dial",
"display_name": "Can Two Step Conference",
+
"display_name": "Outbound Timed Preview Auto Dial",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "-1",
"description": "Enables two-step conference for voice calls.",
+
"description": "Specifies whether agents in Preview, Push preview, and Reschedule preview campaigns can manually dial a record, have the call auto-dialed as soon as the record is accepted, or have the call auto-dialed after a specified number of seconds. If set to 0, the interaction is dialed as soon as it is accepted. A value of -1 disables automatic dialing. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.48",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any integer greater than or equal to -1",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,123: Line 3,405:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-set-interaction-disposition",
+
"id": "outbound.callback-types",
"display_name": "Can Set Interaction Disposition",
+
"display_name": "Outbound Callback Types",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Personal,Campaign",
"description": "Enables an agent to set the disposition code on voice interactions.",
+
"description": "Specifies the list of callback types (Personal,Campaign) from which an agent can select when rescheduling an outbound record. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.42",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Personal,Campaign",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,136: Line 3,419:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-two-step-transfer",
+
"id": "outbound.call-result-is-mandatory",
"display_name": "Can Two Step Transfer",
+
"display_name": "Outbound Call Result",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables two-step transfer of a voice call.",
+
"description": "Specifies whether it is mandatory for an agent to seelct a call result other than 'Unknown' before marking the interaction as done.",
 +
"version": "9.0.000.51",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,149: Line 3,433:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-forward",
+
"id": "outbound.agent-preview-mode",
"display_name": "Can forward",
+
"display_name": "Outbound Agent Preview Mode",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to forward voice calls.",
+
"description": "Specifies if Workspace sends PreviewDialingModeStart and PreviewDialingModeStop events to OCS for every campaign running in Preview mode.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,162: Line 3,447:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-reject-call",
+
"id": "outbound.direct-push-preview-toast.timeout",
"display_name": "Can Reject Call",
+
"display_name": "Outbound Direct Push Preview Toast",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "20",
"description": "Enables an agent to reject an incoming voice call.",
+
"description": "Specifies the time duration in seconds for which Workspace waits for the agent to accept/reject a toast for a Direct Push Preview interaction before automatically removing the toast and rejecting the record and telling OCS to send a new one.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A integer from 5 through 60",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,175: Line 3,461:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-extend-after-call-work",
+
"id": "outbound.direct-push-preview.no-record-timeout",
"display_name": "Can Extend the After Call Work",
+
"display_name": "Outbound Direct Push Preview Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "10",
"description": "Enables an agent to extend the After Call Work state.",
+
"description": "Specifies the duration, in seconds, for which Workspace, after having sent a Preview Mode Start request, waits for OCS to send a Direct Push Preview record before displaying a toast to the agent informing them that there are no more records in the current campaign.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A integer from 10 through 60",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,188: Line 3,475:
 
},
 
},
 
{
 
{
"id": "privilege.voice.make-call.can-use-caller-id",
+
"id": "outbound.push-preview-mode",
"display_name": "Can Use Caller Id - Make Call",
+
"display_name": "Outbound Push Preview Mode",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "regular",
"description": "Enables agents to use caller ID for making calls.",
+
"description": "Specifies whether Outbound Push Preview camapigns are running in regular or direct mode. In direct mode, OCS communicates directly with Workspace instead of utilizing Interaction Server to handle interactions. This means that there is no automatic agent state control.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "One of either regular or direct",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,201: Line 3,489:
 
},
 
},
 
{
 
{
"id": "voice.use-caller-id-display-name",
+
"id": "outbound.dispositions-allowing-treatment-on-reschedule",
"display_name": "Use Caller Id Display Name",
+
"display_name": "Outbound Treatment on Reschedule",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies that the Caller Id Display Name is to be used when caller id is used. This feature requires that the value of the SIP Server TServer/use-display-name option be set to true. The Caller Id Display Name should be the display name of the caller ID in business attribute value specified by the intercommunication.voice.make-call-caller-id-business-attribute option.",
+
"description": "Specifies the list of disposition codes that, if at least one is selected by an agent when handling and Outbound call, causes the treatment specified by the outbound-treatment-mode option to be sent to OCS when the interaction is marked Done after it is rescheduled. This option can be overridden by a routing strategy as described in Configuration Guide.",
 +
"version": "9.0.000.73",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Comma seperated list of valid disposition codes",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,214: Line 3,503:
 
},
 
},
 
{
 
{
"id": "privilege.voice.single-step-conference.can-use-caller-id",
+
"id": "privilege.outbound.can-use",
"display_name": "Can Use Caller Id - Single Step Conference",
+
"display_name": "Can use",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to use caller ID for single-step conferences.",
+
"description": "Enables access to the Outbound Campaign functions.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,227: Line 3,517:
 
},
 
},
 
{
 
{
"id": "privilege.voice.single-step-transfer.can-use-caller-id",
+
"id": "privilege.outbound.push-preview.can-use",
"display_name": "Can Use Caller Id - Single Step Transfer",
+
"display_name": "Push Preview can use",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to use caller ID for single-step transfers.",
+
"description": "Enables access to the Push Preview Outbound Campaign functions.",
 +
"version": "9.0.000.26",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,240: Line 3,531:
 
},
 
},
 
{
 
{
"id": "privilege.voice.consultation.can-use-caller-id",
+
"id": "privilege.outbound.can-mark-do-not-call",
"display_name": "Can Use Caller Id - Consultation",
+
"display_name": "Can Mark Do Not Call",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to use caller ID for consultations.",
+
"description": "Enables an agent to mark a contact as Do Not Call.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,253: Line 3,545:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-show-hold-duration",
+
"id": "privilege.outbound.can-set-call-result",
"display_name": "Can Show Hold Duration",
+
"display_name": "Can Set Call Result",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to see the amount of time that a voice call has been on hold.",
+
"description": "Enables an agent to set a call result to the outbound record.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,266: Line 3,559:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-show-post-call-duration",
+
"id": "privilege.outbound.can-reject-record",
"display_name": "Can Show Post Call Duration",
+
"display_name": "Can Reject Record",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to see the post call duration in the tooltip and in the interaction bar of a voice call.",
+
"description": "Enables an agent to decline a preview record. If an agent declines a preview record, it can be processed by another agent in the campaign.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,279: Line 3,573:
 
},
 
},
 
{
 
{
"id": "voice.hold-indicator-timer",
+
"id": "privilege.outbound.can-cancel-record",
"display_name": "Hold Indicator Timer",
+
"display_name": "Can Cancel Record",
 
"type": "config",
 
"type": "config",
"default_value": "30,60",
+
"default_value": "true",
"description": "Specifies two alarm thresholds, in seconds, that warn agents that a voice call is on hold for a long time. Three levels are displayed: before the warning time, between the warning time and the maximum time, and after the maximum time.",
+
"description": "Enables an agent to cancel a preview record. If an agent cancels a preview record, it is not processed again during the current campaign.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list value: warning time, maximum time",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,292: Line 3,587:
 
},
 
},
 
{
 
{
"id": "voice.restore-state-on-back-in-service.is-enabled",
+
"id": "privilege.outbound.can-dial-on-new-number",
"display_name": "State restoring on back in service",
+
"display_name": "an Dial On New Number for outbound",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "If voice channel goes Out of Service, this option specifies whether Workspace should attempt to automatically set the voice channel back to its previous state when it is back in service.",
+
"description": "Enables agents to dial an outbound contact on a new number, resulting in a new record added to the chain. Depends on 'Outbound - Can Use' and 'Can Dial Alternative Chained Record'.",
 +
"version": "9.0.000.68",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,305: Line 3,601:
 
},
 
},
 
{
 
{
"id": "voice.restore-state-on-back-in-service.time",
+
"id": "privilege.outbound.can-dial-alternative-chained-record",
"display_name": "State restoring on back in service time",
+
"display_name": "Can Dial Alternative Chained Record",
 
"type": "config",
 
"type": "config",
"default_value": "3",
+
"default_value": "true",
"description": "If voice channel goes Out of Service and the value of the voice.restore-state-on-back-in-service.is-enabled option is true, this option specifies the amount of time, in seconds, to set channel back to its previous state when it is back in service.",
+
"description": "Enables an agent to dial a number from the preview record chain that is different than the number selected by the system.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer from 0 through 10.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,318: Line 3,615:
 
},
 
},
 
{
 
{
"id": "voice.dial-plan-rule-<rule-name>",
+
"id": "privilege.outbound.can-get-next-preview-record",
"display_name": "Dial Plan rule",
+
"display_name": "Get Next Preview Record",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the rules that are used to transform destination numbers into the requested format before being dialed",
+
"description": "Enables an agent to request a new preview record while processing of the previous preview record terminates.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A rule in the format: pattern => digit translation #comment",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,331: Line 3,629:
 
},
 
},
 
{
 
{
"id": "standard-response.categories",
+
"id": "privilege.outbound.can-reschedule",
"display_name": "Categories to display from Standard Response Library",
+
"display_name": "Can Reschedule",
 
"type": "config",
 
"type": "config",
"default_value": "&#36;All&#36;",
+
"default_value": "false",
"description": "Specifies the list of categories used to filter Standard Responses. Agents see only those Standard Responses that are part of the sub-tree of categories set in the value for this option.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Enables an agent to reschedule an outbound record for an active call. Use the privilege.outbound.can-reschedule-before-call privilege to allow rescheduling before the call is dialed.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of category names or full path category starting at the root category. &#36;All&#36; to display Standard Responses from all categories.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,344: Line 3,643:
 
},
 
},
 
{
 
{
"id": "standard-response.field.<CustomFieldCode>",
+
"id": "privilege.outbound.can-reschedule-before-call",
"display_name": "Field to display from Standard Response Library",
+
"display_name": "Can Reschedule Before Call",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "In the name of the option, CustomFieldCode represents a field code that is called in a Standard Response object created in eServices Manager and stored in Universal Contact Server. Use this option to specify a custom field code such as a role, department, or other qualification. The value of the option is specific to the agent, agent group, tenant, or application. The value of this option represents the data that is used to populate the corresponding field codes when a Standard Response is inserted into an interaction. You can format CustomFieldCode to represent a custom agent attribute. Example: standard-response.field.Department = Sales",
+
"description": "Enables an agent to reschedule an outbound record before calling the contact.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid text string.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,357: Line 3,657:
 
},
 
},
 
{
 
{
"id": "standard-response.field.Agent.<CustomFieldCode>",
+
"id": "privilege.outbound.can-reschedule-on-new-number",
"display_name": "Field to display from Standard Response Library",
+
"display_name": "Can Reschedule On New Number",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "In the name of the option, CustomFieldCode represents a field code that is called in a Standard Response object created in eServices Manager and stored in Universal Contact Server. Use this option to specify a custom field code such as an agent nickname, role, department, or other qualification. The value of the option is specific to the agent, agent group, tenant, or application. The value of this option represents the data that is used to populate the corresponding field codes when a Standard Response is inserted into an interaction. You can format CustomFieldCode to represent a custom agent attribute. Example: standard-response.field.Agent.Nickname = Lee",
+
"description": "Enables an agent to reschedule an outbound record on a new number (which adds a new record to the chain).",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid text string.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,370: Line 3,671:
 
},
 
},
 
{
 
{
"id": "standard-response.shortcuts.<keyword>",
+
"id": "privilege.outbound.record-information.can-view",
"display_name": "Standard Response shortcut keyword template",
+
"display_name": "Outbound Record Information",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the 'keyword' for a shortcut where the name of the option represents the keyword to be entered by agents to use the shortcut. For example: 'standard-response.shortcuts.JulySale'. Specify the path to the Response that is defined in Knowledge Manager as the value for this option. For example '2021Specials\\JulySale'.",
+
"description": "Enables agents to view the Record Information area in an Outbound Record.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Path to the standard response as defined in the Knowledge Manager.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,383: Line 3,685:
 
},
 
},
 
{
 
{
"id": "privilege.standard-response.shortcuts.can-use",
+
"id": "privilege.outbound.record-information.can-update",
"display_name": "Enable shortcuts for Standard Responses",
+
"display_name": "Outbound Record Information",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to use shortcuts to insert Standard Responses.",
+
"description": "Enables agents to edit or update fields in the Record Information area of an Outbound Record that are configured as editable. If this privilege is present, then the value of the privilege.outbound.record-information.can-view privilege is implicitly considered to be set to true.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,396: Line 3,699:
 
},
 
},
 
{
 
{
"id": "privilege.standard-response.shortcuts.can-filter",
+
"id": "privilege.voice.can-make-call",
"display_name": "Filter Standard Responses with shortcuts",
+
"display_name": "Can Make Call",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to filter Standard Responses in the Standard Responses tree view to show only those with shortcuts.",
+
"description": "Enables an agent to make a new voice call from any area enabling voice calls.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,409: Line 3,713:
 
},
 
},
 
{
 
{
"id": "privilege.standard-response.favorites.can-use",
+
"id": "privilege.voice.can-answer-call",
"display_name": "Enable favorite Standard Response",
+
"display_name": "Can Answer Call",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables agents to use favorites for Standard Responses.",
+
"description": "Enables an agent to manually answer an incoming voice call. Setting this option to false hides the Accept button in the Interaction notification pop-up.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,422: Line 3,727:
 
},
 
},
 
{
 
{
"id": "privilege.SRL.can-use",
+
"id": "privilege.voice.can-release-call",
"display_name": "Can Use",
+
"display_name": "Can Release Call",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables access to the Standard Response Library functions.",
+
"description": "Enables agents to manually end voice calls.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,435: Line 3,741:
 
},
 
},
 
{
 
{
"id": "privilege.SRL.can-quick-search",
+
"id": "privilege.voice.can-release-a-held-call",
"display_name": "Can do Quick Search",
+
"display_name": "Can Release Held Call",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables an agent to perform a Quick Search of the Standard Response Library.",
+
"description": "Enables agents to manually end voice calls in held state.",
 +
"version": "9.0.000.27",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,448: Line 3,755:
 
},
 
},
 
{
 
{
"id": "privilege.voicemail.can-use",
+
"id": "privilege.voice.can-hold-retrieve-call",
"display_name": "Can Use",
+
"display_name": "Can Hold/Retrieve Call",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enalbes agents to use the voicemail functionality. This privilege is required to control and monitor voicemail boxes.",
+
"description": "Enables and agent to hold or retrieve a voice call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,461: Line 3,769:
 
},
 
},
 
{
 
{
"id": "voicemail.access-number",
+
"id": "privilege.voice.can-one-step-conference",
"display_name": "Voice Mail Directory Number",
+
"display_name": "Can One Step Conference",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the number to call to access your voicemail system.",
+
"description": "Enables instant conferencing of a voice call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any Valid DN",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,474: Line 3,783:
 
},
 
},
 
{
 
{
"id": "voicemail.notification-types",
+
"id": "privilege.voice.can-one-step-transfer",
"display_name": "Types of displayed mailboxes",
+
"display_name": "Can One Step Transfer",
 
"type": "config",
 
"type": "config",
"default_value": "personal, public",
+
"default_value": "true",
"description": "Specifies the types of voicemail boxes included in the count of unread voicemail messages in the Main Window. personal refers to the voicemail box that is identified as the personal voicemail box of the agent; public refers to the group voicemail boxes to which the agent has access.",
+
"description": "Enables instant conferencing of a voice call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of action names from the following list: personal, public",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,487: Line 3,797:
 
},
 
},
 
{
 
{
"id": "voicemail.request-timeout",
+
"id": "privilege.voice.can-two-step-conference",
"display_name": "Request timeout",
+
"display_name": "Can Two Step Conference",
 
"type": "config",
 
"type": "config",
"default_value": "1",
+
"default_value": "true",
"description": "Specifies the time, in seconds, to wait for voicemail messages from Feature Server. If no voicemail messages are received during this timeout, a request is sent to Feature Server to get them.",
+
"description": "Enables two-step conference for voice calls.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,500: Line 3,811:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.actions.display-mode",
+
"id": "privilege.voice.can-set-interaction-disposition",
"display_name": "Action display mode",
+
"display_name": "Can Set Interaction Disposition",
 
"type": "config",
 
"type": "config",
"default_value": "hover",
+
"default_value": "true",
"description": "Specifies the display mode for Team Communicator action buttons.",
+
"description": "Enables an agent to set the disposition code on voice interactions.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: hover (actions appear only on mouseover on related entry), block (expose a default action button for all entries).",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,513: Line 3,825:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.<media-type>.list-status-reachable",
+
"id": "privilege.voice.can-two-step-transfer",
"display_name": "List of reachable status for voice call",
+
"display_name": "Can Two Step Transfer",
 
"type": "config",
 
"type": "config",
"default_value": "NotReady",
+
"default_value": "true",
"description": "Specifies the list of unavailable statuses for which a target agent can be contacted for consultation, transfer, and conference requests. If the unavailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.",
+
"description": "Enables two-step transfer of a voice call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,526: Line 3,839:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.voice.list-status-reachable",
+
"id": "privilege.voice.can-forward",
"display_name": "List of reachable status for voice call",
+
"display_name": "Can forward",
 
"type": "config",
 
"type": "config",
"default_value": "NotReady",
+
"default_value": "true",
"description": "Specifies the list of unavailable statuses for which a target agent can be contacted for consultation, transfer, and conference requests. If the unavailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.",
+
"description": "Enables an agent to forward voice calls.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,539: Line 3,853:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.email.list-status-reachable",
+
"id": "privilege.voice.can-reject-call",
"display_name": "List of reachable status for email",
+
"display_name": "Can Reject Call",
 
"type": "config",
 
"type": "config",
"default_value": "NotReady",
+
"default_value": "true",
"description": "Specifies the list of unvailable statuses for which a target agent can be contacted for transfer requests. If the unvailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for transfer requests. Depends on 'Email - Can Use Email Channel' and 'TeamCommunicator - Evaluate Presence'.",
+
"description": "Enables an agent to reject an incoming voice call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,552: Line 3,867:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.chat.list-status-reachable",
+
"id": "privilege.voice.can-extend-after-call-work",
"display_name": "List of reachable status for chat",
+
"display_name": "Can Extend the After Call Work",
 
"type": "config",
 
"type": "config",
"default_value": "NotReady",
+
"default_value": "false",
"description": "Specifies the list of unvailable statuses for which a target agent can be contacted for consultation, transfer, and conference, requests. If the unvailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests. Depends on 'Chat - Can Use Chat Channel' and 'TeamCommunicator - Evaluate Presence'.",
+
"description": "Enables an agent to extend the After Call Work state.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,565: Line 3,881:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.load-at-startup",
+
"id": "privilege.voice.make-call.can-use-caller-id",
"display_name": "Load Elements at startup",
+
"display_name": "Can Use Caller Id - Make Call",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Specifies whether all the configuration elements (Agents, Agent Groups, Queues, Routing Points, Skills) needed by Team Communicator are loaded at login. This option is used to help with performance at login if many agents login at the same time. When this option is set to false, the elements are not loaded at login, they are loaded the first time the focus is placed in the Team Communicator.",
+
"description": "Enables agents to use caller ID for making calls.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,578: Line 3,895:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.routing-point-presence-metrics",
+
"id": "voice.use-caller-id-display-name",
"display_name": "Routing Point Presence Metrics",
+
"display_name": "Use Caller Id Display Name",
 
"type": "config",
 
"type": "config",
"default_value": "routing-point-presence",
+
"default_value": "false",
"description": "Specifies a list of routing point presence sections. Each of these sections contains a valid statistic name related to the routing point, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.",
+
"description": "Specifies that the Caller Id Display Name is to be used when caller id is used. This feature requires that the value of the SIP Server TServer/use-display-name option be set to true. The Caller Id Display Name should be the display name of the caller ID in business attribute value specified by the intercommunication.voice.make-call-caller-id-business-attribute option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma separated value list of routing point presence options section names.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,591: Line 3,909:
 
},
 
},
 
{
 
{
"id": "presence.evaluate-presence",
+
"id": "privilege.voice.single-step-conference.can-use-caller-id",
"display_name": "Evaluate Presence",
+
"display_name": "Can Use Caller Id - Single Step Conference",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether the presence (availability) of agents, agent groups and Routing Points (when configured) is shown in Team Communicator in the search results.",
+
"description": "Enables agents to use caller ID for single-step conferences.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,604: Line 3,923:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.always-clear-textbox-on-new-interaction",
+
"id": "privilege.voice.single-step-transfer.can-use-caller-id",
"display_name": "always clear textbox on new interaction",
+
"display_name": "Can Use Caller Id - Single Step Transfer",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether the Team Communicator text search box is cleared after the interaction is initiated when the agent presses 'Enter' or clicks one of the medias in the Team Communicator results. When set to false, the Team Communicator text search box is cleared only if an interaction is initiated by the agent pressing 'Enter'.",
+
"description": "Enables agents to use caller ID for single-step transfers.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,617: Line 3,937:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.list-filter-showing",
+
"id": "privilege.voice.consultation.can-use-caller-id",
"display_name": "Displayed Object Types",
+
"display_name": "Can Use Caller Id - Consultation",
 
"type": "config",
 
"type": "config",
"default_value": "Agent,AgentGroup,RoutingPoint,Skill,InteractionQueue,Contact,CustomContact",
+
"default_value": "false",
"description": "Specifies the list of filters that an agent can use to search for contacts and internal targets by using the team communicator. The object types are presented in the specified order.",
+
"description": "Enables agents to use caller ID for consultations.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of filter items to be displayed in the team communicator, for example: Agent,AgentGroup,RoutingPoint,Skill,Contact,InteractionQueue,CustomContact.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,630: Line 3,951:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.max-suggestion-size",
+
"id": "privilege.voice.can-show-hold-duration",
"display_name": "Max suggestion size",
+
"display_name": "Can Show Hold Duration",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "false",
"description": "Specifies the maximum size of the suggestion list that is displayed while an agent is entering a contact or target name.",
+
"description": "Enables agents to see the amount of time that a voice call has been on hold.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 1 through 50.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,643: Line 3,965:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.recent-max-records",
+
"id": "privilege.voice.can-show-post-call-duration",
"display_name": "Maximum Recent Records",
+
"display_name": "Can Show Post Call Duration",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "false",
"description": "Specifies the number of recent internal targets to display in the list of recent targets.",
+
"description": "Enables agents to see the post call duration in the tooltip and in the interaction bar of a voice call.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 1 through 50.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,656: Line 3,979:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.max-favorites-size",
+
"id": "voice.hold-indicator-timer",
"display_name": "Max favorites size",
+
"display_name": "Hold Indicator Timer",
 
"type": "config",
 
"type": "config",
"default_value": "50",
+
"default_value": "30,60",
"description": "Specifies the maximum size of the favorites list that is displayed while an agent is displaying favorites.",
+
"description": "Specifies two alarm thresholds, in seconds, that warn agents that a voice call is on hold for a long time. Three levels are displayed: before the warning time, between the warning time and the maximum time, and after the maximum time.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 0 through 100.",
+
"data_type": "A comma-separated list value: warning time, maximum time",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,669: Line 3,993:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.max-size",
+
"id": "voice.restore-state-on-back-in-service.is-enabled",
"display_name": "Max size",
+
"display_name": "State restoring on back in service",
 
"type": "config",
 
"type": "config",
"default_value": "50",
+
"default_value": "false",
"description": "Specifies the maximum size of the default list when the value of teamcommunicator.show-all-internal-targets is set to true.",
+
"description": "If voice channel goes Out of Service, this option specifies whether Workspace should attempt to automatically set the voice channel back to its previous state when it is back in service.",
 +
"version": "9.0.000.50",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 0 through 100.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,682: Line 4,007:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.show-all-internal-targets",
+
"id": "voice.restore-state-on-back-in-service.time",
"display_name": "Show all internal targets",
+
"display_name": "State restoring on back in service time",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "3",
"description": "Specifies whether all internal targets are displayed by default in the Team Communicator when an agent is searching for a transfer or conference target, including all Agents, Agent Groups, Skills, and Routing Points.",
+
"description": "If voice channel goes Out of Service and the value of the voice.restore-state-on-back-in-service.is-enabled option is true, this option specifies the amount of time, in seconds, to set channel back to its previous state when it is back in service.",
 +
"version": "9.0.000.50",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 0 through 10.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,695: Line 4,021:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.corporate-favorites",
+
"id": "voice.dial-plan-rule-<rule-name>",
"display_name": "Corporate Favorite List",
+
"display_name": "Dial Plan rule",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the list of corporate favorites (quick dial favorites) that are configured in the Configuration Server for an Agent, Agent Group, Skill, Routing Point, or Custom Contact. See the procedure 'Creating Corporate Favorites' in the Configuration Guide for information about creating Corporate Favorite objects in the configuration layer. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the rules that are used to transform destination numbers into the requested format before being dialed. Also overrides for Routing Points, caller id business attribute and enabling of anonymous caller id can be set as parameters. For details, refer to https://docs.genesys.com/Options:Genesys_Web_Services:interaction-workspace:voice-dial-plan-rule-zrule-name-",
 +
"version": "9.0.000.61",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of favorite names (section names) that are defined in the Workspace application.",
+
"data_type": "A rule in the format: pattern => digit translation[;parameters...]#comment",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,708: Line 4,035:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.request-start-timer",
+
"id": "voice.dial-plan.types-enabled",
"display_name": "Request start timer",
+
"display_name": "Enabled Dial Plan Types",
 
"type": "config",
 
"type": "config",
"default_value": "500",
+
"default_value": "Contact, TypeDestination",
"description": "Specifies the request start timer wait interval, in milliseconds, between the last key pressed and the beginning of the search through the contact database.",
+
"description": "Specifies the list of targets to which the dial plan is applied. Valid targets include Agent, RoutingPoint, Contact, and TypeDestination objects.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 1 through 5000.",
+
"data_type": "A comma-separated list of target types",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,721: Line 4,049:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.add-recent-filters.voice",
+
"id": "voice.dial-plan-can-set-intercommunication-options",
"display_name": "Incoming interaction filter (Voice)",
+
"display_name": "Dial Plan rule",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies whether to store incoming interactions into the Recent buffer. By default, the Recent buffer stores only the actions of the agent, such as recent outbound voice calls. If one or more of the valid values is specified, then recent inbound interactions of that type are also stored in the Recent buffer. This enables agents to see a record of missed calls of the specified type(s).",
+
"description": "Specifies whether dial plan rules are extended to configure routing points, caller id business attributes, and anonymous caller id configurations specific to the dialed number.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of interaction types taken from the following values: internal, external, consultation.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,734: Line 4,063:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.voice.make-call.exclude-numbers",
+
"id": "standard-response.categories",
"display_name": "Phone Numbers to exclude from Make Call action in Team Communicator",
+
"display_name": "Categories to display from Standard Response Library",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "&#36;All&#36;",
"description": "Specifies the format for a phone number to exclude on making a call. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
+
"description": "Specifies the list of categories used to filter Standard Responses. Agents see only those Standard Responses that are part of the sub-tree of categories set in the value for this option.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression.",
+
"data_type": "A comma-separated value list of category names or full path category starting at the root category. &#36;All&#36; to display Standard Responses from all categories.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,747: Line 4,077:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.voice.single-step-transfer.exclude-numbers",
+
"id": "standard-response.field.<CustomFieldCode>",
"display_name": "Phone Numbers to exclude from Single Step Transfer action in Team Communicator",
+
"display_name": "Field to display from Standard Response Library",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the format for a phone number to exclude on single-step transfer. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
+
"description": "In the name of the option, CustomFieldCode represents a field code that is called in a Standard Response object created in eServices Manager and stored in Universal Contact Server. Use this option to specify a custom field code such as a role, department, or other qualification. The value of the option is specific to the agent, agent group, tenant, or application. The value of this option represents the data that is used to populate the corresponding field codes when a Standard Response is inserted into an interaction. You can format CustomFieldCode to represent a custom agent attribute. Example: standard-response.field.Department = Sales",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression.",
+
"data_type": "Any valid text string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,760: Line 4,091:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.voice.single-step-conference.exclude-numbers",
+
"id": "standard-response.field.Agent.<CustomFieldCode>",
"display_name": "Phone Numbers to exclude from Single Step Conference action in Team Communicator",
+
"display_name": "Field to display from Standard Response Library",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the format for a phone number to exclude on single-step conference. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
+
"description": "In the name of the option, CustomFieldCode represents a field code that is called in a Standard Response object created in eServices Manager and stored in Universal Contact Server. Use this option to specify a custom field code such as an agent nickname, role, department, or other qualification. The value of the option is specific to the agent, agent group, tenant, or application. The value of this option represents the data that is used to populate the corresponding field codes when a Standard Response is inserted into an interaction. You can format CustomFieldCode to represent a custom agent attribute. Example: standard-response.field.Agent.Nickname = Lee",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression.",
+
"data_type": "Any valid text string.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,773: Line 4,105:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.voice.consultation.exclude-numbers",
+
"id": "standard-response.shortcuts.<keyword>",
"display_name": "Phone Numbers to exclude from Consultation action in Team Communicator",
+
"display_name": "Standard Response shortcut keyword template",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the format for a phone number to exclude on consultation. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
+
"description": "Specifies the 'keyword' for a shortcut where the name of the option represents the keyword to be entered by agents to use the shortcut. For example: 'standard-response.shortcuts.JulySale'. Specify the path to the Response that is defined in Knowledge Manager as the value for this option. For example '2021Specials\\JulySale'.",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A regular expression.",
+
"data_type": "Path to the standard response as defined in the Knowledge Manager.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,786: Line 4,119:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.permissions.agent.restrict-to-agent-groups",
+
"id": "standard-response.suggested-responses.min-relevance",
"display_name": "restrict search of agents to agent-groups",
+
"display_name": "Minimum relevance above which suggested response are displayed",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "50",
"description": "Specifies the list of agent groups (virtual agent groups aren't supported) used to restrict agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are included in the list.",
+
"description": "Specifies the minimum level of relevance to filter the display of suggested responses in the Responses view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Agent Groups; empty means no restriction applied.",
+
"data_type": "Any integer between 1 to 100",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,799: Line 4,133:
 
},
 
},
 
{
 
{
"id": "teamcommunicator.permissions.agent.exclude-from-agent-groups",
+
"id": "standard-response.suggested-categories.max-number",
"display_name": "search exclude agents from agent-groups",
+
"display_name": "Maximum number of suggested categories to be displayed",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "20",
"description": "Specifies the list of agent groups (virtual agent groups aren't supported) used to exclude agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are excluded from the list. Note: This overrides the teamcommunicator.permissions.agent.restrict-to-agent-groups filter where there is overlap. For example, if an agent belongs to groups A and B, and the exclude filter specifies B while the include filter specifies A, the agent is excluded from the returned list.",
+
"description": "Specifies the maximum number of suggested response categories displayed in the Responses view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
+
"data_type": "An integer between 1 and 20",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,812: Line 4,147:
 
},
 
},
 
{
 
{
"id": "permissions.agent-group.exclude",
+
"id": "privilege.standard-response.shortcuts.can-use",
"display_name": "exclude agent-groups",
+
"display_name": "Enable shortcuts for Standard Responses",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the list of agent groups to be excluded from searches and statistics. Virtual agent groups are not supported. This option is overridden by the permissions.agent-group.restrict option.",
+
"description": "Enables agents to use shortcuts to insert Standard Responses.",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,825: Line 4,161:
 
},
 
},
 
{
 
{
"id": "permissions.agent-group.restrict",
+
"id": "privilege.standard-response.shortcuts.can-filter",
"display_name": "Restrict search of agent-groups",
+
"display_name": "Filter Standard Responses with shortcuts",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the list of agent groups that are returned for searches and statistics. Overrides the permissions.agent-group.exclude option. Virtual agent groups are not supported.",
+
"description": "Enables agents to filter Standard Responses in the Standard Responses tree view to show only those with shortcuts.",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Agent Groups; empty means no filtering.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,838: Line 4,175:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use",
+
"id": "privilege.standard-response.favorites.can-use",
"display_name": "Can Use",
+
"display_name": "Enable favorite Standard Response",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables access to the Contact features.",
+
"description": "Enables agents to use favorites for Standard Responses.",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,851: Line 4,189:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-delete-contact",
+
"id": "privilege.SRL.can-use",
"display_name": "Can Delete Contact",
+
"display_name": "Can Use",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to delete contacts from the contact database.",
+
"description": "Enables access to the Standard Response Library functions.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,864: Line 4,203:
 
},
 
},
 
{
 
{
"id": "contact.enable-force-delete-contact",
+
"id": "privilege.SRL.can-quick-search",
"display_name": "Can Force Delete Contact",
+
"display_name": "Can do Quick Search",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies whether an agent is allowed to delete a contact even if the contact has one or more in-progress interactions.",
+
"description": "Enables an agent to perform a Quick Search of the Standard Response Library.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,877: Line 4,217:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-create-contact",
+
"id": "privilege.standard-response.suggested-response.can-use",
"display_name": "Can Create Contact",
+
"display_name": "Enable suggested responses",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables agents to create contacts.",
+
"description": "Enables an agent to use suggested responses in the Responses view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,890: Line 4,231:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-history",
+
"id": "privilege.voicemail.can-use",
"display_name": "Can Use Contact History",
+
"display_name": "Can Use",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables agents to access the Contact History view.",
+
"description": "Enables agents to use the voicemail functionality. This privilege is required to control and monitor voicemail boxes.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,903: Line 4,245:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-information",
+
"id": "privilege.voicemail.can-use-empty-shared-mailbox",
"display_name": "Can Use Contact Information",
+
"display_name": "Can Use Empty Shared Mailbox",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables agents to view and manage contact information.",
+
"description": "Enables agents to dial both their personal and group voice mailboxes whether they have a message waiting or not.",
 +
"version": "9.0.000.79",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,916: Line 4,259:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-directory",
+
"id": "voicemail.access-number",
"display_name": "Can Use Contact Directory",
+
"display_name": "Voice Mail Directory Number",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables agents to view and search the Contact Directory.",
+
"description": "Specifies the number to call to access your voicemail system.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Any Valid DN",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,929: Line 4,273:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-history-detail",
+
"id": "voicemail.notification-types",
"display_name": "Can Use Contact History Detail",
+
"display_name": "Types of displayed mailboxes",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "personal, public",
"description": "Enables agents to see the detail of interactions in the Contact History view.",
+
"description": "Specifies the types of voicemail boxes included in the count of unread voicemail messages in the Main Window. personal refers to the voicemail box that is identified as the personal voicemail box of the agent; public refers to the group voicemail boxes to which the agent has access.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Comma-separated list of action names from the following list: personal, public",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,942: Line 4,287:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-history-notepad",
+
"id": "voicemail.request-timeout",
"display_name": "Can Use Contact History Notepad",
+
"display_name": "Request timeout",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "1",
"description": "Enables agents to see notes about interactions in the Contact History view.",
+
"description": "Specifies the time, in seconds, to wait for voicemail messages from Feature Server. If no voicemail messages are received during this timeout, a request is sent to Feature Server to get them.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,955: Line 4,301:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-history-case-data",
+
"id": "voicemail.voicemail-service.request-interval",
"display_name": "Can Use Contact History CaseData",
+
"display_name": "Voicemail Service Request Interval",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "60",
"description": "Enables agents to see the case information of interactions in the Contact History view.",
+
"description": "Specifies the frequency, in seconds, with which to query the voicemail service for voicemail MWI.",
 +
"version": "9.0.000.86",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer between 30 and 300",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,968: Line 4,315:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-save-contact",
+
"id": "teamcommunicator.actions.display-mode",
"display_name": "Can Edit Contact",
+
"display_name": "Action display mode",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "hover",
"description": "Enables agents to commit (save) modifications to contact information.",
+
"description": "Specifies the display mode for Team Communicator action buttons.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A value from the following list: hover (actions appear only on mouseover on related entry), block (expose a default action button for all entries).",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 3,981: Line 4,329:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-interaction-notepad",
+
"id": "teamcommunicator.enable-lazy-loading",
"display_name": "Can Use Interaction Notepad",
+
"display_name": "Enable Team Communicator Lazy Loading mechanism (IE11 only)",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to display and edit the interaction notepad while handling an interaction.",
+
"description": "For Internet Explorer 11 environments, if Team Communicator is slow to load due to a large number of search results, including Favorites and Recents, you can use this option to enable Lazy (asynchronous) loading to load only those results that are currently visible in the scrolling list.",
 +
"version": "9.0.000.75",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 3,994: Line 4,343:
 
},
 
},
 
{
 
{
"id": "contact.default-directory-page-size",
+
"id": "teamcommunicator.<media-type>.list-status-reachable",
"display_name": "Default directory page size",
+
"display_name": "List of reachable status for voice call",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "NotReady",
"description": "Specifies the default value for the number of rows per page in the contact directory search result view. The value must be defined in the option contact.available-directory-page-size.",
+
"description": "Specifies the list of unavailable statuses for which a target agent can be contacted for consultation, transfer, and conference requests. If the unavailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.",
 +
"version": "9.0.000.53",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer from 1 through 50.",
+
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,007: Line 4,357:
 
},
 
},
 
{
 
{
"id": "contact.available-directory-page-sizes",
+
"id": "teamcommunicator.voice.list-status-reachable",
"display_name": "Available directory page sizes",
+
"display_name": "List of reachable status for voice call",
 
"type": "config",
 
"type": "config",
"default_value": "5,10,25,50",
+
"default_value": "NotReady",
"description": "Specifies the possible values for the number of rows per page in the contact directory search result view.",
+
"description": "Specifies the list of unavailable statuses for which a target agent can be contacted for consultation, transfer, and conference requests. If the unavailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
+
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,020: Line 4,371:
 
},
 
},
 
{
 
{
"id": "contact.mandatory-attributes",
+
"id": "teamcommunicator.email.list-status-reachable",
"display_name": "Mandatory attributes",
+
"display_name": "List of reachable status for email",
 
"type": "config",
 
"type": "config",
"default_value": "FirstName,LastName",
+
"default_value": "NotReady",
"description": "Specifies the list of Contact fields that must be completed for a contact.",
+
"description": "Specifies the list of unvailable statuses for which a target agent can be contacted for transfer requests. If the unvailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for transfer requests. Depends on 'Email - Can Use Email Channel' and 'TeamCommunicator - Evaluate Presence'.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names, for example: LastName, FirstName, PhoneNumber, EmailAddress.",
+
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,033: Line 4,385:
 
},
 
},
 
{
 
{
"id": "contact.multiple-value-attributes",
+
"id": "teamcommunicator.chat.list-status-reachable",
"display_name": "Multiple Value attributes",
+
"display_name": "List of reachable status for chat",
 
"type": "config",
 
"type": "config",
"default_value": "PhoneNumber,EmailAddress",
+
"default_value": "NotReady",
"description": "Specifies the list of contact attributes that can support multiple values.",
+
"description": "Specifies the list of unvailable statuses for which a target agent can be contacted for consultation, transfer, and conference, requests. If the unvailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests. Depends on 'Chat - Can Use Chat Channel' and 'TeamCommunicator - Evaluate Presence'.",
 +
"version": "9.0.000.11",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma separated value list of Attribute Value names that correspond to contact field names.",
+
"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,046: Line 4,399:
 
},
 
},
 
{
 
{
"id": "contact.displayed-attributes",
+
"id": "teamcommunicator.load-at-startup",
"display_name": "Diplayed attributes",
+
"display_name": "Load Elements at startup",
 
"type": "config",
 
"type": "config",
"default_value": "Title,FirstName,LastName,PhoneNumber,EmailAddress",
+
"default_value": "true",
"description": "Specifies the list of contact fields that are displayed when a Contact record is displayed.",
+
"description": "Specifies whether all the configuration elements (Agents, Agent Groups, Queues, Routing Points, Skills) needed by Team Communicator are loaded at login. This option is used to help with performance at login if many agents login at the same time. When this option is set to false, the elements are not loaded at login, they are loaded the first time the focus is placed in the Team Communicator.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,059: Line 4,413:
 
},
 
},
 
{
 
{
"id": "contact.directory-displayed-columns",
+
"id": "teamcommunicator.routing-point-presence-metrics",
"display_name": "Diplayed Columns",
+
"display_name": "Routing Point Presence Metrics",
 
"type": "config",
 
"type": "config",
"default_value": "LastName,FirstName,PhoneNumber,EmailAddress",
+
"default_value": "routing-point-presence",
"description": "Specifies the list of contact fields that are displayed when the results of a contact search are displayed.",
+
"description": "Specifies a list of routing point presence sections. Each of these sections contains a valid statistic name related to the routing point, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names -- for example: LastName,FirstName,PhoneNumber,EmailAddress.",
+
"data_type": "A comma separated value list of routing point presence options section names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,072: Line 4,427:
 
},
 
},
 
{
 
{
"id": "contact.directory-search-attributes",
+
"id": "teamcommunicator.queue-presence-metrics",
"display_name": "Directory search attributes",
+
"display_name": "Queue Presence Metrics",
 
"type": "config",
 
"type": "config",
"default_value": "LastName,FirstName,PhoneNumber,EmailAddress",
+
"default_value": "queue-presence",
"description": "Specifies the list of Contact fields that can be used as search parameters.",
+
"description": "Specifies a list of Queue presence sections. Each of these sections contains a valid statistic name related to the Queue, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.",
 +
"version": "9.0.000.87",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names that can be used as search parameters.",
+
"data_type": "A comma separated value list of queue presence options section names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,085: Line 4,441:
 
},
 
},
 
{
 
{
"id": "contact.directory-search-mode",
+
"id": "presence.evaluate-presence",
"display_name": "Directory search mode",
+
"display_name": "Evaluate Presence",
 
"type": "config",
 
"type": "config",
"default_value": "sql",
+
"default_value": "true",
"description": "Specifies the technical mode used in the Contact Directory view to search for contacts. The lucene mode must be used for large database of contacts.",
+
"description": "Specifies whether the presence (availability) of agents, agent groups, Routing Points and Queues (when configured) is shown in Team Communicator in the search results.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: sql, lucene",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,098: Line 4,455:
 
},
 
},
 
{
 
{
"id": "contact.lookup.enable",
+
"id": "teamcommunicator.always-clear-textbox-on-new-interaction",
"display_name": "Enable Contact Lookup",
+
"display_name": "always clear textbox on new interaction",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Specifies that Universal Contact Server (UCS) lookup is activated for contacts when an interaction is presented to the Agent. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option is taken into account only when attached data 'IdentifyCreateContact' is not set in the interaction and the contact.lookup.<media-type>.enable option is not specified for the applicable media type.",
+
"description": "Specifies whether the Team Communicator text search box is cleared after the interaction is initiated when the agent presses 'Enter' or clicks one of the medias in the Team Communicator results. When set to false, the Team Communicator text search box is cleared only if an interaction is initiated by the agent pressing 'Enter'.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,111: Line 4,469:
 
},
 
},
 
{
 
{
"id": "contact.lookup.enable-create-contact",
+
"id": "teamcommunicator.list-filter-showing",
"display_name": "Enable Contact Creation on Lookup",
+
"display_name": "Displayed Object Types",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "Agent,AgentGroup,RoutingPoint,Skill,InteractionQueue,Contact,CustomContact",
"description": "When the value of this option is true and the value of ontact.lookup.enable is also set to true, this option specifies that Universal Contact Server (UCS) creates a contact if the initial search does not find a matching existing contact. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option is taken into account only when attached data 'IdentifyCreateContact' is not set in the interaction and the contact.lookup.<media-type>.enable-create-contact option is not specified for the applicable media type.",
+
"description": "Specifies the list of filters that an agent can use to search for contacts and internal targets by using the team communicator. The object types are presented in the specified order.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Skill, Contact, InteractionQueue, ACDQueue, CustomContact, Teams.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,124: Line 4,483:
 
},
 
},
 
{
 
{
"id": "contact.lookup.auto-assign-mode",
+
"id": "teamcommunicator.max-suggestion-size",
"display_name": "Enable Contact Lookup Auto Assign",
+
"display_name": "Max suggestion size",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "10",
"description": "Specifies the contact assignment policy when Contact Lookup is enabled. If set to false and there are multiple matched contacts for an interaction, they are listed as suggested contacts. If set to true, the first contact will be assigned automatically irrespective of the number of matched contacts. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the maximum size of the suggestion list that is displayed while an agent is entering a contact or target name.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "An integer value from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,137: Line 4,497:
 
},
 
},
 
{
 
{
"id": "contact.lookup.<media-type>.auto-assign-mode",
+
"id": "teamcommunicator.recent-max-records",
"display_name": "Enable Contact Lookup Auto Assign for <media-type>",
+
"display_name": "Maximum Recent Records",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "10",
"description": "Specifies the contact assignment policy when Contact Lookup is enabled for the specified media type. If set to false and there are multiple matched contacts for an interaction, they are listed as suggested contacts. If set to true, the first contact will be assigned automatically irrespective of number of matched contacts.This option overrides contact.lookup.auto-assign-mode for the specified media type. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the number of recent internal targets to display in the list of recent targets.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "An integer value from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,150: Line 4,511:
 
},
 
},
 
{
 
{
"id": "contact.suggested.contacts.max-limit",
+
"id": "teamcommunicator.max-favorites-size",
"display_name": "Maximum displayed suggested contacts",
+
"display_name": "Max favorites size",
 
"type": "config",
 
"type": "config",
 
"default_value": "50",
 
"default_value": "50",
"description": "Specifies the maximum number of suggested contacts to be displayed",
+
"description": "Specifies the maximum size of the favorites list that is displayed while an agent is displaying favorites.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 1 through 50.",
+
"data_type": "An integer value from 0 through 100.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,163: Line 4,525:
 
},
 
},
 
{
 
{
"id": "contact.lookup.<media-type>.enable",
+
"id": "teamcommunicator.max-size",
"display_name": "Enable <media-type> Contact Lookup",
+
"display_name": "Max size",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "50",
"description": "Specifies that the Workspace features that rely on Universal Contact Server (UCS) for contact lookup when an interaction of the given media type is presented to the Agent are activated. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable option. It is not taken into account when the attached data IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup behavior in the context of outbound campaign interactions.",
+
"description": "Specifies the maximum size of the default list when the value of teamcommunicator.show-all-internal-targets is set to true.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "An integer value from 0 through 100.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,176: Line 4,539:
 
},
 
},
 
{
 
{
"id": "contact.lookup.<media-type>.enable-create-contact",
+
"id": "teamcommunicator.show-all-internal-targets",
"display_name": "Enable <media-type> Contact Creation on Lookup",
+
"display_name": "Show all internal targets",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "When contact lookup is enabled in the context of the current interaction, this option specifies that the Universal Contact Server (UCS) creates a contact if the initial search cannot find any existing contact. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable-create-contact option. It is not taken into account when the attached data 'IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup and create behavior in the context of outbound campaign interactions.",
+
"description": "Specifies whether all internal targets are displayed by default in the Team Communicator when an agent is searching for a transfer or conference target, including all Agents, Agent Groups, Skills, and Routing Points.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,189: Line 4,553:
 
},
 
},
 
{
 
{
"id": "contact.lookup.voice.use-dialed-phone-number",
+
"id": "teamcommunicator.corporate-favorites",
"display_name": "Lookup contact using the dialed number",
+
"display_name": "Corporate Favorite List",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "If contact lookup is enabled, this option specifies that contact lookup is performed on the normalized phone number that was manually dialed by the agent rather than the number resulting from the application of dial plan rules, if any.",
+
"description": "Specifies the list of corporate favorites (quick dial favorites) that are configured in the Configuration Server for an Agent, Agent Group, Skill, Routing Point, Queue, Interaction Queue, or Custom Contact. See the procedure 'Creating Corporate Favorites' in the Configuration Guide for information about creating Corporate Favorite objects in the configuration layer. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of favorite names (section names) that are defined in the Workspace application.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,202: Line 4,567:
 
},
 
},
 
{
 
{
"id": "contact.lookup.voice.intercommunication.use-dialed-phone-number",
+
"id": "teamcommunicator.request-start-timer",
"display_name": "Lookup contact using the dialed number, for Intercommunication",
+
"display_name": "Request start timer",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "500",
"description": "If contact lookup is enabled, and intercommunication is configured, this option specifies that contact lookup is performed on the phone number typed by an agent for an outgoing call to Routing Point.",
+
"description": "Specifies the request start timer wait interval, in milliseconds, between the last key pressed and the beginning of the search through the contact database.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "An integer value from 1 through 5000.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,215: Line 4,581:
 
},
 
},
 
{
 
{
"id": "contact.ucs-interaction.voice.enable-create",
+
"id": "teamcommunicator.add-recent-filters.voice",
"display_name": "Enable History Record Creation for Voice interactions",
+
"display_name": "Incoming interaction filter (Voice)",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Voice interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether to store incoming interactions into the Recent buffer. By default, the Recent buffer stores only the actions of the agent, such as recent outbound voice calls. If one or more of the valid values is specified, then recent inbound interactions of that type are also stored in the Recent buffer. This enables agents to see a record of missed calls of the specified type(s).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A comma-separated list of interaction types taken from the following values: internal, external, consultation.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,228: Line 4,595:
 
},
 
},
 
{
 
{
"id": "contact.ucs-interaction.voice-campaign.enable-create",
+
"id": "teamcommunicator.voice.apply-exclude-to-favorites",
"display_name": "Enable History Record Creation for Outbound Campaign Voice interactions",
+
"display_name": "apply exclude options to favorites",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Voice Outbound Campaign interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies whether to apply exclude options to all targets, including favorites.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,241: Line 4,609:
 
},
 
},
 
{
 
{
"id": "contact.ucs-interaction.<media-type>.enable-create",
+
"id": "teamcommunicator.voice.make-call.exclude-numbers",
"display_name": "Enable History Record Creation for Open Media Workitem interactions (For Chat, Email, Facebook, Twitter media, the interactions are automatically created in UCS interaction history)",
+
"display_name": "Phone Numbers to exclude from Make Call action in Team Communicator",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Open Media Workitem interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
+
"description": "Specifies the format for a phone number to exclude on making a call. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,254: Line 4,623:
 
},
 
},
 
{
 
{
"id": "contact.ucs-interaction.voice.unanswered.enable-create",
+
"id": "teamcommunicator.voice.single-step-transfer.exclude-numbers",
"display_name": "Enable History Record Creation for Unanswered Voice interactions",
+
"display_name": "Phone Numbers to exclude from Single Step Transfer action in Team Communicator",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether a call history is created in UCS for outgoing calls that are not answered by a contact. If this option is set to true, unanswered calls are added to the UCS database and are viewable in the My History, Contact Directory, Interaction History, and Contact History tabs. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
+
"description": "Specifies the format for a phone number to exclude on single-step transfer. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "A regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,267: Line 4,637:
 
},
 
},
 
{
 
{
"id": "interaction.voice.anonymous-contact.key-name",
+
"id": "teamcommunicator.voice.single-step-conference.exclude-numbers",
"display_name": "Contact anonymous key name",
+
"display_name": "Phone Numbers to exclude from Single Step Conference action in Team Communicator",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the name of the attached data key that specifies whether contact information is treated as anonymous in the interaction view, case information, and history. If the key value is 1, contact information is masked.",
+
"description": "Specifies the format for a phone number to exclude on single-step conference. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid key name.",
+
"data_type": "A regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,280: Line 4,651:
 
},
 
},
 
{
 
{
"id": "contact.history-displayed-columns",
+
"id": "teamcommunicator.voice.consultation.exclude-numbers",
"display_name": "Diplayed Columns in History",
+
"display_name": "Phone Numbers to exclude from Consultation action in Team Communicator",
 
"type": "config",
 
"type": "config",
"default_value": "Status,Subject,StartDate,EndDate,OwnerId",
+
"default_value": "No default value",
"description": "Specifies the list of Contact History items that are displayed in the interaction view.",
+
"description": "Specifies the format for a phone number to exclude on consultation. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}&#36;.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Contact History items to display in the interaction view, for example: Status, Subject, StartDate, EndDate, OwnerId.",
+
"data_type": "A regular expression.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,293: Line 4,665:
 
},
 
},
 
{
 
{
"id": "contact.myhistory-displayed-columns",
+
"id": "teamcommunicator.permissions.agent.restrict-to-agent-groups",
"display_name": "My History Diplayed Columns",
+
"display_name": "restrict search of agents to agent-groups",
 
"type": "config",
 
"type": "config",
"default_value": "Status,Subject,StartDate,EndDate",
+
"default_value": "No default value",
"description": "Specifies the list of Contact History items that are displayed in the My History view.",
+
"description": "Specifies the list of agent groups or virtual agent groups used to restrict agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are included in the list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Contact History items to display in the interaction view MyHistory, for example: Status, Subject, StartDate, EndDate.",
+
"data_type": "Comma-separated list of Agent Groups; empty means no restriction applied.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,306: Line 4,679:
 
},
 
},
 
{
 
{
"id": "contact.all-interactions-displayed-columns",
+
"id": "teamcommunicator.permissions.agent.exclude-from-agent-groups",
"display_name": "Interactions Search Diplayed Columns",
+
"display_name": "search exclude agents from agent-groups",
 
"type": "config",
 
"type": "config",
"default_value": "Status,Subject,StartDate,EndDate",
+
"default_value": "No default value",
"description": "Specifies the list of interaction attributes that are displayed in the result list of the Interaction Search view.",
+
"description": "Specifies the list of agent groups or virtual agent groups used to exclude agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are excluded from the list. Note: This overrides the teamcommunicator.permissions.agent.restrict-to-agent-groups filter where there is overlap. For example, if an agent belongs to groups A and B, and the exclude filter specifies B while the include filter specifies A, the agent is excluded from the returned list.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Contact History items to display in the interaction view MyHistory, for example: Status, Subject, StartDate, EndDate.",
+
"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,319: Line 4,693:
 
},
 
},
 
{
 
{
"id": "contact.all-interactions-quick-search-attributes",
+
"id": "teamcommunicator.permissions.ms-teams.restrict-to-ad-group-id",
"display_name": "Interaction Search Quick Search Attributes",
+
"display_name": "Group ID for Graph API",
 
"type": "config",
 
"type": "config",
"default_value": "Subject",
+
"default_value": "No default value",
"description": "Specifies the interaction attributes that are used to search interactions in the Quick Search mode of the Interaction Search view.",
+
"description": "Specifies the id of the Azure Active Directory group to which searches of MS Teams users is to be restricted.",
 +
"version": "9.0.000.95",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject",
+
"data_type": "A valid Azure Active Directory group identifier.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,332: Line 4,707:
 
},
 
},
 
{
 
{
"id": "contact.myhistory-quick-search-attributes",
+
"id": "teamcommunicator.permissions.ms-teams.restrict-to",
"display_name": "My History Quick Search Attributes",
+
"display_name": "Attribute name for detailed search in Graph API",
 
"type": "config",
 
"type": "config",
"default_value": "Subject",
+
"default_value": "No default value",
"description": "Specifies the interaction attributes that are used to search interactions in the quick search mode of the My History view. These attributes must be text attributes. You can use custom interaction attibutes. For more information, see 'Making an Attribute Searchable from the Desktop' in the PureEngage Digital Administrator's Guide.",
+
"description": "Specifies the user properties of Azure Active Directory users to which searches of MS Teams are to be restricted.",
 +
"version": "9.0.000.95",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject. Possible searchable attributes are: BccAddresses, CcAddresses, FromAddress, FromPersonal, Id, Mailbox, ReplyToAddress, StructuredText, Subject, Text, TheComment, ToAddresses",
+
"data_type": "A valid user properties attribute name and attribute value pair, grouped by parentheses in the Azure Active Directory.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,345: Line 4,721:
 
},
 
},
 
{
 
{
"id": "contact.history-quick-search-attributes",
+
"id": "teamcommunicator.permissions.ms-teams.exclude",
"display_name": "Contact History Quick Search Attributes",
+
"display_name": "Attribute name for exclude from search in Graph API",
 
"type": "config",
 
"type": "config",
"default_value": "Subject",
+
"default_value": "No default value",
"description": "Specifies the interaction attributes that are used to search interactions in the quick search mode of the Contact History view. These attributes should be text attributes. You can use custom interaction attributes. For more information, see 'Making an Attribute Searchable from the Desktop' in the PureEngage Digital Administrator's Guide.",
+
"description": "Specifies the user properties of Azure Active Directory users from which searches of MS Teams are to be excluded.",
 +
"version": "9.0.000.95",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject. Possible searchable attributes are: BccAddresses, CcAddresses, FromAddress, FromPersonal, Id, Mailbox, ReplyToAddress, StructuredText, Subject, Text, TheComment, ToAddresses",
+
"data_type": "A valid user properties attribute name and attribute value pair, grouped by parentheses in the Azure Active Directory.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,358: Line 4,735:
 
},
 
},
 
{
 
{
"id": "contact.history-search-attributes",
+
"id": "teamcommunicator.one-step-transfer-with-consultation.enabled",
"display_name": "History Search Attributes",
+
"display_name": "Team Communicator - Enable One Step Transfer with Consultation",
 
"type": "config",
 
"type": "config",
"default_value": "Status,StartDate,EndDate,Subject",
+
"default_value": "true",
"description": "Specifies the list of interaction attributes that an agent can use in Advanced Search mode of the Contact History, My History and Interaction Search views. You can also use custom interaction attributes.",
+
"description": "Specifies whether agents can make a one-step transfer of a call when there is an active consultation on the call. When the value of this option is set to false, the one-step transfer button is not displayed and agents cannot perform a one-step transfer operation when there is an active consultation.",
 +
"version": "9.0.000.84",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Interaction attributes.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,371: Line 4,749:
 
},
 
},
 
{
 
{
"id": "contact.history-search-attribute-group.<group-name>",
+
"id": "teamcommunicator.one-step-conference-with-consultation.enabled",
"display_name": "History Search Attributes",
+
"display_name": "Team Communicator - Enable One Step Conference with Consultation",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies a group of interaction search attributes. Use this option as a template, modifying the name by replacing the <group-name> by the name of a group to be displayed in the Advanced Search mode of Contact History, My History, and Interaction Search views.",
+
"description": "Specifies whether agents can make a one-step conference of a call when there is an active consultation on the call. When the value of this option is set to false, the one-step conference button is not displayed and agents cannot perform a one-step conference operation when there is an active consultation.",
 +
"version": "9.0.000.84",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value list of Interaction attributes.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,384: Line 4,763:
 
},
 
},
 
{
 
{
"id": "contact.date-search-types",
+
"id": "permissions.agent-group.exclude",
"display_name": "Types of Date Search",
+
"display_name": "exclude agent-groups",
 
"type": "config",
 
"type": "config",
"default_value": "On,OnOrAfter,Before,Between",
+
"default_value": "No default value",
"description": "Specifies the list of search types that are available for the agent to use to search the contact database by date.",
+
"description": "Specifies the list of agent groups to be excluded from searches and statistics. This option is overridden by the permissions.agent-group.restrict option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select at least one from the list.",
+
"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,397: Line 4,777:
 
},
 
},
 
{
 
{
"id": "contact.history-default-time-filter-main",
+
"id": "permissions.agent-group.restrict",
"display_name": "Contact History Default Time Filter",
+
"display_name": "Restrict search of agent-groups",
 
"type": "config",
 
"type": "config",
"default_value": "1M",
+
"default_value": "No default value",
"description": "Specifies which Time Filter option is selected by default in the Contact History view when an agent accesses the main history data source:\n*  All: All interactions from  the main Universal Contact Server (UCS) database.\n*  1M: Interactions from main UCS database that were created less than 1 month ago.\n*  1W: Interactions from main UCS database that were created less than 1 week ago.\n*  1D: Interactions from main UCS database that were created less than 1 day ago.",
+
"description": "Specifies the list of agent groups that are returned for searches and statistics. Overrides the permissions.agent-group.exclude option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: All, 1M, 1W, 1D",
+
"data_type": "Comma-separated list of Agent Groups; empty means no filtering.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,410: Line 4,791:
 
},
 
},
 
{
 
{
"id": "contact.myhistory-default-time-filter-main",
+
"id": "privilege.contact.can-use",
"display_name": "My History Default Time Filter",
+
"display_name": "Can Use",
 
"type": "config",
 
"type": "config",
"default_value": "1M",
+
"default_value": "false",
"description": "Specifies which Time Filter option is selected by default in the My History view when an agent accesses the main history data source:\n*  All: All interactions from the main Universal Contact Server (UCS) database.\n*  1M: Interactions from main UCS database that were created less than 1 month ago.\n*  1W: Interactions from main UCS database that were created less than 1 week ago.\n*  1D: Interactions from main UCS database that were created less than 1 day ago.",
+
"description": "Enables access to the Contact features.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: All, 1M, 1W, 1D",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,423: Line 4,805:
 
},
 
},
 
{
 
{
"id": "contact.all-interactions-default-time-filter-main",
+
"id": "privilege.contact.can-delete-contact",
"display_name": "All Interactions Default Time Filter",
+
"display_name": "Can Delete Contact",
 
"type": "config",
 
"type": "config",
"default_value": "1M",
+
"default_value": "false",
"description": "Specifies which Time Filter is selected by default in the All Interactions Search view when an agent accesses the view.<br><ul><li>All: all interactions from Main UCS Data Base.</li><li>1M: interactions from Main UCS Data Base that were created less than 1 month ago.</li><li>1W: interactions from Main UCS Data Base that were created less than 1 week ago.</li><li>1D: interactions from Main UCS Data Base that were created less than 1 day ago.</li></ul>",
+
"description": "Enables agents to delete contacts from the contact database.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: All, 1M, 1W, 1D",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,436: Line 4,819:
 
},
 
},
 
{
 
{
"id": "contact.history.media-filters",
+
"id": "contact.enable-force-delete-contact",
"display_name": "Contact history Media Filters",
+
"display_name": "Can Force Delete Contact",
 
"type": "config",
 
"type": "config",
"default_value": "voice,email,chat,twitter,facebook,&#36;OtherMedia&#36;",
+
"default_value": "false",
"description": "Specifies the list of media types that can be used to filter the Contact History (depends on privilege.contact.can-filter-contact-history), My History (depends on privilege.contact.can-filter-my-history), and the result list of Interaction Search(depends on privilege.contact.can-filter-all-interactions). &#36;OtherMedia&#36; allows to add the filter returning any media not listed in this option.",
+
"description": "Specifies whether an agent is allowed to delete a contact even if the contact has one or more in-progress interactions.",
 +
"version": "9.0.000.70",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated value of valid media type names or &#36;OtherMedia&#36;.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,449: Line 4,833:
 
},
 
},
 
{
 
{
"id": "contact.email-address-validation.attributes",
+
"id": "privilege.contact.can-create-contact",
"display_name": "Validation for the email address attributes",
+
"display_name": "Can Create Contact",
 
"type": "config",
 
"type": "config",
"default_value": "EmailAddress",
+
"default_value": "true",
"description": "Specifies which contact attributes from the Contact Profile are considered to be email addresses to be validated.<br>The default expression used for validation is specified by the expression.validate.email-address option.",
+
"description": "Enables agents to create contacts.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A list of contact attributes that can support email expression pattern validation",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,462: Line 4,847:
 
},
 
},
 
{
 
{
"id": "contact.phone-number-validation.attributes",
+
"id": "privilege.contact.can-use-contact-history",
"display_name": "Validation for the phone number attributes",
+
"display_name": "Can Use Contact History",
 
"type": "config",
 
"type": "config",
"default_value": "PhoneNumber",
+
"default_value": "true",
"description": "Specifies which contact attributes from the Contact Profile are considered to be phone numbers to be validated.<br>The default expression used for validation is specified by the expression.validate.phone-number option.",
+
"description": "Enables agents to access the Contact History view.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A list of contact attributes that can support phone number expression pattern validation",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,475: Line 4,861:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-search-contact-history",
+
"id": "privilege.contact.can-use-contact-information",
"display_name": "Can Search Contact History",
+
"display_name": "Can Use Contact Information",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to search for interactions in the Contact History view.",
+
"description": "Enables agents to view and manage contact information.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,488: Line 4,875:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-filter-contact-history",
+
"id": "privilege.contact.can-use-contact-directory",
"display_name": "Can Filter Contact History",
+
"display_name": "Can Use Contact Directory",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to filter interactions in the Contact History view.",
+
"description": "Enables agents to view and search the Contact Directory.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,501: Line 4,889:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-advanced-search-contact-history",
+
"id": "privilege.contact.can-use-contact-history-detail",
"display_name": "Can Do Advanced Search in Contact History",
+
"display_name": "Can Use Contact History Detail",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to do advanced searches within the Contact History view.",
+
"description": "Enables agents to see the detail of interactions in the Contact History view.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,514: Line 4,903:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-mark-done.<media-type>.from-history",
+
"id": "privilege.contact.can-use-contact-history-notepad",
"display_name": "Can Mark Done from History",
+
"display_name": "Can Use Contact History Notepad",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to mark done in-progress interactions of the corresponding media-type from history. Depends on 'Contact - Can Use'.",
+
"description": "Enables agents to see notes about interactions in the Contact History view.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,527: Line 4,917:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-open.<media-type>.from-history",
+
"id": "privilege.contact.can-use-contact-history-case-data",
"display_name": "Can Open from History",
+
"display_name": "Can Use Contact History CaseData",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to open in-progress workitems of the corresponding media-type from history. Depends on 'Contact - Can Use'.",
+
"description": "Enables agents to see the case information of interactions in the Contact History view.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,540: Line 4,931:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-mark-done.email.from-history",
+
"id": "privilege.contact.can-use-save-contact",
"display_name": "Can mark done email from History",
+
"display_name": "Can Edit Contact",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to mark done in-progress email interactions from the interaction history. Depends on 'Contact - Can Use'.",
+
"description": "Enables agents to commit (save) modifications to contact information.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,553: Line 4,945:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-open.email.from-history",
+
"id": "privilege.contact.can-use-interaction-notepad",
"display_name": "Can Open email from History",
+
"display_name": "Can Use Interaction Notepad",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to open in-progress email interactions from the interaction history. Depends on 'Contact - Can Use'.",
+
"description": "Enables an agent to display and edit the interaction notepad while handling an interaction.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,566: Line 4,959:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-resend.email.from-history",
+
"id": "privilege.contact.can-use-related-interactions",
"display_name": "Can re-send email from History",
+
"display_name": "Enables Conversation View Tab",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to re-send an email from the interaction history. Depends on 'Contact - Can Use'.",
+
"description": "Enables an agent to access the Related tab in the Case Side View. The Related tab contains interactions in the same thread (conversations) as the current interaction. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.90",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,579: Line 4,973:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-inline-forward.email.from-history",
+
"id": "privilege.contact.can-mark-done-related-interactions",
"display_name": "Can forward email inline from History",
+
"display_name": "Can mark done from related view.",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to forward email interactions from the Interaction History that are marked as Done.",
+
"description": "Enables an agent to use the Related tab in the interaction view to mark as Done single and multiple related interactions and apply the same disposition code to each.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,592: Line 4,987:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-filter-all-interactions",
+
"id": "privilege.contact.can-delete-related-interactions",
"display_name": "Can Filter All Interactions",
+
"display_name": "Can delete from related view.",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to filter interactions in the Interaction Search view.",
+
"description": "Enables an agent to delete single and multiple related interactions from the Related tab in the interaction view",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 4,605: Line 5,001:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-search-all-interactions",
+
"id": "contact.related-interactions.custom-attributes",
"display_name": "Can Search All Interactions",
+
"display_name": "Related interactions custom attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables agents to search among all interactions.",
+
"description": "Specifies the list of interaction custom attributes to be displayed in the Related tab interaction cards. Only the first two attributes are displayed. If you specify more than two attributes, the others are ignored.",
 +
"version": "9.0.000.90",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of interaction custom attributes",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,618: Line 5,015:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-advanced-search-all-interactions",
+
"id": "contact.related-interactions.sort-by.attributes",
"display_name": "Can Do Advanced Search for All Interactions",
+
"display_name": "Related interactions sort by attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "&#36;All&#36;",
"description": "Enables agents to do advanced searches of all interactions.",
+
"description": "Specifies the list of predefined and custom attributes by which the interactions in the Related tab may be sorted. In the Sort By menu, the attributes are displayed in the configured order. Custom attributes specified by this option must also be specified by the contact.related-interactions.custom-attribute.",
 +
"version": "9.0.000.90",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of predefined and custom attributes of an interaction. Example: StartDate,Status,Subject,OwnerId,TypeId,CustomAttr1. To include all predefined and custom attributes, use the value &#36;All&#36; in this option.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,631: Line 5,029:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-filter-my-history",
+
"id": "contact.related-interactions.open.max-number",
"display_name": "Can Filter My History",
+
"display_name": "Maximum Number of Related Interactions Open",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "10",
"description": "Enables agents to filter interactions within the My history view.",
+
"description": "Specifies the maximum number of related interactions that may be opened simultaneously by a single Open action.",
 +
"version": "9.0.000.90",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 1 through 10.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,644: Line 5,043:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-search-my-history",
+
"id": "contact.default-directory-page-size",
"display_name": "Can Search My History",
+
"display_name": "Default directory page size",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "10",
"description": "Enables agents to search for interactions in the My History view.",
+
"description": "Specifies the default value for the number of rows per page in the contact directory search result view. The value must be defined in the option contact.available-directory-page-size.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,657: Line 5,057:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-advanced-search-my-history",
+
"id": "contact.available-directory-page-sizes",
"display_name": "Can Do Advanced Search in My History",
+
"display_name": "Available directory page sizes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "5,10,25,50",
"description": "Enables agents to do advanced searches within My History.",
+
"description": "Specifies the possible values for the number of rows per page in the contact directory search result view.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,670: Line 5,071:
 
},
 
},
 
{
 
{
"id": "contact.last-called-agent.enable",
+
"id": "contact.mandatory-attributes",
"display_name": "Enable Last Called Agent",
+
"display_name": "Mandatory attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "FirstName,LastName",
"description": "Specifies if the last called agent properties are set in the contact when an interaction is presented to the agent. This option is taken into account only when the contact.last-called-agent.<media-type>.enable option is not defined for the applicable media type.",
+
"description": "Specifies the list of Contact fields that must be completed for a contact.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names, for example: LastName, FirstName, PhoneNumber, EmailAddress.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,683: Line 5,085:
 
},
 
},
 
{
 
{
"id": "contact.last-called-agent.<media-type>.enable",
+
"id": "contact.multiple-value-attributes",
"display_name": "Enable Last Called Agent",
+
"display_name": "Multiple Value attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "PhoneNumber,EmailAddress",
"description": "Specifies if the last called agent properties are set in the contact when an interaction of the corresponding media type is presented to the agent. This option overrides the contact.last-called-agent.enable option. Use the voice-campaign media-type to define the look-up behavior for outbound campaign interactions.",
+
"description": "Specifies the list of contact attributes that can support multiple values.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma separated value list of Attribute Value names that correspond to contact field names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,696: Line 5,099:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-contact-myhistory",
+
"id": "contact.displayed-attributes",
"display_name": "Can Use My Contact History",
+
"display_name": "Diplayed attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "Title,FirstName,LastName,PhoneNumber,EmailAddress",
"description": "Enables an agent to access their own history of interactions with contacts.",
+
"description": "Specifies the list of contact fields that are displayed when a Contact record is displayed.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,709: Line 5,113:
 
},
 
},
 
{
 
{
"id": "privilege.contact.can-use-assign-contact",
+
"id": "contact.directory-displayed-columns",
"display_name": "Can Assign Contact",
+
"display_name": "Diplayed Columns",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "LastName,FirstName,PhoneNumber,EmailAddress",
"description": "Enables agents to assign a contact to an interaction.",
+
"description": "Specifies the list of contact fields that are displayed when the results of a contact search are displayed.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names -- for example: LastName,FirstName,PhoneNumber,EmailAddress.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,722: Line 5,127:
 
},
 
},
 
{
 
{
"id": "privilege.screen-recording.can-use",
+
"id": "contact.directory-search-attributes",
"display_name": "Can Use",
+
"display_name": "Directory search attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "LastName,FirstName,PhoneNumber,EmailAddress",
"description": "Enables the usage of Screen Recording Client.",
+
"description": "Specifies the list of Contact fields that can be used as search parameters.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names that can be used as search parameters.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,735: Line 5,141:
 
},
 
},
 
{
 
{
"id": "screen-recording.client.address",
+
"id": "contact.directory-search-mode",
"display_name": "Client address",
+
"display_name": "Directory search mode",
 
"type": "config",
 
"type": "config",
"default_value": "127.0.0.1",
+
"default_value": "sql",
"description": "Specifies the IP address or host name on which Screen Recording Client listens for credentials.",
+
"description": "Specifies the technical mode used in the Contact Directory view to search for contacts. The lucene mode must be used for large database of contacts.",
 +
"version": "9.0.000.37",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "String corresponding to the Screen Recording Client ip address or host name",
+
"data_type": "A value from the following list: sql, lucene",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,748: Line 5,155:
 
},
 
},
 
{
 
{
"id": "screen-recording.client.port",
+
"id": "contact.lookup.enable",
"display_name": "Client Port",
+
"display_name": "Enable Contact Lookup",
 
"type": "config",
 
"type": "config",
"default_value": "443",
+
"default_value": "true",
"description": "Specifies the port on which Screen Recording Client listens for credentials.",
+
"description": "Specifies that Universal Contact Server (UCS) lookup is activated for contacts when an interaction is presented to the Agent. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option is taken into account only when attached data 'IdentifyCreateContact' is not set in the interaction and the contact.lookup.<media-type>.enable option is not specified for the applicable media type.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "String corresponding to the Screen Recording Client port number",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,761: Line 5,169:
 
},
 
},
 
{
 
{
"id": "screen-recording.client.secure-connection",
+
"id": "contact.lookup.enable-create-contact",
"display_name": "Flag specifying if to use secure connection to Screen Recording Client",
+
"display_name": "Enable Contact Creation on Lookup",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Specifies whether a secure connection is used for communication with Screen Recording Client",
+
"description": "When the value of this option is true and the value of ontact.lookup.enable is also set to true, this option specifies that Universal Contact Server (UCS) creates a contact if the initial search does not find a matching existing contact. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option is taken into account only when attached data 'IdentifyCreateContact' is not set in the interaction and the contact.lookup.<media-type>.enable-create-contact option is not specified for the applicable media type.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "True or false, specifying if secure connection will be used",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,774: Line 5,183:
 
},
 
},
 
{
 
{
"id": "screen-recording.client.server-url",
+
"id": "contact.lookup.auto-assign-mode",
"display_name": "Specifies the GWS Server address for SRS.",
+
"display_name": "Enable Contact Lookup Auto Assign",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Defines the address of the RWS server to be used for communication by Screen Recording Client. The field code &#36;GWS_URL&#36; is supported allowing to specify the usage of the same origin as WWE UI. If the option is empty, the WWE UI origin is used. A list of RWS/WWE UI pairs can be defined based on the pattern: <rws_origin_url>(<wwe_origin_url>). This list could be based on a single pair. In case of none matching, the default behavior is used.",
+
"description": "Specifies the contact assignment policy when Contact Lookup is enabled. If set to false and there are multiple matched contacts for an interaction, they are listed as suggested contacts. If set to true, the first contact will be assigned automatically irrespective of the number of matched contacts. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Valid URL",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,787: Line 5,197:
 
},
 
},
 
{
 
{
"id": "privilege.interaction-management.can-use",
+
"id": "contact.lookup.<media-type>.auto-assign-mode",
"display_name": "Can Use",
+
"display_name": "Enable Contact Lookup Auto Assign for open media interactions",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables supervisors to access the Interaction Management feature.",
+
"description": "Specifies the contact assignment policy when Contact Lookup is enabled for the specified media type. If set to false and there are multiple matched contacts for an interaction, they are listed as suggested contacts. If set to true, the first contact will be assigned automatically irrespective of number of matched contacts.This option overrides contact.lookup.auto-assign-mode for the specified media type. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,800: Line 5,211:
 
},
 
},
 
{
 
{
"id": "privilege.interaction-management.case-data.can-edit",
+
"id": "contact.create-contact.check-duplicate",
"display_name": "Can Edit case Data",
+
"display_name": "Alert Duplicate contact ",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables supervisors to edit case data for interactions directly from Workbins and Interaction Queues without pulling the interactions first.",
+
"description": "If an agent tries to create a contact that potentially matches one or more in the contact database, Workspace displays the list of potential matches, then allows an agent to either create the new contact or select an existing contact instead. Use the following options to control what UCS attributes are searched to determine whether a new contact is a potential duplicate. These options can be configured individually or together to allow \\\"AND\\\" and \\\"OR\\\" searches.<br> *contact.potential-match.search-query.and-clause\n* contact.potential-match.search-query.or-clause<br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.74",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,813: Line 5,225:
 
},
 
},
 
{
 
{
"id": "privilege.interaction-management.can-move-to-queue",
+
"id": "contact.potential-match.search-query.and-clause",
"display_name": "Can Move to queue",
+
"display_name": "List of Attributes for Search Rule AND",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables supervisors to move interactions to a queue.",
+
"description": "Specifies the list of contact attributes, each of which will be added as an AND clause in the search query to retrieve potential duplicate contacts from UCS during contact creation in Workspace.",
 +
"version": "9.0.000.74",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "List of contact attributes including custom attributes",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,826: Line 5,239:
 
},
 
},
 
{
 
{
"id": "privilege.interaction-management.can-move-to-workbin",
+
"id": "contact.potential-match.search-query.or-clause",
"display_name": "Can Move to Workbins",
+
"display_name": "List of Attributes for Search Rule OR",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "PhoneNumber, EmailAddress",
"description": "Enables supervisors to move interactions to a workbin.",
+
"description": "Specifies the list of contact attributes, each of which will be added as an OR clause in the search query to retrieve potential duplicate contacts from UCS during contact creation in Workspace.",
 +
"version": "9.0.000.74",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "List of contact attributes including custom attributes",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,839: Line 5,253:
 
},
 
},
 
{
 
{
"id": "privilege.interaction-management.can-search-interactions",
+
"id": "contact.lookup.<media-type>.enable",
"display_name": "Can Search interactions",
+
"display_name": "Enable Contact Lookup for open-media interactions",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables agents to search for interactions in interaction queues content.",
+
"description": "Specifies that the Workspace features that rely on Universal Contact Server (UCS) for contact lookup when an interaction of the given media type is presented to the Agent are activated. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable option. It is not taken into account when the attached data IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup behavior in the context of outbound campaign interactions.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,852: Line 5,267:
 
},
 
},
 
{
 
{
"id": "interaction-management.available-interaction-page-sizes",
+
"id": "contact.lookup.<media-type>.enable-create-contact",
"display_name": "Available Content Page Sizes",
+
"display_name": "Enable Contact Creation on Lookup for open-media interactions",
 
"type": "config",
 
"type": "config",
"default_value": "5,10,25,50",
+
"default_value": "true",
"description": "Specifies the possible values for the number of rows per page in the Interaction Management content view. Values grater than 100 are not recommended due to performance impact. The maximum value depends on the content of interactions and the robustness of your network. If you specify a value that is too high, the request to get a snapshot fails and an error message is displayed.",
+
"description": "When contact lookup is enabled in the context of the current interaction, this option specifies that the Universal Contact Server (UCS) creates a contact if the initial search cannot find any existing contact. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable-create-contact option. It is not taken into account when the attached data 'IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup and create behavior in the context of outbound campaign interactions.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,865: Line 5,281:
 
},
 
},
 
{
 
{
"id": "interaction-management.default-interaction-page-size",
+
"id": "contact.lookup.voice.use-dialed-phone-number",
"display_name": "Default content page size",
+
"display_name": "Lookup contact using the dialed number",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "false",
"description": "Specifies the default value for the number of rows per page in the Interaction Management content view.",
+
"description": "If contact lookup is enabled, this option specifies that contact lookup is performed on the normalized phone number that was manually dialed by the agent rather than the number resulting from the application of dial plan rules, if any.",
 +
"version": "9.0.000.61",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer from 1 through 50.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,878: Line 5,295:
 
},
 
},
 
{
 
{
"id": "interaction-management.filters",
+
"id": "contact.lookup.voice.use-formatted-number",
"display_name": "Filters",
+
"display_name": "Inbound Contact Creation",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the filters that are displayed to the supervisor for interaction management. The filter names refer to the names of the Application Option sections that define the Filters. See 'Creating Interaction Filters for Team Leads' in the Configuration Guide for more information.",
+
"description": "Specifies that the phone number of an inbound voice interaction is subject to processing by the expression.phone-number.supported-characters option prior to contact lookup. This option depends on the option contact.lookup.enable-create-contact. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of Filter names.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,891: Line 5,309:
 
},
 
},
 
{
 
{
"id": "interaction-management.interactions-filter.displayed-columns",
+
"id": "contact.lookup.voice.intercommunication.use-dialed-phone-number",
"display_name": "Displayed Columns Configuration of Interaction Queue",
+
"display_name": "Lookup contact using the dialed number, for Intercommunication",
 
"type": "config",
 
"type": "config",
"default_value": "From,To,Subject,Received",
+
"default_value": "true",
"description": "Specifies the list of interaction fields that are displayed as columns in Interaction Queue view when displayed-columns is not defined in the Filter.",
+
"description": "If contact lookup is enabled, and intercommunication is configured, this option specifies that contact lookup is performed on the phone number typed by an agent for an outgoing call to Routing Point.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of attached data, for example: From,Subject,Received",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,904: Line 5,323:
 
},
 
},
 
{
 
{
"id": "interaction-management.filters.quick-search-attributes",
+
"id": "contact.phone-number-validation.enable",
"display_name": "Quick Search Attributes of Interaction Queue",
+
"display_name": "Enable Contact Phone Number Validation",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in an interaction queue for which quick-search-attributes is not defined in the Filter.",
+
"description": " In environments using UCSX server, this option specifies whether phone numbers are validated on the client side when contact records are created or updated.",
 +
"version": "9.0.000.85",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of attached data, for example: AssignedTo,FromAddress",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,917: Line 5,337:
 
},
 
},
 
{
 
{
"id": "interaction-management.move-to-workbin.restrict-to-my-team",
+
"id": "contact.ucs-interaction.voice.enable-create",
"display_name": "restrict move to workbins to workbins of the logged agent team.",
+
"display_name": "Enable History Record Creation for Voice interactions",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies if the search applied in Team Communicator for Move to Workbin action should be restricted to the workbins of the logged agent team.",
+
"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Voice interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,930: Line 5,351:
 
},
 
},
 
{
 
{
"id": "privilege.monitor-dashboard.can-use",
+
"id": "contact.ucs-interaction.voice.enable-create-without-contact",
"display_name": "Can use the Dashboard",
+
"display_name": "Contact - Enable History Record Creation for voice interaction without contact",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables the Contact Center Statistics dashboard tab.",
+
"description": "Specifies whether a voice interaction is created in Universal Contact Server (UCS) when there is no associated contact. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,943: Line 5,365:
 
},
 
},
 
{
 
{
"id": "statistics.default-page-size",
+
"id": "contact.ucs-interaction.voice-campaign.create-without-contact",
"display_name": "Default page size",
+
"display_name": "Contact - Enable History Record Creation for outbound campaign interaction without contact",
 
"type": "config",
 
"type": "config",
"default_value": "50",
+
"default_value": "false",
"description": "Specifies the default value for the number of statistics objects per page in the Contact Center Statistics view. The value must be defined in the option statistics.available-page-size.",
+
"description": "Specifies whether a outbound campaign interaction is created in Universal Contact Server (UCS) when there is no associated contact. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.90",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer from 10 through 100.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,956: Line 5,379:
 
},
 
},
 
{
 
{
"id": "statistics.available-page-sizes",
+
"id": "contact.ucs-interaction.voice-campaign.enable-create",
"display_name": "Available page sizes",
+
"display_name": "Enable History Record Creation for Outbound Campaign Voice interactions",
 
"type": "config",
 
"type": "config",
"default_value": "10,20,30",
+
"default_value": "false",
"description": "Specifies the possible values for the number of statistics objects per page in the contact center statistics view.",
+
"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Voice Outbound Campaign interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of numbers that define the number of statistics objects per result page from which the agent can make selections.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,969: Line 5,393:
 
},
 
},
 
{
 
{
"id": "statistics.routing-points",
+
"id": "contact.ucs-interaction.<media-type>.enable-create",
"display_name": "List of routing points displayed in the dashboard, and in Contact Center Statistics",
+
"display_name": "Enable History Record Creation for Open Media Workitem interactions (For Chat, Email, Facebook, Twitter media, the interactions are automatically created in UCS interaction history)",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the list of routing points that are displayed in the Contact Center Statistics tab. If empty, no routing points are displayed. If set to a list and none of the routing points match an existing routing point, no routing points are displayed.",
+
"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Open Media Workitem interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,982: Line 5,407:
 
},
 
},
 
{
 
{
"id": "statistics.agent-groups",
+
"id": "contact.ucs-interaction.voice.unanswered.enable-create",
"display_name": "List of agent groups or virtual agent groups displayed in the Contact Center Statistics",
+
"display_name": "Enable History Record Creation for Unanswered Voice interactions",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the list of agent groups and virtual agent groups that are displayed in the Contact Center Statistics tab. If empty, no agent groups or virtual agent groups are displayed. If set to a list and none of the groups in the list match an existing group, no agent groups or virtual agent groups are displayed.",
+
"description": "Specifies whether a call history is created in UCS for outgoing calls that are not answered by a contact. If this option is set to true, unanswered calls are added to the UCS database and are viewable in the My History, Contact Directory, Interaction History, and Contact History tabs. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
 +
"version": "9.0.000.67",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 4,995: Line 5,421:
 
},
 
},
 
{
 
{
"id": "statistics.virtual-queues",
+
"id": "interaction.voice.anonymous-contact.key-name",
"display_name": "List of virtual queues displayed in the Contact Center Statistics",
+
"display_name": "Contact anonymous key name",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the list of virtual queues that are displayed in the Contact Center Statistics tab. If empty, no virtual queues are displayed. If set to a list and none of the virtual queues in the list match an existing virtual queue, no virtual queues are displayed.",
+
"description": "Specifies the name of the attached data key that specifies whether contact information is treated as anonymous in the interaction view, case information, and history. If the key value is 1, contact information is masked.",
 +
"version": "9.0.000.61",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "",
+
"data_type": "A valid key name.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,008: Line 5,435:
 
},
 
},
 
{
 
{
"id": "statistics.queue-groups",
+
"id": "contact.history-displayed-columns",
"display_name": "List of group of queues (dn groups) displayed in the Contact Center Statistics",
+
"display_name": "Diplayed Columns in History",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Status,Subject,StartDate,EndDate,OwnerId",
"description": "Specifies the list of queue groups that are displayed in the Contact Center Statistics tab. If empty, no queue groups are displayed. If set to a list and none of the queue groups in the list match an existing queue group, no queue groups are displayed.",
+
"description": "Specifies the list of Contact History items that are displayed in the interaction view.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "",
+
"data_type": "A comma-separated value list of Contact History items to display in the interaction view, for example: Status, Subject, StartDate, EndDate, OwnerId.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,021: Line 5,449:
 
},
 
},
 
{
 
{
"id": "privilege.my-team-workbins.can-use",
+
"id": "contact.myhistory-displayed-columns",
"display_name": "Can Use My Team Workbins",
+
"display_name": "My History Diplayed Columns",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "Status,Subject,StartDate,EndDate",
"description": "Enables access to My Team Workbins.",
+
"description": "Specifies the list of Contact History items that are displayed in the My History view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated value list of Contact History items to display in the interaction view MyHistory, for example: Status, Subject, StartDate, EndDate.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,034: Line 5,463:
 
},
 
},
 
{
 
{
"id": "my-team-workbins.agent-page-size",
+
"id": "contact.all-interactions-displayed-columns",
"display_name": "Agent page size",
+
"display_name": "Interactions Search Displayed Columns",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "Status,Subject,StartDate,EndDate",
"description": "Specifies the value for the number of agents per page in My Team Workbins sub-tree of My Workbins view.",
+
"description": "Specifies the list of interaction attributes that are displayed in the result list of the Interaction Search view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer from 1 through 50.",
+
"data_type": "A comma-separated value list of Contact History items to display in the interaction view MyHistory, for example: Status, Subject, StartDate, EndDate.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,047: Line 5,477:
 
},
 
},
 
{
 
{
"id": "workbin.email.draft",
+
"id": "contact.history-displayed-columns-conversations",
"display_name": "Draft E-Mail workbin",
+
"display_name": "Displayed Columns in History Conversations View",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Status,Subject,StartDate,EndDate",
"description": "Specifies the name of the workbin to be used to store draft email.",
+
"description": "Specifies the list of interaction fields that are displayed in the Contact History view in the conversation (thread) mode.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
+
"data_type": "A comma-separated list of Contact History items to display in the History conversations view - for example: Subject, StartDate, EndDate, Status.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,060: Line 5,491:
 
},
 
},
 
{
 
{
"id": "workbin.email.in-progress",
+
"id": "contact.myhistory-displayed-columns-conversations",
"display_name": "In Progress E-Mail workbin",
+
"display_name": "Displayed columns in My History conversations View",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Status,Subject,StartDate,EndDate",
"description": "Specifies the name of the workbin that is to be used to store inbound email for later processing, after an agent explicitly saved the email or submitted an outbound reply.",
+
"description": "Specifies the list of interaction fields that are displayed in the My History view in the conversation (thread) mode.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
+
"data_type": "A Comma-separated list of interaction fields to display in My History conversations view - for example: Subject, StartDate, EndDate, Status.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,073: Line 5,505:
 
},
 
},
 
{
 
{
"id": "workbin.email.in-progress.displayed-columns",
+
"id": "contact.all-interactions-quick-search-attributes",
"display_name": "In Progress E-mail workbin Displayed Columns",
+
"display_name": "Interaction Search Quick Search Attributes",
 
"type": "config",
 
"type": "config",
"default_value": "From,Subject,Received",
+
"default_value": "Subject",
"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores inbound email for later processing.",
+
"description": "Specifies the interaction attributes that are used to search interactions in the Quick Search mode of the Interaction Search view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Interaction Server interaction properties, for example: From,Subject,Received",
+
"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,086: Line 5,519:
 
},
 
},
 
{
 
{
"id": "workbin.email.draft.displayed-columns",
+
"id": "contact.myhistory-quick-search-attributes",
"display_name": "Draft E-Mail workbin Displayed Columns",
+
"display_name": "My History Quick Search Attributes",
 
"type": "config",
 
"type": "config",
"default_value": "To,Subject,Submitted",
+
"default_value": "Subject",
"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores draft email interactions.",
+
"description": "Specifies the interaction attributes that are used to search interactions in the quick search mode of the My History view. These attributes must be text attributes. You can use custom interaction attibutes. For more information, see 'Making an Attribute Searchable from the Desktop' in the PureEngage Digital Administrator's Guide.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Interaction Server interaction properties, for example: To,Subject,Submitted",
+
"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject. Possible searchable attributes are: BccAddresses, CcAddresses, FromAddress, FromPersonal, Id, Mailbox, ReplyToAddress, StructuredText, Subject, Text, TheComment, ToAddresses",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,099: Line 5,533:
 
},
 
},
 
{
 
{
"id": "workbin.email.review",
+
"id": "contact.history-quick-search-attributes",
"display_name": "QA Review E-Mail workbin",
+
"display_name": "Contact History Quick Search Attributes",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Subject",
"description": "Specifies the name of the workbin that is to be used to store QA reviews for later processing, after a reviewer explicitly saved the email.",
+
"description": "Specifies the interaction attributes that are used to search interactions in the quick search mode of the Contact History view. These attributes should be text attributes.  You can use custom interaction attributes. For more information, see 'Making an Attribute Searchable from the Desktop' in the PureEngage Digital Administrator's Guide.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
+
"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject. Possible searchable attributes are: BccAddresses, CcAddresses, FromAddress, FromPersonal, Id, Mailbox, ReplyToAddress, StructuredText, Subject, Text, TheComment, ToAddresses",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,112: Line 5,547:
 
},
 
},
 
{
 
{
"id": "workbin.email.review.displayed-columns",
+
"id": "contact.history.quick-search.max-input-length",
"display_name": "QA Review E-Mail workbin Displayed Columns",
+
"display_name": "History Interactions Quick Search Input Length",
 
"type": "config",
 
"type": "config",
"default_value": "To,Subject,Submitted",
+
"default_value": "10",
"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores QA reviews.",
+
"description": "Specifies the maximum number of words that can be used to make a quick search of interaction in My History, Contact History and Interaction Search",
 +
"version": "9.0.000.85",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of Interaction Server interaction properties, for example: To,Subject,Submitted",
+
"data_type": "An integer value from 1 through 20.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,125: Line 5,561:
 
},
 
},
 
{
 
{
"id": "workbin.<media-type>.in-progress",
+
"id": "contact.history-search-attributes",
"display_name": "Template for Workitem Workbin declaration",
+
"display_name": "History Search Attributes",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "Status,StartDate,EndDate,Subject",
"description": "Specifies the name of the workbin to be used to store interactions of a particular workitem media type. Agents can open interactions from this workbin but not save interactions in it.",
+
"description": "Specifies the list of interaction attributes that an agent can use in Advanced Search mode of the Contact History, My History and Interaction Search views. You can also use custom interaction attributes.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
+
"data_type": "A comma-separated value list of Interaction attributes.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,138: Line 5,575:
 
},
 
},
 
{
 
{
"id": "workbin.<media-type>.<workbin-nickname>",
+
"id": "contact.history-search-attribute-group.<group-name>",
"display_name": "Template for Custom Workbin declaration",
+
"display_name": "History Search Attributes",
 
"type": "config",
 
"type": "config",
 
"default_value": "No default value",
 
"default_value": "No default value",
"description": "Specifies the name of the workbin to be used to store interactions of a particular workitem media type. Agents can open interactions from this workbin but not save interactions in it.",
+
"description": "Specifies a group of interaction search attributes. Use this option as a template, modifying the name by replacing the <group-name> by the name of a group to be displayed in the Advanced Search mode of Contact History, My History, and Interaction Search views.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
+
"data_type": "A comma-separated value list of Interaction attributes.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,151: Line 5,589:
 
},
 
},
 
{
 
{
"id": "workbin.<media-type>.<workbin-nickname>.displayed-columns",
+
"id": "contact.date-search-types",
"display_name": "Template for Displayed Columns Configuration of a Custom Workbin",
+
"display_name": "Types of Date Search",
 
"type": "config",
 
"type": "config",
"default_value": "From,To,Subject,Received",
+
"default_value": "On,OnOrAfter,Before,Between",
"description": "Specifies the list of interaction fields displayed as columns in the specified workbin.",
+
"description": "Specifies the list of search types that are available for the agent to use to search the contact database by date.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of Interaction Server interaction properties, for example: From,Subject,Received",
+
"data_type": "Select at least one from the list.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,164: Line 5,603:
 
},
 
},
 
{
 
{
"id": "workbin.bulk-operation.nb-interactions-perf-impact",
+
"id": "contact.history-default-time-filter-main",
"display_name": "Bulk Operation nb Interactions Performance Impact",
+
"display_name": "Contact History Default Time Filter",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "1M",
"description": "Specifies the number of interactions before which a bulk operation will impact performance.",
+
"description": "Specifies which Time Filter option is selected by default in the Contact History view when an agent accesses the main history data source:\n*  All: All interactions from  the main Universal Contact Server (UCS) database.\n*  1M: Interactions from main UCS database that were created less than 1 month ago.\n*  1W: Interactions from main UCS database that were created less than 1 week ago.\n*  1D: Interactions from main UCS database that were created less than 1 day ago.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A integer value greater than or equal to 1",
+
"data_type": "A value from the following list: All, 1M, 1W, 1D",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,177: Line 5,617:
 
},
 
},
 
{
 
{
"id": "workbin.quick-search-attributes",
+
"id": "contact.myhistory-default-time-filter-main",
"display_name": "Quick Search Attributes of Workbin",
+
"display_name": "My History Default Time Filter",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "1M",
"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in a workbin for which workbin.<media-type>.<workbin-nickname>.quick-search-attributes is not defined.",
+
"description": "Specifies which Time Filter option is selected by default in the My History view when an agent accesses the main history data source:\n*  All: All interactions from the main Universal Contact Server (UCS) database.\n*  1M: Interactions from main UCS database that were created less than 1 month ago.\n*  1W: Interactions from main UCS database that were created less than 1 week ago.\n*  1D: Interactions from main UCS database that were created less than 1 day ago.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of Interaction Server interaction properties, for example: AssignedTo,FromAddress",
+
"data_type": "A value from the following list: All, 1M, 1W, 1D",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,190: Line 5,631:
 
},
 
},
 
{
 
{
"id": "workbin.<media-type>.<workbin-nickname>.quick-search-attributes",
+
"id": "contact.all-interactions-default-time-filter-main",
"display_name": "Template for Interaction Quick Search Attributes Configuration of a Custom Workbin",
+
"display_name": "All Interactions Default Time Filter",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "1M",
"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in the specified workbin. Default value of this option is the Value of workbin.quick-search-attributes if defined.",
+
"description": "Specifies which Time Filter is selected by default in the All Interactions Search view when an agent accesses the view.<br><ul><li>All: all interactions from Main UCS Data Base.</li><li>1M: interactions from Main UCS Data Base that were created less than 1 month ago.</li><li>1W: interactions from Main UCS Data Base that were created less than 1 week ago.</li><li>1D: interactions from Main UCS Data Base that were created less than 1 day ago.</li></ul>",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of Interaction Server interaction properties, for example: AssignedTo,FromAddress",
+
"data_type": "A value from the following list: All, 1M, 1W, 1D",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,203: Line 5,645:
 
},
 
},
 
{
 
{
"id": "privilege.workbin.can-search-my-workbins-trees",
+
"id": "contact.history.media-filters",
"display_name": "Can Search Workbin",
+
"display_name": "Contact history Media Filters",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "voice,email,chat,twitter,facebook,&#36;OtherMedia&#36;",
"description": "Enables agents to search for workbins in the navigation tree of the My Workbins View.",
+
"description": "Specifies the list of media types that can be used to filter the Contact History (depends on privilege.contact.can-filter-contact-history), My History (depends on privilege.contact.can-filter-my-history), and the result list of Interaction Search(depends on privilege.contact.can-filter-all-interactions). &#36;OtherMedia&#36; allows to add the filter returning any media not listed in this option.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated value of valid media type names or &#36;OtherMedia&#36;.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,216: Line 5,659:
 
},
 
},
 
{
 
{
"id": "privilege.workbin.can-search-interactions",
+
"id": "contact.email-address-validation.attributes",
"display_name": "Can Search interactions",
+
"display_name": "Validation for the email address attributes",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "EmailAddress",
"description": "Enables agents to search for interactions in workbins content.",
+
"description": "Specifies which contact attributes from the Contact Profile are considered to be email addresses to be validated.<br>The default expression used for validation is specified by the expression.validate.email-address option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A list of contact attributes that can support email expression pattern validation",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,229: Line 5,673:
 
},
 
},
 
{
 
{
"id": "teamlead.monitoring-scope",
+
"id": "contact.phone-number-validation.attributes",
"display_name": "Monitoring Scope",
+
"display_name": "Validation for the phone number attributes",
 
"type": "config",
 
"type": "config",
"default_value": "call",
+
"default_value": "PhoneNumber",
"description": "Specifies the scope of monitoring that is to be used for voice interactions. If the value call is specified, the supervisor remains on the call until it is finished. This mode enables barge-in. If the value agent is specified, the system disconnects the supervisor automatically from the call when the monitored agent leaves the call. In this mode, the barge-in operation is not possible.",
+
"description": "Specifies which contact attributes from the Contact Profile are considered to be phone numbers to be validated.<br>The default expression used for validation is specified by the expression.validate.phone-number option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select a value from the following list: agent,call",
+
"data_type": "A list of contact attributes that can support phone number expression pattern validation",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,242: Line 5,687:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.default-page-size",
+
"id": "privilege.contact.can-search-contact-history",
"display_name": "Default page size",
+
"display_name": "Can Search Contact History",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "false",
"description": "Specifies the default value for the number of rows per page in the My Agents view. The value is added to the list defined by the option teamlead.myagents.available-page-sizes.",
+
"description": "Enables agents to search for interactions in the Contact History view.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer from 1 through 50.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,255: Line 5,701:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.available-page-sizes",
+
"id": "privilege.contact.can-filter-contact-history",
"display_name": "Available page sizes",
+
"display_name": "Can Filter Contact History",
 
"type": "config",
 
"type": "config",
"default_value": "5,10,25,50",
+
"default_value": "false",
"description": "Specifies the possible values for the number of rows per page in the My Agents view.",
+
"description": "Enables agents to filter interactions in the Contact History view.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,268: Line 5,715:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.refresh-rate",
+
"id": "privilege.contact.can-advanced-search-contact-history",
"display_name": "My Agents refresh rate",
+
"display_name": "Can Do Advanced Search in Contact History",
 
"type": "config",
 
"type": "config",
"default_value": "30",
+
"default_value": "false",
"description": "Specifies the frequency, in seconds, to refresh the list of agents. To disable automatic refresh, specify a value less than 5 to indicate manual refresh. Automatic refresh is also disabled if the value of the accessibility.visual-impairment-profile option is true.",
+
"description": "Enables agents to do advanced searches within the Contact History view.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Valid values are integer values between 5 and 5000. Values less than 5 disables the automatic refresh.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,281: Line 5,729:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.manual-refresh.enabled",
+
"id": "privilege.contact.can-mark-done.<media-type>.from-history",
"display_name": "My Agents enable manual refresh",
+
"display_name": "Can Mark Done from History",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether the manual refresh button is displayed in the My Agents view. Manual refresh is automatically enabled if automatic refresh is disabled by the teamlead.myagents.refresh-rate option.",
+
"description": "Enables agents to mark done in-progress interactions of the corresponding media-type from history. Depends on 'Contact - Can Use'.",
 +
"version": "9.0.000.24",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,294: Line 5,743:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.enabled-channels",
+
"id": "privilege.contact.can-open.<media-type>.from-history",
"display_name": "My Agents enabled channels",
+
"display_name": "Can Open from History",
 
"type": "config",
 
"type": "config",
"default_value": "voice,chat,email",
+
"default_value": "false",
"description": "Specifies the channels that are displayed in the My Agents view. Channels are displayed in the order in which they appear in the list.",
+
"description": "Enables agents to open in-progress workitems of the corresponding media-type from history. Depends on 'Contact - Can Use'.",
 +
"version": "9.0.000.24",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of channel names from the following list: voice, chat, email, facebook, twitter, workitem",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,307: Line 5,757:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.thresholds.enabled",
+
"id": "privilege.contact.can-open.<media-type>.from-universal-queue",
"display_name": "My Agents enable thresholds",
+
"display_name": "Can Open from Universal Queue",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enable thresholds to be used for channels specified by the teamlead.myagents.thresholds.<media-type> option.",
+
"description": "Enables agents to open in-progress emails and workitems of the corresponding media type from the Universal Queue. Depends on 'Contact - Can Use', 'Contact - Can Open from History' and 'Contact - Can use interaction workfow state'.",
 +
"version": "9.0.000.84",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,320: Line 5,771:
 
},
 
},
 
{
 
{
"id": "teamlead.myagents.thresholds.<media-type>",
+
"id": "privilege.contact.can-re-open.<media-type>.from-universal-queue",
"display_name": "My Agents media thresholds",
+
"display_name": "Can Re-Open from Universal Queue",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the name of a threshold section that determine when an agent state is considered to be Busy or Not Ready for the specified channel. You must create the threshold sections on the Application object.",
+
"description": "Enables agents to re-open completed emails and workitems of the corresponding media type from the Universal Queue. Depends on 'Contact - Can Use' and 'Contact - Can use interaction workfow state'.",
 +
"version": "9.0.000.84",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A threshold section name.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,333: Line 5,785:
 
},
 
},
 
{
 
{
"id": "kpi.displayed-kpis",
+
"id": "privilege.contact.can-mark-done.email.from-history",
"display_name": "Displayed KPIs",
+
"display_name": "Can mark done email from History",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the KPIs that are displayed to the agent. The KPI names refer to the names of the Application Option sections that are defining the KPIs.",
+
"description": "Enables agents to mark done in-progress email interactions from the interaction history. Depends on 'Contact - Can Use'.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of KPI names.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,346: Line 5,799:
 
},
 
},
 
{
 
{
"id": "privilege.performance-tracker.can-use",
+
"id": "privilege.contact.can-open.email.from-history",
"display_name": "Can use Performance Tracker",
+
"display_name": "Can Open email from History",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables access to the Performance Tracker",
+
"description": "Enables agents to open in-progress email interactions from the interaction history. Depends on 'Contact - Can Use'.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,359: Line 5,813:
 
},
 
},
 
{
 
{
"id": "statistics.displayed-statistics",
+
"id": "privilege.contact.can-use-interaction-workflow-state",
"display_name": "Displayed Statistics",
+
"display_name": "Can use interaction workfow state",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the statistics that are displayed in the Contact Center Statistics tab. The statistics specified by this option match the names of the statistics defined in the options of the Application sections.",
+
"description": "When viewing digital interactions in the Contact History view, agents can see the exact status of an interaction while it is being processed. Depends on 'Contact - Can Use'.",
 +
"version": "9.0.000.73",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of Statistic names.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,372: Line 5,827:
 
},
 
},
 
{
 
{
"id": "statistics.gadget-statistics",
+
"id": "privilege.contact.can-open.from-queue",
"display_name": "Gadget Statistics displayed",
+
"display_name": "Can Open from queue",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the statistics, up to 10, that are displayed in the Statistics Gadget. Each statistics specified in this option is the name of a section containing the statistic definition or the statistic object.",
+
"description": "From the History, enables agents to open interactions that are in the In-Progress state and are in a queue. Depends on 'Contact - Can Use', 'Contact - Can Open from History' and 'Contact - Can use interaction workfow state'.",
 +
"version": "9.0.000.73",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of Statistic names.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,385: Line 5,841:
 
},
 
},
 
{
 
{
"id": "statistics.gadget-statistics.max-size",
+
"id": "privilege.contact.can-open.from-other-personal-workbins",
"display_name": "Maximum quantity of Gadget Statistics displayed",
+
"display_name": "Can Open from other personal workbins",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "true",
"description": "Specifies the maximum number of statistics that are displayed in the Statistics Gadget. If more statistics are specified by the statistics.gadget-statistics option, only the first 'n' statistics are displayed.",
+
"description": "From the History, enables agents to open interactions that are in the In-Progress state and are in the Workbin of another agent. Depends on 'Contact - Can Use', 'Contact - Can Open from History' and 'Contact - Can use interaction workfow state'.",
 +
"version": "9.0.000.73",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value from 1 through 50.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,398: Line 5,855:
 
},
 
},
 
{
 
{
"id": "statistics.refresh-time",
+
"id": "privilege.contact.can-resend.email.from-history",
"display_name": "Refresh Time",
+
"display_name": "Can re-send email from History",
 
"type": "config",
 
"type": "config",
"default_value": "20",
+
"default_value": "false",
"description": "Specifies, in seconds, how often statistics are refreshed in the Contact Center Statistics tab. When set to 0, no automatic refresh occurs (the agent must manually refresh statistics).",
+
"description": "Enables agents to re-send an email from the interaction history. Depends on 'Contact - Can Use'.",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than 0.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,411: Line 5,869:
 
},
 
},
 
{
 
{
"id": "privilege.sipendpoint.can-use",
+
"id": "privilege.contact.can-inline-forward.email.from-history",
"display_name": "Can Use Genesys Softphone",
+
"display_name": "Can forward email inline from History",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables the usage of Genesys Softphone. Depends on 'Voice - Can Use Voice Channel'. If SIP Endpoint is enabled, the login.prompt-place option must be set to false.",
+
"description": "Enables agents to forward email interactions from the Interaction History that are marked as Done.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,424: Line 5,883:
 
},
 
},
 
{
 
{
"id": "privilege.sipendpoint.can-change-microphone-volume",
+
"id": "privilege.contact.can-filter-all-interactions",
"display_name": "can change microphone volume",
+
"display_name": "Can Filter All Interactions",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to change the volume of the microphone.",
+
"description": "Enables agents to filter interactions in the Interaction Search view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,437: Line 5,897:
 
},
 
},
 
{
 
{
"id": "privilege.sipendpoint.can-change-speaker-volume",
+
"id": "privilege.contact.can-search-all-interactions",
"display_name": "can change speaker volume",
+
"display_name": "Can Search All Interactions",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables agents to change the volume of the speaker.",
+
"description": "Enables agents to search among all interactions.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,450: Line 5,911:
 
},
 
},
 
{
 
{
"id": "privilege.sipendpoint.can-mute-microphone",
+
"id": "privilege.contact.can-advanced-search-all-interactions",
"display_name": "Workspace Web SIP Endpoint Options - can mute microphone",
+
"display_name": "Can Do Advanced Search for All Interactions",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables an agent to mute and unmute the microphone. Depends on 'Voice - Can Use Voice Channel' and 'Workspace Web SIP Endpoint Options - Can Use Genesys Softphone'.",
+
"description": "Enables agents to do advanced searches of all interactions.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,463: Line 5,925:
 
},
 
},
 
{
 
{
"id": "privilege.sipendpoint.can-mute-speaker",
+
"id": "privilege.contact.can-filter-my-history",
"display_name": "Workspace Web SIP Endpoint Options - can mute speaker",
+
"display_name": "Can Filter My History",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables an agent to mute and unmute the speaker. Depends on 'Voice - Can Use Voice Channel' and 'Workspace Web SIP Endpoint Options - Can Use Genesys Softphone'.",
+
"description": "Enables agents to filter interactions within the My history view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,476: Line 5,939:
 
},
 
},
 
{
 
{
"id": "sipendpoint.uri",
+
"id": "privilege.contact.can-search-my-history",
"display_name": "Sip Endpoint URI",
+
"display_name": "Can Search My History",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the URI of the SIP endpoint used in connector mode. For example: https://localhost:8000.",
+
"description": "Enables agents to search for interactions in the My History view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A correct uri",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,489: Line 5,953:
 
},
 
},
 
{
 
{
"id": "sipendpoint.sip-server-address",
+
"id": "privilege.contact.can-advanced-search-my-history",
"display_name": "Sip Server Address",
+
"display_name": "Can Do Advanced Search in My History",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "false",
"description": "Specifies the host name or IP Address of the Session Border Controller where the SIP REGISTER request will be sent by Workspace Endpoint. If this option is empty, the SIP REGISTER request will be sent to the address specified in the TServer option sip-address of the SIP Server that monitors the DN of this agent. In Business Continuity environment this corresponds to the preferred site registration. (Tip: To set the Domain\\/Realm of your contact center instead of an IP when Workspace SIP Endpoint tries to register through a session border controller (SBC) device, set the value of the this option to the FQDN of your domain instead of just the IP Address).",
+
"description": "Enables agents to do advanced searches within My History.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A correct uri",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,502: Line 5,967:
 
},
 
},
 
{
 
{
"id": "sipendpoint.sip-server-address.peer",
+
"id": "privilege.contact.can-use-conversations",
"display_name": "Workspace Web SIP Endpoint Options - Sip Server Address",
+
"display_name": "Can display interactions in conversations View",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "In a Business Continuity environment, specifies the host name or IP Address of the Session Border Controller where the peer SIP REGISTER request will be sent by Workspace SIP Endpoint. If this option is empty, the SIP REGISTER request will be sent to the address specified in the TServer option sip-address of the SIP Server that monitors the DN of this agent. In Business Continuity environment this corresponds to the peer site registration. (Tip: To set the Domain\\/Realm of your contact center instead of an IP when Workspace SIP Endpoint tries to register through a session border controller (SBC) device, set the value of the this option to the FQDN of your domain instead of just the IP Address).",
+
"description": "Enables agent to toggle the interaction display format from flat view to the threaded conversations view.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Any valid host name (either with or without a Fully Qualified Domain Name) or IP Address.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,515: Line 5,981:
 
},
 
},
 
{
 
{
"id": "sipendpoint.register-interval",
+
"id": "contact.history-default-view-conversations",
"display_name": "Register Interval",
+
"display_name": "Display interactions in conversations View by default",
 
"type": "config",
 
"type": "config",
"default_value": "1500",
+
"default_value": "false",
"description": "Specifies the interval, in milliseconds, between each register on Genesys Softphone.",
+
"description": "Specifies whether the My History and Contact History are displayed in conversation (thread) mode or Normal (flat) mode, by default.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid integer",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,528: Line 5,995:
 
},
 
},
 
{
 
{
"id": "sipendpoint.wait-user-max-attempts",
+
"id": "contact.last-called-agent.enable",
"display_name": "Max Check Waiting User Failed",
+
"display_name": "Enable Last Called Agent",
 
"type": "config",
 
"type": "config",
"default_value": "20",
+
"default_value": "false",
"description": "Specifies the number of failed waiting user-actions that are allowed before timeout.",
+
"description": "Specifies if the last called agent properties are set in the contact when an interaction is presented to the agent. This option is taken into account only when the contact.last-called-agent.<media-type>.enable option is not defined for the applicable media type.",
 +
"version": "9.0.000.21",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid integer",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,541: Line 6,009:
 
},
 
},
 
{
 
{
"id": "sipendpoint.register-max-attempts",
+
"id": "contact.last-called-agent.<media-type>.enable",
"display_name": "Max Check Activation Failed",
+
"display_name": "Enable Last Called Agent",
 
"type": "config",
 
"type": "config",
"default_value": "10",
+
"default_value": "false",
"description": "Specifies the number of 'failed on check if endpoint' is active allowed.",
+
"description": "Specifies if the last called agent properties are set in the contact when an interaction of the corresponding media type is presented to the agent. This option overrides the contact.last-called-agent.enable option. Use the voice-campaign media-type to define the look-up behavior for outbound campaign interactions.",
 +
"version": "9.0.000.21",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid integer",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,554: Line 6,023:
 
},
 
},
 
{
 
{
"id": "sipendpoint.ping-interval",
+
"id": "privilege.contact.can-use-contact-myhistory",
"display_name": "Ping Interval",
+
"display_name": "Can Use My Contact History",
 
"type": "config",
 
"type": "config",
"default_value": "2000",
+
"default_value": "false",
"description": "Specifies the interval, in milliseconds, between each ping of the Genesys Softphone.",
+
"description": "Enables an agent to access their own history of interactions with contacts.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid integer",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,567: Line 6,037:
 
},
 
},
 
{
 
{
"id": "sipendpoint.max-failed-ping",
+
"id": "privilege.contact.can-use-assign-contact",
"display_name": "Max Ping Failed",
+
"display_name": "Can Assign Contact",
 
"type": "config",
 
"type": "config",
"default_value": "5",
+
"default_value": "false",
"description": "Specifies the number of failed pings allowed on Genesys Softphone.",
+
"description": "Enables agents to assign a contact to an interaction.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid integer",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,580: Line 6,051:
 
},
 
},
 
{
 
{
"id": "sipendpoint.transport-protocol",
+
"id": "privilege.screen-recording.can-use",
"display_name": "Workspace Web SIP Endpoint Options - Transport Protocol",
+
"display_name": "Can Use",
 
"type": "config",
 
"type": "config",
"default_value": "UDP",
+
"default_value": "false",
"description": "Specifies whether UDP, TCP, TLS, HTTP, or HTTPS is used for the SIP transport protocol.",
+
"description": "Enables the usage of Screen Recording Client.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Select a value from the following list: UDP, TCP, TLS, HTTP, HTTPS.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,593: Line 6,065:
 
},
 
},
 
{
 
{
"id": "sipendpoint.headset-unplugged-set-not-ready",
+
"id": "screen-recording.client.address",
"display_name": "Not Ready when Headset is Unplugged",
+
"display_name": "Client address",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "127.0.0.1",
"description": "Specifies whether the agent SIP DN is set automatically to Not Ready when the headset that is configured for the agent is unplugged.",
+
"description": "Specifies the IP address or host name on which Screen Recording Client listens for credentials.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "String corresponding to the Screen Recording Client ip address or host name",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,606: Line 6,079:
 
},
 
},
 
{
 
{
"id": "sipendpoint.headset-unplugged.not-ready-reason",
+
"id": "screen-recording.client.port",
"display_name": "Not Ready Reason on Headset Unplugged Detection",
+
"display_name": "Client Port",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "443",
"description": "Specifies the Not Ready reason that is to be set for the SIP DN when the headset that is used by the agent is unplugged if the value of the sipendpoint.headset-unplugged-set-not-ready option is set to true.",
+
"description": "Specifies the port on which Screen Recording Client listens for credentials.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid not ready reason",
+
"data_type": "String corresponding to the Screen Recording Client port number",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,619: Line 6,093:
 
},
 
},
 
{
 
{
"id": "sipendpoint.enable-webrtc-auth",
+
"id": "screen-recording.client.secure-connection",
"display_name": "Enable WebRTC Auth with OAuth 2 protocol",
+
"display_name": "Flag specifying if to use secure connection to Screen Recording Client",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies whether the Softphone authenticates using the OAuth 2 protocol.",
+
"description": "Specifies whether a secure connection is used for communication with Screen Recording Client",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "True or false, specifying if secure connection will be used",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,632: Line 6,107:
 
},
 
},
 
{
 
{
"id": "sipendpoint.enable-auto-mute",
+
"id": "screen-recording.client.server-url",
"display_name": "Auto mute/unmute speakers and microphone if volume is 0",
+
"display_name": "Specifies the GWS Server address for SRS.",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether mute and unmute are done automatically when agent sets speaker or microphone volume to 0.",
+
"description": "Defines the address of the RWS server to be used for communication by Screen Recording Client. The field code &#36;GWS_URL&#36; is supported allowing to specify the usage of the same origin as WWE UI. If the option is empty, the WWE UI origin is used. A list of RWS/WWE UI pairs can be defined based on the pattern: <rws_origin_url>(<wwe_origin_url>). This list could be based on a single pair. In case of none matching, the default behavior is used.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false",
+
"data_type": "Valid URL",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,645: Line 6,121:
 
},
 
},
 
{
 
{
"id": "privilege.mychannels.can-use",
+
"id": "privilege.interaction-management.can-use",
"display_name": "Can Use My Channels",
+
"display_name": "Can Use",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to access the My Channels tab.",
+
"description": "Enables supervisors to access the Interaction Management feature.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,658: Line 6,135:
 
},
 
},
 
{
 
{
"id": "privilege.mychannels.pending-state.can-use",
+
"id": "privilege.interaction-management.case-data.can-edit",
"display_name": "Can Use Pending State in My Channels",
+
"display_name": "Can Edit case Data",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables the pending state to be displayed in the My Channels view while the agent is engaged in a call, chat, or email interaction. When the value of this option is set to true, if an agent sets his or her status to Not Ready or Not Ready Reason while he or she is still handling an interaction, the timer for that state will not start until the call is released, the chat is ended, or the email is sent or put into a workbin.",
+
"description": "Enables supervisors to edit case data for interactions directly from Workbins and Interaction Queues without pulling the interactions first.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,671: Line 6,149:
 
},
 
},
 
{
 
{
"id": "privilege.security.can-change-password",
+
"id": "privilege.interaction-management.can-move-to-queue",
"display_name": "Can Manually Change Password",
+
"display_name": "Can Move to queue",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables an agent to change their own password by using a menu action.",
+
"description": "Enables supervisors to move interactions to a queue.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,684: Line 6,163:
 
},
 
},
 
{
 
{
"id": "login.show-change-account-link",
+
"id": "privilege.interaction-management.can-move-to-workbin",
"display_name": "Show Change Account Link",
+
"display_name": "Can Move to Workbins",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Show or Hide the change login account link on login error page and second step login page.",
+
"description": "Enables supervisors to move interactions to a workbin.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,697: Line 6,177:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-use",
+
"id": "privilege.interaction-management.can-search-interactions",
"display_name": "Can Use Voice Channel",
+
"display_name": "Can Search interactions",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables the agent to use the Voice channel.",
+
"description": "Enables agents to search for interactions in interaction queues content.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,710: Line 6,191:
 
},
 
},
 
{
 
{
"id": "privilege.voice-history.can-click-to-dial",
+
"id": "interaction-management.available-interaction-page-sizes",
"display_name": "Can Click to Dial",
+
"display_name": "Available Content Page Sizes",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "5,10,25,50",
"description": " Enables an agent to use the Click-to-dial feature to dial a voice call from the Details tab of the history of a voice interaction in any History view.",
+
"description": "Specifies the possible values for the number of rows per page in the Interaction Management content view. Values grater than 100 are not recommended due to performance impact. The maximum value depends on the content of interactions and the robustness of your network. If you specify a value that is too high, the request to get a snapshot fails and an error message is displayed.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,723: Line 6,205:
 
},
 
},
 
{
 
{
"id": "privilege.voice-history.can-click-to-search",
+
"id": "interaction-management.default-interaction-page-size",
"display_name": "Can Click to Search",
+
"display_name": "Default content page size",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "10",
"description": "Enables an agent to use Click-to-search to open the Contact Directory by clicking a Contact name in the Details tab of the My History or Interaction Search views.",
+
"description": "Specifies the default value for the number of rows per page in the Interaction Management content view.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,736: Line 6,219:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-use",
+
"id": "interaction-management.filters",
"display_name": "Can Use Chat Channel",
+
"display_name": "Filters",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables the agent to use the Chat channel.",
+
"description": "Specifies the filters that are displayed to the supervisor for interaction management. The filter names refer to the names of the Application Option sections that define the Filters. See 'Creating Interaction Filters for Team Leads' in the Configuration Guide for more information.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of Filter names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,749: Line 6,233:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-decline",
+
"id": "interaction-management.interactions-filter.displayed-columns",
"display_name": "Can Decline",
+
"display_name": "Displayed Columns Configuration of Interaction Queue",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "From,To,Subject,Received",
"description": "Enables the agent to decline incoming chat interactions.",
+
"description": "Specifies the list of interaction fields that are displayed as columns in Interaction Queue view when displayed-columns is not defined in the Filter.",
 +
"version": "9.0.000.19",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of attached data, for example: From,Subject,Received",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,762: Line 6,247:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-release",
+
"id": "interaction-management.filters.quick-search-attributes",
"display_name": "Can Release",
+
"display_name": "Quick Search Attributes of Interaction Queue",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables the agent to manually end chat conversations.",
+
"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in an interaction queue for which quick-search-attributes is not defined in the Filter.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of attached data, for example: AssignedTo,FromAddress",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,775: Line 6,261:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-release-consultation",
+
"id": "interaction-management.move-to-workbin.restrict-to-my-team",
"display_name": "Can Release consultation",
+
"display_name": "restrict move to workbins to workbins of the logged agent team.",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables the agent to manually end chat consultations.",
+
"description": "Specifies if the search applied in Team Communicator for Move to Workbin action should be restricted to the workbins of the logged agent team.",
 +
"version": "9.0.000.48",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,788: Line 6,275:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-set-interaction-disposition",
+
"id": "interaction-management.markdone.mandatory-case-data-check.enable",
"display_name": "Can Set Interaction Disposition",
+
"display_name": "Mandatory case data check before Mark Done.",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to set the disposition code on chat interactions.",
+
"description": "Specifies if a check is to be made to ensure interactions are not missing mandatory case data before they are allowed to be marked done.",
 +
"version": "9.0.000.94",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,801: Line 6,289:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-two-step-transfer",
+
"id": "privilege.monitor-dashboard.can-use",
"display_name": "Can Two Step Transfer",
+
"display_name": "Can use the Dashboard",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables chat transfer in two steps, started by a chat consultation.",
+
"description": "Enables the Contact Center Statistics dashboard tab.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,814: Line 6,303:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-two-step-conference",
+
"id": "statistics.default-page-size",
"display_name": "Can Two Step Conference",
+
"display_name": "Default page size",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "50",
"description": "Enables chat conference in two steps, started by a chat consultation.",
+
"description": "Specifies the default value for the number of statistics objects per page in the Contact Center Statistics view. The value must be defined in the option statistics.available-page-size.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 10 through 100.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,827: Line 6,317:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-consult",
+
"id": "statistics.available-page-sizes",
"display_name": "Can Use Chat Consult",
+
"display_name": "Available page sizes",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "10,20,30",
"description": "Enables the agent to use the Chat consultation feature.",
+
"description": "Specifies the possible values for the number of statistics objects per page in the contact center statistics view.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of numbers that define the number of statistics objects per result page from which the agent can make selections.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,840: Line 6,331:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-one-step-conference",
+
"id": "statistics.routing-points",
"display_name": "Can One Step Conference",
+
"display_name": "List of routing points displayed in the dashboard, and in Contact Center Statistics",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables the agent to use the instant chat conference feature.",
+
"description": "Specifies the list of routing points that are displayed in the Contact Center Statistics tab. If empty, no routing points are displayed. If set to a list and none of the routing points match an existing routing point, no routing points are displayed.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,853: Line 6,345:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-one-step-transfer",
+
"id": "statistics.agent-groups",
"display_name": "Can One Step Transfer",
+
"display_name": "List of agent groups or virtual agent groups displayed in the Contact Center Statistics",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables the agent to use the instant chat transfer feature.",
+
"description": "Specifies the list of agent groups and virtual agent groups that are displayed in the Contact Center Statistics tab. If empty, no agent groups or virtual agent groups are displayed. If set to a list and none of the groups in the list match an existing group, no agent groups or virtual agent groups are displayed.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,866: Line 6,359:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-push-url",
+
"id": "statistics.virtual-queues",
"display_name": "Can Push Url",
+
"display_name": "List of virtual queues displayed in the Contact Center Statistics",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables the agent to push URL's to customers during chat sessions.",
+
"description": "Specifies the list of virtual queues that are displayed in the Contact Center Statistics tab. If empty, no virtual queues are displayed. If set to a list and none of the virtual queues in the list match an existing virtual queue, no virtual queues are displayed.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,879: Line 6,373:
 
},
 
},
 
{
 
{
"id": "privilege.chat.show-monitoring.can-use",
+
"id": "statistics.queue-groups",
"display_name": "Show Monitoring",
+
"display_name": "List of group of queues (dn groups) displayed in the Contact Center Statistics",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables the agent to be informed that the current chat interaction is monitored by a supervisor.",
+
"description": "Specifies the list of queue groups that are displayed in the Contact Center Statistics tab. If empty, no queue groups are displayed. If set to a list and none of the queue groups in the list match an existing queue group, no queue groups are displayed.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,892: Line 6,387:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-click-to-dial",
+
"id": "privilege.my-team-workbins.can-use",
"display_name": "Can Click to Dial",
+
"display_name": "Can Use My Team Workbins",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables the agent to use the Click to Dial feature in chat based on the expression.identify.phone-number option to detect phone numbers.",
+
"description": "Enables access to My Team Workbins.",
 +
"version": "9.0.000.20",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 5,905: Line 6,401:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-click-to-email",
+
"id": "my-team-workbins.agent-page-size",
"display_name": "Can Click to Email",
+
"display_name": "Agent page size",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "10",
"description": "Enables the agent to use the Click to Email feature in chat based on the expression.identify.email-address option to detect email addresses.",
+
"description": "Specifies the value for the number of agents per page in My Team Workbins sub-tree of My Workbins view.",
 +
"version": "9.0.000.30",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,918: Line 6,415:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-place-on-hold-async",
+
"id": "workbin.email.draft",
"display_name": "Can Place on Hold Async Chat",
+
"display_name": "Draft E-Mail workbin",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables the agent to put on hold an async chat.",
+
"description": "Specifies the name of the workbin to be used to store draft email.",
 +
"version": "9.0.000.12",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,931: Line 6,429:
 
},
 
},
 
{
 
{
"id": "chat.os-emoji-is-enabled",
+
"id": "workbin.email.in-progress",
"display_name": "Use the native OS Emojis in Chat",
+
"display_name": "In Progress E-Mail workbin",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Specifies whether emojis are displayed as images or as standard OS/browser emojis.",
+
"description": "Specifies the name of the workbin that is to be used to store inbound email for later processing, after an agent explicitly saved the email or submitted an outbound reply.",
 +
"version": "9.0.000.12",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,944: Line 6,443:
 
},
 
},
 
{
 
{
"id": "privilege.chat.can-use-emoji-picker",
+
"id": "workbin.email.in-progress.displayed-columns",
"display_name": "Can Use the Emoji Picker in Chat",
+
"display_name": "In Progress E-mail workbin Displayed Columns",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "From,Subject,Received",
"description": "Enables the agent to use an emoji picker.",
+
"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores inbound email for later processing.",
 +
"version": "9.0.000.12",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Comma-separated list of Interaction Server interaction properties, for example: From,Subject,Received",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,957: Line 6,457:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-use",
+
"id": "workbin.email.draft.displayed-columns",
"display_name": "Can Use E-mail Channel",
+
"display_name": "Draft E-Mail workbin Displayed Columns",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "To,Subject,Submitted",
"description": "Enables the agent is use the Email channel.",
+
"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores draft email interactions.",
 +
"version": "9.0.000.12",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Comma-separated list of Interaction Server interaction properties, for example: To,Subject,Submitted",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,970: Line 6,471:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-mark-done",
+
"id": "workbin.email.review",
"display_name": "Can Mark Done Interaction",
+
"display_name": "QA Review E-Mail workbin",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables the agent to mark done an interaction without further processing.",
+
"description": "Specifies the name of the workbin that is to be used to store QA reviews for later processing, after a reviewer explicitly saved the email.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,983: Line 6,485:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-click-to-dial",
+
"id": "workbin.email.review.displayed-columns",
"display_name": "Can Click to Dial",
+
"display_name": "QA Review E-Mail workbin Displayed Columns",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "To,Subject,Submitted",
"description": "Enables the agent to use the Click to Dial feature in email based on the expression.identify.phone-number option to detect phone numbers.",
+
"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores QA reviews.",
 +
"version": "9.0.000.16",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Comma-separated list of Interaction Server interaction properties, for example: To,Subject,Submitted",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 5,996: Line 6,499:
 
},
 
},
 
{
 
{
"id": "privilege.email.can-decline",
+
"id": "workbin.<media-type>.in-progress",
"display_name": "Can Decline",
+
"display_name": "Template for Workitem Workbin declaration",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables the agent to decline incoming email interactions. Depends on 'Email - Can Use Email Channel'.",
+
"description": "Specifies the name of the workbin to be used to store interactions of a particular workitem media type. Agents can open interactions from this workbin but not save interactions in it.",
 +
"version": "9.0.000.24",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,009: Line 6,513:
 
},
 
},
 
{
 
{
"id": "privilege.workbins.can-use",
+
"id": "workbin.<media-type>.<workbin-nickname>",
"display_name": "Can Use Workbins",
+
"display_name": "Template for Custom Workbin declaration",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables agents to access My Team Workbins.",
+
"description": "Specifies the name of the workbin to be used to store interactions of a particular workitem media type. Agents can open interactions from this workbin but not save interactions in it.",
 +
"version": "9.0.000.24",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,022: Line 6,527:
 
},
 
},
 
{
 
{
"id": "privilege.workitem-channels.can-use",
+
"id": "workbin.<media-type>.<workbin-nickname>.displayed-columns",
"display_name": "Can Use All Channels",
+
"display_name": "Template for Displayed Columns Configuration of a Custom Workbin",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "From,To,Subject,Received",
"description": "Enables agents to use all WorkItem channels configured in the openmedia.workitem-channels option.",
+
"description": "Specifies the list of interaction fields displayed as columns in the specified workbin.",
 +
"version": "9.0.000.24",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of Interaction Server interaction properties, for example: From,Subject,Received",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,035: Line 6,541:
 
},
 
},
 
{
 
{
"id": "privilege.<media-type>.can-mark-done",
+
"id": "workbin.quick-search-attributes",
"display_name": "Can Mark Done Interaction",
+
"display_name": "Quick Search Attributes of Workbin",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables agents to mark done an interaction without further processing.",
+
"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in a workbin for which workbin.<media-type>.<workbin-nickname>.quick-search-attributes is not defined.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of Interaction Server interaction properties, for example: AssignedTo,FromAddress",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,048: Line 6,555:
 
},
 
},
 
{
 
{
"id": "privilege.<media-type>.can-decline",
+
"id": "workbin.<media-type>.<workbin-nickname>.quick-search-attributes",
"display_name": "Can Decline",
+
"display_name": "Template for Interaction Quick Search Attributes Configuration of a Custom Workbin",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables agents to decline incoming workitem interactions. Depends on 'Workitem - Can Use Workitem Channel'.",
+
"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in the specified workbin. Default value of this option is the Value of workbin.quick-search-attributes if defined.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of Interaction Server interaction properties, for example: AssignedTo,FromAddress",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,061: Line 6,569:
 
},
 
},
 
{
 
{
"id": "privilege.<media-type>.can-one-step-transfer",
+
"id": "privilege.workbin.can-search-my-workbins-trees",
"display_name": "Can One Step Transfer",
+
"display_name": "Can Search Workbin",
 
"type": "config",
 
"type": "config",
 
"default_value": "true",
 
"default_value": "true",
"description": "Enables agents to use instant workitem transfer. Depends on 'Workitem - Can Use Workitem Channel'.",
+
"description": "Enables agents to search for workbins in the navigation tree of the My Workbins View.",
 +
"version": "9.0.000.30",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 6,074: Line 6,583:
 
},
 
},
 
{
 
{
"id": "privilege.<media-type>.can-set-interaction-disposition",
+
"id": "privilege.workbin.can-search-interactions",
"display_name": "Can Set Interaction Disposition",
+
"display_name": "Can Search interactions",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables agents to set the disposition code of workitem interactions. Depends on 'Workitem - Can Use Workitem Channel'.",
+
"description": "Enables agents to search for interactions in workbins content.",
 +
"version": "9.0.000.39",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 6,087: Line 6,597:
 
},
 
},
 
{
 
{
"id": "privilege.<media-type>.can-move-to-workbin",
+
"id": "teamlead.monitoring-scope",
"display_name": "Can Move Workitem to Workbin",
+
"display_name": "Monitoring Scope",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "call",
"description": "Enables agents to move an interaction to the workbin. Depends on 'Workitem - Can Use Workitem Channel'.",
+
"description": "Specifies the scope of monitoring that is to be used for voice interactions. If the value call is specified, the supervisor remains on the call until it is finished. This mode enables barge-in. If the value agent is specified, the system disconnects the supervisor automatically from the call when the monitored agent leaves the call. In this mode, the barge-in operation is not possible.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Select a value from the following list: agent,call",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,100: Line 6,611:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-use",
+
"id": "teamlead.monitoring-current-call-timeout",
"display_name": "Can Use TeamLead",
+
"display_name": "Monitoring Current Call Timeout",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "0",
"description": "Enables a supervisor to use the agent call and chat monitoring functionality.",
+
"description": "In scenarios where a contact has opted out of call monitoring, use this option to specify the duration before monitoring and coaching of the current call is considered failed due to time out. To disable timeout, specify a value less than 5.",
 +
"version": "9.0.000.76",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value from 5 to 300.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,113: Line 6,625:
 
},
 
},
 
{
 
{
"id": "privilege.myagents.can-use",
+
"id": "teamlead.myagents.default-page-size",
"display_name": "Can Use My Agents View",
+
"display_name": "Default page size",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "10",
"description": "Enables supervisors to access the My Agents view, where they can view and update the state for agents in the groups they supervise. Supervisors can also remotely log off agents from media channels in this view.",
+
"description": "Specifies the default value for the number of rows per page in the My Agents view. The value is added to the list defined by the option teamlead.myagents.available-page-sizes.",
 +
"version": "9.0.000.48",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,126: Line 6,639:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-monitor-voice",
+
"id": "teamlead.myagents.available-page-sizes",
"display_name": "Can Monitor Voice",
+
"display_name": "Available page sizes",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "5,10,25,50",
"description": "Enables a supervisor to monitor voice interactions.",
+
"description": "Specifies the possible values for the number of rows per page in the My Agents view.",
 +
"version": "9.0.000.48",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,139: Line 6,653:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-monitor-chat",
+
"id": "teamlead.myagents.refresh-rate",
"display_name": "Can Monitor Chat",
+
"display_name": "My Agents refresh rate",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "30",
"description": "Enables a supervisor to monitor chat interactions.",
+
"description": "Specifies the frequency, in seconds, to refresh the list of agents. To disable automatic refresh, specify a value less than 5 to indicate manual refresh. Automatic refresh is also disabled if the value of the accessibility.visual-impairment-profile option is true.",
 +
"version": "9.0.000.31",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Valid values are integer values between 5 and 5000. Values less than 5 disables the automatic refresh.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,152: Line 6,667:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-monitor-current-voice",
+
"id": "teamlead.myagents.manual-refresh.enabled",
"display_name": "Can Monitor Current Voice",
+
"display_name": "My Agents enable manual refresh",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Enables a supervisor to monitor the current voice interaction.",
+
"description": "Specifies whether the manual refresh button is displayed in the My Agents view. Manual refresh is automatically enabled if automatic refresh is disabled by the teamlead.myagents.refresh-rate option.",
 +
"version": "9.0.000.31",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,165: Line 6,681:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-coach-voice",
+
"id": "teamlead.myagents.enabled-channels",
"display_name": "Can Coach Voice",
+
"display_name": "My Agents enabled channels",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "voice,chat,email",
"description": "Enables a supervisor to coach voice interactions.",
+
"description": "Specifies the channels that are displayed in the My Agents view. Channels are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.31",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Comma-separated list of channel names from the following list: voice, chat, email, facebook, twitter, workitem",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,178: Line 6,695:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-coach-current-voice",
+
"id": "teamlead.myagents.thresholds.enabled",
"display_name": "Can Coach Current Voice",
+
"display_name": "My Agents enable thresholds",
 
"type": "config",
 
"type": "config",
 
"default_value": "false",
 
"default_value": "false",
"description": "Enables a supervisor to coach the current voice interaction.",
+
"description": "Enable thresholds to be used for channels specified by the teamlead.myagents.thresholds.<media-type> option.",
 +
"version": "9.0.000.31",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,191: Line 6,709:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-coach-chat",
+
"id": "teamlead.myagents.thresholds.<media-type>",
"display_name": "Can Coach Chat",
+
"display_name": "My Agents media thresholds",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Enables a supervisor to coach chat interactions.",
+
"description": "Specifies the name of a threshold section that determine when an agent state is considered to be Busy or Not Ready for the specified channel. You must create the threshold sections on the Application object.",
 +
"version": "9.0.000.31",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A threshold section name.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,204: Line 6,723:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-switch-to-coach-chat",
+
"id": "kpi.displayed-kpis",
"display_name": "Can Switch To Coach for Chat",
+
"display_name": "Displayed KPIs",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables a supervisor to switch to coach mode for monitored chat interactions.",
+
"description": "Specifies the KPIs that are displayed to the agent. The KPI names refer to the names of the Application Option sections that are defining the KPIs.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of KPI names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,217: Line 6,737:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-switch-to-barge-in-voice",
+
"id": "privilege.performance-tracker.can-use",
"display_name": "Can Switch To BargeIn for Voice",
+
"display_name": "Can use Performance Tracker",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables a supervisor to switch to barge-in mode for monitored voice interactions.",
+
"description": "Enables access to the Performance Tracker",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 6,230: Line 6,751:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-switch-to-barge-in-chat",
+
"id": "statistics.displayed-statistics",
"display_name": "Can Switch To BargeIn for Chat",
+
"display_name": "Displayed Statistics",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables a supervisor to switch to barge-in mode for monitored chat interactions.",
+
"description": "Specifies the statistics that are displayed in the Contact Center Statistics tab. The statistics specified by this option match the names of the statistics defined in the options of the Application sections.",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of Statistic names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,243: Line 6,765:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-stop-monitoring-voice",
+
"id": "statistics.gadget-statistics",
"display_name": "Can Stop Monitoring Voice",
+
"display_name": "Gadget Statistics displayed",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables a supervisor to stop monitoring voice interactions.",
+
"description": "Specifies the statistics, up to 10, that are displayed in the Statistics Gadget. Each statistics specified in this option is the name of a section containing the statistic definition or the statistic object.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A comma-separated list of Statistic names.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,256: Line 6,779:
 
},
 
},
 
{
 
{
"id": "privilege.teamlead.can-stop-monitoring-chat",
+
"id": "statistics.gadget-statistics.max-size",
"display_name": "Can Stop Monitoring Chat",
+
"display_name": "Maximum quantity of Gadget Statistics displayed",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "10",
"description": "Enables a supervisor to stop monitoring chat interactions.",
+
"description": "Specifies the maximum number of statistics that are displayed in the Statistics Gadget. If more statistics are specified by the statistics.gadget-statistics option, only the first 'n' statistics are displayed.",
 +
"version": "9.0.000.17",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value from 1 through 50.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,269: Line 6,793:
 
},
 
},
 
{
 
{
"id": "privilege.voice.can-send-dtmf",
+
"id": "statistics.refresh-time",
"display_name": "Can Send DTMF",
+
"display_name": "Refresh Time",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "20",
"description": "Enables agents to send DTMF during a voice call by using the on screen number keypad.",
+
"description": "Specifies, in seconds, how often statistics are refreshed in the Contact Center Statistics tab. When set to 0, no automatic refresh occurs (the agent must manually refresh statistics).",
 +
"version": "9.0.000.10",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "An integer value greater than 0.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,282: Line 6,807:
 
},
 
},
 
{
 
{
"id": "privilege.voice.show-monitoring.can-use",
+
"id": "privilege.sipendpoint.can-use",
"display_name": "Show Monitoring",
+
"display_name": "Can Use Genesys Softphone",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables agents to be notified that the current call is monitored by a supervisor.",
+
"description": "Enables the usage of Genesys Softphone. Depends on 'Voice - Can Use Voice Channel'.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 6,295: Line 6,821:
 
},
 
},
 
{
 
{
"id": "privilege.active-recording.can-use",
+
"id": "privilege.sipendpoint.can-change-microphone-volume",
"display_name": "Can Use",
+
"display_name": "can change microphone volume",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to use the Active Recording functionality.",
+
"description": "Enables agents to change the volume of the microphone.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,308: Line 6,835:
 
},
 
},
 
{
 
{
"id": "privilege.active-recording.can-monitor-recording",
+
"id": "privilege.sipendpoint.can-change-speaker-volume",
"display_name": "Can Monitor Voice Recording",
+
"display_name": "can change speaker volume",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Specifies whether the call monitoring indicator is displayed to agents when their calls are being recorded. The Call Recording functionality (for VoIP\\/SIP enabled agents only) enables you to record the current voice interaction with a contact or an internal target.",
+
"description": "Enables agents to change the volume of the speaker.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,321: Line 6,849:
 
},
 
},
 
{
 
{
"id": "privilege.active-recording.can-start",
+
"id": "privilege.sipendpoint.can-mute-microphone",
"display_name": "Can Start",
+
"display_name": "Workspace Web SIP Endpoint Options - can mute microphone",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to start the Active Recording.",
+
"description": "Enables an agent to mute and unmute the microphone. Depends on 'Voice - Can Use Voice Channel' and 'Workspace Web SIP Endpoint Options - Can Use Genesys Softphone'.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,334: Line 6,863:
 
},
 
},
 
{
 
{
"id": "privilege.active-recording.can-stop",
+
"id": "privilege.sipendpoint.can-mute-speaker",
"display_name": "Can Stop",
+
"display_name": "Workspace Web SIP Endpoint Options - can mute speaker",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "false",
"description": "Enables an agent to stop the Active Recording.",
+
"description": "Enables an agent to mute and unmute the speaker. Depends on 'Voice - Can Use Voice Channel' and 'Workspace Web SIP Endpoint Options - Can Use Genesys Softphone'.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,347: Line 6,877:
 
},
 
},
 
{
 
{
"id": "privilege.active-recording.can-resume",
+
"id": "sipendpoint.uri",
"display_name": "Can Resume",
+
"display_name": "Sip Endpoint URI",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to resume the Active Recording.",
+
"description": "Specifies the URI of the SIP endpoint used in connector mode. For example: https://localhost:8000.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A correct uri",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,360: Line 6,891:
 
},
 
},
 
{
 
{
"id": "privilege.active-recording.can-pause",
+
"id": "sipendpoint.sip-server-address",
"display_name": "Can Pause",
+
"display_name": "Sip Server Address",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables an agent to pause the Active Recording.",
+
"description": "Specifies the FQDN, hostname, or IP Address of the SIP Entity (Session Border Controller, SIP Proxy, SIP Server) where the SIP REGISTER request will be sent by Genesys Softphone. In a Business Continuity environment designed for dual SIP registration, this corresponds to the preferred site registration (Tip: To set the Domain\\/Realm of your contact center instead of an IP when Workspace SIP Endpoint tries to register through a session border controller (SBC) device, set the value of this option to the FQDN of your domain instead of just the IP Address).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A correct URI. In case of DNS SRV: <FQDN>; in case of A-Record: <FQDN>:<port>; for IP Address: <IP>:<port>.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,373: Line 6,905:
 
},
 
},
 
{
 
{
"id": "privilege.teamcommunicator.can-use",
+
"id": "sipendpoint.sip-server-address.peer",
"display_name": "Can Use",
+
"display_name": "Workspace Web SIP Endpoint Options - Sip Server Address",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "No default value",
"description": "Enables access to the Team Communicator.",
+
"description": "In a Business Continuity environment designed for dual SIP registration, specifies the FQDN, hostname, or IP Address of the SIP Entity (Session Border Controller, SIP Proxy, SIP Server) corresponding to the secondary SIP destination where the SIP REGISTER request will be sent by Genesys Softphone (Tip: To set the Domain\\/Realm of your contact center instead of an IP when Workspace SIP Endpoint tries to register through a session border controller (SBC) device, set the value of this option to the FQDN of your domain instead of just the IP Address).",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A correct URI. In case of DNS SRV: <FQDN>; in case of A-Record: <FQDN>:<port>; for IP Address: <IP>:<port>.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,386: Line 6,919:
 
},
 
},
 
{
 
{
"id": "privilege.teamcommunicator.can-view-all",
+
"id": "sipendpoint.register-max-attempts",
"display_name": "Can Search All",
+
"display_name": "Max Check Activation Failed",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "10",
"description": "Enables an agent to search within all internal targets and contacts in Team Communicator.",
+
"description": "Specifies the number of checks after a registration request is made that Workspace makes while waiting for Genesys Softphone to become active.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,399: Line 6,933:
 
},
 
},
 
{
 
{
"id": "privilege.teamcommunicator.can-view-favorites",
+
"id": "sipendpoint.register-interval",
"display_name": "Can View Favorites",
+
"display_name": "Register Interval",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "1500",
"description": "Enables an agent to view favorites in Team Communicator.",
+
"description": "Specifies the interval, in milliseconds, that Workspace waits between each check for the successful registration to Genesys Softphone. The number of attempted checks is specified by the sipendpoint.register-max-attempts option.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,412: Line 6,947:
 
},
 
},
 
{
 
{
"id": "privilege.teamcommunicator.can-view-recent-calls",
+
"id": "sipendpoint.wait-user-max-attempts",
"display_name": "Can View Recent Calls",
+
"display_name": "Max Check Waiting User Failed",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "20",
"description": "Enables an agent to view recently contacted resources in Team Communicator.",
+
"description": "Specifies the number of failed waiting user-actions that are allowed before timeout.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,425: Line 6,961:
 
},
 
},
 
{
 
{
"id": "privilege.teamcommunicator.can-manage-favorites",
+
"id": "sipendpoint.ping-interval",
"display_name": "Can Manage Favorites",
+
"display_name": "Ping Interval",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "2000",
"description": "Enables an agent to add, edit, and remove personal favorites in Team Communicator.",
+
"description": "Specifies the interval, in milliseconds, between each ping of the Genesys Softphone.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,438: Line 6,975:
 
},
 
},
 
{
 
{
"id": "privilege.teamcommunicator.display-agent-groups-availability",
+
"id": "sipendpoint.max-failed-ping",
"display_name": "Display agent Groups availability",
+
"display_name": "Max Ping Failed",
 
"type": "config",
 
"type": "config",
"default_value": "true",
+
"default_value": "5",
"description": "Enables an agent to view the number of agents in the Ready state in agent groups in Team Communicator. Depends on 'Team Communicator - Can Use' and 'Team Communicator - Can View Favorites'.",
+
"description": "Specifies the number of failed pings allowed on Genesys Softphone.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,451: Line 6,989:
 
},
 
},
 
{
 
{
"id": "accessibility.focus-on-interaction-toast",
+
"id": "sipendpoint.transport-protocol",
"display_name": "Focus on interaction toast",
+
"display_name": "Workspace Web SIP Endpoint Options - Transport Protocol",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "UDP",
"description": "Specifies whether all Interaction Notification views receive the focus when they are displayed. This option does not rely on accessibility.visual-impairment-profile; therefore, it applies to all configured agents, not just visually impaired agents.",
+
"description": "Specifies whether UDP, TCP, TLS, HTTP, or HTTPS is used for the SIP transport protocol.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "Select a value from the following list: UDP, TCP, TLS, HTTP, HTTPS.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,464: Line 7,003:
 
},
 
},
 
{
 
{
"id": "accessibility.<media-type>.focus-on-interaction-toast",
+
"id": "sipendpoint.headset-unplugged-set-not-ready",
"display_name": "Focus on interaction toast",
+
"display_name": "Not Ready when Headset is Unplugged",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies whether all Interaction Notification views receive the focus when they are displayed. This option does not rely on accessibility.visual-impairment-profile; therefore, it applies to all configured agents, not just visually impaired agents.",
+
"description": "Specifies whether the agent SIP DN is set automatically to Not Ready when the headset that is configured for the agent is unplugged.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,477: Line 7,017:
 
},
 
},
 
{
 
{
"id": "accessibility.visual-impairment-profile",
+
"id": "sipendpoint.headset-unplugged.not-ready-reason",
"display_name": "Activate Visual Impairment Profile",
+
"display_name": "Not Ready Reason on Headset Unplugged Detection",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "No default value",
"description": "Specifies whether the profile for visually impaired users is active. This option enables users to navigate interface elements from keyboard navigation and tooltips by using a Screen Reader application. Some components might change their behavior in this mode. For example, Team Communicator is collapsed in this configuration.",
+
"description": "Specifies the Not Ready reason that is to be set for the SIP DN when the headset that is used by the agent is unplugged if the value of the sipendpoint.headset-unplugged-set-not-ready option is set to true.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "true, false.",
+
"data_type": "A valid not ready reason",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,490: Line 7,031:
 
},
 
},
 
{
 
{
"id": "editor.fonts",
+
"id": "sipendpoint.disconnected.not-ready-reason",
"display_name": "Fonts",
+
"display_name": "Not Ready Reason on SIP Endpoint connectivity loss",
 
"type": "config",
 
"type": "config",
"default_value": "Serif,Sans-serif,Monospace,Cursive,Fantasy,Tahoma,Roboto,Arial,Helvetica",
+
"default_value": "No default value",
"description": "Specifies the list of available fonts in the Fonts menu of new and reply HTML format email interactions. The fonts are displayed in the order in which they appear in the list.",
+
"description": "Specifies the Not Ready reason that is to be set for the SIP DN when the SIP Endpoint is considered as disconnected.",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of fonts from the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto, Arial, Helvetica.",
+
"data_type": "A valid not ready reason",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,503: Line 7,045:
 
},
 
},
 
{
 
{
"id": "editor.default-font",
+
"id": "sipendpoint.disconnected.max-attempts-to-set-not-ready",
"display_name": "Default font",
+
"display_name": "Max Ping Failed before NotReady state",
 
"type": "config",
 
"type": "config",
"default_value": "Serif",
+
"default_value": "1",
"description": "Specifies the default font in the Font menu of new and reply HTML format email  interactions. If this option is left empty, the last selected font is used for email interactions by default.",
+
"description": "Specifies the maximum number of failed pings with SIP Endpoint before the voice channel state is changed to NotReady (with an eventual reason code specified by option 'sipendpoint.disconnected.not-ready-reason').",
 +
"version": "9.0.000.88",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto. Empty means no default font specified.",
+
"data_type": "A valid integer",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,516: Line 7,059:
 
},
 
},
 
{
 
{
"id": "editor.font-sizes",
+
"id": "sipendpoint.enable-auto-mute",
"display_name": "Font sizes",
+
"display_name": "Auto mute/unmute speakers and microphone if volume is 0",
 
"type": "config",
 
"type": "config",
"default_value": "8,9,10,11,12,14,16,18,20,22,24,26,28,36,48,72",
+
"default_value": "false",
"description": "Specifies the font sizes available in the Font Size menu of new and reply HTML formatted email interactions. The sizes are displayed in the order in which they appear in the list.",
+
"description": "Specifies whether mute and unmute are done automatically when agent sets speaker or microphone volume to 0.",
 +
"version": "9.0.000.35",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of font sizes from the following list: 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72.",
+
"data_type": "true, false",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,529: Line 7,073:
 
},
 
},
 
{
 
{
"id": "editor.default-font-size",
+
"id": "privilege.mychannels.can-use",
"display_name": "Default font size",
+
"display_name": "Can Use My Channels",
 
"type": "config",
 
"type": "config",
"default_value": "9",
+
"default_value": "true",
"description": "Specifies the default font size in the Font Size menu of new and reply HTML formatted email interactions. If empty, the last selected font size is used for email interactions by default.",
+
"description": "Enables an agent to access the My Channels tab.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A value from the following list: the following list: 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72. Empty means no default font size specified.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,542: Line 7,087:
 
},
 
},
 
{
 
{
"id": "editor.SRL.shortcuts.prefix",
+
"id": "privilege.mychannels.pending-state.can-use",
"display_name": "Editor Shortcuts Prefix",
+
"display_name": "Can Use Pending State in My Channels",
 
"type": "config",
 
"type": "config",
"default_value": "#",
+
"default_value": "false",
"description": "Specifies the prefix, such as '#', that identifies that a keyword is a shortcut for a Standard Response.",
+
"description": "Enables the pending state to be displayed in the My Channels view while the agent is engaged in a call, chat, or email interaction. When the value of this option is set to true, if an agent sets his or her status to Not Ready or Not Ready Reason while he or she is still handling an interaction, the timer for that state will not start until the call is released, the chat is ended, or the email is sent or put into a workbin.",
 +
"version": "9.0.000.07",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid character.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,555: Line 7,101:
 
},
 
},
 
{
 
{
"id": "security.web-content.sandbox-rights.default-authorizations",
+
"id": "privilege.security.can-change-password",
"display_name": "List of default sandbox rights authorization options for the embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes)",
+
"display_name": "Can Manually Change Password",
 
"type": "config",
 
"type": "config",
"default_value": "ALLOW-SCRIPTS,ALLOW-FORMS,ALLOW-POPUPS,ALLOW-SAME-ORIGIN",
+
"default_value": "false",
"description": "Specifies the default sandbox rights authorization options that are set up to embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes), in order to remove restrictions and enable features.",
+
"description": "Enables an agent to change their own password by using a menu action.",
 +
"version": "9.0.000.71",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "Comma-separated list of default sandbox rights authorization that are set up for the embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes) in order to unlock some security restrictions : ALLOW-SCRIPTS, ALLOW-FORMS, ALLOW-POPUPS, ALLOW-SAME-ORIGIN, ALLOW-PRESENTATION, ALLOW-POINTER-LOCK",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,568: Line 7,115:
 
},
 
},
 
{
 
{
"id": "workspace-toolkit.enable",
+
"id": "login.show-change-account-link",
"display_name": "Workspace Toolkit usage enablement",
+
"display_name": "Show Change Account Link",
 
"type": "config",
 
"type": "config",
"default_value": "false",
+
"default_value": "true",
"description": "Specifies whether Workspace Toolkit use is authorized or not. This option must be set in the WS_Cluster application.",
+
"description": "Show or Hide the change login account link on login error page and second step login page.",
 +
"version": "9.0.000.46",
 
"category": "interaction-workspace",
 
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
Line 6,581: Line 7,129:
 
},
 
},
 
{
 
{
"id": "attachment.restrict-to-file-types",
+
"id": "privilege.voice.can-use",
"display_name": "Allowed attachment file types",
+
"display_name": "Can Use Voice Channel",
 
"type": "config",
 
"type": "config",
"default_value": "jpg,png,gif,pdf,doc,docx,ppt,pptx,xls,xlsx,txt,json",
+
"default_value": "true",
"description": "Specifies the list of file extensions that represent file types that are to be prevented from being used as attachments. The request is rejected if extension of file is not part of restricted types. This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": "Enables the agent to use the Voice channel.",
"category": "workspace-service",
+
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of file extensions that represent file types that are to be restricted.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,594: Line 7,143:
 
},
 
},
 
{
 
{
"id": "attachment.<media-type>.restrict-to-file-types",
+
"id": "privilege.voice-history.can-click-to-dial",
"display_name": "Allowed media attachment file types",
+
"display_name": "Can Click to Dial",
 
"type": "config",
 
"type": "config",
"default_value": "jpg,png,gif,pdf,doc,docx,ppt,pptx,xls,xlsx,txt,json",
+
"default_value": "true",
"description": "Specifies the list of file extensions that represent file types that are to be prevented from being used as attachments for a specific media. The request is rejected if extension of file is not part of restricted types. This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": " Enables an agent to use the Click-to-dial feature to dial a voice call from the Details tab of the history of a voice interaction in any History view.",
"category": "workspace-service",
+
"version": "9.0.000.61",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma-separated list of file extensions that represent file types that are to be restricted.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,607: Line 7,157:
 
},
 
},
 
{
 
{
"id": "attachment.max-file-upload-size",
+
"id": "privilege.voice-history.can-click-to-search",
"display_name": "Allowed media attachment size",
+
"display_name": "Can Click to Search",
 
"type": "config",
 
"type": "config",
"default_value": "8",
+
"default_value": "true",
"description": "Specifies the maximum size (in MB) of one file that agents can attach to an interaction. The value 0 means that attaching is not allowed. The maximum allowed attachment size is 50 MB. This option cannot be overridden and must be set in the WS_Cluster application.",
+
"description": "Enables an agent to use Click-to-search to open the Contact Directory by clicking a Contact name in the Details tab of the My History or Interaction Search views.",
"category": "workspace-service",
+
"version": "9.0.000.61",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "An integer value greater than or equal to 0.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,620: Line 7,171:
 
},
 
},
 
{
 
{
"id": "statistic-name",
+
"id": "privilege.chat.can-use",
"display_name": "Statistic Name",
+
"display_name": "Can Use Chat Channel",
 
"type": "config",
 
"type": "config",
"default_value": "AverageWaitingTime",
+
"default_value": "false",
"description": "The name of the statistic used to evaluate the presence for Routing Points.",
+
"description": "Enables the agent to use the Chat channel.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A valid name of a statistic server statistic for routing point.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,633: Line 7,185:
 
},
 
},
 
{
 
{
"id": "statistic-text",
+
"id": "privilege.chat.can-decline",
"display_name": "Statistic Text",
+
"display_name": "Can Decline",
 
"type": "config",
 
"type": "config",
"default_value": "&#36;I18n.AverageWaitingTime&#36;",
+
"default_value": "true",
"description": "Specifies the formatting to be used to display the Stat Server metric used for the presence of the displayed object. If no valid format is found in the option, the display format of the Stat Server metric is set automatically to TimeFormat if a time metric is recognized, or Percentage if a percentage is recognized. If a number metric is recognized or if the type of metric is not recognized, then a raw number format is used.",
+
"description": "Enables the agent to decline incoming chat interactions.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "One of the 2 predefined constant &#36;I18n.AverageWaitingTime&#36; or &#36;I18n.NumberInteractionsWaiting&#36;. Or a string containing a valid time or number format according to Windows rules number format (https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx). For example: 'interaction(s) Q4001 {0:HH:mm:ss} average waiting time' or 'interaction(s) Q4001 {0}% abandoned'.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,646: Line 7,199:
 
},
 
},
 
{
 
{
"id": "warning-level",
+
"id": "privilege.chat.can-release",
"display_name": "Warning Level",
+
"display_name": "Can Release",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "true",
"description": "The value at which a statistic is considered to be at the warning level.",
+
"description": "Enables the agent to manually end chat conversations.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A positive integer or a double value.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,659: Line 7,213:
 
},
 
},
 
{
 
{
"id": "error-level",
+
"id": "privilege.chat.can-release-consultation",
"display_name": "Error Level",
+
"display_name": "Can Release consultation",
 
"type": "config",
 
"type": "config",
"default_value": "0",
+
"default_value": "true",
"description": "The value at which a statistic is considered to be at the error level.",
+
"description": "Enables the agent to manually end chat consultations.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A positive integer or a double value.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,672: Line 7,227:
 
},
 
},
 
{
 
{
"id": "object-ids",
+
"id": "privilege.chat.can-set-interaction-disposition",
"display_name": "Object Identifiers",
+
"display_name": "Can Set Interaction Disposition",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "A comma separated list of DN identifiers that represent Routing Point objects presented in Team Communicator for which this presence metric is applicable. Object identifier format is: <DN Number>@<Switch Name> This key is optional. If it is absent from the section, the presence metric applies to all Routing Point objects that don't have explicit presence metric assignment.",
+
"description": "Enables an agent to set the disposition code on chat interactions.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,685: Line 7,241:
 
},
 
},
 
{
 
{
"id": "associated-object-ids",
+
"id": "privilege.chat.can-two-step-transfer",
"display_name": "Associated Object Identifiers",
+
"display_name": "Can Two Step Transfer",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "A comma separated list of object identifiers that represent the objects that store the statistic requested from Stat Server that is displayed as the 'presence metric' of the object displayed in Team Communicator. The type of those objects must match the type specified by the value of the associated-statistic-type option. If multiple values are specified by the value of the object-ids option, this option must contain the same number to associate the first object of object-ids with the first object of associated-object-ids, the second object of the object-ids with the second object of associated-object-ids and so on. This option is applicable only if associated-statistic-type is also set.",
+
"description": "Enables chat transfer in two steps, started by a chat consultation.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-two-step-conference",
 +
"display_name": "Can Two Step Conference",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables chat conference in two steps, started by a chat consultation.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-consult",
 +
"display_name": "Can Use Chat Consult",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables the agent to use the Chat consultation feature.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-one-step-conference",
 +
"display_name": "Can One Step Conference",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables the agent to use the instant chat conference feature.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 
"constraints": {
 
"constraints": {
"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
+
"data_type": "true, false.",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,698: Line 7,297:
 
},
 
},
 
{
 
{
"id": "associated-object-type",
+
"id": "privilege.chat.can-one-step-transfer",
"display_name": "Associated Object Type",
+
"display_name": "Can One Step Transfer",
 
"type": "config",
 
"type": "config",
"default_value": "No default value",
+
"default_value": "true",
"description": "Specifies the statistic type (from Stat Server reference) that is requested to display the presence metric when this metric is not calculated directly on the object displayed in Team Communicator, but on the objects referenced in option associated-object-ids.",
+
"description": "Enables the agent to use the instant chat transfer feature.",
"category": "routing-point-presence",
+
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-push-url",
 +
"display_name": "Can Push Url",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to push URL's to customers during chat sessions.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.show-monitoring.can-use",
 +
"display_name": "Show Monitoring",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to be informed that the current chat interaction is monitored by a supervisor.",
 +
"version": "9.0.000.14",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-click-to-dial",
 +
"display_name": "Can Click to Dial",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to use the Click to Dial feature in chat based on the expression.identify.phone-number option to detect phone numbers.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-click-to-email",
 +
"display_name": "Can Click to Email",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to use the Click to Email feature in chat based on the expression.identify.email-address option to detect email addresses.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-place-on-hold-async",
 +
"display_name": "Can Place on Hold Async Chat",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to put on hold an async chat.",
 +
"version": "9.0.000.17",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "chat.os-emoji-is-enabled",
 +
"display_name": "Use the native OS Emojis in Chat",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether emojis are displayed as images or as standard OS/browser emojis.",
 +
"version": "9.0.000.23",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat.can-use-emoji-picker",
 +
"display_name": "Can Use the Emoji Picker in Chat",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to use an emoji picker.",
 +
"version": "9.0.000.23",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.email.can-use",
 +
"display_name": "Can Use E-mail Channel",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent is use the Email channel.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.email.can-mark-done",
 +
"display_name": "Can Mark Done Interaction",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables the agent to mark done an interaction without further processing.",
 +
"version": "9.0.000.12",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.email.can-click-to-dial",
 +
"display_name": "Can Click to Dial",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables the agent to use the Click to Dial feature in email based on the expression.identify.phone-number option to detect phone numbers.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.email.can-decline",
 +
"display_name": "Can Decline",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables the agent to decline incoming email interactions. Depends on 'Email - Can Use Email Channel'.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.workbins.can-use",
 +
"display_name": "Can Use Workbins",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to access My Team Workbins.",
 +
"version": "9.0.000.12",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.workitem-channels.can-use",
 +
"display_name": "Can Use All Channels",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to use all WorkItem channels configured in the openmedia.workitem-channels option.",
 +
"version": "9.0.000.17",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.<media-type>.can-mark-done",
 +
"display_name": "Can Mark Done Interaction",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to mark done an interaction without further processing.",
 +
"version": "9.0.000.17",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.<media-type>.can-decline",
 +
"display_name": "Can Decline",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to decline incoming workitem interactions. Depends on 'Workitem - Can Use Workitem Channel'.",
 +
"version": "9.0.000.17",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.<media-type>.can-one-step-transfer",
 +
"display_name": "Can One Step Transfer",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to use instant workitem transfer. Depends on 'Workitem - Can Use Workitem Channel'.",
 +
"version": "9.0.000.17",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.<media-type>.can-set-interaction-disposition",
 +
"display_name": "Can Set Interaction Disposition",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to set the disposition code of workitem interactions. Depends on 'Workitem - Can Use Workitem Channel'.",
 +
"version": "9.0.000.17",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.<media-type>.can-move-to-workbin",
 +
"display_name": "Can Move Workitem to Workbin",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to move an interaction to the workbin. Depends on 'Workitem - Can Use Workitem Channel'.",
 +
"version": "9.0.000.24",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-use",
 +
"display_name": "Can Use TeamLead",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to use the agent call and chat monitoring functionality.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.myagents.can-use",
 +
"display_name": "Can Use My Agents View",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables supervisors to access the My Agents view, where they can view and update the state for agents in the groups they supervise. Supervisors can also remotely log off agents from media channels in this view.",
 +
"version": "9.0.000.31",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-monitor-voice",
 +
"display_name": "Can Monitor Voice",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to monitor voice interactions.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-monitor-chat",
 +
"display_name": "Can Monitor Chat",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables a supervisor to monitor chat interactions.",
 +
"version": "9.0.000.14",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-monitor-current-voice",
 +
"display_name": "Can Monitor Current Voice",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables a supervisor to monitor the current voice interaction.",
 +
"version": "8.5.200.52",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-coach-voice",
 +
"display_name": "Can Coach Voice",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to coach voice interactions.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-coach-current-voice",
 +
"display_name": "Can Coach Current Voice",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables a supervisor to coach the current voice interaction.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-coach-chat",
 +
"display_name": "Can Coach Chat",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables a supervisor to coach chat interactions.",
 +
"version": "9.0.000.14",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-switch-to-coach-chat",
 +
"display_name": "Can Switch To Coach for Chat",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to switch to coach mode for monitored chat interactions.",
 +
"version": "9.0.000.14",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-switch-to-barge-in-voice",
 +
"display_name": "Can Switch To BargeIn for Voice",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to switch to barge-in mode for monitored voice interactions.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-switch-to-barge-in-chat",
 +
"display_name": "Can Switch To BargeIn for Chat",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to switch to barge-in mode for monitored chat interactions.",
 +
"version": "9.0.000.14",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-stop-monitoring-voice",
 +
"display_name": "Can Stop Monitoring Voice",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to stop monitoring voice interactions.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-stop-monitoring-chat",
 +
"display_name": "Can Stop Monitoring Chat",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables a supervisor to stop monitoring chat interactions.",
 +
"version": "9.0.000.14",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.voice.can-send-dtmf",
 +
"display_name": "Can Send DTMF",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to send DTMF during a voice call by using the on screen number keypad.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.voice.show-monitoring.can-use",
 +
"display_name": "Show Monitoring",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to be notified that the current call is monitored by a supervisor.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.voice.alert-prevent-recording.can-use",
 +
"display_name": "Alert Recording Prevention",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables agents to be alerted if the current call is not being recorded.",
 +
"version": "9.0.000.76",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.active-recording.can-use",
 +
"display_name": "Can Use",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to use the Active Recording functionality.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.active-recording.can-monitor-recording",
 +
"display_name": "Can Monitor Voice Recording",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the call monitoring indicator is displayed to agents when their calls are being recorded. The Call Recording functionality (for VoIP\\/SIP enabled agents only) enables you to record the current voice interaction with a contact or an internal target.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.active-recording.can-start",
 +
"display_name": "Can Start",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to start the Active Recording.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.active-recording.can-stop",
 +
"display_name": "Can Stop",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to stop the Active Recording.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.active-recording.can-resume",
 +
"display_name": "Can Resume",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to resume the Active Recording.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.active-recording.can-pause",
 +
"display_name": "Can Pause",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to pause the Active Recording.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamcommunicator.can-use",
 +
"display_name": "Can Use",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables access to the Team Communicator.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamcommunicator.can-view-all",
 +
"display_name": "Can Search All",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to search within all internal targets and contacts in Team Communicator.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamcommunicator.can-view-favorites",
 +
"display_name": "Can View Favorites",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to view favorites in Team Communicator.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamcommunicator.can-view-recent-calls",
 +
"display_name": "Can View Recent Calls",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to view recently contacted resources in Team Communicator.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamcommunicator.can-manage-favorites",
 +
"display_name": "Can Manage Favorites",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables an agent to add, edit, and remove personal favorites in Team Communicator.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamcommunicator.display-agent-groups-availability",
 +
"display_name": "Display agent Groups availability",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables an agent to view the number of agents in the Ready state in agent groups in Team Communicator. Depends on 'Team Communicator - Can Use' and 'Team Communicator - Can View Favorites'.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "accessibility.focus-on-interaction-toast",
 +
"display_name": "Focus on interaction toast",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether all Interaction Notification views receive the focus when they are displayed. This option does not rely on accessibility.visual-impairment-profile; therefore, it applies to all configured agents, not just visually impaired agents.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "accessibility.<media-type>.focus-on-interaction-toast",
 +
"display_name": "Focus on interaction toast",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether all Interaction Notification views receive the focus when they are displayed. This option does not rely on accessibility.visual-impairment-profile; therefore, it applies to all configured agents, not just visually impaired agents.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "accessibility.visual-impairment-profile",
 +
"display_name": "Activate Visual Impairment Profile",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the profile for visually impaired users is active. This option enables users to navigate interface elements from keyboard navigation and tooltips by using a Screen Reader application. Some components might change their behavior in this mode. For example, Team Communicator is collapsed in this configuration.",
 +
"version": "9.0.000.07",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "accessibility.tooltip.show-on-focus",
 +
"display_name": "Enables tooltip activation by keyboard focus",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the tooltip is displayed automatically when the related component has the focus. This option is forced to false if the value of the accessibility.visual-impairment-profile option is true.",
 +
"version": "9.0.000.84",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "accessibility.tooltip.hide-on-click",
 +
"display_name": "Enables tooltip hiding by clicking on target element",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether a custom tooltip is hidden when a target element is clicked. This option is forced to false if the value of the accessibility.visual-impairment-profile option is true.",
 +
"version": "9.0.000.84",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "accessibility.tooltip.is-hoverable",
 +
"display_name": "Enables hoverable tooltips",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the tooltip is displayed when the mouse pointer is hovered above the tooltip/tooltip body. This option is forced to false if the value of the accessibility.visual-impairment-profile option is true.",
 +
"version": "9.0.000.84",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "editor.fonts",
 +
"display_name": "Fonts",
 +
"type": "config",
 +
"default_value": "Serif,Sans-serif,Monospace,Cursive,Fantasy,Tahoma,Roboto,Arial,Helvetica",
 +
"description": "Specifies the list of available fonts in the Fonts menu of new and reply HTML format email interactions. The fonts are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of fonts from the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto, Arial, Helvetica.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "editor.default-font",
 +
"display_name": "Default font",
 +
"type": "config",
 +
"default_value": "Serif",
 +
"description": "Specifies the default font in the Font menu of new and reply HTML format email  interactions. If this option is left empty, the last selected font is used for email interactions by default.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A value from the following list: the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto. Empty means no default font specified.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "editor.font-sizes",
 +
"display_name": "Font sizes",
 +
"type": "config",
 +
"default_value": "8,9,10,11,12,14,16,18,20,22,24,26,28,36,48,72",
 +
"description": "Specifies the font sizes available in the Font Size menu of new and reply HTML formatted email interactions. The sizes are displayed in the order in which they appear in the list.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of font sizes from the following list: 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "editor.default-font-size",
 +
"display_name": "Default font size",
 +
"type": "config",
 +
"default_value": "9",
 +
"description": "Specifies the default font size in the Font Size menu of new and reply HTML formatted email interactions. If empty, the last selected font size is used for email interactions by default.",
 +
"version": "9.0.000.11",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A value from the following list: the following list: 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72. Empty means no default font size specified.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "editor.SRL.shortcuts.prefix",
 +
"display_name": "Editor Shortcuts Prefix",
 +
"type": "config",
 +
"default_value": "#",
 +
"description": "Specifies the prefix, such as '#', that identifies that a keyword is a shortcut for a Standard Response.",
 +
"version": "9.0.000.71",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid character.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "security.web-content.sandbox-rights.default-authorizations",
 +
"display_name": "List of default sandbox rights authorization options for the embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes)",
 +
"type": "config",
 +
"default_value": "ALLOW-SCRIPTS,ALLOW-FORMS,ALLOW-POPUPS,ALLOW-SAME-ORIGIN",
 +
"description": "Specifies the default sandbox rights authorization options that are set up to embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes), in order to remove restrictions and enable features.",
 +
"version": "9.0.000.19",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of default sandbox rights authorization that are set up for the embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes) in order to unlock some security restrictions : ALLOW-SCRIPTS, ALLOW-FORMS, ALLOW-POPUPS, ALLOW-SAME-ORIGIN, ALLOW-DOWNLOADS, ALLOW-PRESENTATION, ALLOW-POINTER-LOCK",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat-nexus.can-use",
 +
"display_name": "Can use Nexus Chat View",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to access the contents of the Nexus Conversation tab in the Case Side View of the Chat interaction view.",
 +
"version": "9.0.000.87",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat-nexus.can-use-contact-history-detail",
 +
"display_name": "Can Use Specific Chat Nexus History Detail",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to access Nexus chat interaction details in the Details tab of the Contact History view.",
 +
"version": "9.0.000.98",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "chat-nexus.service-url",
 +
"display_name": "Nexus URL",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the web-socket url of the Nexus service url to access the Chat API.",
 +
"version": "9.0.000.87",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "chat-nexus.web-components.url",
 +
"display_name": "Nexus-Ux WebComponents URL",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the Nexus-ux WebComponents url to display the nexus-ux view. Use this option if the url is different from the standard url.",
 +
"version": "9.0.000.87",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat-nexus.communication.can-use",
 +
"display_name": "Can use Nexus Communication Chat View",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to use the Communication tab in the Connect group.",
 +
"version": "9.0.000.87",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.chat-nexus.communication.can-send",
 +
"display_name": "Can send messages from Nexus Communication Chat View",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to manage contact subscriptions and send messages to contacts from the Communication tab.",
 +
"version": "9.0.000.87",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "chat-nexus.interaction-bar.tooltip-enabled",
 +
"display_name": "Enable Nexus Rendering in the Interaction Bar Tooltip",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enable the Nexus chat rendering in the interaction bar tooltip view.",
 +
"version": "9.0.000.98",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "expression.gws-url.capturing-groups",
 +
"display_name": "Expression to capture groups from the GWS url.",
 +
"type": "config",
 +
"default_value": "https:\\/\\/(?:gapi{{!}}gwa)-(.*)\\.genesyscloud\\.com",
 +
"description": "Specifies that Workspace should extract a part of its url to capture groups containing information shared among services, such as the tenant or region.",
 +
"version": "9.0.000.51",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "expression.gws-url.capturing-groups-<n>",
 +
"display_name": "Expression to capture groups from the GWS url using pairs mapping to extract the region.",
 +
"type": "config",
 +
"default_value": "https:\\/\\/(.*)-(?:gapi{{!}}gwa)-(.*)\\.genesyscloud\\.com",
 +
"description": "Specifies that Workspace should extract a part of its url to capture groups containing information shared among services, such as the tenant or region. This option supports plugins and pair mapping (for example: system.telemetry.service-url-<n>, for MPLS networks).",
 +
"version": "9.0.000.51",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "disaster-recovery.enabled",
 +
"display_name": "Disaster recovery enabled",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Business Continuity (Disaster Recovery) functionality is activated for SIP Server and Genesys Web Services.",
 +
"version": "9.0.000.31",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "disaster-recovery.authentication-mode",
 +
"display_name": "Disaster recovery authentication mode",
 +
"type": "config",
 +
"default_value": "INTERNAL",
 +
"description": "Specifies which authentication mode is used when trying to authenticate with another site (INTERNAL iframe, EXTERNAL popup or REDIRECT refresh on backup-site).",
 +
"version": "9.0.000.31",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Select a value from the following list of modes that can be used for authentication with Toolkit : INTERNAL, EXTERNAL, REDIRECT",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "voice.disaster-recovery.timeout",
 +
"display_name": "Disaster recovery timeout",
 +
"type": "config",
 +
"default_value": "0",
 +
"description": "Specifies the duration, in seconds, for which Workspace waits for the Voice Channel to be back in service before triggering the Disaster Recovery process during and active session.",
 +
"version": "9.0.000.31",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value greater than 0 to specify the timeout, 0 to disable Voice Disaster Recovery.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.telemetry.enabled",
 +
"display_name": "Telemetry monitoring enabled",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether telemetry is used to push metrics and traces to the Telemetry Service.",
 +
"version": "9.0.000.65",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.telemetry.enable-metrics",
 +
"display_name": "Enable metrics for Telemetry",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether UI metrics and events are sent to the Telemetry Service. Depends on system.telemetry.enabled",
 +
"version": "9.0.000.65",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.telemetry.enable-traces",
 +
"display_name": "Enable traces for Telemetry",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether UI traces are sent to the Telemetry Service. Depends on system.telemetry.enabled",
 +
"version": "9.0.000.65",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.telemetry.service-url",
 +
"display_name": "Telemetry service url",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "The url of the Telemetry Service.",
 +
"version": "9.0.000.65",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Specifies the valid FQDN of the Telemetry Service (for example: https://telemetry-fqdn).",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.telemetry.service-url-<n>",
 +
"display_name": "Telemetry service url",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the url of one of the Telemetry Services when there are multiple pairs in a region. (Refer to the expression.gws-url.capturing-groups-<n> option)",
 +
"version": "9.0.000.65",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid FQDN of Telemetry Service (for example: https://telemetry-fqdn-1).",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.telemetry.monitor-interval",
 +
"display_name": "Telemetry metric interval",
 +
"type": "config",
 +
"default_value": "60",
 +
"description": "Specifies the duration, in seconds, between two checks of the metrics, events, or traces before publishing the data to the Telemetry Service.",
 +
"version": "9.0.000.65",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "From 0 to MAXINT.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.callback.can-use",
 +
"display_name": "Can Use Callback",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables an agent to create callback interactions and displays the Schedule a Callback button in the interaction toolbar.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "callback.callback-information.content",
 +
"display_name": "Content for Callback Information",
 +
"type": "config",
 +
"default_value": "PhoneNumber,Comments",
 +
"description": "Specifies the list of Callback data that is displayed in the Callback Information Area. The Callback data entries are displayed in the order in which they appear in this list.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma separated list of data items from the following list: PhoneNumber,Comments",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "callback.callback-types-business-attribute",
 +
"display_name": "Callback Type Business Attribute",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the name of the Business Attribute that defines the list of Service Types. Service Types consist of the GES service name and user data key-value pairs.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid Business Attribute name.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "callback.default-date.is-automatically-selected",
 +
"display_name": "Callback Date Default",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the current date is the default displayed in the Date field of the New Callback Schedule window.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "callback.time-slot.field-type",
 +
"display_name": "Callback Time Slot Control",
 +
"type": "config",
 +
"default_value": "WIDGET",
 +
"description": "Specifies whether the Time slots field displays the time slot picker widget or a drop-down list. If not set or set to an invalid value, the widget is displayed. The value of this option is forced to DROPDOWN if the value of the accessibility.visual-impairment-profile option is true.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Select a value from the following list: WIDGET, DROPDOWN.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.agent-assist.can-use",
 +
"display_name": "Can use Agent Assist for Athena server",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to view the 'Agent Assist' tab in the Case Side View and Voice transcripts in voice interaction sub view.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.service-url",
 +
"display_name": "Agent Assist Athena Server URL",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the web-socket url of the AI Connector (Anthena) service to access the Agent Assist API.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid web-socket Url.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.voice-transcript.enable",
 +
"display_name": "Enable Voice Transcript",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the voice transcript view is displayed in the voice interaction view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.suggestion.enable",
 +
"display_name": "Enable Suggestions",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the suggestion view is displayed in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.confidence.faq.enable",
 +
"display_name": "Enable Confidence (FAQ)",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the confidence percentage for FAQ suggestions is displayed in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.confidence.article.enable",
 +
"display_name": "Enable Confidence (Article)",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the confidence percentage for knowledge article suggestions is displayed in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.confidence.faq.threshold.low",
 +
"display_name": "Low Threshold for Confidence Color",
 +
"type": "config",
 +
"default_value": "50",
 +
"description": "Specifies the low threshold, in percentage, to display the low confidence color (red) for FAQ suggestions. The value must be less than the value specified for the agent-assist.confidence.faq.threshold.high option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value between 0 and 100.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.confidence.faq.threshold.high",
 +
"display_name": "High Threshold for Confidence Color",
 +
"type": "config",
 +
"default_value": "80",
 +
"description": "Specifies the high threshold, in percentage, to display the high confidence color (green) for FAQ suggestions. The value must be greater than the value specified for the agent-assist.confidence.faq.threshold.low option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value between 0 and 100.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.confidence.article.threshold.low",
 +
"display_name": "Low Threshold for Confidence Color",
 +
"type": "config",
 +
"default_value": "50",
 +
"description": "Specifies the low threshold, in percentage, to display the low confidence color (red) for knowledge article suggestions. The value must be less than the value specified for the agent-assist.confidence.article.threshold.high option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value between 0 and 100.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.confidence.article.threshold.high",
 +
"display_name": "High Threshold for Confidence Color",
 +
"type": "config",
 +
"default_value": "80",
 +
"description": "Specifies the high threshold, in percentage, to display the high confidence color (green) for knowledge article suggestions. The value must be greater than the value specified for the agent-assist.confidence.article.threshold.low option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value between 0 and 100.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.feedback.faq.enable",
 +
"display_name": "Enable Feedback Buttons (FAQ)",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the thumbs-up and thumbs-down feedback buttons are displayed for each FAQ suggestion in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "agent-assist.feedback.article.enable",
 +
"display_name": "Enable Feedback Buttons (Article)",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the thumbs-up and thumbs-down feedback buttons are displayed for each knowledge article suggestion in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"version": "9.0.000.95",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "workspace-toolkit.enable",
 +
"display_name": "Workspace Toolkit usage enablement",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Workspace Toolkit use is authorized or not. This option must be set in the WS_Cluster application.",
 +
"version": "9.0.000.59",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.multi-tabs-defense.enable",
 +
"display_name": "Enable defense for Multi-Tabs",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables the defense for Multi-Tabs use-cases.",
 +
"version": "9.0.000.80",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "attachment.restrict-to-file-types",
 +
"display_name": "Allowed attachment file types",
 +
"type": "config",
 +
"default_value": "jpg,png,gif,pdf,doc,docx,ppt,pptx,xls,xlsx,txt,json",
 +
"description": "Specifies the list of file extensions that represent file types that are allowed to be used as attachments. The request is rejected if extension of file is not part of restricted types. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.34",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A comma-separated list of file extensions that represent file types that are allowed.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "attachment.<media-type>.restrict-to-file-types",
 +
"display_name": "Allowed media attachment file types",
 +
"type": "config",
 +
"default_value": "jpg,png,gif,pdf,doc,docx,ppt,pptx,xls,xlsx,txt,json",
 +
"description": "Specifies the list of file extensions that represent file types that are allowed to be used as attachments for a specific media. The request is rejected if extension of file is not part of restricted types. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.34",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A comma-separated list of file extensions that represent file types that are allowed.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "attachment.max-file-upload-size",
 +
"display_name": "Allowed media attachment size",
 +
"type": "config",
 +
"default_value": "8",
 +
"description": "Specifies the maximum size (in MB) of one file that agents can attach to an interaction. The value 0 means that attaching is not allowed. The maximum allowed attachment size is 50 MB. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.34",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "An integer value greater than or equal to 0.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "chat.message.max-length",
 +
"display_name": "Message max length",
 +
"type": "config",
 +
"default_value": "64000",
 +
"description": " Specifies the maximum number of characters in the chat message. This option cannot be overridden and must be set in the WS_Cluster application.",
 +
"version": "9.0.000.86",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A positive integer",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "openmedia.chat-channels",
 +
"display_name": "Enabled Chat Extension Channels",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the list of Chat channels an agent may use.",
 +
"version": "9.0.000.97",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid Media Types.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "openmedia.chat-history-channels",
 +
"display_name": "Enabled Chat History Details View for Openmedia Channels",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the list of Open Media channels for which the transcript is to be handled as a chat interactions, such as Facebook public and Twitter public, and displayed in the interaction details pane of the History views.",
 +
"version": "9.0.000.95",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid Media Types.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "statistic-name",
 +
"display_name": "Statistic Name",
 +
"type": "config",
 +
"default_value": "AverageWaitingTime",
 +
"description": "The name of the statistic used to evaluate the presence for Routing Points.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 +
"constraints": {
 +
"data_type": "A valid name of a statistic server statistic for routing point.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "statistic-text",
 +
"display_name": "Statistic Text",
 +
"type": "config",
 +
"default_value": "&#36;I18n.AverageWaitingTime&#36;",
 +
"description": "Specifies the formatting to be used to display the Stat Server metric used for the presence of the displayed object. If no valid format is found in the option, the display format of the Stat Server metric is set automatically to TimeFormat if a time metric is recognized, or Percentage if a percentage is recognized. If a number metric is recognized or if the type of metric is not recognized, then a raw number format is used.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 +
"constraints": {
 +
"data_type": "One of the 2 predefined constant &#36;I18n.AverageWaitingTime&#36; or &#36;I18n.NumberInteractionsWaiting&#36;. Or a string containing a valid time or number format according to Windows rules number format (https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx). For example: 'interaction(s) Q4001 {0:HH:mm:ss} average waiting time' or 'interaction(s) Q4001 {0}% abandoned'.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "warning-level",
 +
"display_name": "Warning Level",
 +
"type": "config",
 +
"default_value": "0",
 +
"description": "The value at which a statistic is considered to be at the warning level.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 +
"constraints": {
 +
"data_type": "A positive integer or a double value.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "error-level",
 +
"display_name": "Error Level",
 +
"type": "config",
 +
"default_value": "0",
 +
"description": "The value at which a statistic is considered to be at the error level.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 +
"constraints": {
 +
"data_type": "A positive integer or a double value.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "object-ids",
 +
"display_name": "Object Identifiers",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "A comma separated list of DN identifiers that represent Routing Point objects presented in Team Communicator for which this presence metric is applicable. Object identifier format is: <DN Number>@<Switch Name> This key is optional. If it is absent from the section, the presence metric applies to all Routing Point objects that don't have explicit presence metric assignment.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 +
"constraints": {
 +
"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "associated-object-ids",
 +
"display_name": "Associated Object Identifiers",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "A comma separated list of object identifiers that represent the objects that store the statistic requested from Stat Server that is displayed as the 'presence metric' of the object displayed in Team Communicator. The type of those objects must match the type specified by the value of the associated-statistic-type option. If multiple values are specified by the value of the object-ids option, this option must contain the same number to associate the first object of object-ids with the first object of associated-object-ids, the second object of the object-ids with the second object of associated-object-ids and so on. This option is applicable only if associated-statistic-type is also set.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 
"constraints": {
 
"constraints": {
 
"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
 
"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "associated-object-type",
 +
"display_name": "Associated Object Type",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the statistic type (from Stat Server reference) that is requested to display the presence metric when this metric is not calculated directly on the object displayed in Team Communicator, but on the objects referenced in option associated-object-ids.",
 +
"version": "9.0.000.67",
 +
"category": "routing-point-presence",
 +
"constraints": {
 +
"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "statistic-name",
 +
"display_name": "Statistic Name",
 +
"type": "config",
 +
"default_value": "AverageWaitingTime",
 +
"description": "The name of the statistic used to evaluate the presence for Queues.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "A valid name of a statistic server statistic for queue.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "statistic-text",
 +
"display_name": "Statistic Text",
 +
"type": "config",
 +
"default_value": "&#36;I18n.AverageWaitingTime&#36;",
 +
"description": "Specifies the formatting to be used to display the Stat Server metric used for the presence of the displayed object. If no valid format is found in the option, the display format of the Stat Server metric is set automatically to TimeFormat if a time metric is recognized, or Percentage if a percentage is recognized. If a number metric is recognized or if the type of metric is not recognized, then a raw number format is used.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "One of the 2 predefined constant &#36;I18n.AverageWaitingTime&#36; or &#36;I18n.NumberInteractionsWaiting&#36;. Or a string containing a valid time or number format according to Windows rules number format (https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx). For example: 'interaction(s) Q4001 {0:HH:mm:ss} average waiting time' or 'interaction(s) Q4001 {0}% abandoned'.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "warning-level",
 +
"display_name": "Warning Level",
 +
"type": "config",
 +
"default_value": "0",
 +
"description": "The value at which a statistic is considered to be at the warning level.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "A positive integer or a double value.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "error-level",
 +
"display_name": "Error Level",
 +
"type": "config",
 +
"default_value": "0",
 +
"description": "The value at which a statistic is considered to be at the error level.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "A positive integer or a double value.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "object-ids",
 +
"display_name": "Object Identifiers",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "A comma separated list of DN identifiers that represent Queue objects presented in Team Communicator for which this presence metric is applicable. Object identifier format is: <DN Number>@<Switch Name> This key is optional. If it is absent from the section, the presence metric applies to all Queue objects that don't have explicit presence metric assignment.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "A comma separated list of DN identifiers that represent Queue objects.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "associated-object-ids",
 +
"display_name": "Associated Object Identifiers",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "A comma separated list of object identifiers that represent the objects that store the statistic requested from Stat Server that is displayed as the 'presence metric' of the object displayed in Team Communicator. The type of those objects must match the type specified by the value of the associated-statistic-type option. If multiple values are specified by the value of the object-ids option, this option must contain the same number to associate the first object of object-ids with the first object of associated-object-ids, the second object of the object-ids with the second object of associated-object-ids and so on. This option is applicable only if associated-statistic-type is also set.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "A comma separated list of DN identifiers that represent Queue objects.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "associated-object-type",
 +
"display_name": "Associated Object Type",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the statistic type (from Stat Server reference) that is requested to display the presence metric when this metric is not calculated directly on the object displayed in Team Communicator, but on the objects referenced in option associated-object-ids.",
 +
"version": "9.0.000.87",
 +
"category": "queue-presence",
 +
"constraints": {
 +
"data_type": "A comma separated list of DN identifiers that represent Queue objects.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "click-to-dial.preprocessing-rules",
 +
"display_name": "Click to Dial Preprocessing Rules",
 +
"type": "config",
 +
"default_value": "default",
 +
"description": "Specifies the pre-processing rules to apply to the phone number before making a dial request",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "default, none, or a comma-separated list of pre-processing rule section names",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.enabled-call-types",
 +
"display_name": "Voice Activity Log",
 +
"type": "config",
 +
"default_value": "Inbound,Outbound,Internal,Consult",
 +
"description": "Specifies the call types the adapter should create activity history entries for in Salesforce.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A comma-separated list of call types (Inbound, Outbound, Internal, Consult) or an empty value to disable all.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.enabled-chat-types",
 +
"display_name": "Chat Activity Log",
 +
"type": "config",
 +
"default_value": "Inbound",
 +
"description": "Specifies the chat types the adapter should create activity history entries for in Salesforce",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A comma-separated list of chat types (Inbound, Consult) or an empty value to disable all.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.enabled-openmedia-types",
 +
"display_name": "Open Media Activity Log",
 +
"type": "config",
 +
"default_value": "Inbound",
 +
"description": "Specifies the open media (workitem) types Adapter should create activity log entries for in Salesforce. To disable open media activity log creation set option to None.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "Open media (workitem) types (Inbound) or leave empty to disable all activity creation.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.field-mapping",
 +
"display_name": "Activity Log Field Mapping",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the name of the configuration section where the mapping is defined.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "The name of a configuration section that contains the mapping.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.mode",
 +
"display_name": "Auto Activity Log Association",
 +
"type": "config",
 +
"default_value": "search_query",
 +
"description": "Specifies the Salesforce criterion to use to associate the Activity Log Task when the interaction is completed.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "search_query, open_page",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.on-screenpop",
 +
"display_name": "Activity Log on Screen Pop",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Adapter creates the activity in Salesforce on screen pop and modifies logged activity when interaction is marked done. Activity on screen pop is created for inbound and internal calls",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.status",
 +
"display_name": "Salesforce Activity Log Status",
 +
"type": "config",
 +
"default_value": "Completed",
 +
"description": "Specifies the custom task status to be applied when an activity log is created by Adapter. Prerequisite: Status exists in the Salesforce Task Status Picklist",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "Any string representing a status. Cannot contain the following character: &",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.ui-association",
 +
"display_name": "UI Activity Log Association",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Gplus Adapter displays the Activity Log Task Object Association table when the interaction is completed.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.block-adapter-multitab",
 +
"display_name": "Prevent Gplus in Browser Multitab",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies that Gplus Adapter can't work in several tabs.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.chat.include-transcript-in-desc",
 +
"display_name": "Chat Include Transcript in Description",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether Adapter saves the chat transcript as part of the activity description in Salesforce.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.chat.transcript-custom-field-name",
 +
"display_name": "Chat Transcript Custom Field Name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the name of a custom activity field in Salesforce. If set, Adapter saves the chat transcript to this field in Salesforce. Note: Salesforce Lightning Experience supports only 255 characters for Text fields. If you configure the Text fields to store the chat transcripts and set the length of characters as 255, only the first 255 characters of the chat transcript will be saved in the Activity History and the remaining transcript will be truncated. However, you can still view the Details and Case Data of the chat interaction in the My History tab in Agent Desktop. Whereas, if you configure the Text field's character length with a value less than 255, then, an activity might not get created in Salesforce if the chat transcript exceeds the configured character length.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": " Name of a custom field in Salesforce.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.debug-notifications",
 +
"display_name": "UI Activity Log Association",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Gplus Adapter displays all notifications (positive and negative).",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.email.include-body-in-desc",
 +
"display_name": "Email Include in Activity Description",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "When set to true, includes the text version of the email body in the activity description in Salesforce. The email body is saved only for inbound emails and outbound replies",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.enable-click-to-dial",
 +
"display_name": "Enable Click to dial",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "If this option is set to true, Gplus Adapter enables Salesforce click-to-dial, or, if set to false, Gplus Adapter does not accept click-to-dial requests, regardless of whether or not click-to-dial is enabled in Salesforce",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.enable-in-focus-page-transfer",
 +
"display_name": "Update Attached Data on Transfer",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether to update the call data with the ID of the object the agent is looking at in Salesforce when performing a voice or chat conference or transfer. If set to true, the agent receiving the voice or chat conference or transfer gets a screen pop for the most relevant object",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.keep-session-alive",
 +
"display_name": "Keep Alive Sync",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether to prevent Adapter from logging out of Salesforce when there is no activity in Salesforce beyond a configurable time period. If set to true, Adapter refreshes the Salesforce session at short intervals and keeps Adapter-Salesforce session alive.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.message-channel.name",
 +
"display_name": "Salesforce Message Channel Name for Service Client API",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the name of the message channel in Salesforce for Service Client API in the format: NameSpacePrefix__ChannelName__c or ChannelName__c.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of a message channel in Salesforce in the following format: NameSpacePrefix__ChannelName__c or ChannelName__c",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.new-record.field-mapping",
 +
"display_name": "Salesforce New Record Field Mapping",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the name of the configuration section where the mapping is defined. In the section, each key must correspond to an interaction UserData key and each value must correspond to the name of the Salesforce standard or custom object field.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "The name of a configuration section that contains the mapping of a new record custom field mapping.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.notifications",
 +
"display_name": "Salesforce Notification",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Gplus Adapter displays notifications (positive only).",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.message-channel.name",
 +
"display_name": "Salesforce Message Channel Name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the name of the message channel in Salesforce for Service Client API in the format: NameSpacePrefix__ChannelName__c or ChannelName__c.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of a message channel in Salesforce in the following format: NameSpacePrefix__ChannelName__c or ChannelName__c",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.run-apex.class",
 +
"display_name": "Apex Class Name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configures the name for a Salesforce custom apex class.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "Apex Class Name",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.run-apex.events",
 +
"display_name": "Run Salesforce Apex on Interaction Events",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies interaction event which triggers Salesforce Apex to run.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "RINGING, DIALING, ESTABLISHED, RELEASED, INVITED, ACCEPTED, CREATED, REMOVED",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.run-apex.userdata-key-list",
 +
"display_name": "Apex Data",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies comma-separated list of the userData key names that will be delivered to Salesforce Apex. Example of value format: userDataKeyName1, userDataKeyName2, userDataKeyName3",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "Comma-separated list of fields in userData that will be delivered to Salesforce Apex parameter eventData.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.user-data.object-id-key",
 +
"display_name": "Salesforce Object Key",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the key Adapter uses when saving the ID of the focused Salesforce object to attached data.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A valid user key name to store the Salesforce object id. For example: sf_object_key",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.user-data.object-name-key",
 +
"display_name": "Salesforce Object Name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the key Adapter uses when saving the name of the focused Salesforce object to attached data.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A valid user key name to store the Salesforce object name. For example: sf_object_name",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.user-data.object-type-key",
 +
"display_name": "Salesforce Object Type",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the key Adapter uses when saving the type of the focused Salesforce object to attached data.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A valid user key name to store the Salesforce object type name. For example: sf_object_type",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.chat.on-invite",
 +
"display_name": "Screen Pop on Chat Invite",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the chat invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the chat invite.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.email.on-create",
 +
"display_name": "Screen Pop on Outbound Email Create",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Adapter initiates a screen pop in Salesforce immediately after creating the email",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.email.on-invite",
 +
"display_name": "Screen Pop on Email Invite",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the email invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the email invite.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.enable-for-consult",
 +
"display_name": "Enable Screen Pop for Consult",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the ability to attach current Salesforce object in context when using voice consult. This option works with option salesforce.enable-in-focus-page-transfer",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.enable-for-internal-calls",
 +
"display_name": "Screen Pop for Internal Calls",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the adapter initiates screen pops for internal calls",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.for-outbound",
 +
"display_name": "Screen Pop For Outbound Calls",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies whether the Adapter initiates screen pops in Salesforce for outbound calls. None: no screen pops are initiated for outbound calls, Dialing: the Adapter initiates a screen pop on dialing, Established: the Adapter initiates a screen pop when the call is established.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "established, dialing",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.id-key-regex",
 +
"display_name": "Screenpop Id Key Regex",
 +
"type": "config",
 +
"default_value": "^id_",
 +
"description": "Specifies a regular expression pattern used to match a UserData key. This key's value should contain the ID of an object to screen pop in Salesforce. As with the existing screen pop behavior using the 'id_' prefix, if multiple matching keys are present, Adapter only uses the first one. If this option isn't defined, Adapter uses the existing 'id_'prefix logic.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A regular expression that matches a UserData key.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.include-ani-in-search",
 +
"display_name": "Use ANI in Screen Pop Search",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the ANI is used in the screen pop search",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.include-dnis-in-search",
 +
"display_name": "Use DNIS in Screen Pop Search",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the DNIS is used in the screen pop search",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-api-name",
 +
"display_name": "Screenpop Object Api Name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the Salesforce custom object API name. To find the API name, go to Salesforce Setup - Object Manager - Custom Object - Details - API Name.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "The name of a Salesforce custom object API",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type",
 +
"display_name": "Screen pop object type",
 +
"type": "config",
 +
"default_value": "SOBJECT",
 +
"description": "Specifies object type to screen pop in Salesforce.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "SOBJECT, FLOW, URL, OBJECTHOME, LIST, SEARCH, NEW_RECORD_MODAL",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type-flow",
 +
"display_name": "Screen pop Flow section name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configure section name Flow for screenpop object type.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of the custom section that you have defined to contain the Flow to be executed during the ringing or established phase.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type-list",
 +
"display_name": "Screen pop List section name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configure section name List for screenpop object type.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of the custom section that you have defined to contain the List to be executed during the ringing or established phase.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type-new-record",
 +
"display_name": "Screen pop New record section name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configure section name New record for screenpop object type.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of the custom section that you have defined to contain the new object type record name.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type-object-home",
 +
"display_name": "Screen pop Object home section name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configure section name Object home for screenpop object type.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of the custom section you have defined to contain the Object Home.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type-search",
 +
"display_name": "Screen pop Search section name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configure section name Search for screenpop object type",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of the custom section that you have defined to contain the default search string. The search string must be at least 3 characters.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.object-type-url",
 +
"display_name": "Screen pop URL section name",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Configure section name URL for screenpop object type.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string that contains the name of the custom section you have defined to contain the URL.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.on-ringing",
 +
"display_name": "Screen Pop on Ringing",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the adapter initiates a screen pop in Salesforce when the call is ringing. If not set or false, the adapter initiates a screen pop when the call is established",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.openmedia.on-invite",
 +
"display_name": "Screen Pop on Open Media Invite",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Adapter initiates a screen pop in Salesforce immediately after displaying the open media invite notification. If the option is not set or false, Adapter initiates a screen pop only when the agent accepts the open media invite. This option supports the open media items configured in the openmedia.workitem-channels option.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "salesforce.activity-log.display-on-creation",
 +
"display_name": "Display Activity Log On Creation",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether Gplus Adapter displays the Activity Log in Salesforce when interaction is completed.",
 +
"version": "9.0.000.98",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.preprocessing-rule",
 +
"display_name": "Screen Pop Preprocessing Rule",
 +
"type": "config",
 +
"default_value": "default",
 +
"description": "Specifies the pre-processing rule to apply to the ANI before showing the screen pop",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "default, none, or a pre-processing rule section name.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.save-new-record-criterion",
 +
"display_name": "Create New Salesforce Record on Screenpop",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies whether Gplus Adapter creates new Salesforce record on screenpop. None: no new Salesforce record is created, No Matching Record: new Salesforce record is created when Salesforce search returns no matching record, Always: new Salesforce record is created for every screenpop. Depends on Salesforce Object API Name and New Salesforce Record Field Mapping options.",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "no_matching_record, always",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.search-key-regex",
 +
"display_name": "RegEx to Match UserData",
 +
"type": "config",
 +
"default_value": "^cti_",
 +
"description": "Specifies a regular expression pattern used to match one or more UserData keys. The values for these keys are used to build the search and screen pop expression in Salesforce. If this option is not defined, the adapter uses the existing 'cti_' prefix logic",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A regular expression that matches a UserData key.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "screenpop.transfer-object-key",
 +
"display_name": "Object ID UserData key",
 +
"type": "config",
 +
"default_value": "id_transfer_object",
 +
"description": "Specifies the custom UserData key the adapter should use for the object ID of the focused page in Salesforce",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A valid key",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.inbound-voice.subject",
 +
"display_name": "Templates Salesforce Inbound-Voice Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.outbound-voice.subject",
 +
"display_name": "Templates Salesforce outbound-voice Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.transfer-voice.subject",
 +
"display_name": "Templates Salesforce transfer-voice Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.chat.subject",
 +
"display_name": "Templates Salesforce chat Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.email.subject",
 +
"display_name": "Templates Salesforce email Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.openmedia.subject",
 +
"display_name": "Templates Salesforce openmedia Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "templates.salesforce.internal-voice.subject",
 +
"display_name": "Templates Salesforce internal-voice Subject",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
 +
"version": "9.0.000.95",
 +
"category": "crm-adapter",
 +
"constraints": {
 +
"data_type": "A string with custom template variables wrapped in { and }",
 
"required": false,
 
"required": false,
 
"dynamic": true
 
"dynamic": true
Line 6,711: Line 9,733:
 
}
 
}
 
],
 
],
"version": "9.0.000.72"
+
"version": "9.0.000.98"
 
}</pre>
 
}</pre>

Latest revision as of 17:11, September 16, 2022

options 9.0.000.98

{
	"parameters": [
		{
			"id": "system.cometd.timeout",
			"display_name": "Losing Server Connection Timeout",
			"type": "config",
			"default_value": "60000",
			"description": "Specifies the duration, in milliseconds, before the session is considered closed when the connection with the server is lost.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.timer.blinking-timeout",
			"display_name": "System timer blinking timeout",
			"type": "config",
			"default_value": "5",
			"description": "Specifies, in seconds, the timer blinking interval.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "from 0 to MAXINT",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.cometd.service-availability-delay",
			"display_name": "CometD Availability Notification delay",
			"type": "config",
			"default_value": "2000",
			"description": "Specifies the delay in milliseconds before triggering the CometD 'unavailability' ('Connection lost, reconnecting') message toast. In case a CometD 'availability' event is received before this delay, 'unavailability' message toast is canceled.",
			"version": "9.0.000.36",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.cometd.service-availability.show-on-user-action",
			"display_name": "CometD Availability Notification delay",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the CometD disconnection period. This option is independent from 'system.notif.cometd.service-availability-delay'.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.disconnected.browser-notif.events",
			"display_name": "Disconnected Browser Notification Events",
			"type": "config",
			"default_value": "ReconnectFailure,DisasterRecoveryFailure,LoginRequired",
			"description": "Specifies which connection failure and connection recovery states should display a browser notification.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of events associated with application disconnection and disaster recovery.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.browser-unsupported.ie11",
			"display_name": "Show unsupported notification for IE11",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a browser unsupported notification is to be shown for IE11 browser",
			"version": "9.0.000.98",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "alert.timeout",
			"display_name": "Contextual Message Display Timeout",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the duration, in seconds, that contextual warning messages are displayed in the windows of the application.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.url",
			"display_name": "URL",
			"type": "config",
			"default_value": "(http:\\/\\/(www.)?{{!}}https:\\/\\/(www.)?{{!}}ftp:\\/\\/(www.){{!}}www.){1}([0-9A-Za-z+&@#\\/%?=~_{{!}}!:,.;-]+\\.+[0-9A-Za-z]{2,6})([0-9A-Za-z+&@#\\/%?=~_{{!}}!:,.;-]*)?",
			"description": "Specifies the regular expression that identifies a URL in the Case Information area. This option can be overridden by a routing strategy as described in this [https://docs.genesys.com/Documentation/HTCC/Current/IWWDep/OverridingInteractionWorkspaceOptions Configuration Guide].",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.feedback",
			"display_name": "Active the feedback feature.",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a Feedback button is displayed in the About window.",
			"version": "9.0.000.25",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.feedback.message.max-length",
			"display_name": "The feedback message.",
			"type": "config",
			"default_value": "10000",
			"description": "Specifies the maximum number of characters in the feedback message.",
			"version": "9.0.000.25",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 500 through 50000.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.feedback.submit-after-disconnect",
			"display_name": "Enabled feedback submit after disconnect.",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a Feedback dialog box is displayed the next time the agent logs in after a session closed due to the Cometd defense. Managed by the system.cometd.timeout option.",
			"version": "9.0.000.25",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.log-level",
			"display_name": "The global log level",
			"type": "config",
			"default_value": "Trace",
			"description": "Specifies the global log level.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.feedback.log-level",
			"display_name": "The Feedback log level",
			"type": "config",
			"default_value": "trace",
			"description": "Specifies the feedback log level.",
			"version": "9.0.000.25",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.log-level",
			"display_name": "The Telemetry log level",
			"type": "config",
			"default_value": "Info",
			"description": "Specifies the telemetry log level.",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.open-media.service-availability-delay",
			"display_name": "OpenMedia Service Availability Notification delay",
			"type": "config",
			"default_value": "15000",
			"description": "Specifies the delay, in milliseconds, before triggering the OpenMedia (Interaction Server) unavailability notification to an agent. If an OpenMedia availability is received before the delay, unavailability notification is cancelled.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.open-media.service-availability.show-on-user-action",
			"display_name": "OpenMedia Service Availability Notification",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the OpenMedia (Interaction Server) disconnection period. This option is independent from 'system.notif.open-media.service-availability-delay'.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.contact.service-availability-delay",
			"display_name": "Contact Service Availability Notification delay",
			"type": "config",
			"default_value": "15000",
			"description": "Specifies the delay, in milliseconds, before triggering the UCS (Contact Server) unavailability notification to an agent. If a UCS availability is received before the delay, unavailability notification is cancelled.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.contact.service-availability.show-on-user-action",
			"display_name": "Contact Service Availability Notification",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the Contact (UCS) disconnection period. This option is independent from 'system.notif.contact.service-availability-delay'.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.statistic.service-availability-delay",
			"display_name": "Statistic Service Availability Notification delay",
			"type": "config",
			"default_value": "-1",
			"description": "Specifies the delay, in milliseconds, before triggering the Statistic Server unavailability notification to an agent. If a Statistic server availability is received before the delay, unavailability notification is cancelled.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.statistic.service-availability.show-on-user-action",
			"display_name": "Statistic Service Availability Notification",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if a notification is displayed when an agent action involves a call to the back-end during the Statistic server disconnection period. This option is independent from 'system.notif.statistic.service-availability-delay'.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.voice.service-availability-delay",
			"display_name": "Voice Service Availability Notification delay",
			"type": "config",
			"default_value": "15000",
			"description": "Specifies the delay, in milliseconds, before triggering the Voice unavailability notification to an agent. If a Voice availability is received before the delay, unavailability notification is cancelled.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0, or -1 to disable the notification.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.notif.voice.service-availability.show-on-user-action",
			"display_name": "Statistic Service Availability Notification",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a notification is displayed when an agent action involves a call to the back-end during the Voice server disconnection period. This option is independent from 'system.notif.voice.service-availability-delay'.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "auth.session.invalidate-on-logout",
			"display_name": "Invalidate Auth SSO session on Workspace logout",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the Auth SSO session persists when an agent logs out.<br>If true, when an agent exits Workspace, both Workspace and the Auth session are removed and the gent is redirected to the Auth login view.<br>If false, when an agent exits Workspace, only the Workspace session is removed and agent is redirected to a Workspace session ended view.",
			"version": "9.0.000.46",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "openmedia.workitem-channels",
			"display_name": "Enabled Workitem Channels",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of Workitem channels an agent may use.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid Media Types.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "<media-type>.ringing-bell",
			"display_name": "Ringing bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the path of the sound file that is played when the interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "<media-type>.auto-answer",
			"display_name": "Auto Accept Incoming Interaction",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether an interaction is automatically accepted and joined when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "<media-type>.auto-answer.timer",
			"display_name": "Auto Accept Timer For Incoming Interaction",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the time, in seconds, after which the inbound interaction of the specified type is automatically answered. A value of 0 means call is auto-ansewered immediately. For outbound push-preview interactions, use the 'outbound.push-preview.auto-answer.timer' instead. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.68",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "<media-type>.auto-answer.enable-reject",
			"display_name": "Reject button for incoming interaction with auto accept timer",
			"type": "config",
			"default_value": "false",
			"description": "When the option '<media-type>.auto-answer' with matching media type is set to true and '<media-type>.auto-answer.timer' is greater than 0, this option specifies whether the 'Reject' button is enabled when the corresponding privilige is granted. For outbound push-preview interactions, use the 'outbound.push-preview.auto-answer.enable-reject' option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.68",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "<media-type>.prompt-for-done",
			"display_name": "Prompt for done",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the application prompts a confirmation message when a user clicks the 'Done' button. This option is only available for interaction open media. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.<media-type>.queue",
			"display_name": "Routing Based Queue for Workitem",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for a Workitem. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Name of a valid Script object of type Interaction Queue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.<media-type>.routing-based-actions",
			"display_name": "Routing based actions for Workitem",
			"type": "config",
			"default_value": "OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.<media-type>.routing-based-targets",
			"display_name": "Routing based targets for Workitem",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.<media-type>.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "security.inactivity-timeout",
			"display_name": "Inactivity Timeout",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the amount of time, in minutes, of agent inactivity (no mouse or keyboard usage) that triggers the application to log out. If the agent has been inactive longer than the number of minutes that are specified by this inactivity timeout, the agent session is ended. A value of 0 disables this inactivity timeout.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "security.inactivity-alert-dialog-before-timeout",
			"display_name": "Inactivity Alert Dialog before Timeout",
			"type": "config",
			"default_value": "30",
			"description": "Specifies when Workspace displays an alert dialog to warn the agent of the upcoming inactivity timeout. The value of this option, in seconds, tells Workspace how soon to display the alert before the timeout occurs. You must set this option to a value less than the value of security.inactivity-timeout.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "security.login.inactivity-timeout",
			"display_name": "Inactivity Timeout",
			"type": "config",
			"default_value": "60",
			"description": "Specifies the amount of time, in seconds, of agent inactivity (no mouse or keyboard usage) that triggers the application to log out for the second step of the login (place selection, queue selection, language selection, etc.). If the agent has been inactive longer than the number of seconds that are specified by this inactivity timeout, the agent session is ended. A value of 0 disables this inactivity timeout.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "security.login.inactivity-alert-dialog-before-timeout",
			"display_name": "Inactivity Alert Dialog before Timeout",
			"type": "config",
			"default_value": "20",
			"description": "Specifies when Workspace displays an alert dialog to warn the agent of the upcoming inactivity timeout for the second step of the login (place selection, queue selection, language selection, etc.). The value of this option, in seconds, tells Workspace how soon to display the alert before the timeout occurs. You must set this option to a value less than the value of security.login.inactivity-timeout.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workspace.web-content",
			"display_name": "Workspace web extension views",
			"type": "config",
			"default_value": "No default value",
			"description": "The list of Web Applications that are configured to be displayed at the Workspace level. Refer to the [[Documentation:HTCC:IWWDep:SettingUpAgents:Current{{!}}Procedure: Enabling integration of web applications in the agent interface]] for information about creating web application objects in the configuration layer.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of option section names that correspond to the extension views, for example: Extension1, Extension2, etc...",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workspace.web-content.url-encoding-defense-enabled",
			"display_name": "Workspace web extension views URL Encoding",
			"type": "config",
			"default_value": "INTERNAL",
			"description": "Specifies the list of modes on which the url encoding defense is applied. If the '<mode>' is not set, the url is unmodified (not encoded). If the '<mode>' is set but no hexadecimal character (%XX, where X is a hexa) is found in the url, the url is encoded. If the '<mode>{{!}}FORCE' is set, the url is always encoded.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of one or more modes and the optional FORCE modifier in this format: <mode>[{{!}}FORCE]. Valid modes: INTERNAL, BACKGROUND, HIDDEN, EXTERNAL.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.accepted-web-content-origins",
			"display_name": "Workspace web service API granted origins and allowed API",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of granted origins and allowed APIs that are used in the web extension views. You can filter requested API with the following self-explanatory keywords:\n* 'agent.get'\n* 'agent.getStateList'\n* 'agent.setState'\n* 'agent.getState'\n* 'interaction.getInteractions'\n* 'interaction.getByInteractionId'\n* 'interaction.getByBundleId'\n* 'interaction.getByCaseId'\n* 'interaction.setUserData'\n* 'interaction.deleteUserData'\n* 'system.closeToast'\n* 'system.popupToast'\n* 'system.updateToast'\n* 'voice.dial'\n* 'voice.startCallRecording'\n* 'voice.stopCallRecording'\n* 'voice.pauseCallRecording'\n* 'voice.resumeCallRecording'\n* 'email.create'.<br>For example, the value for of this option could now be: http://my-web-server0, http://my-web-server1 , http://my-web-server2 (agent.*, voice.dial), http://my-web-server3 (agent.*, interaction.*).<br><br>In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following requests are allowed: 'agent.get', 'agent.getStateList', 'agent.setState', 'agent.getState', 'voice.dial'. For the http://my-web-server3 domain, only the following requests are allowed:\n* 'agent.get'\n* 'agent.getStateList'\n* 'agent.setState'\n* 'agent.getState'\n* 'interaction.getInteractions'\n* 'interaction.getByInteractionId'\n* 'interaction.getByBundleId'\n* 'interaction.getByCaseId'\n* 'interaction.setUserData'\n* 'interaction.deleteUserData'.<br>In addition to filtering by origin, you can filter by API with a wildcard in parentheses after the allowed origin. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of URL or '*', for example: 'http://my-web-server-1,http://my-web-server-2' or '*'.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.user-data.read-allowed",
			"display_name": "Service user data allowed to read",
			"type": "config",
			"default_value": "*",
			"description": "Specifies the list of keys that can be read in the user data. This applies to the userData property of the Interaction object returned by a function or an event.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of user data key to allow, or '*' to allow every keys, for example: Key1,Key2,Key3",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.user-data.write-allowed",
			"display_name": "Service user data allowed to write",
			"type": "config",
			"default_value": "*",
			"description": "Specifies the list of keys that the [[Documentation:HTCC:Dev:InteractionNamespace:Current#setUserData{{!}}interaction.setUserData()]] and [[Documentation:HTCC:Dev:InteractionNamespace:Current#deleteUserData{{!}}interaction.deleteUserData()]] functions can write to in the user data.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of user data key to allow, or '*' to allow every keys, for example: Key1,Key2,Key3",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.rate-limit",
			"display_name": "Service request global rate limit",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the limit for the maximum number of requests per minute on the Service Client API. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0. 0 for unlimited rate.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.rate-limit.<service-name>",
			"display_name": "Service request per API rate limit",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the limit for the maximum number of requests per minute on a specific API request on the Service Client API. The <service-name> can be one of the following: \n* agent.get\n* agent.getStateList\n* agent.setState\n* agent.getState\n* interaction.getInteractions\n* interaction.getByInteractionId\n* interaction.deleteUserData\n* interaction.setUserData\n* media.getMediaList\n* media.setState\n* system.closeToast\n* system.popupToast\n* system.updateToast\n* voice.dial\n* voice.startCallRecording\n* voice.stopCallRecording\n* voice.pauseCallRecording\n* voice.resumeCallRecording\n* email.create<br>This option cannot be overridden, it must be set in the WSA Cluster Application.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0. 0 for unlimited rate.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.rate-limit-quarantine-delay",
			"display_name": "Service request global quarantine delay once the rate limit reached",
			"type": "config",
			"default_value": "30",
			"description": "Specifies the quarantine delay, in seconds, during which requests are ignored once the rate limit is reached. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0. 0 for infinite quarantine delay.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.block-markdone-timeout",
			"display_name": "Block MarkDone Timeout",
			"type": "config",
			"default_value": "1000",
			"description": "Specifies the duration, in milliseconds, of the timeout started by the 'interaction.blockMarkdone()' service. If this option is set, when an agent marks an interaction as Done, the Mark Done operation is delayed until the specified timeout has elapsed. During this interval, Mark Done can be blocked by using the serviceClientAPI 'blockMarkdone' operation. If Mark Done is blocked by 'serviceClientAPI', the Mark Done operation is cancelled. If the Mark Done is not blocked, the Mark Done operation occurs after the specified duration has elapsed. If Mark Done has been blocked by the 'blockMarkDone' operation from the 'serviceClientAPI', it can be unblocked by using the 'unblockMarkDone' operation from the 'serviceClientAPI'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.option.read-allowed-web-content-origin",
			"display_name": "Workspace web service API granted origins and read allowed options permission",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of granted origins and read allowed options that are used in the web extension views. You can filter access to provisioning with the following self-explanatory keywords:\n* 'voice.*'\n* 'sipendpoint.*'\n* '...'<br>For example, the value of this option could now be: http://my-web-server0, http://my-web-server1 (*) , http://my-web-server2 (voice.*, system.*), http://my-web-server3 (sipendpoint.*, CustomSection/*).<br><br>In this example, all requests are allowed for the http://my-web-server0 and http://my-web-server1 domains. For the http://my-web-server2 domain, only the following access to provisioning are allowed: 'voice.*', 'system.*'. For the http://my-web-server3 domain, only the following access to provisioning are allowed:\n* 'sipendpoint.*'\n* 'CustomSection/*'<br>This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.38",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of URL or '*', with patterns for example: 'http://my-web-server-1,http://my-web-server-2(*),http://my-web-server-3(voice.*)' or '*'.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "main-window.window-title",
			"display_name": "Window Title",
			"type": "config",
			"default_value": "$Window.Title$",
			"description": "Specifies the title of the browser window or tab. You can specify any string andor combination of valid field codes up to the maximum width of the browser window title bar or tab. If all field codes are empty, the following field codes are used: $Window.Title$.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "$Window.Title$,$Application.Title$,$Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.workmode",
			"display_name": "Workmode",
			"type": "config",
			"default_value": "unknown",
			"description": "Specifies the workmode that is applied when the voice DN logs in. To determine whether your switch supports the workmodem refer to the deployment guide of the relevant T-Server.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: unknown, auto-in, manual-in.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-status.ready-workmode",
			"display_name": "Ready workmode",
			"type": "config",
			"default_value": "unknown",
			"description": "Specifies which workmode is applied on Ready operation done manually from the Global State menu and My Channels. This option is also applicable for the login.voice.is-auto-ready option. Supported workmodes are unknown, manual-in, auto-in.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: unknown, manual-in, auto-in. Empty means no workmode specified.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "keyboard.shortcut.interaction.previous",
			"display_name": "Jump to Previous Case Interaction",
			"type": "config",
			"default_value": "Alt+B",
			"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump to the previous case interaction.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "keyboard.shortcut.interaction.next",
			"display_name": "Jump to Next Case Interaction",
			"type": "config",
			"default_value": "Alt+N",
			"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump to the next case interaction.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "keyboard.shortcut.jump-to-last-error",
			"display_name": "Jump the focus to the last error.",
			"type": "config",
			"default_value": "Alt+L",
			"description": "Specifies the combination of keys that can be used as a keyboard shortcut to jump the focus to the last error.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a key or a key combination the begins with one of the following modifier key names: Ctrl, Shift, Alt, and ends with a character key. Separate the modifier key name from the character key with the '+' character.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "reporting.case.report-case-in-focus-duration",
			"display_name": "Report In Focus Duration",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the time that an interaction has been in the focus of the agent during its handling is reported to T-Server or Interaction Server at the end of its processing by the agent. When it is enabled, this notification allows Genesys Interaction Concentrator and Genesys Infomart to calculate some focus time metrics.",
			"version": "9.0.000.34",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.SideBarRegion.order",
			"display_name": "Views order in Region SideBarRegion",
			"type": "config",
			"default_value": "TeamCommunicatorView,NotificationsView,VoiceMailView,PerformanceTrackerView",
			"description": "Specifies the order (top to bottom) in which the views are displayed in the SideBar Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): TeamCommunicatorView,NotificationsView,VoiceMailView,PerformanceTrackerView",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "side-bar.web-content.url-encoding-defense-enabled",
			"display_name": "Custom Views URL Encoding in Region SideBarRegion",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of modes on which the url encoding defense is applied. If the '<mode>' is not set, the url is unmodified (not encoded). If the '<mode>' is set but no hexadecimal character (%XX, where X is a hexa) is found in the url, the url is encoded. If the '<mode>{{!}}FORCE' is set, the url is always encoded.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of one or more modes and the optional FORCE modifier in this format: <mode>[{{!}}FORCE]. Valid modes: INTERNAL, BACKGROUND, HIDDEN, EXTERNAL.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.NavigationBarRegion.activate-order",
			"display_name": "Views order in Region NavigationBarRegion",
			"type": "config",
			"default_value": "ConnectRegion,MonitoringRegion",
			"description": "Specifies in precedence order the view selected by default in the Navigation Bar Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom subregion specified in a section): Connect, Monitoring.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.NavigationBarRegion.order",
			"display_name": "Views order in Region NavigationBarRegion",
			"type": "config",
			"default_value": "ConnectRegion,MonitoringRegion",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Navigation Bar Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom subregion specified in a section): Connect, Monitoring.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.NavigationBarRegion.ConnectRegion.activate-order",
			"display_name": "Views order in Region ConnectRegion",
			"type": "config",
			"default_value": "MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
			"description": "Specifies in precedence order the view selected by default in the Connect Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.NavigationBarRegion.ConnectRegion.order",
			"display_name": "Views order in Region ConnectRegion",
			"type": "config",
			"default_value": "MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Connect Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): MyChannelsView,MyCampaignsView,MyHistoryView,WorkbinsView,InteractionsSearchView,ContactDirectoryView",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.NavigationBarRegion.MonitoringRegion.activate-order",
			"display_name": "Views order in Region MonitoringRegion",
			"type": "config",
			"default_value": "DashboardView,MyAgentsView",
			"description": "Specifies in precedence order the view selected by default in the Monitoring Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): DashboardView,MyAgentsView",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.NavigationBarRegion.MonitoringRegion.order",
			"display_name": "Views order in Region MonitoringRegion",
			"type": "config",
			"default_value": "DashboardView,MyAgentsView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Monitoring Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'workspace.web-content'): DashboardView,MyAgentsView",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.ContactRegion.order",
			"display_name": "Views order in Region ContactRegion",
			"type": "config",
			"default_value": "ContactInformationView,ContactHistoryView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Contact Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInformationView,ContactHistoryView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.ContactRegion.activate-order",
			"display_name": "Default View In Region ContactRegion",
			"type": "config",
			"default_value": "ContactInformationView,ContactHistoryView",
			"description": "Specifies, in order of precedence, the view selected by default in the Contact region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInformationView,ContactHistoryView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.HistoryInteractionDetailsRegion.order",
			"display_name": "Views order in Region HistoryInteractionDetailsRegion",
			"type": "config",
			"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the History Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.HistoryInteractionDetailsRegion.activate-order",
			"display_name": "Default view in Region HistoryInteractionDetailsRegion",
			"type": "config",
			"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
			"description": "Specifies, in order of precedence, the view selected by default in the History Interaction Details Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.WorkbinInteractionDetailsRegion.order",
			"display_name": "Views order in Region WorkbinInteractionDetailsRegion",
			"type": "config",
			"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Workbin Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.WorkbinInteractionDetailsRegion.activate-order",
			"display_name": "Default view in Region WorkbinInteractionDetailsRegion",
			"type": "config",
			"default_value": "InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView",
			"description": "Specifies in precedence order the view selected by default in the Workbin Interaction Details Region (Default view is the first configured view, if visible; else it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used except where an item order is specified.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): InteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.InteractionDetailsRegion.order",
			"display_name": "Views order in Region InteractionDetailsRegion",
			"type": "config",
			"default_value": "DispositionView,ContactInteractionNotePadView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Interaction Details Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): DispositionView,ContactInteractionNotePadView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.InteractionDetailsRegion.activate-order",
			"display_name": "Default view in Region InteractionDetailsRegion",
			"type": "config",
			"default_value": "ContactInteractionNotePadView,DispositionView",
			"description": "Specifies, in order of precedence, the view selected by default in the Interaction Details Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on). If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionNotePadView,DispositionView.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.CaseSideRegion.order",
			"display_name": "Views order in Region CaseSideRegion",
			"type": "config",
			"default_value": "AgentAssistSuggestionsView,CoBrowseView,ContactView,SRLView,RelatedView",
			"description": "Specifies the order (left to right, top to bottom) in which the views are displayed in the Case Side Region. If this option is not configured, then the default ordering is used. If you do not specify all the options, then the default setting is used for any item not specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'interaction.web-content'): ExtensionSectionName,CoBrowseView,ContactView,SRLView,RelatedView. CoBrowseView is not supported for on-premises deployments.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.CaseSideRegion.activate-order",
			"display_name": "Default view in Region CaseSideRegion",
			"type": "config",
			"default_value": "AgentAssistSuggestionsView,ContactView,SRLView,RelatedView,CoBrowseView",
			"description": "Specifies, in order of precedence, the view selected by default in the Case Side Region. (The default view is the first configured view, if visible; otherwise, it's the second configured view, if visible, and so on.) If this option is not configured, then the default setting is used. If you do not specify all the options, then the default order is used, except where an item order is specified.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views specified by the section names in the option 'interaction.web-content'): ContactView,ExtensionSectionName,SRLView,RelatedView,CoBrowseView. CoBrowseView is not supported for on-premises deployments.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.identify.phone-number",
			"display_name": "Phone Number",
			"type": "config",
			"default_value": "(?:(?:[\\+]?([\\d]{1,3}(?:[ ]*{{!}}[\\-.])))?[(]?([\\d]{1,3})[\\-\\/)]?(?:[ ]+{{!}}[\\-.])?)?([\\d]{3,})",
			"description": "Specifies the regular expression that identifies a phone number in the chat or email transcript. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.phone-number.supported-characters",
			"display_name": "Phone Number Supported Characters",
			"type": "config",
			"default_value": "0123456789+",
			"description": "Specifies the characters that are permitted when building a request to the T-Server that relies on a phone number. Any other characters from the original string coming from the User Interface are removed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Letters A to Z and a to z. Numbers 0 through 9. All special characters that are valid Windows file names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.validate.phone-number",
			"display_name": "Team Communicator Phone Number",
			"type": "config",
			"default_value": "^[\\(\\)\\-\\.\\+\\d\\s\\*#]*[\\d]+[\\(\\)\\-\\.\\+\\d\\s\\*#/]*$",
			"description": "Specifies the regular expression used to validate a phone number. It is used to recognize the phone number of a target entered in the Team Communicator when performing a call, a transfer, or a conference. If the number entered by the agent in the Team Communicator edit box matches this expression, the 'Call', 'Start Voice Consultation', 'Instant Transfer', or 'Instant Conference' action is enabled for this number. When the agent executes the action, the entered phone number is modified by the logic specified by the expression.phone-number.supported-characters option before the telephony operation is executed. This expression is also used to display a warning message if the phone number on the Contact Profile is incorrect.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.validate.email-address",
			"display_name": "Team Communicator Email Address",
			"type": "config",
			"default_value": "^([A-Za-z0-9._-]+)@([A-Za-z0-9.-]+)\\.([A-Za-z]{2,6})$",
			"description": "Specifies the regular expression used to validate an email address. It is used to recognize an email address of a target entered in the Team Communicator, and also to display warning message if the email address on the Contact Profile is incorrect.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.identify.email-address",
			"display_name": "Email Address",
			"type": "config",
			"default_value": "(\\w+([-+.]\\w+)*@\\w+([-.]\\w+)*\\.\\w+([-.]\\w+)*)",
			"description": "Specifies the regular expression that identifies an email address in a chat.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.outbound-campaign-phone-number",
			"display_name": "Outbound campaign phone number",
			"type": "config",
			"default_value": "^[\\(\\)\\-\\.\\+\\d\\s\\*#]*[\\d]+[\\(\\)\\-\\.\\+\\d\\s\\*#/]*$",
			"description": "Specifies the regular expression to validate a phone number in the 'New Phone Number' dialog to dial an Outbound Preview Record on a new phone number. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.68",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-status.enabled-actions-global",
			"display_name": "Enabled actions global",
			"type": "config",
			"default_value": "Ready,NotReady,NotReadyReason,AfterCallWork,AfterCallWorkReason,LogOff",
			"description": "Specifies the available agent states in the global Status menu. The agent state commands are displayed in the order in which they appear in the list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, Dnd, NotReadyReason, AfterCallWork, AfterCallWorkReason, LogOn, LogOff.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-status.enabled-actions-by-channel",
			"display_name": "Enabled actions by channel",
			"type": "config",
			"default_value": "Ready,NotReady,NotReadyReason,AfterCallWork,AfterCallWorkReason,LogOff",
			"description": "Specifies the available agent state actions in the My Channels contextual menu. The actions are displayed in the order in which they appear in the list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, NotReadyReason, AfterCallWork, AfterCallWorkReason, Dnd, LogOn, LogOff.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-status.not-ready-reasons",
			"display_name": "Not ready reasons",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the available reasons in the Agent Status menus (global and My Channels). The reason commands are displayed in the order in which they appear in the list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Action Code names of type Not Ready; empty means all not ready action codes are considered",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-status.after-call-work-reasons",
			"display_name": "AfterCallWork reasons",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the available reasons in the Agent Status menus (global and My Channels). Workspace displays the reason commands in the order in which they appear in the list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Action Code names of type After Call Work; empty means all not ready action codes are considered",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.agent-state-change-bell",
			"display_name": "Agent-state change bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the agent state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.permanent-statistics-change-bell",
			"display_name": "Permanent-statistics change bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the permanent statistics change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.89",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.interaction-state-change-bell",
			"display_name": "Interaction-state change bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the interaction state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.supervision-state-change-bell",
			"display_name": "Supervision state change bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the supervision state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.warning-message-bell",
			"display_name": "Warning message bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the warning message sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.dialog-bell",
			"display_name": "Dialog bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the dialog sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.dialog-error-bell",
			"display_name": "Error dialog bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the error alert sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1.The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.outbound-campaign-state-change-bell",
			"display_name": "Outbound campaign state change bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the outbound campaign state change sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.voicemail-message-change-bell",
			"display_name": "VoiceMail Message change bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Voice Mail counter change sound-configuration string for new or old messages. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound-callback.ringing-bell",
			"display_name": "Outbound campaign callback ringing-bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the outbound callback ringing sound configuration string of a scheduled callback pushed to the agent as a preview. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.new-message-bell",
			"display_name": "New Message Bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the path of the sound file Workspace plays when a new chat message arrives. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.ringing-bell",
			"display_name": "Ringing bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the path of the sound file Workspace plays when a chat interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.ringing-bell",
			"display_name": "Ringing bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the path of the sound file Workspace plays when an email interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.notification.on-party-update.enabled",
			"display_name": "Call Release Tracking Enabling",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the agent is notified when a participant leaves or joins an interaction they are handling. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.notification.on-party-update.tooltip-history-ttl",
			"display_name": "Call Release Tracking Tooltip TTL",
			"type": "config",
			"default_value": "2000",
			"description": "Specifies the duration in microseconds that the participant status notification is displayed.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "From 0 to MAXINT.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.notification.on-party-update.blink-interaction",
			"display_name": "Call Release Tracking blinking enabling",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether interactions that do not have the focus blink when the status of a participant changes.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.ringing-bell",
			"display_name": "Ringing bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the path of the sound file Workspace plays when a voice interaction is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.sip-preview.ringing-bell",
			"display_name": "Ringing bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the path of the sound file that is played when the SIP Preview is ringing. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.70",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.dialing-bell",
			"display_name": "Dialing bell",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the voice channel dialing sound-configuration string. For example: 'BELL{{!}}7{{!}}0{{!}}100'. The value has four components that are separated by the pipe ('{{!}}') character.<br>1. The sound file name (the BELL, RING, CHORD or WARNING predefined aliases or an absolute URL to a MP3 file).<br>2. A priority: the higher the integer, the higher the priority.<br>3. The duration, which can have the following values:\n* -1: play and repeat the sound until an explicit message, such as event established, causes it to stop,\n* 0: play the whole sound once,\n* an integer greater than 0: the length of time, in milliseconds, to play and repeat the sound.<br>4. The volume from 0 to 100 (100 is the default).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "All special characters that are valid URL file path, '{{!}}' separator and numeric values.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.reject-route",
			"display_name": "Reject Route",
			"type": "config",
			"default_value": "No default value",
			"description": "Workspace enables the Reject voice call operation in SIP Server environments that use multi-site routing. The reject route mechanism has been extended to accommodate different types of 'reject' implementations, depending on the context. Use this option to enable the reject route mechanism by specifying a string as a key to be used at run-time to retrieve the behavior description from the interaction user data. It is the responsibility of the administrator to define the multi-site reject criteria. The reject route is specified in the interaction user data in the following format: <reject-method>:<dn>@<switch>. When reject-method is specified, ensure that the following characters are also specified: :, @, and the switch field. The following are possible values for the reject-method attribute:<br><br>sst: Reject applies the following action: SingleStepTransfer(OtherDN=<dn>,Location=<switch>).<br>release: Reject applies the following action: releaseCall. This value must be applied when the value of the TServer/divert-on-ringing SIP Server configuration option is set to false.<br>redirect: Reject applies the following action: redirectCall<br><br>Warning: If the value of dn@switch corresponds to the same routing point as the one that is handling the call that is being delivered to the agent, the action will succeed only if the value of the TServer/divert-on-ringing SIP Server configuration option is set to true.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A string that represents an attached data key.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.reject-route.default-method",
			"display_name": "Default operation for Reject voice call",
			"type": "config",
			"default_value": "redirect",
			"description": "Specifies the default operation for a rejected voice call for environments where the mechanism specified by the interaction.reject-route option is not used for routing. This option supports the SIP Server Hunt Groups reject route mechanism. Refer to the SIP Server Deployment Guide. Specify one of the following values:\n*  redirect - Reject applies the following action: redirectCall\n*  release - Reject applies the following action: releaseCall. This value must be applied when the value of the TServer/divert-on-ringing SIP Server configuration option is set to false or for calls distributed from a Hunt Group.",
			"version": "9.0.000.86",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Specify a value from the following list: Redirect, Release.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.is-expanded-on-display",
			"display_name": "Auto expand all disposition",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the disposition tree is expanded rather than collapsed when displayed:\n*  true: Expand all dispositions\n*  false: Collapse all dispositions",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "<media-type>.detail-region.default-display-mode",
			"display_name": "Detail Region Default Display Mode",
			"type": "config",
			"default_value": "Medium",
			"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px, and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.59",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.detail-region.default-display-mode",
			"display_name": "Detail Region Default Display Mode",
			"type": "config",
			"default_value": "Medium",
			"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.59",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.detail-region.default-display-mode",
			"display_name": "Detail Region Default Display Mode",
			"type": "config",
			"default_value": "Medium",
			"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.59",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.detail-region.default-display-mode",
			"display_name": "Detail Region Default Display Mode",
			"type": "config",
			"default_value": "Medium",
			"description": "Specifies the default display mode for the Details view in the interaction view: Medium for 200px, Large for 400px and Collapsed. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.59",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Specify a value from the following list: Medium, Large, Collapsed.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-bar.quick-access-modes",
			"display_name": "Quick Access Modes",
			"type": "config",
			"default_value": "Pinned,Floating",
			"description": "Specifies the list of modes that are available to present interactions. The available modes are:\n*  Pinned: the interaction view occupies the full available size, shared with Supporting Views like Contact and Responses.\n*  Floating: the interaction view is presented in a floating window that is painted above any other kind of content and that fits the visual material to display. This view cannot display content displayed on the right part, such as Contact Profile or Responses.    <br>When more than one mode is specified, by default the first mode in the configured list is used. The end user can switch from one mode to the other using a dedicated control. For a given media type, this option can be overridden by option interaction-bar.quick-access-modes.<media-type>.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-bar.quick-access-modes.<media-type>",
			"display_name": "Quick Access Modes for open media interactions",
			"type": "config",
			"default_value": "Pinned,Floating",
			"description": "Use this option as a template to specify the list of modes available to present interactions of the given media type. The available modes are: \n*  Pinned: the interaction view occupies the full available size, shared with Supporting Views like Contact and Responses.\n*  Floating: the interaction view is presented in a floating window that is painted above any other kind of content and that fits the visual material to display. This view cannot display content displayed on the right part, such as Contact Profile or Responses. <br>When more than one mode is specified, by default the first mode in the configured list is used. The end user can switch from one mode to the other using a dedicated control. When it is defined for a media type, this option overwrites the definition of the generic option interaction-bar.quick-access-modes.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.override-option-key",
			"display_name": "Override option key",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies that certain application options can be overridden by using a transaction object. The value of this option provides the key name of the attached data that contains the list of transaction objects.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An attached data key name (string). The list is provided in the Attached Data in the strategy.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.is-mandatory",
			"display_name": "Disposition is mandatory",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether it is mandatory for the agent to set a disposition code before Marking Done an interaction. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.value-business-attribute",
			"display_name": "Disposition values Business Attribute",
			"type": "config",
			"default_value": "DispositionCode",
			"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid Business Attribute name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.related.disposition.value-business-attribute",
			"display_name": "Disposition values Business Attribute for related interactions.",
			"type": "config",
			"default_value": "$Default$",
			"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for a disposition code displayed in the Related tab. The value $Default$ specifies that the value of the interaction.disposition.value-business-attribute option is used.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid Business Attribute name or $Default$.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.related.disposition.key-name",
			"display_name": "Disposition key name for related interactions.",
			"type": "config",
			"default_value": "$Default$",
			"description": "Specifies the key that is used to populate the attached data or a user event when a disposition code is submitted from the Related tab to the back-end system, such as T-Server, Interaction Server, or Contact Server. The value $Default$ specifies that the value of the interaction.disposition.key-name option is used.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid key name or $Default$.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.key-name",
			"display_name": "Disposition key name",
			"type": "config",
			"default_value": "DispositionCode",
			"description": "Specifies the key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid key name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.folder-name-depth-<n>",
			"display_name": "Disposition folder name at depth n",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the key that is used to populate attached data or a user event when a disposition code is submitted to the back-end system, such as T-Server, Interaction Server, and Contact Server. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Valid key name associated with a disposition.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.cache-timeout-delay",
			"display_name": "Cache timeout delay for disposition",
			"type": "config",
			"default_value": "-1",
			"description": "Specifies the delay, in seconds, before the cache of a disposition request result is cleared. If set to -1, the dispositions are kept in cache until the browser page is refreshed, or until the agent logs out and logs back in.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "From -1 to MAXINT.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.web-content",
			"display_name": "Web extension views",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of Web Applications that are configured to be displayed at the Interaction level. Refer to 'Enabling integration of web applications in the agent interface in the Configuration Guide for information about creating web application objects in the configuration layer. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of option section names that correspond to web extension views. For example: Extension1, Extension2",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interation.web-content.url-encoding-defense-enabled",
			"display_name": "Web extension views URL Encoding",
			"type": "config",
			"default_value": "INTERNAL,BACKGROUND,HIDDEN{{!}}FORCE",
			"description": "Specifies the list of modes on which the url encoding defense is applied. If the '<mode>' is not set, the url is unmodified (not encoded). If the '<mode>' is set but no hexadecimal character (%XX, where X is a hexa) is found in the url, the url is encoded. If the '<mode>{{!}}FORCE' is set, the url is always encoded. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of one or more modes and the optional FORCE modifier in this format: <mode>[{{!}}FORCE]. Valid modes: INTERNAL, BACKGROUND, HIDDEN, EXTERNAL.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.auto-focus",
			"display_name": "Interaction auto focus",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the inbound interaction is in focus automatically when it is accepted. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.38",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.auto-focus.<media-type>",
			"display_name": "Interaction auto focus per media",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the inbound interaction of the specfied media type is in focus automatically when is accepted. This option overrides the 'interaction.auto-focus' option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.38",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.group-recovered-interactions.enable",
			"display_name": "Allow grouping the recovered interactions",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the recovered interactions are grouped at the start of the session.",
			"version": "9.0.000.85",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.group-recovered-interactions.activate-threshold",
			"display_name": "Threshold to group the recovered interactions",
			"type": "config",
			"default_value": "15",
			"description": "When the option 'interaction.group-recovered-interactions.enable' is true, specifies the threshold to start grouping all the recovered interactions.",
			"version": "9.0.000.85",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 5.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.case-data.enable-hyperlink",
			"display_name": "Case Data Enable hyperlink",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a hyperlink that is part of the case information may be displayed. See also the expression.url option. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.case-data.format-business-attribute",
			"display_name": "Case Data format Business Attribute",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Business Attribute that contains the Business Attribute values that are used to filter and render attached data in the interaction. This option can be overridden by a routing strategy as described in the Configuration Guide. You can define the display order of Business Attribute Values by creating an interaction-workspace section in the annex of the Business Attribute, then add the interaction.case-data.order option. This option is a comma-separated list of Business Attributes Value Names that specifies the order of  the Business Attribute Values. The Attributes Values that are not listed in interaction.case-data.order option are put at the bottom of the list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Business Attribute.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.case-data.frame-color",
			"display_name": "Case Data frame color",
			"type": "config",
			"default_value": "#17849D",
			"description": "Specifies the color of the border of the Case Data view frame. Examples: #FFFFBA00 for a Gold color, #FF6F7074 for a Silver color, #FFB8400B for a Bronze color. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Valid Hexadecimal (HTML) color code.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "toast.case-data.format-business-attribute",
			"display_name": "Case Data format Business Attribute",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Business Attribute that contains the Business Attribute Values that are used to filter and render attached data in the toast interaction preview.<br><br>You can define the display order of Business Attribute Values by creating an interaction-workspace section in the annex of the Business Attribute, then add the toast.case-data.order option. Use this option to specify a comma-separated list of Business Attributes Value Names that define the order of  the Business Attribute Values. The Attributes Values that are not listed in option toast.case-data.order are put at the bottom of the list.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The valid name of a Business Attribute.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "toast.window-title",
			"display_name": "Window Title",
			"type": "config",
			"default_value": "($Contact.FirstName$ $Contact.LastName${{!}}$Interaction.MainParty$)",
			"description": "Specifies the title of the Toast window by defining a string that contains the following field codes:$Window.Title$,$Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$,$Interaction.CaseId$,$Interaction.MainParty$,$Contact.X$,$AttachedData.Y$ (X: name of contact attribute, Y: attached data key name). If all field codes are empty, the following field codes are used: '$Window.Title$ - $Interaction.MainParty$'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "$Window.Title$,$Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$,$Interaction.CaseId$,$Interaction.MainParty$,$Contact.X$,$AttachedData.Y$ (X: name of contact attribute, Y: attached data key name).",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "service-client-api.toast.width",
			"display_name": "Toast Width for SCAPI",
			"type": "config",
			"default_value": "400",
			"description": "Specifies a custom toast width in pixel for the API system.popupToast()",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 140.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "case-data.float-separator",
			"display_name": "Float Separator",
			"type": "config",
			"default_value": ".",
			"description": "Specifies the float separator that is used for Case data. This option should be used when the decimal symbol in the regional settings of the agent workstation is different from the one provided by the database.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid float separator. Typical float separators are: '.' ',' '\\'",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.case-data.content",
			"display_name": "Case Data Content",
			"type": "config",
			"default_value": "History,CaseData",
			"description": "Specifies the content of the Case Information area in the interaction. The CaseData key enables the display of the attached data that is defined by the interaction.case-data.format-business-attribute option. The History key enables the display of interaction history information like the Origin field. The order in which the values are specified defines the order of the Case Data and History information in the Case Information area. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "History, CaseData",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "toast.case-data.content",
			"display_name": "Case Data Content",
			"type": "config",
			"default_value": "History,CaseData",
			"description": "Specifies the content of the Case Information area in the toast interaction preview. The CaseData key enables the display of the attached data that is defined by the toast.case-data.format-business-attribute option. The History key enables the display of interaction history information. The order in which the values are specified defines the order of the Case Data and History information in the Case Information area. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "History, CaseData",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.is-auto-ready",
			"display_name": "Is Auto Ready",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the voice channels are in the Ready state at login.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.auto-not-ready-reason",
			"display_name": "Is Auto Not Ready Reason",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the NotReady Reason code if the Voice channel is automatically set to NotReady when the agent logs in.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid not ready reason.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.prompt-dn-less-phone-number",
			"display_name": "Prompt DN Less Phone Number",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a new page is displayed during the login phase to show the current phone number assigned to the agent and also permits the agent to update it. This option is specific to SIP Server environment with no Config Server proxy connected to GWS.",
			"version": "9.0.000.09",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.nb-dn-less-phone-number-stored",
			"display_name": "Nb Dn Less Phone Number stored",
			"type": "config",
			"default_value": "1",
			"description": "Specifies the number of phone numbers which are stored for the agent. For this option to apply, the value of login.voice.prompt-dn-less-phone-number.enable-dynamic-dn must be true.<br>0: no phone number is pre-filled in the second login screen.<br>1: the last entered phone number is displayed in the second login screen.<br>A number greater than 1 specifies the maximum number of phone numbers that can be displayed in the second login screen.",
			"version": "9.0.000.09",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 0 through 10.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.expression.dn-less-phone-number",
			"display_name": "Expression for the DN Less Phone Number",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the valid format for a new phone number. A regular expression can be used to check the DN-less phone number format in the login window.",
			"version": "9.0.000.09",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.dn-less-phone-number.valid-format",
			"display_name": "DN Less Phone Number Valid Format",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the correct format information to be displayed to the agent when the DN less phone number format is not correct.",
			"version": "9.0.000.09",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A string",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.dn-less-phone-number.sample",
			"display_name": "DN Less Phone Number Sample",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies a sample of a DN-less phone number to be displayed in the second step of the login procedure.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A string",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.list-available-queues",
			"display_name": "Prompt Queue",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the ACD Queues that are displayed in the login window. If the option value is left blank, no queue is displayed to the agent; the agent can enter any valid login queue name. If a single queue is specified and the value of the login.voice.prompt-queue no queue information is displayed during login.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of queues.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.voice.prompt-queue",
			"display_name": "Prompt Queue",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the agent must enter the ACD Queue for the voice channel in the login window.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.prompt-place",
			"display_name": "Prompt Place",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the agent must enter his place in the login window. When this option is set to true, a new page is displayed during the login phase to specify a place. Enabling this option disables login.voice.prompt-dn-less-phone-number.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.store-recent-place",
			"display_name": "Store recent place",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the most recently used Place is stored. This option is available if the login.prompt-place option is set to true.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.list-available-locales",
			"display_name": "List of available languages",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the language that the agent can select at login time.<BR>Either, set this option empty to prevent the agent from selecting the language or set this option to $All$ to get all the languages available, or set this option to a list of languages (possible values are Brazilian (pt-BR), French (fr-FR), French Canadian (fr-CA), German (de-DE), Japanese (ja), Spanish (es), Korean (ko), Italian (it), Dutch (nl), Polish (pl), Simplified Chinese (zh-CN) and Traditional Chinese (zh-CHT)). English is the default language, and is always available.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of valid locale names based on format LanguageCode-CountryCode from the following list: $All$, en-US, pt-BR, fr-FR, fr-CA, de-DE, ja, es, ko, it, nl, pl, zh-CN, zh-CHT.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.floating-interaction-mode.auto-collapse",
			"display_name": "Auto collapse Dropdown Interaction",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether new floating voice interactions are displayed collapsed automatically.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.consultation.merge-attached-data-to-main",
			"display_name": "Merge consultation attached data to the main interaction",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether any attached data specific to the consultation (for example those defined in a corporate favorite) is merged to the main interaction.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.hold-active-call-on-make-call",
			"display_name": "Hold active call on Make Call",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the active call is turned to hold before placing an independent call. When disabled, the make call operation isn't available when there is a call on hold.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.enable-dtmf-tone",
			"display_name": "Play dtmf locally",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a tone is played when an agent clicks a DTMF key.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.auto-answer",
			"display_name": "Auto answer incoming phone call",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a voice interaction is automatically answered when a EventRinging message is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.auto-answer.is-enabled-on-already-in-call",
			"display_name": "Auto answer only if there is no other active call",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a voice interaction is automatically answered if there is other active call(s) (used only with voice.auto-answer set to true). This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.prompt-for-end",
			"display_name": "Prompt for end",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Workspace displays a confirmation message when the agent clicks End. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.mark-done-on-release",
			"display_name": "Mark done on release",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if an interaction should be closed automatically if a Release message is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.reject.counter-key-name",
			"display_name": "Reject counter key name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the key that is used to populate a counter in attached data when a call is rejected. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid key name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.cancel-after-call-work-on-done",
			"display_name": "Cancel After Call Work On Done",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the voice channel should be forced to its former status when the agent marks the voice interaction as 'Done' while his voice channel is in After Call Work status.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": " true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.cancel-after-call-work-on-business-call",
			"display_name": "Cancel After Call On Business Call",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the voice channel should be canceled its After Call Work status when the agents switches from After Call Work to Ready or Not Ready during a business call. This option is specific to SIP Server environment.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": " true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.clear-conference-on-release",
			"display_name": "Clear Conference On Release",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the conference call is cleared (all the parties in the conference are released) when the last agent leaves the conference.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.user-data.send-only-updated-data-on-complete",
			"display_name": "Send Only Updated User Data On Complete",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether only the updated user data is sent for reporting purposes when a call is completed. Otherwise, all the user data is sent when a call is completed.",
			"version": "9.0.000.68",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.enable-agent-reservation",
			"display_name": "Support agent reservation on voice media",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether Workspace should prevent an agent from manually setting the voice channel to Not Ready, Do Not Disturb, After Call Work, or Logged Off status, or from exiting the application if the agent has been marked as Reserved by the Router or any other server that can reserve an Agent for call distribution.",
			"version": "9.0.000.90",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.display-name.key-name",
			"display_name": "Attached data key for display name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the attached data key name of inbound voice interactions that contains the 'From' information of the inbound call, if the interaction does not have a contact set or the contact does not have a firstname or lastname property set. This information is displayed in the Interaction notification title and in the Recents list of Team Communicator. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.91",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid attached data key name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.<media-type>.is-auto-ready",
			"display_name": "Is Media Openmedia Auto Ready",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the channel for the specified media-type (open media) is in the Ready state at login.",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.chat.is-auto-ready",
			"display_name": "Is Media Chat Auto Ready",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the chat channel is in the Ready state at login. This option also applies to social media channels (Facebook, Twitter, SMS, and WhatsApp) which are handled in the Chat interaction view.",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.email.is-auto-ready",
			"display_name": "Is Media Email Auto Ready",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the email channel is in the Ready state at login.",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.auto-answer",
			"display_name": "Auto Accept Incoming Chat",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a chat interaction is automatically accepted and joined when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.nickname",
			"display_name": "Agent Nickname",
			"type": "config",
			"default_value": "$Agent.UserName$",
			"description": "Specifies the agent's nickname that is displayed to contacts during chat sessions. The nickname string may contain regular characters and field codes. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A string that contains a compilation of characters and field codes from the following list: $Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.FullName$,$Agent.EmployeeId$,$FirstNameLastInitial$..",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.enable-auto-disconnect",
			"display_name": "Enable Auto Disconnect",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the chat session is automatically disconnected if the agent is the last party remaining in the chat session.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.prompt-for-done",
			"display_name": "Prompt for done",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the application prompts a confirmation message when a user clicks Done. This option is only available for open media interactions. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.prompt-for-end",
			"display_name": "Prompt for end",
			"type": "config",
			"default_value": "false",
			"description": "Specifies Whether the application displays a confirmation message when an agent clicks End. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.pending-response-to-customer",
			"display_name": "Pending Customer Message Timer",
			"type": "config",
			"default_value": "30,50",
			"description": "Specifies two alarm thresholds, in seconds, that warn agents that they have a pending response to a chat from a customer. Three levels are displayed: before the warning time, between the warning time and the maximum time, and after the maximum time.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list value: warning time, maximum time",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.typing-is-enabled",
			"display_name": "Typing is enabled",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether typing notification is sent to the contact during a chat interaction. It should be disabled for Chat Server lower than 8.0.1.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.typing-timeout",
			"display_name": "Typing timeout",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the duration, in seconds, that the typing notification is displayed after the last keystroke and before the agent or contact sends their message.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A positive integer value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.time-stamp",
			"display_name": "Show Message Time Stamp",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the time stamp is displayed in the Chat transcript area.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.push-url.max-records",
			"display_name": "Maximum size of pushed URL list",
			"type": "config",
			"default_value": "20",
			"description": "Specifies maximum size of pushed URL list.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any positive integer value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.on-hold-queue",
			"display_name": "On hold queue",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Interaction Queue where the chat interaction is placed when the agent clicks Place chat on hold. This option can be overridden by a routing strategy, as described in Overriding Options by Using a Routing Strategy in the Configuration Guide.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid name of a Script of type Interaction Queue.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.print.print-content",
			"display_name": "Email interaction fields to print.",
			"type": "config",
			"default_value": "From,To,Cc,Subject,Body,Date,Attachment,InteractionType",
			"description": "Specifies the list of fields to print for an email interaction. Supported fields are: From, To, Cc, Subject, Body, Date, Attachment, InteractionType, CaseData, Note.",
			"version": "9.0.000.48",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of one or valid more email interaction fields.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.auto-answer",
			"display_name": "Auto Accept Incoming E-Mail",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether an email interaction is automatically accepted when a Interaction Server Invite event is received. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.default-queue",
			"display_name": "Default Submission Queue",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Interaction queue in which new or reply outgoing emails are submitted.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid name of a Script of type Interaction Queue.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.outbound-queue",
			"display_name": "Default Outbound Queue",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Interaction Queue in which outgoing emails are placed when agents click Send or Send Interim. This options is used only when Interaction Workflow does not set Queue for New Interactions when it is routing inbound email interactions to agents.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid name of a Script of type Interaction Queue.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.inline-forward-queue",
			"display_name": "In-line Forward Queue",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Interaction queue in which in-line forwarded inbound emails are submitted.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid name of a Script of type Interaction Queue.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.from-addresses",
			"display_name": "Default From addresses",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies a character string that specifies the name of the Business Attribute which contains the Attribute Values that are used as available addresses. These come from the addresses of email interactions. You can set a default value by using the flag from the Business Attribute value. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Business Attribute.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.allowed-image-extensions",
			"display_name": "Allowed image extensions",
			"type": "config",
			"default_value": "jpg,gif,png",
			"description": "Specifies the list of image extensions that agents can attach to an email interaction. The attachment is refused by the system and an error message is displayed to the agent if the image extension is not in the list of allowed image extensions.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated values of list of image extensions.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.max-attachment-size",
			"display_name": "Max attachment size",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the maximum number of megabytes of one file that agents can attach to an external email interaction. The attachment is refused by the system and an error message is displayed to the agent if the size in megabytes of the attached file exceeds this value. The value 0 means that there is no restriction.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A positive integer.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.max-attachments-size",
			"display_name": "Max attachments size",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the maximum number of total megabytes of files that agents can attach to an external email interaction. An error message is displayed to the agent if the total number of megabytes for all attached files exceeds this value. The value 0 means that there is no restriction.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A positive integer.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.prompt-for-done",
			"display_name": "Prompt for done",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the application prompts a confirmation message when the user clicks Done. This option is only available for interaction open media. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.reply-prefix",
			"display_name": "Reply prefix",
			"type": "config",
			"default_value": "Re: ",
			"description": "Specifies the reply prefix that is added to subject of the inbound email interaction.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.inline-forward-prefix",
			"display_name": "In-line forward prefix",
			"type": "config",
			"default_value": "Fwd: ",
			"description": "Specifies the inline forward prefix that is added to subject of the forwarded inbound email interaction.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.quote-char",
			"display_name": "Quote Char",
			"type": "config",
			"default_value": ">",
			"description": "For outgoing email that is formatted as plain text, specifies the characters that are used to quote the contents of the inbound email interaction in the outgoing email interaction body.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.include-original-text-in-reply",
			"display_name": "Include Original text in reply",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the text of the original inbound email interaction is included in the outgoing reply email. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.reply-format",
			"display_name": "Reply Format",
			"type": "config",
			"default_value": "auto",
			"description": "Specifies the format of an outgoing email reply:\n* auto: outgoing email reply format is the same as corresponding inbound email.\n* html: outgoing email reply format is forced to html.\n* plain-text: outgoing email reply format is forced to plain text.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: auto, html, plain-text.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.html-format",
			"display_name": "HTML format",
			"type": "config",
			"default_value": "true",
			"description": "Specifies the format of a new outgoing email. When set to true, new email is formatted in HTML.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.enable-toggle-format",
			"display_name": "Enable to toggle format",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the agent is permitted to switch between text and html in the email editor. Depends on 'E-Mail - Can Use E-mail Channel'. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.quote-header",
			"display_name": "Quote Header",
			"type": "config",
			"default_value": "On <date>, <contact> wrote:",
			"description": "Specifies the character string that is used to introduce the quoted inbound email interaction content in the body of the outgoing email. The value $FullHeader$ inserts the entire header of the inbound email into the outgoing email. You can also choose to include any other text. The following tags are supported: <contact>, <date>. This enables you to create a custom header, such as: 'On <date>, <contact> wrote:'.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.inline-forward-header",
			"display_name": "Inline Forward Header",
			"type": "config",
			"default_value": "$FullHeader$",
			"description": "Specifies the character string that is used to introduce the inbound email content in the body of the inline forward email. The value $FullHeader$ inserts the entire header of the inbound email interaction into the inline forwarded email. You can also choose to include any other text. The following tags are supported: <contact>, <date>. This enables you to create a custom header, such as: 'On <date>, <contact> wrote:'.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.signature.line-<n>",
			"display_name": "signature",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the row number of the signature by a string that can contain regular characters and the following field codes: $Agent.LastName$,$Agent.FirstName$,$Agent.FullName$. <n> is starting at 0. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.signature",
			"display_name": "Signature using a standard response",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the type and location of the signature template that Workspace should add to outgoing emails. The value has two components that are separated by a colon:<br>1. 'response'<br>2. The standard response name and the full path of the parent category in the Standard Response Library.<br>For example, 'response:Signatures\\Classic'.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "\\\"response:\\\" followed by the response path to the standard response",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.signature.attachments.enable",
			"display_name": "Enable attachments for email signature",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the attachments from a standard response, set in the email.signature option, are included in the related email interaction.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.qa-review-dispositions-business-attribute",
			"display_name": "QA review disposition business attributes",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as an enumerated value for qa-review-dispositions code. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.enable-email-address-validation",
			"display_name": "Enable email address validation",
			"type": "config",
			"default_value": "true",
			"description": "Specifies that the To, Cc, and Bcc addresses are validated when completing sending and forwarding.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.outbound.editable-to-addresses",
			"display_name": "Add To addresses",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether an agent can add To addresses to a new or reply outgoing email. This option can be overridden by a routing strategy, as described in the Configuiration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.outbound.editable-cc-addresses",
			"display_name": "Add Cc addresses",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether an agent can add Cc addresses to a new, reply, or forward outgoing email. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.outbound.editable-bcc-addresses",
			"display_name": "Add Bcc addresses",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether an agent can add Bcc addresses to a new, reply, or forward outgoing email. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.mandatory-subject",
			"display_name": "Mandatory subject",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the subject of an outgoing email must be specified to enable the Send operation:<ul><li>false: No control is applied on the content of the subject field.</li><li>true: Email sending cannot be completed until the subject field is not empty. An error message is displayed.</li><li>prompt: If the subject is empty, a confirmation box is displayed to prompt the agent to add a subject or proceed with sending without a subject.</li></ul>",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.insert-url.max-records",
			"display_name": "Maximum size of modified URL list",
			"type": "config",
			"default_value": "20",
			"description": "Specifies the maximum number of modified URLs in the menu in the Insert Link and Edit Link dialog boxes.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any positive integer value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "email.inline-forward.exclude-case-data-keys",
			"display_name": "List of attached data keys to be excluded in email inline forward for Case Data",
			"type": "config",
			"default_value": "ContactId,EmailAddress,FirstName,LastName,PhoneNumber,toAddresses",
			"description": "Specifies the list of attached data keys to be excluded in a email inline forward when the agent makes email inline forward.",
			"version": "9.0.000.98",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of attached data keys.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-print",
			"display_name": "Can print email",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to print email interactions from the My history and My Workbin views, and from the Contact History tabs of the Contact Directory, Interaction Search, and Interaction Detail views.",
			"version": "9.0.000.48",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-move-to-workbin",
			"display_name": "Can move to workbin",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to move email interactions to workbins.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-reply",
			"display_name": "Can use reply",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to reply to inbound email interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-reply-all",
			"display_name": "Can  reply all",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to reply to all parties included in the distribution of inbound email interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-send",
			"display_name": "Can  send",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to send outgoing email interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-interim-send",
			"display_name": "Can Interim send",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to send interim outgoing email interactions.",
			"version": "9.0.000.34",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-save",
			"display_name": "Can  save",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to save in-progress outgoing email interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-add-attachment",
			"display_name": "Can add attachment ",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to add attached files to outgoing emails.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-delete",
			"display_name": "Can delete",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to delete outgoing email interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-one-step-transfer",
			"display_name": "Can use one step transfer",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to one-step transfer email interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-inline-forward",
			"display_name": "Can use inline forward",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to forward an email inline instead of as an attachment.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-delete-attachment-from-inbound",
			"display_name": "Can delete attachment for inbound email",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to delete attachments from an inbound email interaction.",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.embedded-images.can-use",
			"display_name": "Can show embedded image",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to view embedded images in email interactions.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.embedded-images.can-add",
			"display_name": "Can add embedded image",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to add embedded images in outgoing email interactions. Depends on the option privilege.email.embedded-images.can-use.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-insert-link",
			"display_name": "Can insert link",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to insert links in outgoing email interactions.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.routing-points",
			"display_name": "Routing Points for voice",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the call number that is used by the Routing Base feature. The following attached data are added by Worskpace: IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of call number names in the following format: $dn_name@switch$",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.routing-based-actions",
			"display_name": "Routing based actions for voice",
			"type": "config",
			"default_value": "MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer",
			"description": "Specifies the list of Routing Based Actions that an agent may perform.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid operation names from the following list: MakeCall, OneStepTransfer, InitTransfer, InitConference, OneStepConference.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.routing-based-targets",
			"display_name": "Routing based targets for voice",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of targets that are contacted through the routing based mechanism for the requests that are defined by the intercommunication.voice.routing-based-actions option. Note: The targets AgentGroup and Skill are always addressed through routing; therefore, they are not affected by this option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, RoutingPoint, ACDQueue, TypeDestination, OutboundRecord, Contact",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.make-call-caller-id-business-attribute",
			"display_name": "Make call caller-id business attribute",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Business Attribute that contains the Attribute Values that are used as outbound caller IDs. This option is only applicable for external calls.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Letters A to Z and a to z. Numbers 0 through 9. The underscore and space characters.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.make-call-caller-id-enable-anonymous",
			"display_name": "Enable Anonymous on Make Call Caller-ID",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether anonymous is enabled on make call with caller id. This option is only applicable for external calls. This functionality can currently only be used in conjunction with the SIP Server TServer\\/enforce-p-asserted-identity option configured on the outbound PSTN Trunk DN. This must be configured in the environment where the PSTN Provider (Carrier) implements Calling Line Identification Restriction (CLIR) and allows masking the displayed number (Caller ID) only if privacy SIP headers are correctly constructed and 'anonymous@anonymous.invalid' is specified in the From field.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.caller-id.key-name",
			"display_name": "Attached Data Key for Caller Id",
			"type": "config",
			"default_value": "IW_SelectedCallerId",
			"description": "Specifies the key name of the attached data that contains the selected caller id information.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An attached data key name (string)",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.single-step-conference-enabled",
			"display_name": "Single Step Conference enabled for voice",
			"type": "config",
			"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
			"description": "Specifies the list of targets enabled in Team Communication for a single step conference.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.single-step-transfer-enabled",
			"display_name": "Single Step Transfer enabled for voice",
			"type": "config",
			"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
			"description": "Specifies the list of targets enabled in Team Communication for a single step transfer.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.consultation-enabled",
			"display_name": "Consultation enabled for voice",
			"type": "config",
			"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
			"description": "Specifies the list of targets enabled in Team Communication for a consultation.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.make-call-enabled",
			"display_name": "Make Call enabled",
			"type": "config",
			"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
			"description": "Specifies the list of targets enabled in Team Communication for making call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, ACDQueue, Contact, TypeDestination, Skill, Teams.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.chat.queue",
			"display_name": "Routing Based Queue for chat",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Chat. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Name of a valid Script object of type Interaction Queue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.chat.routing-based-actions",
			"display_name": "Routing based actions for chat",
			"type": "config",
			"default_value": "InitTransfer,OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid operation names from the following list: InitTransfer, OneStepTransfer, OneStepConference.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.chat.routing-based-targets",
			"display_name": "Routing based targets for chat",
			"type": "config",
			"default_value": "No default value",
			"description": "Defines the list of targets that are contacted through the 'routing based' mechanism for the requests that are defined in the option 'intercommunication.chat.routing-based-actions'. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.email.queue",
			"display_name": "Routing Based Queue for email",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for email. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Name of a valid Script object of type Interaction Queue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.email.routing-based-actions",
			"display_name": "Routing based actions for email",
			"type": "config",
			"default_value": "OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.email.routing-based-targets",
			"display_name": "Routing based targets for email",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are specified in the 'intercommunication.email.routing-based-actions' option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.workitem.queue",
			"display_name": "Routing Based Queue for workitem",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Interaction Queue that is used by the 'routing based' feature for Workitem. The following attached data are added by Worskpace:IW_RoutingBasedOriginalEmployeeId,IW_RoutingBasedTargetId,IW_RoutingBasedTargetType,IW_RoutingBasedRequestType.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Name of a valid Script object of type Interaction Queue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.workitem.routing-based-actions",
			"display_name": "Routing based actions for workitem",
			"type": "config",
			"default_value": "OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid operation names from the following list: OneStepTransfer.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.workitem.routing-based-targets",
			"display_name": "Routing based targets for workitem",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of targets that are contacted through the 'routing based' mechanism for the requests that are specified in the 'intercommunication.workitem.routing-based-actions' option. Note: The targets 'AgentGroup' and 'Skill' are always addressed through routing; therefore, they are not affected by this option.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, InteractionQueue",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.call-result-values",
			"display_name": "Call result values",
			"type": "config",
			"default_value": "Answered,AnsweringMachine,Busy,NoAnswer,WrongNumber",
			"description": "Specifies the list of call results that are available for the agent to use for an outbound interaction. The call results are displayed in the order in which they appear in the list.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select at least one item from the list.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.call-result-automatically-selected",
			"display_name": "Call Result automatically selected",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the call result to be selected by default for outbound records. The specified call result must be defined by the values that are specified for the outbound.call-result-values option. If set to an empty value, the current call result of the outbound record is selected, or unknown is selected if there is no current value.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any available call result value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.preview.max-simultaneous-preview-record",
			"display_name": "Maximum number of simultaneous preview record",
			"type": "config",
			"default_value": "-1",
			"description": "Specifies the maximum number of simultaneous Outbound Preview records an agent can view in the interaction window. A 0 or a negative value indicates no limit.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.treatment-mode",
			"display_name": "Treatment Mode",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the type of treatment to be applied for the outbound record after it is marked as processed. If not set or set to 'none', no treatment is applied for the outbound record. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "personal, campaign",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.negotiate-logout-on-exit",
			"display_name": "Negotiate Logout",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether negotiated logout with Outbound Server is enabled for Outbound campaigns. In negotiated logout, agents cannot log out of Workspace if they are the target of an outbound record or have an unclosed record. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.38",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.timed-preview-auto-dial",
			"display_name": "Outbound Timed Preview Auto Dial",
			"type": "config",
			"default_value": "-1",
			"description": "Specifies whether agents in Preview, Push preview, and Reschedule preview campaigns can manually dial a record, have the call auto-dialed as soon as the record is accepted, or have the call auto-dialed after a specified number of seconds. If set to 0, the interaction is dialed as soon as it is accepted. A value of -1 disables automatic dialing. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.48",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any integer greater than or equal to -1",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.callback-types",
			"display_name": "Outbound Callback Types",
			"type": "config",
			"default_value": "Personal,Campaign",
			"description": "Specifies the list of callback types (Personal,Campaign) from which an agent can select when rescheduling an outbound record. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.42",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Personal,Campaign",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.call-result-is-mandatory",
			"display_name": "Outbound Call Result",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether it is mandatory for an agent to seelct a call result other than 'Unknown' before marking the interaction as done.",
			"version": "9.0.000.51",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.agent-preview-mode",
			"display_name": "Outbound Agent Preview Mode",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if Workspace sends PreviewDialingModeStart and PreviewDialingModeStop events to OCS for every campaign running in Preview mode.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.direct-push-preview-toast.timeout",
			"display_name": "Outbound Direct Push Preview Toast",
			"type": "config",
			"default_value": "20",
			"description": "Specifies the time duration in seconds for which Workspace waits for the agent to accept/reject a toast for a Direct Push Preview interaction before automatically removing the toast and rejecting the record and telling OCS to send a new one.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A integer from 5 through 60",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.direct-push-preview.no-record-timeout",
			"display_name": "Outbound Direct Push Preview Timeout",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the duration, in seconds, for which Workspace, after having sent a Preview Mode Start request, waits for OCS to send a Direct Push Preview record before displaying a toast to the agent informing them that there are no more records in the current campaign.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A integer from 10 through 60",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.push-preview-mode",
			"display_name": "Outbound Push Preview Mode",
			"type": "config",
			"default_value": "regular",
			"description": "Specifies whether Outbound Push Preview camapigns are running in regular or direct mode. In direct mode, OCS communicates directly with Workspace instead of utilizing Interaction Server to handle interactions. This means that there is no automatic agent state control.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "One of either regular or direct",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "outbound.dispositions-allowing-treatment-on-reschedule",
			"display_name": "Outbound Treatment on Reschedule",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of disposition codes that, if at least one is selected by an agent when handling and Outbound call, causes the treatment specified by the outbound-treatment-mode option to be sent to OCS when the interaction is marked Done after it is rescheduled. This option can be overridden by a routing strategy as described in Configuration Guide.",
			"version": "9.0.000.73",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma seperated list of valid disposition codes",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-use",
			"display_name": "Can use",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to the Outbound Campaign functions.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.push-preview.can-use",
			"display_name": "Push Preview can use",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to the Push Preview Outbound Campaign functions.",
			"version": "9.0.000.26",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-mark-do-not-call",
			"display_name": "Can Mark Do Not Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to mark a contact as Do Not Call.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-set-call-result",
			"display_name": "Can Set Call Result",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to set a call result to the outbound record.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-reject-record",
			"display_name": "Can Reject Record",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to decline a preview record. If an agent declines a preview record, it can be processed by another agent in the campaign.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-cancel-record",
			"display_name": "Can Cancel Record",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to cancel a preview record. If an agent cancels a preview record, it is not processed again during the current campaign.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-dial-on-new-number",
			"display_name": "an Dial On New Number for outbound",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to dial an outbound contact on a new number, resulting in a new record added to the chain. Depends on 'Outbound - Can Use' and 'Can Dial Alternative Chained Record'.",
			"version": "9.0.000.68",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-dial-alternative-chained-record",
			"display_name": "Can Dial Alternative Chained Record",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to dial a number from the preview record chain that is different than the number selected by the system.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-get-next-preview-record",
			"display_name": "Get Next Preview Record",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to request a new preview record while processing of the previous preview record terminates.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-reschedule",
			"display_name": "Can Reschedule",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to reschedule an outbound record for an active call. Use the privilege.outbound.can-reschedule-before-call privilege to allow rescheduling before the call is dialed.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-reschedule-before-call",
			"display_name": "Can Reschedule Before Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to reschedule an outbound record before calling the contact.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.can-reschedule-on-new-number",
			"display_name": "Can Reschedule On New Number",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to reschedule an outbound record on a new number (which adds a new record to the chain).",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.record-information.can-view",
			"display_name": "Outbound Record Information",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to view the Record Information area in an Outbound Record.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.outbound.record-information.can-update",
			"display_name": "Outbound Record Information",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to edit or update fields in the Record Information area of an Outbound Record that are configured as editable. If this privilege is present, then the value of the privilege.outbound.record-information.can-view privilege is implicitly considered to be set to true.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-make-call",
			"display_name": "Can Make Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to make a new voice call from any area enabling voice calls.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-answer-call",
			"display_name": "Can Answer Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to manually answer an incoming voice call. Setting this option to false hides the Accept button in the Interaction notification pop-up.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-release-call",
			"display_name": "Can Release Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to manually end voice calls.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-release-a-held-call",
			"display_name": "Can Release Held Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to manually end voice calls in held state.",
			"version": "9.0.000.27",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-hold-retrieve-call",
			"display_name": "Can Hold/Retrieve Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables and agent to hold or retrieve a voice call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-one-step-conference",
			"display_name": "Can One Step Conference",
			"type": "config",
			"default_value": "true",
			"description": "Enables instant conferencing of a voice call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-one-step-transfer",
			"display_name": "Can One Step Transfer",
			"type": "config",
			"default_value": "true",
			"description": "Enables instant conferencing of a voice call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-two-step-conference",
			"display_name": "Can Two Step Conference",
			"type": "config",
			"default_value": "true",
			"description": "Enables two-step conference for voice calls.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-set-interaction-disposition",
			"display_name": "Can Set Interaction Disposition",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to set the disposition code on voice interactions.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-two-step-transfer",
			"display_name": "Can Two Step Transfer",
			"type": "config",
			"default_value": "true",
			"description": "Enables two-step transfer of a voice call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-forward",
			"display_name": "Can forward",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to forward voice calls.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-reject-call",
			"display_name": "Can Reject Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to reject an incoming voice call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-extend-after-call-work",
			"display_name": "Can Extend the After Call Work",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to extend the After Call Work state.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.make-call.can-use-caller-id",
			"display_name": "Can Use Caller Id - Make Call",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to use caller ID for making calls.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.use-caller-id-display-name",
			"display_name": "Use Caller Id Display Name",
			"type": "config",
			"default_value": "false",
			"description": "Specifies that the Caller Id Display Name is to be used when caller id is used. This feature requires that the value of the SIP Server TServer/use-display-name option be set to true. The Caller Id Display Name should be the display name of the caller ID in business attribute value specified by the intercommunication.voice.make-call-caller-id-business-attribute option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.single-step-conference.can-use-caller-id",
			"display_name": "Can Use Caller Id - Single Step Conference",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use caller ID for single-step conferences.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.single-step-transfer.can-use-caller-id",
			"display_name": "Can Use Caller Id - Single Step Transfer",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use caller ID for single-step transfers.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.consultation.can-use-caller-id",
			"display_name": "Can Use Caller Id - Consultation",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use caller ID for consultations.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-show-hold-duration",
			"display_name": "Can Show Hold Duration",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to see the amount of time that a voice call has been on hold.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-show-post-call-duration",
			"display_name": "Can Show Post Call Duration",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to see the post call duration in the tooltip and in the interaction bar of a voice call.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.hold-indicator-timer",
			"display_name": "Hold Indicator Timer",
			"type": "config",
			"default_value": "30,60",
			"description": "Specifies two alarm thresholds, in seconds, that warn agents that a voice call is on hold for a long time. Three levels are displayed: before the warning time, between the warning time and the maximum time, and after the maximum time.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list value: warning time, maximum time",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.restore-state-on-back-in-service.is-enabled",
			"display_name": "State restoring on back in service",
			"type": "config",
			"default_value": "false",
			"description": "If voice channel goes Out of Service, this option specifies whether Workspace should attempt to automatically set the voice channel back to its previous state when it is back in service.",
			"version": "9.0.000.50",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.restore-state-on-back-in-service.time",
			"display_name": "State restoring on back in service time",
			"type": "config",
			"default_value": "3",
			"description": "If voice channel goes Out of Service and the value of the voice.restore-state-on-back-in-service.is-enabled option is true, this option specifies the amount of time, in seconds, to set channel back to its previous state when it is back in service.",
			"version": "9.0.000.50",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 0 through 10.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.dial-plan-rule-<rule-name>",
			"display_name": "Dial Plan rule",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the rules that are used to transform destination numbers into the requested format before being dialed. Also overrides for Routing Points, caller id business attribute and enabling of anonymous caller id can be set as parameters. For details, refer to https://docs.genesys.com/Options:Genesys_Web_Services:interaction-workspace:voice-dial-plan-rule-zrule-name-",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A rule in the format: pattern => digit translation[;parameters...]#comment",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.dial-plan.types-enabled",
			"display_name": "Enabled Dial Plan Types",
			"type": "config",
			"default_value": "Contact, TypeDestination",
			"description": "Specifies the list of targets to which the dial plan is applied. Valid targets include Agent, RoutingPoint, Contact, and TypeDestination objects.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of target types",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.dial-plan-can-set-intercommunication-options",
			"display_name": "Dial Plan rule",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether dial plan rules are extended to configure routing points, caller id business attributes, and anonymous caller id configurations specific to the dialed number.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "standard-response.categories",
			"display_name": "Categories to display from Standard Response Library",
			"type": "config",
			"default_value": "$All$",
			"description": "Specifies the list of categories used to filter Standard Responses. Agents see only those Standard Responses that are part of the sub-tree of categories set in the value for this option.<br><br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of category names or full path category starting at the root category. $All$ to display Standard Responses from all categories.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "standard-response.field.<CustomFieldCode>",
			"display_name": "Field to display from Standard Response Library",
			"type": "config",
			"default_value": "No default value",
			"description": "In the name of the option, CustomFieldCode represents a field code that is called in a Standard Response object created in eServices Manager and stored in Universal Contact Server. Use this option to specify a custom field code such as a role, department, or other qualification. The value of the option is specific to the agent, agent group, tenant, or application. The value of this option represents the data that is used to populate the corresponding field codes when a Standard Response is inserted into an interaction. You can format CustomFieldCode to represent a custom agent attribute. Example: standard-response.field.Department = Sales",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid text string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "standard-response.field.Agent.<CustomFieldCode>",
			"display_name": "Field to display from Standard Response Library",
			"type": "config",
			"default_value": "No default value",
			"description": "In the name of the option, CustomFieldCode represents a field code that is called in a Standard Response object created in eServices Manager and stored in Universal Contact Server. Use this option to specify a custom field code such as an agent nickname, role, department, or other qualification. The value of the option is specific to the agent, agent group, tenant, or application. The value of this option represents the data that is used to populate the corresponding field codes when a Standard Response is inserted into an interaction. You can format CustomFieldCode to represent a custom agent attribute. Example: standard-response.field.Agent.Nickname = Lee",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid text string.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "standard-response.shortcuts.<keyword>",
			"display_name": "Standard Response shortcut keyword template",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the 'keyword' for a shortcut where the name of the option represents the keyword to be entered by agents to use the shortcut. For example: 'standard-response.shortcuts.JulySale'. Specify the path to the Response that is defined in Knowledge Manager as the value for this option. For example '2021Specials\\JulySale'.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Path to the standard response as defined in the Knowledge Manager.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "standard-response.suggested-responses.min-relevance",
			"display_name": "Minimum relevance above which suggested response are displayed",
			"type": "config",
			"default_value": "50",
			"description": "Specifies the minimum level of relevance to filter the display of suggested responses in the Responses view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any integer between 1 to 100",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "standard-response.suggested-categories.max-number",
			"display_name": "Maximum number of suggested categories to be displayed",
			"type": "config",
			"default_value": "20",
			"description": "Specifies the maximum number of suggested response categories displayed in the Responses view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer between 1 and 20",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.standard-response.shortcuts.can-use",
			"display_name": "Enable shortcuts for Standard Responses",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use shortcuts to insert Standard Responses.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.standard-response.shortcuts.can-filter",
			"display_name": "Filter Standard Responses with shortcuts",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to filter Standard Responses in the Standard Responses tree view to show only those with shortcuts.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.standard-response.favorites.can-use",
			"display_name": "Enable favorite Standard Response",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to use favorites for Standard Responses.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.SRL.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to the Standard Response Library functions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.SRL.can-quick-search",
			"display_name": "Can do Quick Search",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to perform a Quick Search of the Standard Response Library.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.standard-response.suggested-response.can-use",
			"display_name": "Enable suggested responses",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to use suggested responses in the Responses view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voicemail.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use the voicemail functionality. This privilege is required to control and monitor voicemail boxes.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voicemail.can-use-empty-shared-mailbox",
			"display_name": "Can Use Empty Shared Mailbox",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to dial both their personal and group voice mailboxes whether they have a message waiting or not.",
			"version": "9.0.000.79",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voicemail.access-number",
			"display_name": "Voice Mail Directory Number",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the number to call to access your voicemail system.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any Valid DN",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voicemail.notification-types",
			"display_name": "Types of displayed mailboxes",
			"type": "config",
			"default_value": "personal, public",
			"description": "Specifies the types of voicemail boxes included in the count of unread voicemail messages in the Main Window. personal refers to the voicemail box that is identified as the personal voicemail box of the agent; public refers to the group voicemail boxes to which the agent has access.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of action names from the following list: personal, public",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voicemail.request-timeout",
			"display_name": "Request timeout",
			"type": "config",
			"default_value": "1",
			"description": "Specifies the time, in seconds, to wait for voicemail messages from Feature Server. If no voicemail messages are received during this timeout, a request is sent to Feature Server to get them.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voicemail.voicemail-service.request-interval",
			"display_name": "Voicemail Service Request Interval",
			"type": "config",
			"default_value": "60",
			"description": "Specifies the frequency, in seconds, with which to query the voicemail service for voicemail MWI.",
			"version": "9.0.000.86",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer between 30 and 300",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.actions.display-mode",
			"display_name": "Action display mode",
			"type": "config",
			"default_value": "hover",
			"description": "Specifies the display mode for Team Communicator action buttons.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: hover (actions appear only on mouseover on related entry), block (expose a default action button for all entries).",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.enable-lazy-loading",
			"display_name": "Enable Team Communicator Lazy Loading mechanism (IE11 only)",
			"type": "config",
			"default_value": "false",
			"description": "For Internet Explorer 11 environments, if Team Communicator is slow to load due to a large number of search results, including Favorites and Recents, you can use this option to enable Lazy (asynchronous) loading to load only those results that are currently visible in the scrolling list.",
			"version": "9.0.000.75",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.<media-type>.list-status-reachable",
			"display_name": "List of reachable status for voice call",
			"type": "config",
			"default_value": "NotReady",
			"description": "Specifies the list of unavailable statuses for which a target agent can be contacted for consultation, transfer, and conference requests. If the unavailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.",
			"version": "9.0.000.53",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.voice.list-status-reachable",
			"display_name": "List of reachable status for voice call",
			"type": "config",
			"default_value": "NotReady",
			"description": "Specifies the list of unavailable statuses for which a target agent can be contacted for consultation, transfer, and conference requests. If the unavailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.email.list-status-reachable",
			"display_name": "List of reachable status for email",
			"type": "config",
			"default_value": "NotReady",
			"description": "Specifies the list of unvailable statuses for which a target agent can be contacted for transfer requests. If the unvailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for transfer requests. Depends on 'Email - Can Use Email Channel' and 'TeamCommunicator - Evaluate Presence'.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.chat.list-status-reachable",
			"display_name": "List of reachable status for chat",
			"type": "config",
			"default_value": "NotReady",
			"description": "Specifies the list of unvailable statuses for which a target agent can be contacted for consultation, transfer, and conference, requests. If the unvailable status of the target agent is not in the list of allowed statuses, the target agent will not be listed as available for consultation, transfer, and conference requests. Depends on 'Chat - Can Use Chat Channel' and 'TeamCommunicator - Evaluate Presence'.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A case-sensitive comma-separated list of agent status from the following list: NotReady, Busy, LoggedOff",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.load-at-startup",
			"display_name": "Load Elements at startup",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether all the configuration elements (Agents, Agent Groups, Queues, Routing Points, Skills) needed by Team Communicator are loaded at login. This option is used to help with performance at login if many agents login at the same time. When this option is set to false, the elements are not loaded at login, they are loaded the first time the focus is placed in the Team Communicator.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.routing-point-presence-metrics",
			"display_name": "Routing Point Presence Metrics",
			"type": "config",
			"default_value": "routing-point-presence",
			"description": "Specifies a list of routing point presence sections. Each of these sections contains a valid statistic name related to the routing point, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma separated value list of routing point presence options section names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.queue-presence-metrics",
			"display_name": "Queue Presence Metrics",
			"type": "config",
			"default_value": "queue-presence",
			"description": "Specifies a list of Queue presence sections. Each of these sections contains a valid statistic name related to the Queue, the text to be displayed in Team Communicator, a warning level value, an error level value, and a list of object ids that apply to this presence statistic.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma separated value list of queue presence options section names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "presence.evaluate-presence",
			"display_name": "Evaluate Presence",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the presence (availability) of agents, agent groups, Routing Points and Queues (when configured) is shown in Team Communicator in the search results.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.always-clear-textbox-on-new-interaction",
			"display_name": "always clear textbox on new interaction",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the Team Communicator text search box is cleared after the interaction is initiated when the agent presses 'Enter' or clicks one of the medias in the Team Communicator results. When set to false, the Team Communicator text search box is cleared only if an interaction is initiated by the agent pressing 'Enter'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.list-filter-showing",
			"display_name": "Displayed Object Types",
			"type": "config",
			"default_value": "Agent,AgentGroup,RoutingPoint,Skill,InteractionQueue,Contact,CustomContact",
			"description": "Specifies the list of filters that an agent can use to search for contacts and internal targets by using the team communicator. The object types are presented in the specified order.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Skill, Contact, InteractionQueue, ACDQueue, CustomContact, Teams.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.max-suggestion-size",
			"display_name": "Max suggestion size",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the maximum size of the suggestion list that is displayed while an agent is entering a contact or target name.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.recent-max-records",
			"display_name": "Maximum Recent Records",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the number of recent internal targets to display in the list of recent targets.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.max-favorites-size",
			"display_name": "Max favorites size",
			"type": "config",
			"default_value": "50",
			"description": "Specifies the maximum size of the favorites list that is displayed while an agent is displaying favorites.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 0 through 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.max-size",
			"display_name": "Max size",
			"type": "config",
			"default_value": "50",
			"description": "Specifies the maximum size of the default list when the value of teamcommunicator.show-all-internal-targets is set to true.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 0 through 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.show-all-internal-targets",
			"display_name": "Show all internal targets",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether all internal targets are displayed by default in the Team Communicator when an agent is searching for a transfer or conference target, including all Agents, Agent Groups, Skills, and Routing Points.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.corporate-favorites",
			"display_name": "Corporate Favorite List",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of corporate favorites (quick dial favorites) that are configured in the Configuration Server for an Agent, Agent Group, Skill, Routing Point, Queue, Interaction Queue, or Custom Contact. See the procedure 'Creating Corporate Favorites' in the Configuration Guide for information about creating Corporate Favorite objects in the configuration layer. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of favorite names (section names) that are defined in the Workspace application.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.request-start-timer",
			"display_name": "Request start timer",
			"type": "config",
			"default_value": "500",
			"description": "Specifies the request start timer wait interval, in milliseconds, between the last key pressed and the beginning of the search through the contact database.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 1 through 5000.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.add-recent-filters.voice",
			"display_name": "Incoming interaction filter (Voice)",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies whether to store incoming interactions into the Recent buffer. By default, the Recent buffer stores only the actions of the agent, such as recent outbound voice calls. If one or more of the valid values is specified, then recent inbound interactions of that type are also stored in the Recent buffer. This enables agents to see a record of missed calls of the specified type(s).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of interaction types taken from the following values: internal, external, consultation.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.voice.apply-exclude-to-favorites",
			"display_name": "apply exclude options to favorites",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether to apply exclude options to all targets, including favorites.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.voice.make-call.exclude-numbers",
			"display_name": "Phone Numbers to exclude from Make Call action in Team Communicator",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the format for a phone number to exclude on making a call. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}$.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.voice.single-step-transfer.exclude-numbers",
			"display_name": "Phone Numbers to exclude from Single Step Transfer action in Team Communicator",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the format for a phone number to exclude on single-step transfer. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}$.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.voice.single-step-conference.exclude-numbers",
			"display_name": "Phone Numbers to exclude from Single Step Conference action in Team Communicator",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the format for a phone number to exclude on single-step conference. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}$.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.voice.consultation.exclude-numbers",
			"display_name": "Phone Numbers to exclude from Consultation action in Team Communicator",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the format for a phone number to exclude on consultation. The check is done after Workspace applies a clean-up on the phone number the agent entered in Team Communicator based on the expression.phone-number.supported-characters option. For example, to exclude extensions that are 7 digits and start with the numbers 7 or 8, set this option to ^(7{{!}}8)\\d{6}$.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A regular expression.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.permissions.agent.restrict-to-agent-groups",
			"display_name": "restrict search of agents to agent-groups",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of agent groups or virtual agent groups used to restrict agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are included in the list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Agent Groups; empty means no restriction applied.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.permissions.agent.exclude-from-agent-groups",
			"display_name": "search exclude agents from agent-groups",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of agent groups or virtual agent groups used to exclude agents returned in a Team Communicator search. Agents who belong to at least one of these agent groups are excluded from the list. Note: This overrides the teamcommunicator.permissions.agent.restrict-to-agent-groups filter where there is overlap. For example, if an agent belongs to groups A and B, and the exclude filter specifies B while the include filter specifies A, the agent is excluded from the returned list.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.permissions.ms-teams.restrict-to-ad-group-id",
			"display_name": "Group ID for Graph API",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the id of the Azure Active Directory group to which searches of MS Teams users is to be restricted.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid Azure Active Directory group identifier.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.permissions.ms-teams.restrict-to",
			"display_name": "Attribute name for detailed search in Graph API",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the user properties of Azure Active Directory users to which searches of MS Teams are to be restricted.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid user properties attribute name and attribute value pair, grouped by parentheses in the Azure Active Directory.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.permissions.ms-teams.exclude",
			"display_name": "Attribute name for exclude from search in Graph API",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the user properties of Azure Active Directory users from which searches of MS Teams are to be excluded.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid user properties attribute name and attribute value pair, grouped by parentheses in the Azure Active Directory.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.one-step-transfer-with-consultation.enabled",
			"display_name": "Team Communicator - Enable One Step Transfer with Consultation",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether agents can make a one-step transfer of a call when there is an active consultation on the call. When the value of this option is set to false, the one-step transfer button is not displayed and agents cannot perform a one-step transfer operation when there is an active consultation.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamcommunicator.one-step-conference-with-consultation.enabled",
			"display_name": "Team Communicator - Enable One Step Conference with Consultation",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether agents can make a one-step conference of a call when there is an active consultation on the call. When the value of this option is set to false, the one-step conference button is not displayed and agents cannot perform a one-step conference operation when there is an active consultation.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "permissions.agent-group.exclude",
			"display_name": "exclude agent-groups",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of agent groups to be excluded from searches and statistics. This option is overridden by the permissions.agent-group.restrict option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "permissions.agent-group.restrict",
			"display_name": "Restrict search of agent-groups",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of agent groups that are returned for searches and statistics. Overrides the permissions.agent-group.exclude option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Agent Groups; empty means no filtering.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to the Contact features.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-delete-contact",
			"display_name": "Can Delete Contact",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to delete contacts from the contact database.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.enable-force-delete-contact",
			"display_name": "Can Force Delete Contact",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether an agent is allowed to delete a contact even if the contact has one or more in-progress interactions.",
			"version": "9.0.000.70",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-create-contact",
			"display_name": "Can Create Contact",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to create contacts.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-history",
			"display_name": "Can Use Contact History",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to access the Contact History view.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-information",
			"display_name": "Can Use Contact Information",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to view and manage contact information.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-directory",
			"display_name": "Can Use Contact Directory",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to view and search the Contact Directory.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-history-detail",
			"display_name": "Can Use Contact History Detail",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to see the detail of interactions in the Contact History view.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-history-notepad",
			"display_name": "Can Use Contact History Notepad",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to see notes about interactions in the Contact History view.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-history-case-data",
			"display_name": "Can Use Contact History CaseData",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to see the case information of interactions in the Contact History view.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-save-contact",
			"display_name": "Can Edit Contact",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to commit (save) modifications to contact information.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-interaction-notepad",
			"display_name": "Can Use Interaction Notepad",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to display and edit the interaction notepad while handling an interaction.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-related-interactions",
			"display_name": "Enables Conversation View Tab",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to access the Related tab in the Case Side View. The Related tab contains interactions in the same thread (conversations) as the current interaction. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.90",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-mark-done-related-interactions",
			"display_name": "Can mark done from related view.",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to use the Related tab in the interaction view to mark as Done single and multiple related interactions and apply the same disposition code to each.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-delete-related-interactions",
			"display_name": "Can delete from related view.",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to delete single and multiple related interactions from the Related tab in the interaction view",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.related-interactions.custom-attributes",
			"display_name": "Related interactions custom attributes",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of interaction custom attributes to be displayed in the Related tab interaction cards. Only the first two attributes are displayed. If you specify more than two attributes, the others are ignored.",
			"version": "9.0.000.90",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of interaction custom attributes",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.related-interactions.sort-by.attributes",
			"display_name": "Related interactions sort by attributes",
			"type": "config",
			"default_value": "$All$",
			"description": "Specifies the list of predefined and custom attributes by which the interactions in the Related tab may be sorted. In the Sort By menu, the attributes are displayed in the configured order. Custom attributes specified by this option must also be specified by the contact.related-interactions.custom-attribute.",
			"version": "9.0.000.90",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of predefined and custom attributes of an interaction. Example: StartDate,Status,Subject,OwnerId,TypeId,CustomAttr1. To include all predefined and custom attributes, use the value $All$ in this option.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.related-interactions.open.max-number",
			"display_name": "Maximum Number of Related Interactions Open",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the maximum number of related interactions that may be opened simultaneously by a single Open action.",
			"version": "9.0.000.90",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 1 through 10.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.default-directory-page-size",
			"display_name": "Default directory page size",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the default value for the number of rows per page in the contact directory search result view. The value must be defined in the option contact.available-directory-page-size.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.available-directory-page-sizes",
			"display_name": "Available directory page sizes",
			"type": "config",
			"default_value": "5,10,25,50",
			"description": "Specifies the possible values for the number of rows per page in the contact directory search result view.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.mandatory-attributes",
			"display_name": "Mandatory attributes",
			"type": "config",
			"default_value": "FirstName,LastName",
			"description": "Specifies the list of Contact fields that must be completed for a contact.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names, for example: LastName, FirstName, PhoneNumber, EmailAddress.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.multiple-value-attributes",
			"display_name": "Multiple Value attributes",
			"type": "config",
			"default_value": "PhoneNumber,EmailAddress",
			"description": "Specifies the list of contact attributes that can support multiple values.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma separated value list of Attribute Value names that correspond to contact field names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.displayed-attributes",
			"display_name": "Diplayed attributes",
			"type": "config",
			"default_value": "Title,FirstName,LastName,PhoneNumber,EmailAddress",
			"description": "Specifies the list of contact fields that are displayed when a Contact record is displayed.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.directory-displayed-columns",
			"display_name": "Diplayed Columns",
			"type": "config",
			"default_value": "LastName,FirstName,PhoneNumber,EmailAddress",
			"description": "Specifies the list of contact fields that are displayed when the results of a contact search are displayed.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names -- for example: LastName,FirstName,PhoneNumber,EmailAddress.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.directory-search-attributes",
			"display_name": "Directory search attributes",
			"type": "config",
			"default_value": "LastName,FirstName,PhoneNumber,EmailAddress",
			"description": "Specifies the list of Contact fields that can be used as search parameters.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Attribute Value names that correspond to contact field names that can be used as search parameters.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.directory-search-mode",
			"display_name": "Directory search mode",
			"type": "config",
			"default_value": "sql",
			"description": "Specifies the technical mode used in the Contact Directory view to search for contacts. The lucene mode must be used for large database of contacts.",
			"version": "9.0.000.37",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: sql, lucene",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.enable",
			"display_name": "Enable Contact Lookup",
			"type": "config",
			"default_value": "true",
			"description": "Specifies that Universal Contact Server (UCS) lookup is activated for contacts when an interaction is presented to the Agent. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option is taken into account only when attached data 'IdentifyCreateContact' is not set in the interaction and the contact.lookup.<media-type>.enable option is not specified for the applicable media type.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.enable-create-contact",
			"display_name": "Enable Contact Creation on Lookup",
			"type": "config",
			"default_value": "true",
			"description": "When the value of this option is true and the value of ontact.lookup.enable is also set to true, this option specifies that Universal Contact Server (UCS) creates a contact if the initial search does not find a matching existing contact. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option is taken into account only when attached data 'IdentifyCreateContact' is not set in the interaction and the contact.lookup.<media-type>.enable-create-contact option is not specified for the applicable media type.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.auto-assign-mode",
			"display_name": "Enable Contact Lookup Auto Assign",
			"type": "config",
			"default_value": "true",
			"description": "Specifies the contact assignment policy when Contact Lookup is enabled. If set to false and there are multiple matched contacts for an interaction, they are listed as suggested contacts. If set to true, the first contact will be assigned automatically irrespective of the number of matched contacts. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.<media-type>.auto-assign-mode",
			"display_name": "Enable Contact Lookup Auto Assign for open media interactions",
			"type": "config",
			"default_value": "true",
			"description": "Specifies the contact assignment policy when Contact Lookup is enabled for the specified media type. If set to false and there are multiple matched contacts for an interaction, they are listed as suggested contacts. If set to true, the first contact will be assigned automatically irrespective of number of matched contacts.This option overrides contact.lookup.auto-assign-mode for the specified media type. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.create-contact.check-duplicate",
			"display_name": "Alert Duplicate contact ",
			"type": "config",
			"default_value": "false",
			"description": "If an agent tries to create a contact that potentially matches one or more in the contact database, Workspace displays the list of potential matches, then allows an agent to either create the new contact or select an existing contact instead. Use the following options to control what UCS attributes are searched to determine whether a new contact is a potential duplicate. These options can be configured individually or together to allow \\\"AND\\\" and \\\"OR\\\" searches.<br> *contact.potential-match.search-query.and-clause\n* contact.potential-match.search-query.or-clause<br>This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.74",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.potential-match.search-query.and-clause",
			"display_name": "List of Attributes for Search Rule AND",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of contact attributes, each of which will be added as an AND clause in the search query to retrieve potential duplicate contacts from UCS during contact creation in Workspace.",
			"version": "9.0.000.74",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "List of contact attributes including custom attributes",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.potential-match.search-query.or-clause",
			"display_name": "List of Attributes for Search Rule OR",
			"type": "config",
			"default_value": "PhoneNumber, EmailAddress",
			"description": "Specifies the list of contact attributes, each of which will be added as an OR clause in the search query to retrieve potential duplicate contacts from UCS during contact creation in Workspace.",
			"version": "9.0.000.74",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "List of contact attributes including custom attributes",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.<media-type>.enable",
			"display_name": "Enable Contact Lookup for open-media interactions",
			"type": "config",
			"default_value": "true",
			"description": "Specifies that the Workspace features that rely on Universal Contact Server (UCS) for contact lookup when an interaction of the given media type is presented to the Agent are activated. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable option. It is not taken into account when the attached data IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup behavior in the context of outbound campaign interactions.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.<media-type>.enable-create-contact",
			"display_name": "Enable Contact Creation on Lookup for open-media interactions",
			"type": "config",
			"default_value": "true",
			"description": "When contact lookup is enabled in the context of the current interaction, this option specifies that the Universal Contact Server (UCS) creates a contact if the initial search cannot find any existing contact. This option can be overridden by a routing strategy as described in the Configuration Guide. Note: This option overwrites the contact.lookup.enable-create-contact option. It is not taken into account when the attached data 'IdentifyCreateContact is set in the interaction. Use the voice-campaign media-type to define the lookup and create behavior in the context of outbound campaign interactions.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.voice.use-dialed-phone-number",
			"display_name": "Lookup contact using the dialed number",
			"type": "config",
			"default_value": "false",
			"description": "If contact lookup is enabled, this option specifies that contact lookup is performed on the normalized phone number that was manually dialed by the agent rather than the number resulting from the application of dial plan rules, if any.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.voice.use-formatted-number",
			"display_name": "Inbound Contact Creation",
			"type": "config",
			"default_value": "true",
			"description": "Specifies that the phone number of an inbound voice interaction is subject to processing by the expression.phone-number.supported-characters option prior to contact lookup. This option depends on the option contact.lookup.enable-create-contact. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.voice.intercommunication.use-dialed-phone-number",
			"display_name": "Lookup contact using the dialed number, for Intercommunication",
			"type": "config",
			"default_value": "true",
			"description": "If contact lookup is enabled, and intercommunication is configured, this option specifies that contact lookup is performed on the phone number typed by an agent for an outgoing call to Routing Point.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.phone-number-validation.enable",
			"display_name": "Enable Contact Phone Number Validation",
			"type": "config",
			"default_value": "true",
			"description": " In environments using UCSX server, this option specifies whether phone numbers are validated on the client side when contact records are created or updated.",
			"version": "9.0.000.85",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.ucs-interaction.voice.enable-create",
			"display_name": "Enable History Record Creation for Voice interactions",
			"type": "config",
			"default_value": "true",
			"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Voice interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.ucs-interaction.voice.enable-create-without-contact",
			"display_name": "Contact - Enable History Record Creation for voice interaction without contact",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a voice interaction is created in Universal Contact Server (UCS) when there is no associated contact. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.ucs-interaction.voice-campaign.create-without-contact",
			"display_name": "Contact - Enable History Record Creation for outbound campaign interaction without contact",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a outbound campaign interaction is created in Universal Contact Server (UCS) when there is no associated contact. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.90",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.ucs-interaction.voice-campaign.enable-create",
			"display_name": "Enable History Record Creation for Outbound Campaign Voice interactions",
			"type": "config",
			"default_value": "false",
			"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Voice Outbound Campaign interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.ucs-interaction.<media-type>.enable-create",
			"display_name": "Enable History Record Creation for Open Media Workitem interactions (For Chat, Email, Facebook, Twitter media, the interactions are automatically created in UCS interaction history)",
			"type": "config",
			"default_value": "true",
			"description": "Specifies that the feature that generates the interaction history in Universal Contact Server (UCS) for Open Media Workitem interactions is activated. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.ucs-interaction.voice.unanswered.enable-create",
			"display_name": "Enable History Record Creation for Unanswered Voice interactions",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether a call history is created in UCS for outgoing calls that are not answered by a contact. If this option is set to true, unanswered calls are added to the UCS database and are viewable in the My History, Contact Directory, Interaction History, and Contact History tabs. This option can be overridden by a routing strategy, as described in the Configuration Guide.",
			"version": "9.0.000.67",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.voice.anonymous-contact.key-name",
			"display_name": "Contact anonymous key name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the attached data key that specifies whether contact information is treated as anonymous in the interaction view, case information, and history. If the key value is 1, contact information is masked.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid key name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-displayed-columns",
			"display_name": "Diplayed Columns in History",
			"type": "config",
			"default_value": "Status,Subject,StartDate,EndDate,OwnerId",
			"description": "Specifies the list of Contact History items that are displayed in the interaction view.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Contact History items to display in the interaction view, for example: Status, Subject, StartDate, EndDate, OwnerId.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.myhistory-displayed-columns",
			"display_name": "My History Diplayed Columns",
			"type": "config",
			"default_value": "Status,Subject,StartDate,EndDate",
			"description": "Specifies the list of Contact History items that are displayed in the My History view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Contact History items to display in the interaction view MyHistory, for example: Status, Subject, StartDate, EndDate.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.all-interactions-displayed-columns",
			"display_name": "Interactions Search Displayed Columns",
			"type": "config",
			"default_value": "Status,Subject,StartDate,EndDate",
			"description": "Specifies the list of interaction attributes that are displayed in the result list of the Interaction Search view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Contact History items to display in the interaction view MyHistory, for example: Status, Subject, StartDate, EndDate.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-displayed-columns-conversations",
			"display_name": "Displayed Columns in History Conversations View",
			"type": "config",
			"default_value": "Status,Subject,StartDate,EndDate",
			"description": "Specifies the list of interaction fields that are displayed in the Contact History view in the conversation (thread) mode.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Contact History items to display in the History conversations view - for example: Subject, StartDate, EndDate, Status.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.myhistory-displayed-columns-conversations",
			"display_name": "Displayed columns in My History conversations View",
			"type": "config",
			"default_value": "Status,Subject,StartDate,EndDate",
			"description": "Specifies the list of interaction fields that are displayed in the My History view in the conversation (thread) mode.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A Comma-separated list of interaction fields to display in My History conversations view - for example: Subject, StartDate, EndDate, Status.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.all-interactions-quick-search-attributes",
			"display_name": "Interaction Search Quick Search Attributes",
			"type": "config",
			"default_value": "Subject",
			"description": "Specifies the interaction attributes that are used to search interactions in the Quick Search mode of the Interaction Search view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.myhistory-quick-search-attributes",
			"display_name": "My History Quick Search Attributes",
			"type": "config",
			"default_value": "Subject",
			"description": "Specifies the interaction attributes that are used to search interactions in the quick search mode of the My History view. These attributes must be text attributes. You can use custom interaction attibutes. For more information, see 'Making an Attribute Searchable from the Desktop' in the PureEngage Digital Administrator's Guide.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject. Possible searchable attributes are: BccAddresses, CcAddresses, FromAddress, FromPersonal, Id, Mailbox, ReplyToAddress, StructuredText, Subject, Text, TheComment, ToAddresses",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-quick-search-attributes",
			"display_name": "Contact History Quick Search Attributes",
			"type": "config",
			"default_value": "Subject",
			"description": "Specifies the interaction attributes that are used to search interactions in the quick search mode of the Contact History view. These attributes should be text attributes.  You can use custom interaction attributes. For more information, see 'Making an Attribute Searchable from the Desktop' in the PureEngage Digital Administrator's Guide.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of valid interaction attribute names, for example: Subject. Possible searchable attributes are: BccAddresses, CcAddresses, FromAddress, FromPersonal, Id, Mailbox, ReplyToAddress, StructuredText, Subject, Text, TheComment, ToAddresses",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history.quick-search.max-input-length",
			"display_name": "History Interactions Quick Search Input Length",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the maximum number of words that can be used to make a quick search of interaction in My History, Contact History and Interaction Search",
			"version": "9.0.000.85",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 1 through 20.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-search-attributes",
			"display_name": "History Search Attributes",
			"type": "config",
			"default_value": "Status,StartDate,EndDate,Subject",
			"description": "Specifies the list of interaction attributes that an agent can use in Advanced Search mode of the Contact History, My History and Interaction Search views. You can also use custom interaction attributes.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Interaction attributes.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-search-attribute-group.<group-name>",
			"display_name": "History Search Attributes",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies a group of interaction search attributes. Use this option as a template, modifying the name by replacing the <group-name> by the name of a group to be displayed in the Advanced Search mode of Contact History, My History, and Interaction Search views.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value list of Interaction attributes.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.date-search-types",
			"display_name": "Types of Date Search",
			"type": "config",
			"default_value": "On,OnOrAfter,Before,Between",
			"description": "Specifies the list of search types that are available for the agent to use to search the contact database by date.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select at least one from the list.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-default-time-filter-main",
			"display_name": "Contact History Default Time Filter",
			"type": "config",
			"default_value": "1M",
			"description": "Specifies which Time Filter option is selected by default in the Contact History view when an agent accesses the main history data source:\n*  All: All interactions from  the main Universal Contact Server (UCS) database.\n*  1M: Interactions from main UCS database that were created less than 1 month ago.\n*  1W: Interactions from main UCS database that were created less than 1 week ago.\n*  1D: Interactions from main UCS database that were created less than 1 day ago.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: All, 1M, 1W, 1D",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.myhistory-default-time-filter-main",
			"display_name": "My History Default Time Filter",
			"type": "config",
			"default_value": "1M",
			"description": "Specifies which Time Filter option is selected by default in the My History view when an agent accesses the main history data source:\n*  All: All interactions from the main Universal Contact Server (UCS) database.\n*  1M: Interactions from main UCS database that were created less than 1 month ago.\n*  1W: Interactions from main UCS database that were created less than 1 week ago.\n*  1D: Interactions from main UCS database that were created less than 1 day ago.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: All, 1M, 1W, 1D",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.all-interactions-default-time-filter-main",
			"display_name": "All Interactions Default Time Filter",
			"type": "config",
			"default_value": "1M",
			"description": "Specifies which Time Filter is selected by default in the All Interactions Search view when an agent accesses the view.<br><ul><li>All: all interactions from Main UCS Data Base.</li><li>1M: interactions from Main UCS Data Base that were created less than 1 month ago.</li><li>1W: interactions from Main UCS Data Base that were created less than 1 week ago.</li><li>1D: interactions from Main UCS Data Base that were created less than 1 day ago.</li></ul>",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: All, 1M, 1W, 1D",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history.media-filters",
			"display_name": "Contact history Media Filters",
			"type": "config",
			"default_value": "voice,email,chat,twitter,facebook,$OtherMedia$",
			"description": "Specifies the list of media types that can be used to filter the Contact History (depends on privilege.contact.can-filter-contact-history), My History (depends on privilege.contact.can-filter-my-history), and the result list of Interaction Search(depends on privilege.contact.can-filter-all-interactions). $OtherMedia$ allows to add the filter returning any media not listed in this option.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated value of valid media type names or $OtherMedia$.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.email-address-validation.attributes",
			"display_name": "Validation for the email address attributes",
			"type": "config",
			"default_value": "EmailAddress",
			"description": "Specifies which contact attributes from the Contact Profile are considered to be email addresses to be validated.<br>The default expression used for validation is specified by the expression.validate.email-address option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A list of contact attributes that can support email expression pattern validation",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.phone-number-validation.attributes",
			"display_name": "Validation for the phone number attributes",
			"type": "config",
			"default_value": "PhoneNumber",
			"description": "Specifies which contact attributes from the Contact Profile are considered to be phone numbers to be validated.<br>The default expression used for validation is specified by the expression.validate.phone-number option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A list of contact attributes that can support phone number expression pattern validation",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-search-contact-history",
			"display_name": "Can Search Contact History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to search for interactions in the Contact History view.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-filter-contact-history",
			"display_name": "Can Filter Contact History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to filter interactions in the Contact History view.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-advanced-search-contact-history",
			"display_name": "Can Do Advanced Search in Contact History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to do advanced searches within the Contact History view.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-mark-done.<media-type>.from-history",
			"display_name": "Can Mark Done from History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to mark done in-progress interactions of the corresponding media-type from history. Depends on 'Contact - Can Use'.",
			"version": "9.0.000.24",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-open.<media-type>.from-history",
			"display_name": "Can Open from History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to open in-progress workitems of the corresponding media-type from history. Depends on 'Contact - Can Use'.",
			"version": "9.0.000.24",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-open.<media-type>.from-universal-queue",
			"display_name": "Can Open from Universal Queue",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to open in-progress emails and workitems of the corresponding media type from the Universal Queue. Depends on 'Contact - Can Use', 'Contact - Can Open from History' and 'Contact - Can use interaction workfow state'.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-re-open.<media-type>.from-universal-queue",
			"display_name": "Can Re-Open from Universal Queue",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to re-open completed emails and workitems of the corresponding media type from the Universal Queue. Depends on 'Contact - Can Use' and 'Contact - Can use interaction workfow state'.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-mark-done.email.from-history",
			"display_name": "Can mark done email from History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to mark done in-progress email interactions from the interaction history. Depends on 'Contact - Can Use'.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-open.email.from-history",
			"display_name": "Can Open email from History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to open in-progress email interactions from the interaction history. Depends on 'Contact - Can Use'.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-interaction-workflow-state",
			"display_name": "Can use interaction workfow state",
			"type": "config",
			"default_value": "false",
			"description": "When viewing digital interactions in the Contact History view, agents can see the exact status of an interaction while it is being processed. Depends on 'Contact - Can Use'.",
			"version": "9.0.000.73",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-open.from-queue",
			"display_name": "Can Open from queue",
			"type": "config",
			"default_value": "true",
			"description": "From the History, enables agents to open interactions that are in the In-Progress state and are in a queue. Depends on 'Contact - Can Use', 'Contact - Can Open from History' and 'Contact - Can use interaction workfow state'.",
			"version": "9.0.000.73",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-open.from-other-personal-workbins",
			"display_name": "Can Open from other personal workbins",
			"type": "config",
			"default_value": "true",
			"description": "From the History, enables agents to open interactions that are in the In-Progress state and are in the Workbin of another agent. Depends on 'Contact - Can Use', 'Contact - Can Open from History' and 'Contact - Can use interaction workfow state'.",
			"version": "9.0.000.73",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-resend.email.from-history",
			"display_name": "Can re-send email from History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to re-send an email from the interaction history. Depends on 'Contact - Can Use'.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-inline-forward.email.from-history",
			"display_name": "Can forward email inline from History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to forward email interactions from the Interaction History that are marked as Done.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-filter-all-interactions",
			"display_name": "Can Filter All Interactions",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to filter interactions in the Interaction Search view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-search-all-interactions",
			"display_name": "Can Search All Interactions",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to search among all interactions.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-advanced-search-all-interactions",
			"display_name": "Can Do Advanced Search for All Interactions",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to do advanced searches of all interactions.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-filter-my-history",
			"display_name": "Can Filter My History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to filter interactions within the My history view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-search-my-history",
			"display_name": "Can Search My History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to search for interactions in the My History view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-advanced-search-my-history",
			"display_name": "Can Do Advanced Search in My History",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to do advanced searches within My History.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-conversations",
			"display_name": "Can display interactions in conversations View",
			"type": "config",
			"default_value": "true",
			"description": "Enables agent to toggle the interaction display format from flat view to the threaded conversations view.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.history-default-view-conversations",
			"display_name": "Display interactions in conversations View by default",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the My History and Contact History are displayed in conversation (thread) mode or Normal (flat) mode, by default.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.last-called-agent.enable",
			"display_name": "Enable Last Called Agent",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the last called agent properties are set in the contact when an interaction is presented to the agent. This option is taken into account only when the contact.last-called-agent.<media-type>.enable option is not defined for the applicable media type.",
			"version": "9.0.000.21",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.last-called-agent.<media-type>.enable",
			"display_name": "Enable Last Called Agent",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the last called agent properties are set in the contact when an interaction of the corresponding media type is presented to the agent. This option overrides the contact.last-called-agent.enable option. Use the voice-campaign media-type to define the look-up behavior for outbound campaign interactions.",
			"version": "9.0.000.21",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-contact-myhistory",
			"display_name": "Can Use My Contact History",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to access their own history of interactions with contacts.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.contact.can-use-assign-contact",
			"display_name": "Can Assign Contact",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to assign a contact to an interaction.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.screen-recording.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "false",
			"description": "Enables the usage of Screen Recording Client.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screen-recording.client.address",
			"display_name": "Client address",
			"type": "config",
			"default_value": "127.0.0.1",
			"description": "Specifies the IP address or host name on which Screen Recording Client listens for credentials.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "String corresponding to the Screen Recording Client ip address or host name",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screen-recording.client.port",
			"display_name": "Client Port",
			"type": "config",
			"default_value": "443",
			"description": "Specifies the port on which Screen Recording Client listens for credentials.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "String corresponding to the Screen Recording Client port number",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screen-recording.client.secure-connection",
			"display_name": "Flag specifying if to use secure connection to Screen Recording Client",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a secure connection is used for communication with Screen Recording Client",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "True or false, specifying if secure connection will be used",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screen-recording.client.server-url",
			"display_name": "Specifies the GWS Server address for SRS.",
			"type": "config",
			"default_value": "No default value",
			"description": "Defines the address of the RWS server to be used for communication by Screen Recording Client. The field code $GWS_URL$ is supported allowing to specify the usage of the same origin as WWE UI. If the option is empty, the WWE UI origin is used. A list of RWS/WWE UI pairs can be defined based on the pattern: <rws_origin_url>(<wwe_origin_url>). This list could be based on a single pair. In case of none matching, the default behavior is used.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Valid URL",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.interaction-management.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "false",
			"description": "Enables supervisors to access the Interaction Management feature.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.interaction-management.case-data.can-edit",
			"display_name": "Can Edit case Data",
			"type": "config",
			"default_value": "false",
			"description": "Enables supervisors to edit case data for interactions directly from Workbins and Interaction Queues without pulling the interactions first.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.interaction-management.can-move-to-queue",
			"display_name": "Can Move to queue",
			"type": "config",
			"default_value": "false",
			"description": "Enables supervisors to move interactions to a queue.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.interaction-management.can-move-to-workbin",
			"display_name": "Can Move to Workbins",
			"type": "config",
			"default_value": "false",
			"description": "Enables supervisors to move interactions to a workbin.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.interaction-management.can-search-interactions",
			"display_name": "Can Search interactions",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to search for interactions in interaction queues content.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.available-interaction-page-sizes",
			"display_name": "Available Content Page Sizes",
			"type": "config",
			"default_value": "5,10,25,50",
			"description": "Specifies the possible values for the number of rows per page in the Interaction Management content view. Values grater than 100 are not recommended due to performance impact. The maximum value depends on the content of interactions and the robustness of your network. If you specify a value that is too high, the request to get a snapshot fails and an error message is displayed.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.default-interaction-page-size",
			"display_name": "Default content page size",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the default value for the number of rows per page in the Interaction Management content view.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.filters",
			"display_name": "Filters",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the filters that are displayed to the supervisor for interaction management. The filter names refer to the names of the Application Option sections that define the Filters. See 'Creating Interaction Filters for Team Leads' in the Configuration Guide for more information.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Filter names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.interactions-filter.displayed-columns",
			"display_name": "Displayed Columns Configuration of Interaction Queue",
			"type": "config",
			"default_value": "From,To,Subject,Received",
			"description": "Specifies the list of interaction fields that are displayed as columns in Interaction Queue view when displayed-columns is not defined in the Filter.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of attached data, for example: From,Subject,Received",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.filters.quick-search-attributes",
			"display_name": "Quick Search Attributes of Interaction Queue",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in an interaction queue for which quick-search-attributes is not defined in the Filter.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of attached data, for example: AssignedTo,FromAddress",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.move-to-workbin.restrict-to-my-team",
			"display_name": "restrict move to workbins to workbins of the logged agent team.",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if the search applied in Team Communicator for Move to Workbin action should be restricted to the workbins of the logged agent team.",
			"version": "9.0.000.48",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-management.markdone.mandatory-case-data-check.enable",
			"display_name": "Mandatory case data check before Mark Done.",
			"type": "config",
			"default_value": "false",
			"description": "Specifies if a check is to be made to ensure interactions are not missing mandatory case data before they are allowed to be marked done.",
			"version": "9.0.000.94",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.monitor-dashboard.can-use",
			"display_name": "Can use the Dashboard",
			"type": "config",
			"default_value": "true",
			"description": "Enables the Contact Center Statistics dashboard tab.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.default-page-size",
			"display_name": "Default page size",
			"type": "config",
			"default_value": "50",
			"description": "Specifies the default value for the number of statistics objects per page in the Contact Center Statistics view. The value must be defined in the option statistics.available-page-size.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 10 through 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.available-page-sizes",
			"display_name": "Available page sizes",
			"type": "config",
			"default_value": "10,20,30",
			"description": "Specifies the possible values for the number of statistics objects per page in the contact center statistics view.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of numbers that define the number of statistics objects per result page from which the agent can make selections.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.routing-points",
			"display_name": "List of routing points displayed in the dashboard, and in Contact Center Statistics",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of routing points that are displayed in the Contact Center Statistics tab. If empty, no routing points are displayed. If set to a list and none of the routing points match an existing routing point, no routing points are displayed.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.agent-groups",
			"display_name": "List of agent groups or virtual agent groups displayed in the Contact Center Statistics",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of agent groups and virtual agent groups that are displayed in the Contact Center Statistics tab. If empty, no agent groups or virtual agent groups are displayed. If set to a list and none of the groups in the list match an existing group, no agent groups or virtual agent groups are displayed.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.virtual-queues",
			"display_name": "List of virtual queues displayed in the Contact Center Statistics",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of virtual queues that are displayed in the Contact Center Statistics tab. If empty, no virtual queues are displayed. If set to a list and none of the virtual queues in the list match an existing virtual queue, no virtual queues are displayed.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.queue-groups",
			"display_name": "List of group of queues (dn groups) displayed in the Contact Center Statistics",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of queue groups that are displayed in the Contact Center Statistics tab. If empty, no queue groups are displayed. If set to a list and none of the queue groups in the list match an existing queue group, no queue groups are displayed.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.my-team-workbins.can-use",
			"display_name": "Can Use My Team Workbins",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to My Team Workbins.",
			"version": "9.0.000.20",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "my-team-workbins.agent-page-size",
			"display_name": "Agent page size",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the value for the number of agents per page in My Team Workbins sub-tree of My Workbins view.",
			"version": "9.0.000.30",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.email.draft",
			"display_name": "Draft E-Mail workbin",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the workbin to be used to store draft email.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.email.in-progress",
			"display_name": "In Progress E-Mail workbin",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the workbin that is to be used to store inbound email for later processing, after an agent explicitly saved the email or submitted an outbound reply.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.email.in-progress.displayed-columns",
			"display_name": "In Progress E-mail workbin Displayed Columns",
			"type": "config",
			"default_value": "From,Subject,Received",
			"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores inbound email for later processing.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Interaction Server interaction properties, for example: From,Subject,Received",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.email.draft.displayed-columns",
			"display_name": "Draft E-Mail workbin Displayed Columns",
			"type": "config",
			"default_value": "To,Subject,Submitted",
			"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores draft email interactions.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Interaction Server interaction properties, for example: To,Subject,Submitted",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.email.review",
			"display_name": "QA Review E-Mail workbin",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the workbin that is to be used to store QA reviews for later processing, after a reviewer explicitly saved the email.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.email.review.displayed-columns",
			"display_name": "QA Review E-Mail workbin Displayed Columns",
			"type": "config",
			"default_value": "To,Subject,Submitted",
			"description": "Specifies the list of interaction fields displayed as columns in the workbin that stores QA reviews.",
			"version": "9.0.000.16",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Interaction Server interaction properties, for example: To,Subject,Submitted",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.<media-type>.in-progress",
			"display_name": "Template for Workitem Workbin declaration",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the workbin to be used to store interactions of a particular workitem media type. Agents can open interactions from this workbin but not save interactions in it.",
			"version": "9.0.000.24",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.<media-type>.<workbin-nickname>",
			"display_name": "Template for Custom Workbin declaration",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the workbin to be used to store interactions of a particular workitem media type. Agents can open interactions from this workbin but not save interactions in it.",
			"version": "9.0.000.24",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Script object of type Interaction Workbin that is owned by Agents.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.<media-type>.<workbin-nickname>.displayed-columns",
			"display_name": "Template for Displayed Columns Configuration of a Custom Workbin",
			"type": "config",
			"default_value": "From,To,Subject,Received",
			"description": "Specifies the list of interaction fields displayed as columns in the specified workbin.",
			"version": "9.0.000.24",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Interaction Server interaction properties, for example: From,Subject,Received",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.quick-search-attributes",
			"display_name": "Quick Search Attributes of Workbin",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in a workbin for which workbin.<media-type>.<workbin-nickname>.quick-search-attributes is not defined.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Interaction Server interaction properties, for example: AssignedTo,FromAddress",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workbin.<media-type>.<workbin-nickname>.quick-search-attributes",
			"display_name": "Template for Interaction Quick Search Attributes Configuration of a Custom Workbin",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of interaction properties that are used to build the Quick Search query against Interaction Server when the agent makes a quick search in the specified workbin. Default value of this option is the Value of workbin.quick-search-attributes if defined.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Interaction Server interaction properties, for example: AssignedTo,FromAddress",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.workbin.can-search-my-workbins-trees",
			"display_name": "Can Search Workbin",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to search for workbins in the navigation tree of the My Workbins View.",
			"version": "9.0.000.30",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.workbin.can-search-interactions",
			"display_name": "Can Search interactions",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to search for interactions in workbins content.",
			"version": "9.0.000.39",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.monitoring-scope",
			"display_name": "Monitoring Scope",
			"type": "config",
			"default_value": "call",
			"description": "Specifies the scope of monitoring that is to be used for voice interactions. If the value call is specified, the supervisor remains on the call until it is finished. This mode enables barge-in. If the value agent is specified, the system disconnects the supervisor automatically from the call when the monitored agent leaves the call. In this mode, the barge-in operation is not possible.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: agent,call",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.monitoring-current-call-timeout",
			"display_name": "Monitoring Current Call Timeout",
			"type": "config",
			"default_value": "0",
			"description": "In scenarios where a contact has opted out of call monitoring, use this option to specify the duration before monitoring and coaching of the current call is considered failed due to time out. To disable timeout, specify a value less than 5.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 5 to 300.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.default-page-size",
			"display_name": "Default page size",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the default value for the number of rows per page in the My Agents view. The value is added to the list defined by the option teamlead.myagents.available-page-sizes.",
			"version": "9.0.000.48",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.available-page-sizes",
			"display_name": "Available page sizes",
			"type": "config",
			"default_value": "5,10,25,50",
			"description": "Specifies the possible values for the number of rows per page in the My Agents view.",
			"version": "9.0.000.48",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of numbers that define the number of rows per result page from which the agent can make selections.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.refresh-rate",
			"display_name": "My Agents refresh rate",
			"type": "config",
			"default_value": "30",
			"description": "Specifies the frequency, in seconds, to refresh the list of agents. To disable automatic refresh, specify a value less than 5 to indicate manual refresh. Automatic refresh is also disabled if the value of the accessibility.visual-impairment-profile option is true.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Valid values are integer values between 5 and 5000. Values less than 5 disables the automatic refresh.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.manual-refresh.enabled",
			"display_name": "My Agents enable manual refresh",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the manual refresh button is displayed in the My Agents view. Manual refresh is automatically enabled if automatic refresh is disabled by the teamlead.myagents.refresh-rate option.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.enabled-channels",
			"display_name": "My Agents enabled channels",
			"type": "config",
			"default_value": "voice,chat,email",
			"description": "Specifies the channels that are displayed in the My Agents view. Channels are displayed in the order in which they appear in the list.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of channel names from the following list: voice, chat, email, facebook, twitter, workitem",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.thresholds.enabled",
			"display_name": "My Agents enable thresholds",
			"type": "config",
			"default_value": "false",
			"description": "Enable thresholds to be used for channels specified by the teamlead.myagents.thresholds.<media-type> option.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "teamlead.myagents.thresholds.<media-type>",
			"display_name": "My Agents media thresholds",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of a threshold section that determine when an agent state is considered to be Busy or Not Ready for the specified channel. You must create the threshold sections on the Application object.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A threshold section name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "kpi.displayed-kpis",
			"display_name": "Displayed KPIs",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the KPIs that are displayed to the agent. The KPI names refer to the names of the Application Option sections that are defining the KPIs.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of KPI names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.performance-tracker.can-use",
			"display_name": "Can use Performance Tracker",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to the Performance Tracker",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.displayed-statistics",
			"display_name": "Displayed Statistics",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the statistics that are displayed in the Contact Center Statistics tab. The statistics specified by this option match the names of the statistics defined in the options of the Application sections.",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Statistic names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.gadget-statistics",
			"display_name": "Gadget Statistics displayed",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the statistics, up to 10, that are displayed in the Statistics Gadget. Each statistics specified in this option is the name of a section containing the statistic definition or the statistic object.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of Statistic names.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.gadget-statistics.max-size",
			"display_name": "Maximum quantity of Gadget Statistics displayed",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the maximum number of statistics that are displayed in the Statistics Gadget. If more statistics are specified by the statistics.gadget-statistics option, only the first 'n' statistics are displayed.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 1 through 50.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistics.refresh-time",
			"display_name": "Refresh Time",
			"type": "config",
			"default_value": "20",
			"description": "Specifies, in seconds, how often statistics are refreshed in the Contact Center Statistics tab. When set to 0, no automatic refresh occurs (the agent must manually refresh statistics).",
			"version": "9.0.000.10",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.sipendpoint.can-use",
			"display_name": "Can Use Genesys Softphone",
			"type": "config",
			"default_value": "false",
			"description": "Enables the usage of Genesys Softphone. Depends on 'Voice - Can Use Voice Channel'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.sipendpoint.can-change-microphone-volume",
			"display_name": "can change microphone volume",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to change the volume of the microphone.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.sipendpoint.can-change-speaker-volume",
			"display_name": "can change speaker volume",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to change the volume of the speaker.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.sipendpoint.can-mute-microphone",
			"display_name": "Workspace Web SIP Endpoint Options - can mute microphone",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to mute and unmute the microphone. Depends on 'Voice - Can Use Voice Channel' and 'Workspace Web SIP Endpoint Options - Can Use Genesys Softphone'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.sipendpoint.can-mute-speaker",
			"display_name": "Workspace Web SIP Endpoint Options - can mute speaker",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to mute and unmute the speaker. Depends on 'Voice - Can Use Voice Channel' and 'Workspace Web SIP Endpoint Options - Can Use Genesys Softphone'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.uri",
			"display_name": "Sip Endpoint URI",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the URI of the SIP endpoint used in connector mode. For example: https://localhost:8000.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A correct uri",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.sip-server-address",
			"display_name": "Sip Server Address",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the FQDN, hostname, or IP Address of the SIP Entity (Session Border Controller, SIP Proxy, SIP Server) where the SIP REGISTER request will be sent by Genesys Softphone. In a Business Continuity environment designed for dual SIP registration, this corresponds to the preferred site registration (Tip: To set the Domain\\/Realm of your contact center instead of an IP when Workspace SIP Endpoint tries to register through a session border controller (SBC) device, set the value of this option to the FQDN of your domain instead of just the IP Address).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A correct URI. In case of DNS SRV: <FQDN>; in case of A-Record: <FQDN>:<port>; for IP Address: <IP>:<port>.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.sip-server-address.peer",
			"display_name": "Workspace Web SIP Endpoint Options - Sip Server Address",
			"type": "config",
			"default_value": "No default value",
			"description": "In a Business Continuity environment designed for dual SIP registration, specifies the FQDN, hostname, or IP Address of the SIP Entity (Session Border Controller, SIP Proxy, SIP Server) corresponding to the secondary SIP destination where the SIP REGISTER request will be sent by Genesys Softphone (Tip: To set the Domain\\/Realm of your contact center instead of an IP when Workspace SIP Endpoint tries to register through a session border controller (SBC) device, set the value of this option to the FQDN of your domain instead of just the IP Address).",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A correct URI. In case of DNS SRV: <FQDN>; in case of A-Record: <FQDN>:<port>; for IP Address: <IP>:<port>.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.register-max-attempts",
			"display_name": "Max Check Activation Failed",
			"type": "config",
			"default_value": "10",
			"description": "Specifies the number of checks after a registration request is made that Workspace makes while waiting for Genesys Softphone to become active.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.register-interval",
			"display_name": "Register Interval",
			"type": "config",
			"default_value": "1500",
			"description": "Specifies the interval, in milliseconds, that Workspace waits between each check for the successful registration to Genesys Softphone. The number of attempted checks is specified by the sipendpoint.register-max-attempts option.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.wait-user-max-attempts",
			"display_name": "Max Check Waiting User Failed",
			"type": "config",
			"default_value": "20",
			"description": "Specifies the number of failed waiting user-actions that are allowed before timeout.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.ping-interval",
			"display_name": "Ping Interval",
			"type": "config",
			"default_value": "2000",
			"description": "Specifies the interval, in milliseconds, between each ping of the Genesys Softphone.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.max-failed-ping",
			"display_name": "Max Ping Failed",
			"type": "config",
			"default_value": "5",
			"description": "Specifies the number of failed pings allowed on Genesys Softphone.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.transport-protocol",
			"display_name": "Workspace Web SIP Endpoint Options - Transport Protocol",
			"type": "config",
			"default_value": "UDP",
			"description": "Specifies whether UDP, TCP, TLS, HTTP, or HTTPS is used for the SIP transport protocol.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: UDP, TCP, TLS, HTTP, HTTPS.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.headset-unplugged-set-not-ready",
			"display_name": "Not Ready when Headset is Unplugged",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the agent SIP DN is set automatically to Not Ready when the headset that is configured for the agent is unplugged.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.headset-unplugged.not-ready-reason",
			"display_name": "Not Ready Reason on Headset Unplugged Detection",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Not Ready reason that is to be set for the SIP DN when the headset that is used by the agent is unplugged if the value of the sipendpoint.headset-unplugged-set-not-ready option is set to true.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid not ready reason",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.disconnected.not-ready-reason",
			"display_name": "Not Ready Reason on SIP Endpoint connectivity loss",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Not Ready reason that is to be set for the SIP DN when the SIP Endpoint is considered as disconnected.",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid not ready reason",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.disconnected.max-attempts-to-set-not-ready",
			"display_name": "Max Ping Failed before NotReady state",
			"type": "config",
			"default_value": "1",
			"description": "Specifies the maximum number of failed pings with SIP Endpoint before the voice channel state is changed to NotReady (with an eventual reason code specified by option 'sipendpoint.disconnected.not-ready-reason').",
			"version": "9.0.000.88",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.enable-auto-mute",
			"display_name": "Auto mute/unmute speakers and microphone if volume is 0",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether mute and unmute are done automatically when agent sets speaker or microphone volume to 0.",
			"version": "9.0.000.35",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.mychannels.can-use",
			"display_name": "Can Use My Channels",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to access the My Channels tab.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.mychannels.pending-state.can-use",
			"display_name": "Can Use Pending State in My Channels",
			"type": "config",
			"default_value": "false",
			"description": "Enables the pending state to be displayed in the My Channels view while the agent is engaged in a call, chat, or email interaction. When the value of this option is set to true, if an agent sets his or her status to Not Ready or Not Ready Reason while he or she is still handling an interaction, the timer for that state will not start until the call is released, the chat is ended, or the email is sent or put into a workbin.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.security.can-change-password",
			"display_name": "Can Manually Change Password",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to change their own password by using a menu action.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "login.show-change-account-link",
			"display_name": "Show Change Account Link",
			"type": "config",
			"default_value": "true",
			"description": "Show or Hide the change login account link on login error page and second step login page.",
			"version": "9.0.000.46",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-use",
			"display_name": "Can Use Voice Channel",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to use the Voice channel.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice-history.can-click-to-dial",
			"display_name": "Can Click to Dial",
			"type": "config",
			"default_value": "true",
			"description": " Enables an agent to use the Click-to-dial feature to dial a voice call from the Details tab of the history of a voice interaction in any History view.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice-history.can-click-to-search",
			"display_name": "Can Click to Search",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to use Click-to-search to open the Contact Directory by clicking a Contact name in the Details tab of the My History or Interaction Search views.",
			"version": "9.0.000.61",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-use",
			"display_name": "Can Use Chat Channel",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to use the Chat channel.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-decline",
			"display_name": "Can Decline",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to decline incoming chat interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-release",
			"display_name": "Can Release",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to manually end chat conversations.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-release-consultation",
			"display_name": "Can Release consultation",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to manually end chat consultations.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-set-interaction-disposition",
			"display_name": "Can Set Interaction Disposition",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to set the disposition code on chat interactions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-two-step-transfer",
			"display_name": "Can Two Step Transfer",
			"type": "config",
			"default_value": "true",
			"description": "Enables chat transfer in two steps, started by a chat consultation.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-two-step-conference",
			"display_name": "Can Two Step Conference",
			"type": "config",
			"default_value": "true",
			"description": "Enables chat conference in two steps, started by a chat consultation.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-consult",
			"display_name": "Can Use Chat Consult",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to use the Chat consultation feature.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-one-step-conference",
			"display_name": "Can One Step Conference",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to use the instant chat conference feature.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-one-step-transfer",
			"display_name": "Can One Step Transfer",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to use the instant chat transfer feature.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-push-url",
			"display_name": "Can Push Url",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to push URL's to customers during chat sessions.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.show-monitoring.can-use",
			"display_name": "Show Monitoring",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to be informed that the current chat interaction is monitored by a supervisor.",
			"version": "9.0.000.14",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-click-to-dial",
			"display_name": "Can Click to Dial",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to use the Click to Dial feature in chat based on the expression.identify.phone-number option to detect phone numbers.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-click-to-email",
			"display_name": "Can Click to Email",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to use the Click to Email feature in chat based on the expression.identify.email-address option to detect email addresses.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-place-on-hold-async",
			"display_name": "Can Place on Hold Async Chat",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to put on hold an async chat.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.os-emoji-is-enabled",
			"display_name": "Use the native OS Emojis in Chat",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether emojis are displayed as images or as standard OS/browser emojis.",
			"version": "9.0.000.23",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat.can-use-emoji-picker",
			"display_name": "Can Use the Emoji Picker in Chat",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to use an emoji picker.",
			"version": "9.0.000.23",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-use",
			"display_name": "Can Use E-mail Channel",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent is use the Email channel.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-mark-done",
			"display_name": "Can Mark Done Interaction",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to mark done an interaction without further processing.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-click-to-dial",
			"display_name": "Can Click to Dial",
			"type": "config",
			"default_value": "false",
			"description": "Enables the agent to use the Click to Dial feature in email based on the expression.identify.phone-number option to detect phone numbers.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.email.can-decline",
			"display_name": "Can Decline",
			"type": "config",
			"default_value": "true",
			"description": "Enables the agent to decline incoming email interactions. Depends on 'Email - Can Use Email Channel'.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.workbins.can-use",
			"display_name": "Can Use Workbins",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to access My Team Workbins.",
			"version": "9.0.000.12",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.workitem-channels.can-use",
			"display_name": "Can Use All Channels",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use all WorkItem channels configured in the openmedia.workitem-channels option.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.<media-type>.can-mark-done",
			"display_name": "Can Mark Done Interaction",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to mark done an interaction without further processing.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.<media-type>.can-decline",
			"display_name": "Can Decline",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to decline incoming workitem interactions. Depends on 'Workitem - Can Use Workitem Channel'.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.<media-type>.can-one-step-transfer",
			"display_name": "Can One Step Transfer",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to use instant workitem transfer. Depends on 'Workitem - Can Use Workitem Channel'.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.<media-type>.can-set-interaction-disposition",
			"display_name": "Can Set Interaction Disposition",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to set the disposition code of workitem interactions. Depends on 'Workitem - Can Use Workitem Channel'.",
			"version": "9.0.000.17",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.<media-type>.can-move-to-workbin",
			"display_name": "Can Move Workitem to Workbin",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to move an interaction to the workbin. Depends on 'Workitem - Can Use Workitem Channel'.",
			"version": "9.0.000.24",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-use",
			"display_name": "Can Use TeamLead",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to use the agent call and chat monitoring functionality.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.myagents.can-use",
			"display_name": "Can Use My Agents View",
			"type": "config",
			"default_value": "false",
			"description": "Enables supervisors to access the My Agents view, where they can view and update the state for agents in the groups they supervise. Supervisors can also remotely log off agents from media channels in this view.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-monitor-voice",
			"display_name": "Can Monitor Voice",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to monitor voice interactions.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-monitor-chat",
			"display_name": "Can Monitor Chat",
			"type": "config",
			"default_value": "false",
			"description": "Enables a supervisor to monitor chat interactions.",
			"version": "9.0.000.14",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-monitor-current-voice",
			"display_name": "Can Monitor Current Voice",
			"type": "config",
			"default_value": "false",
			"description": "Enables a supervisor to monitor the current voice interaction.",
			"version": "8.5.200.52",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-coach-voice",
			"display_name": "Can Coach Voice",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to coach voice interactions.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-coach-current-voice",
			"display_name": "Can Coach Current Voice",
			"type": "config",
			"default_value": "false",
			"description": "Enables a supervisor to coach the current voice interaction.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-coach-chat",
			"display_name": "Can Coach Chat",
			"type": "config",
			"default_value": "false",
			"description": "Enables a supervisor to coach chat interactions.",
			"version": "9.0.000.14",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-switch-to-coach-chat",
			"display_name": "Can Switch To Coach for Chat",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to switch to coach mode for monitored chat interactions.",
			"version": "9.0.000.14",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-switch-to-barge-in-voice",
			"display_name": "Can Switch To BargeIn for Voice",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to switch to barge-in mode for monitored voice interactions.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-switch-to-barge-in-chat",
			"display_name": "Can Switch To BargeIn for Chat",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to switch to barge-in mode for monitored chat interactions.",
			"version": "9.0.000.14",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-stop-monitoring-voice",
			"display_name": "Can Stop Monitoring Voice",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to stop monitoring voice interactions.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-stop-monitoring-chat",
			"display_name": "Can Stop Monitoring Chat",
			"type": "config",
			"default_value": "true",
			"description": "Enables a supervisor to stop monitoring chat interactions.",
			"version": "9.0.000.14",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.can-send-dtmf",
			"display_name": "Can Send DTMF",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to send DTMF during a voice call by using the on screen number keypad.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.show-monitoring.can-use",
			"display_name": "Show Monitoring",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to be notified that the current call is monitored by a supervisor.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.voice.alert-prevent-recording.can-use",
			"display_name": "Alert Recording Prevention",
			"type": "config",
			"default_value": "true",
			"description": "Enables agents to be alerted if the current call is not being recorded.",
			"version": "9.0.000.76",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.active-recording.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to use the Active Recording functionality.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.active-recording.can-monitor-recording",
			"display_name": "Can Monitor Voice Recording",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the call monitoring indicator is displayed to agents when their calls are being recorded. The Call Recording functionality (for VoIP\\/SIP enabled agents only) enables you to record the current voice interaction with a contact or an internal target.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.active-recording.can-start",
			"display_name": "Can Start",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to start the Active Recording.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.active-recording.can-stop",
			"display_name": "Can Stop",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to stop the Active Recording.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.active-recording.can-resume",
			"display_name": "Can Resume",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to resume the Active Recording.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.active-recording.can-pause",
			"display_name": "Can Pause",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to pause the Active Recording.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamcommunicator.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "true",
			"description": "Enables access to the Team Communicator.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamcommunicator.can-view-all",
			"display_name": "Can Search All",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to search within all internal targets and contacts in Team Communicator.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamcommunicator.can-view-favorites",
			"display_name": "Can View Favorites",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to view favorites in Team Communicator.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamcommunicator.can-view-recent-calls",
			"display_name": "Can View Recent Calls",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to view recently contacted resources in Team Communicator.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamcommunicator.can-manage-favorites",
			"display_name": "Can Manage Favorites",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to add, edit, and remove personal favorites in Team Communicator.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamcommunicator.display-agent-groups-availability",
			"display_name": "Display agent Groups availability",
			"type": "config",
			"default_value": "true",
			"description": "Enables an agent to view the number of agents in the Ready state in agent groups in Team Communicator. Depends on 'Team Communicator - Can Use' and 'Team Communicator - Can View Favorites'.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.focus-on-interaction-toast",
			"display_name": "Focus on interaction toast",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether all Interaction Notification views receive the focus when they are displayed. This option does not rely on accessibility.visual-impairment-profile; therefore, it applies to all configured agents, not just visually impaired agents.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.<media-type>.focus-on-interaction-toast",
			"display_name": "Focus on interaction toast",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether all Interaction Notification views receive the focus when they are displayed. This option does not rely on accessibility.visual-impairment-profile; therefore, it applies to all configured agents, not just visually impaired agents.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.visual-impairment-profile",
			"display_name": "Activate Visual Impairment Profile",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the profile for visually impaired users is active. This option enables users to navigate interface elements from keyboard navigation and tooltips by using a Screen Reader application. Some components might change their behavior in this mode. For example, Team Communicator is collapsed in this configuration.",
			"version": "9.0.000.07",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.tooltip.show-on-focus",
			"display_name": "Enables tooltip activation by keyboard focus",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the tooltip is displayed automatically when the related component has the focus. This option is forced to false if the value of the accessibility.visual-impairment-profile option is true.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.tooltip.hide-on-click",
			"display_name": "Enables tooltip hiding by clicking on target element",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether a custom tooltip is hidden when a target element is clicked. This option is forced to false if the value of the accessibility.visual-impairment-profile option is true.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "accessibility.tooltip.is-hoverable",
			"display_name": "Enables hoverable tooltips",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the tooltip is displayed when the mouse pointer is hovered above the tooltip/tooltip body. This option is forced to false if the value of the accessibility.visual-impairment-profile option is true.",
			"version": "9.0.000.84",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "editor.fonts",
			"display_name": "Fonts",
			"type": "config",
			"default_value": "Serif,Sans-serif,Monospace,Cursive,Fantasy,Tahoma,Roboto,Arial,Helvetica",
			"description": "Specifies the list of available fonts in the Fonts menu of new and reply HTML format email interactions. The fonts are displayed in the order in which they appear in the list.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of fonts from the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto, Arial, Helvetica.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "editor.default-font",
			"display_name": "Default font",
			"type": "config",
			"default_value": "Serif",
			"description": "Specifies the default font in the Font menu of new and reply HTML format email  interactions. If this option is left empty, the last selected font is used for email interactions by default.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto. Empty means no default font specified.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "editor.font-sizes",
			"display_name": "Font sizes",
			"type": "config",
			"default_value": "8,9,10,11,12,14,16,18,20,22,24,26,28,36,48,72",
			"description": "Specifies the font sizes available in the Font Size menu of new and reply HTML formatted email interactions. The sizes are displayed in the order in which they appear in the list.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of font sizes from the following list: 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "editor.default-font-size",
			"display_name": "Default font size",
			"type": "config",
			"default_value": "9",
			"description": "Specifies the default font size in the Font Size menu of new and reply HTML formatted email interactions. If empty, the last selected font size is used for email interactions by default.",
			"version": "9.0.000.11",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A value from the following list: the following list: 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72. Empty means no default font size specified.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "editor.SRL.shortcuts.prefix",
			"display_name": "Editor Shortcuts Prefix",
			"type": "config",
			"default_value": "#",
			"description": "Specifies the prefix, such as '#', that identifies that a keyword is a shortcut for a Standard Response.",
			"version": "9.0.000.71",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid character.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "security.web-content.sandbox-rights.default-authorizations",
			"display_name": "List of default sandbox rights authorization options for the embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes)",
			"type": "config",
			"default_value": "ALLOW-SCRIPTS,ALLOW-FORMS,ALLOW-POPUPS,ALLOW-SAME-ORIGIN",
			"description": "Specifies the default sandbox rights authorization options that are set up to embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes), in order to remove restrictions and enable features.",
			"version": "9.0.000.19",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of default sandbox rights authorization that are set up for the embedded Web Application in INTERNAL, BACKGROUND or HIDDEN mode (based on iframes) in order to unlock some security restrictions : ALLOW-SCRIPTS, ALLOW-FORMS, ALLOW-POPUPS, ALLOW-SAME-ORIGIN, ALLOW-DOWNLOADS, ALLOW-PRESENTATION, ALLOW-POINTER-LOCK",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat-nexus.can-use",
			"display_name": "Can use Nexus Chat View",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to access the contents of the Nexus Conversation tab in the Case Side View of the Chat interaction view.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat-nexus.can-use-contact-history-detail",
			"display_name": "Can Use Specific Chat Nexus History Detail",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to access Nexus chat interaction details in the Details tab of the Contact History view.",
			"version": "9.0.000.98",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat-nexus.service-url",
			"display_name": "Nexus URL",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the web-socket url of the Nexus service url to access the Chat API.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat-nexus.web-components.url",
			"display_name": "Nexus-Ux WebComponents URL",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Nexus-ux WebComponents url to display the nexus-ux view. Use this option if the url is different from the standard url.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat-nexus.communication.can-use",
			"display_name": "Can use Nexus Communication Chat View",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to use the Communication tab in the Connect group.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.chat-nexus.communication.can-send",
			"display_name": "Can send messages from Nexus Communication Chat View",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to manage contact subscriptions and send messages to contacts from the Communication tab.",
			"version": "9.0.000.87",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat-nexus.interaction-bar.tooltip-enabled",
			"display_name": "Enable Nexus Rendering in the Interaction Bar Tooltip",
			"type": "config",
			"default_value": "false",
			"description": "Enable the Nexus chat rendering in the interaction bar tooltip view.",
			"version": "9.0.000.98",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.gws-url.capturing-groups",
			"display_name": "Expression to capture groups from the GWS url.",
			"type": "config",
			"default_value": "https:\\/\\/(?:gapi{{!}}gwa)-(.*)\\.genesyscloud\\.com",
			"description": "Specifies that Workspace should extract a part of its url to capture groups containing information shared among services, such as the tenant or region.",
			"version": "9.0.000.51",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "expression.gws-url.capturing-groups-<n>",
			"display_name": "Expression to capture groups from the GWS url using pairs mapping to extract the region.",
			"type": "config",
			"default_value": "https:\\/\\/(.*)-(?:gapi{{!}}gwa)-(.*)\\.genesyscloud\\.com",
			"description": "Specifies that Workspace should extract a part of its url to capture groups containing information shared among services, such as the tenant or region. This option supports plugins and pair mapping (for example: system.telemetry.service-url-<n>, for MPLS networks).",
			"version": "9.0.000.51",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "disaster-recovery.enabled",
			"display_name": "Disaster recovery enabled",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Business Continuity (Disaster Recovery) functionality is activated for SIP Server and Genesys Web Services.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "disaster-recovery.authentication-mode",
			"display_name": "Disaster recovery authentication mode",
			"type": "config",
			"default_value": "INTERNAL",
			"description": "Specifies which authentication mode is used when trying to authenticate with another site (INTERNAL iframe, EXTERNAL popup or REDIRECT refresh on backup-site).",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list of modes that can be used for authentication with Toolkit : INTERNAL, EXTERNAL, REDIRECT",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.disaster-recovery.timeout",
			"display_name": "Disaster recovery timeout",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the duration, in seconds, for which Workspace waits for the Voice Channel to be back in service before triggering the Disaster Recovery process during and active session.",
			"version": "9.0.000.31",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than 0 to specify the timeout, 0 to disable Voice Disaster Recovery.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.enabled",
			"display_name": "Telemetry monitoring enabled",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether telemetry is used to push metrics and traces to the Telemetry Service.",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.enable-metrics",
			"display_name": "Enable metrics for Telemetry",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether UI metrics and events are sent to the Telemetry Service. Depends on system.telemetry.enabled",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.enable-traces",
			"display_name": "Enable traces for Telemetry",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether UI traces are sent to the Telemetry Service. Depends on system.telemetry.enabled",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.service-url",
			"display_name": "Telemetry service url",
			"type": "config",
			"default_value": "No default value",
			"description": "The url of the Telemetry Service.",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Specifies the valid FQDN of the Telemetry Service (for example: https://telemetry-fqdn).",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.service-url-<n>",
			"display_name": "Telemetry service url",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the url of one of the Telemetry Services when there are multiple pairs in a region. (Refer to the expression.gws-url.capturing-groups-<n> option)",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid FQDN of Telemetry Service (for example: https://telemetry-fqdn-1).",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.telemetry.monitor-interval",
			"display_name": "Telemetry metric interval",
			"type": "config",
			"default_value": "60",
			"description": "Specifies the duration, in seconds, between two checks of the metrics, events, or traces before publishing the data to the Telemetry Service.",
			"version": "9.0.000.65",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "From 0 to MAXINT.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.callback.can-use",
			"display_name": "Can Use Callback",
			"type": "config",
			"default_value": "false",
			"description": "Enables an agent to create callback interactions and displays the Schedule a Callback button in the interaction toolbar.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "callback.callback-information.content",
			"display_name": "Content for Callback Information",
			"type": "config",
			"default_value": "PhoneNumber,Comments",
			"description": "Specifies the list of Callback data that is displayed in the Callback Information Area. The Callback data entries are displayed in the order in which they appear in this list.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma separated list of data items from the following list: PhoneNumber,Comments",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "callback.callback-types-business-attribute",
			"display_name": "Callback Type Business Attribute",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the Business Attribute that defines the list of Service Types. Service Types consist of the GES service name and user data key-value pairs.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid Business Attribute name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "callback.default-date.is-automatically-selected",
			"display_name": "Callback Date Default",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the current date is the default displayed in the Date field of the New Callback Schedule window.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "callback.time-slot.field-type",
			"display_name": "Callback Time Slot Control",
			"type": "config",
			"default_value": "WIDGET",
			"description": "Specifies whether the Time slots field displays the time slot picker widget or a drop-down list. If not set or set to an invalid value, the widget is displayed. The value of this option is forced to DROPDOWN if the value of the accessibility.visual-impairment-profile option is true.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: WIDGET, DROPDOWN.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.agent-assist.can-use",
			"display_name": "Can use Agent Assist for Athena server",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to view the 'Agent Assist' tab in the Case Side View and Voice transcripts in voice interaction sub view.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.service-url",
			"display_name": "Agent Assist Athena Server URL",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the web-socket url of the AI Connector (Anthena) service to access the Agent Assist API.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid web-socket Url.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.voice-transcript.enable",
			"display_name": "Enable Voice Transcript",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the voice transcript view is displayed in the voice interaction view. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.suggestion.enable",
			"display_name": "Enable Suggestions",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the suggestion view is displayed in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.confidence.faq.enable",
			"display_name": "Enable Confidence (FAQ)",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the confidence percentage for FAQ suggestions is displayed in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.confidence.article.enable",
			"display_name": "Enable Confidence (Article)",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the confidence percentage for knowledge article suggestions is displayed in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.confidence.faq.threshold.low",
			"display_name": "Low Threshold for Confidence Color",
			"type": "config",
			"default_value": "50",
			"description": "Specifies the low threshold, in percentage, to display the low confidence color (red) for FAQ suggestions. The value must be less than the value specified for the agent-assist.confidence.faq.threshold.high option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value between 0 and 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.confidence.faq.threshold.high",
			"display_name": "High Threshold for Confidence Color",
			"type": "config",
			"default_value": "80",
			"description": "Specifies the high threshold, in percentage, to display the high confidence color (green) for FAQ suggestions. The value must be greater than the value specified for the agent-assist.confidence.faq.threshold.low option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value between 0 and 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.confidence.article.threshold.low",
			"display_name": "Low Threshold for Confidence Color",
			"type": "config",
			"default_value": "50",
			"description": "Specifies the low threshold, in percentage, to display the low confidence color (red) for knowledge article suggestions. The value must be less than the value specified for the agent-assist.confidence.article.threshold.high option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value between 0 and 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.confidence.article.threshold.high",
			"display_name": "High Threshold for Confidence Color",
			"type": "config",
			"default_value": "80",
			"description": "Specifies the high threshold, in percentage, to display the high confidence color (green) for knowledge article suggestions. The value must be greater than the value specified for the agent-assist.confidence.article.threshold.low option. Percentage values between high and low are colored yellow. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value between 0 and 100.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.feedback.faq.enable",
			"display_name": "Enable Feedback Buttons (FAQ)",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the thumbs-up and thumbs-down feedback buttons are displayed for each FAQ suggestion in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "agent-assist.feedback.article.enable",
			"display_name": "Enable Feedback Buttons (Article)",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the thumbs-up and thumbs-down feedback buttons are displayed for each knowledge article suggestion in the Agent Assist tab. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"version": "9.0.000.95",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "workspace-toolkit.enable",
			"display_name": "Workspace Toolkit usage enablement",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Workspace Toolkit use is authorized or not. This option must be set in the WS_Cluster application.",
			"version": "9.0.000.59",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.multi-tabs-defense.enable",
			"display_name": "Enable defense for Multi-Tabs",
			"type": "config",
			"default_value": "true",
			"description": "Enables the defense for Multi-Tabs use-cases.",
			"version": "9.0.000.80",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "attachment.restrict-to-file-types",
			"display_name": "Allowed attachment file types",
			"type": "config",
			"default_value": "jpg,png,gif,pdf,doc,docx,ppt,pptx,xls,xlsx,txt,json",
			"description": "Specifies the list of file extensions that represent file types that are allowed to be used as attachments. The request is rejected if extension of file is not part of restricted types. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.34",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A comma-separated list of file extensions that represent file types that are allowed.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "attachment.<media-type>.restrict-to-file-types",
			"display_name": "Allowed media attachment file types",
			"type": "config",
			"default_value": "jpg,png,gif,pdf,doc,docx,ppt,pptx,xls,xlsx,txt,json",
			"description": "Specifies the list of file extensions that represent file types that are allowed to be used as attachments for a specific media. The request is rejected if extension of file is not part of restricted types. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.34",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A comma-separated list of file extensions that represent file types that are allowed.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "attachment.max-file-upload-size",
			"display_name": "Allowed media attachment size",
			"type": "config",
			"default_value": "8",
			"description": "Specifies the maximum size (in MB) of one file that agents can attach to an interaction. The value 0 means that attaching is not allowed. The maximum allowed attachment size is 50 MB. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.34",
			"category": "workspace-service",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "chat.message.max-length",
			"display_name": "Message max length",
			"type": "config",
			"default_value": "64000",
			"description": " Specifies the maximum number of characters in the chat message. This option cannot be overridden and must be set in the WS_Cluster application.",
			"version": "9.0.000.86",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A positive integer",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "openmedia.chat-channels",
			"display_name": "Enabled Chat Extension Channels",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of Chat channels an agent may use.",
			"version": "9.0.000.97",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A comma-separated list of valid Media Types.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "openmedia.chat-history-channels",
			"display_name": "Enabled Chat History Details View for Openmedia Channels",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the list of Open Media channels for which the transcript is to be handled as a chat interactions, such as Facebook public and Twitter public, and displayed in the interaction details pane of the History views.",
			"version": "9.0.000.95",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A comma-separated list of valid Media Types.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistic-name",
			"display_name": "Statistic Name",
			"type": "config",
			"default_value": "AverageWaitingTime",
			"description": "The name of the statistic used to evaluate the presence for Routing Points.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "A valid name of a statistic server statistic for routing point.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistic-text",
			"display_name": "Statistic Text",
			"type": "config",
			"default_value": "$I18n.AverageWaitingTime$",
			"description": "Specifies the formatting to be used to display the Stat Server metric used for the presence of the displayed object. If no valid format is found in the option, the display format of the Stat Server metric is set automatically to TimeFormat if a time metric is recognized, or Percentage if a percentage is recognized. If a number metric is recognized or if the type of metric is not recognized, then a raw number format is used.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "One of the 2 predefined constant $I18n.AverageWaitingTime$ or $I18n.NumberInteractionsWaiting$. Or a string containing a valid time or number format according to Windows rules number format (https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx). For example: 'interaction(s) Q4001 {0:HH:mm:ss} average waiting time' or 'interaction(s) Q4001 {0}% abandoned'.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "warning-level",
			"display_name": "Warning Level",
			"type": "config",
			"default_value": "0",
			"description": "The value at which a statistic is considered to be at the warning level.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "A positive integer or a double value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "error-level",
			"display_name": "Error Level",
			"type": "config",
			"default_value": "0",
			"description": "The value at which a statistic is considered to be at the error level.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "A positive integer or a double value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "object-ids",
			"display_name": "Object Identifiers",
			"type": "config",
			"default_value": "No default value",
			"description": "A comma separated list of DN identifiers that represent Routing Point objects presented in Team Communicator for which this presence metric is applicable. Object identifier format is: <DN Number>@<Switch Name> This key is optional. If it is absent from the section, the presence metric applies to all Routing Point objects that don't have explicit presence metric assignment.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "associated-object-ids",
			"display_name": "Associated Object Identifiers",
			"type": "config",
			"default_value": "No default value",
			"description": "A comma separated list of object identifiers that represent the objects that store the statistic requested from Stat Server that is displayed as the 'presence metric' of the object displayed in Team Communicator. The type of those objects must match the type specified by the value of the associated-statistic-type option. If multiple values are specified by the value of the object-ids option, this option must contain the same number to associate the first object of object-ids with the first object of associated-object-ids, the second object of the object-ids with the second object of associated-object-ids and so on. This option is applicable only if associated-statistic-type is also set.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "associated-object-type",
			"display_name": "Associated Object Type",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the statistic type (from Stat Server reference) that is requested to display the presence metric when this metric is not calculated directly on the object displayed in Team Communicator, but on the objects referenced in option associated-object-ids.",
			"version": "9.0.000.67",
			"category": "routing-point-presence",
			"constraints": {
				"data_type": "A comma separated list of DN identifiers that represent Routing Point objects.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistic-name",
			"display_name": "Statistic Name",
			"type": "config",
			"default_value": "AverageWaitingTime",
			"description": "The name of the statistic used to evaluate the presence for Queues.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "A valid name of a statistic server statistic for queue.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "statistic-text",
			"display_name": "Statistic Text",
			"type": "config",
			"default_value": "$I18n.AverageWaitingTime$",
			"description": "Specifies the formatting to be used to display the Stat Server metric used for the presence of the displayed object. If no valid format is found in the option, the display format of the Stat Server metric is set automatically to TimeFormat if a time metric is recognized, or Percentage if a percentage is recognized. If a number metric is recognized or if the type of metric is not recognized, then a raw number format is used.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "One of the 2 predefined constant $I18n.AverageWaitingTime$ or $I18n.NumberInteractionsWaiting$. Or a string containing a valid time or number format according to Windows rules number format (https://msdn.microsoft.com/en-us/library/8kb3ddd4(v=vs.110).aspx). For example: 'interaction(s) Q4001 {0:HH:mm:ss} average waiting time' or 'interaction(s) Q4001 {0}% abandoned'.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "warning-level",
			"display_name": "Warning Level",
			"type": "config",
			"default_value": "0",
			"description": "The value at which a statistic is considered to be at the warning level.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "A positive integer or a double value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "error-level",
			"display_name": "Error Level",
			"type": "config",
			"default_value": "0",
			"description": "The value at which a statistic is considered to be at the error level.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "A positive integer or a double value.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "object-ids",
			"display_name": "Object Identifiers",
			"type": "config",
			"default_value": "No default value",
			"description": "A comma separated list of DN identifiers that represent Queue objects presented in Team Communicator for which this presence metric is applicable. Object identifier format is: <DN Number>@<Switch Name> This key is optional. If it is absent from the section, the presence metric applies to all Queue objects that don't have explicit presence metric assignment.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "A comma separated list of DN identifiers that represent Queue objects.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "associated-object-ids",
			"display_name": "Associated Object Identifiers",
			"type": "config",
			"default_value": "No default value",
			"description": "A comma separated list of object identifiers that represent the objects that store the statistic requested from Stat Server that is displayed as the 'presence metric' of the object displayed in Team Communicator. The type of those objects must match the type specified by the value of the associated-statistic-type option. If multiple values are specified by the value of the object-ids option, this option must contain the same number to associate the first object of object-ids with the first object of associated-object-ids, the second object of the object-ids with the second object of associated-object-ids and so on. This option is applicable only if associated-statistic-type is also set.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "A comma separated list of DN identifiers that represent Queue objects.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "associated-object-type",
			"display_name": "Associated Object Type",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the statistic type (from Stat Server reference) that is requested to display the presence metric when this metric is not calculated directly on the object displayed in Team Communicator, but on the objects referenced in option associated-object-ids.",
			"version": "9.0.000.87",
			"category": "queue-presence",
			"constraints": {
				"data_type": "A comma separated list of DN identifiers that represent Queue objects.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "click-to-dial.preprocessing-rules",
			"display_name": "Click to Dial Preprocessing Rules",
			"type": "config",
			"default_value": "default",
			"description": "Specifies the pre-processing rules to apply to the phone number before making a dial request",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "default, none, or a comma-separated list of pre-processing rule section names",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.enabled-call-types",
			"display_name": "Voice Activity Log",
			"type": "config",
			"default_value": "Inbound,Outbound,Internal,Consult",
			"description": "Specifies the call types the adapter should create activity history entries for in Salesforce.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A comma-separated list of call types (Inbound, Outbound, Internal, Consult) or an empty value to disable all.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.enabled-chat-types",
			"display_name": "Chat Activity Log",
			"type": "config",
			"default_value": "Inbound",
			"description": "Specifies the chat types the adapter should create activity history entries for in Salesforce",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A comma-separated list of chat types (Inbound, Consult) or an empty value to disable all.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.enabled-openmedia-types",
			"display_name": "Open Media Activity Log",
			"type": "config",
			"default_value": "Inbound",
			"description": "Specifies the open media (workitem) types Adapter should create activity log entries for in Salesforce. To disable open media activity log creation set option to None.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "Open media (workitem) types (Inbound) or leave empty to disable all activity creation.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.field-mapping",
			"display_name": "Activity Log Field Mapping",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the configuration section where the mapping is defined.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "The name of a configuration section that contains the mapping.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.mode",
			"display_name": "Auto Activity Log Association",
			"type": "config",
			"default_value": "search_query",
			"description": "Specifies the Salesforce criterion to use to associate the Activity Log Task when the interaction is completed.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "search_query, open_page",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.on-screenpop",
			"display_name": "Activity Log on Screen Pop",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Adapter creates the activity in Salesforce on screen pop and modifies logged activity when interaction is marked done. Activity on screen pop is created for inbound and internal calls",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.status",
			"display_name": "Salesforce Activity Log Status",
			"type": "config",
			"default_value": "Completed",
			"description": "Specifies the custom task status to be applied when an activity log is created by Adapter. Prerequisite: Status exists in the Salesforce Task Status Picklist",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "Any string representing a status. Cannot contain the following character: &",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.ui-association",
			"display_name": "UI Activity Log Association",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Gplus Adapter displays the Activity Log Task Object Association table when the interaction is completed.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.block-adapter-multitab",
			"display_name": "Prevent Gplus in Browser Multitab",
			"type": "config",
			"default_value": "false",
			"description": "Specifies that Gplus Adapter can't work in several tabs.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.chat.include-transcript-in-desc",
			"display_name": "Chat Include Transcript in Description",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether Adapter saves the chat transcript as part of the activity description in Salesforce.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.chat.transcript-custom-field-name",
			"display_name": "Chat Transcript Custom Field Name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of a custom activity field in Salesforce. If set, Adapter saves the chat transcript to this field in Salesforce. Note: Salesforce Lightning Experience supports only 255 characters for Text fields. If you configure the Text fields to store the chat transcripts and set the length of characters as 255, only the first 255 characters of the chat transcript will be saved in the Activity History and the remaining transcript will be truncated. However, you can still view the Details and Case Data of the chat interaction in the My History tab in Agent Desktop. Whereas, if you configure the Text field's character length with a value less than 255, then, an activity might not get created in Salesforce if the chat transcript exceeds the configured character length.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": " Name of a custom field in Salesforce.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.debug-notifications",
			"display_name": "UI Activity Log Association",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Gplus Adapter displays all notifications (positive and negative).",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.email.include-body-in-desc",
			"display_name": "Email Include in Activity Description",
			"type": "config",
			"default_value": "false",
			"description": "When set to true, includes the text version of the email body in the activity description in Salesforce. The email body is saved only for inbound emails and outbound replies",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.enable-click-to-dial",
			"display_name": "Enable Click to dial",
			"type": "config",
			"default_value": "true",
			"description": "If this option is set to true, Gplus Adapter enables Salesforce click-to-dial, or, if set to false, Gplus Adapter does not accept click-to-dial requests, regardless of whether or not click-to-dial is enabled in Salesforce",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.enable-in-focus-page-transfer",
			"display_name": "Update Attached Data on Transfer",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether to update the call data with the ID of the object the agent is looking at in Salesforce when performing a voice or chat conference or transfer. If set to true, the agent receiving the voice or chat conference or transfer gets a screen pop for the most relevant object",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.keep-session-alive",
			"display_name": "Keep Alive Sync",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether to prevent Adapter from logging out of Salesforce when there is no activity in Salesforce beyond a configurable time period. If set to true, Adapter refreshes the Salesforce session at short intervals and keeps Adapter-Salesforce session alive.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.message-channel.name",
			"display_name": "Salesforce Message Channel Name for Service Client API",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the message channel in Salesforce for Service Client API in the format: NameSpacePrefix__ChannelName__c or ChannelName__c.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of a message channel in Salesforce in the following format: NameSpacePrefix__ChannelName__c or ChannelName__c",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.new-record.field-mapping",
			"display_name": "Salesforce New Record Field Mapping",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the configuration section where the mapping is defined. In the section, each key must correspond to an interaction UserData key and each value must correspond to the name of the Salesforce standard or custom object field.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "The name of a configuration section that contains the mapping of a new record custom field mapping.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.notifications",
			"display_name": "Salesforce Notification",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Gplus Adapter displays notifications (positive only).",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.message-channel.name",
			"display_name": "Salesforce Message Channel Name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the name of the message channel in Salesforce for Service Client API in the format: NameSpacePrefix__ChannelName__c or ChannelName__c.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of a message channel in Salesforce in the following format: NameSpacePrefix__ChannelName__c or ChannelName__c",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.run-apex.class",
			"display_name": "Apex Class Name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configures the name for a Salesforce custom apex class.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "Apex Class Name",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.run-apex.events",
			"display_name": "Run Salesforce Apex on Interaction Events",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies interaction event which triggers Salesforce Apex to run.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "RINGING, DIALING, ESTABLISHED, RELEASED, INVITED, ACCEPTED, CREATED, REMOVED",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.run-apex.userdata-key-list",
			"display_name": "Apex Data",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies comma-separated list of the userData key names that will be delivered to Salesforce Apex. Example of value format: userDataKeyName1, userDataKeyName2, userDataKeyName3",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "Comma-separated list of fields in userData that will be delivered to Salesforce Apex parameter eventData.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.user-data.object-id-key",
			"display_name": "Salesforce Object Key",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the key Adapter uses when saving the ID of the focused Salesforce object to attached data.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A valid user key name to store the Salesforce object id. For example: sf_object_key",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.user-data.object-name-key",
			"display_name": "Salesforce Object Name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the key Adapter uses when saving the name of the focused Salesforce object to attached data.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A valid user key name to store the Salesforce object name. For example: sf_object_name",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.user-data.object-type-key",
			"display_name": "Salesforce Object Type",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the key Adapter uses when saving the type of the focused Salesforce object to attached data.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A valid user key name to store the Salesforce object type name. For example: sf_object_type",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.chat.on-invite",
			"display_name": "Screen Pop on Chat Invite",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the chat invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the chat invite.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.email.on-create",
			"display_name": "Screen Pop on Outbound Email Create",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Adapter initiates a screen pop in Salesforce immediately after creating the email",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.email.on-invite",
			"display_name": "Screen Pop on Email Invite",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the adapter initiates a screen pop in Salesforce immediately after displaying the email invite notification. If the option is not set or false, the adapter initiates a screen pop only when the agent accepts the email invite.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.enable-for-consult",
			"display_name": "Enable Screen Pop for Consult",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the ability to attach current Salesforce object in context when using voice consult. This option works with option salesforce.enable-in-focus-page-transfer",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.enable-for-internal-calls",
			"display_name": "Screen Pop for Internal Calls",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the adapter initiates screen pops for internal calls",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.for-outbound",
			"display_name": "Screen Pop For Outbound Calls",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies whether the Adapter initiates screen pops in Salesforce for outbound calls. None: no screen pops are initiated for outbound calls, Dialing: the Adapter initiates a screen pop on dialing, Established: the Adapter initiates a screen pop when the call is established.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "established, dialing",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.id-key-regex",
			"display_name": "Screenpop Id Key Regex",
			"type": "config",
			"default_value": "^id_",
			"description": "Specifies a regular expression pattern used to match a UserData key. This key's value should contain the ID of an object to screen pop in Salesforce. As with the existing screen pop behavior using the 'id_' prefix, if multiple matching keys are present, Adapter only uses the first one. If this option isn't defined, Adapter uses the existing 'id_'prefix logic.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A regular expression that matches a UserData key.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.include-ani-in-search",
			"display_name": "Use ANI in Screen Pop Search",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the ANI is used in the screen pop search",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.include-dnis-in-search",
			"display_name": "Use DNIS in Screen Pop Search",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the DNIS is used in the screen pop search",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-api-name",
			"display_name": "Screenpop Object Api Name",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the Salesforce custom object API name. To find the API name, go to Salesforce Setup - Object Manager - Custom Object - Details - API Name.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "The name of a Salesforce custom object API",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type",
			"display_name": "Screen pop object type",
			"type": "config",
			"default_value": "SOBJECT",
			"description": "Specifies object type to screen pop in Salesforce.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "SOBJECT, FLOW, URL, OBJECTHOME, LIST, SEARCH, NEW_RECORD_MODAL",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type-flow",
			"display_name": "Screen pop Flow section name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configure section name Flow for screenpop object type.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of the custom section that you have defined to contain the Flow to be executed during the ringing or established phase.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type-list",
			"display_name": "Screen pop List section name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configure section name List for screenpop object type.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of the custom section that you have defined to contain the List to be executed during the ringing or established phase.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type-new-record",
			"display_name": "Screen pop New record section name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configure section name New record for screenpop object type.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of the custom section that you have defined to contain the new object type record name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type-object-home",
			"display_name": "Screen pop Object home section name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configure section name Object home for screenpop object type.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of the custom section you have defined to contain the Object Home.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type-search",
			"display_name": "Screen pop Search section name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configure section name Search for screenpop object type",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of the custom section that you have defined to contain the default search string. The search string must be at least 3 characters.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.object-type-url",
			"display_name": "Screen pop URL section name",
			"type": "config",
			"default_value": "No default value",
			"description": "Configure section name URL for screenpop object type.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string that contains the name of the custom section you have defined to contain the URL.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.on-ringing",
			"display_name": "Screen Pop on Ringing",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the adapter initiates a screen pop in Salesforce when the call is ringing. If not set or false, the adapter initiates a screen pop when the call is established",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.openmedia.on-invite",
			"display_name": "Screen Pop on Open Media Invite",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Adapter initiates a screen pop in Salesforce immediately after displaying the open media invite notification. If the option is not set or false, Adapter initiates a screen pop only when the agent accepts the open media invite. This option supports the open media items configured in the openmedia.workitem-channels option.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "salesforce.activity-log.display-on-creation",
			"display_name": "Display Activity Log On Creation",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether Gplus Adapter displays the Activity Log in Salesforce when interaction is completed.",
			"version": "9.0.000.98",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.preprocessing-rule",
			"display_name": "Screen Pop Preprocessing Rule",
			"type": "config",
			"default_value": "default",
			"description": "Specifies the pre-processing rule to apply to the ANI before showing the screen pop",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "default, none, or a pre-processing rule section name.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.save-new-record-criterion",
			"display_name": "Create New Salesforce Record on Screenpop",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies whether Gplus Adapter creates new Salesforce record on screenpop. None: no new Salesforce record is created, No Matching Record: new Salesforce record is created when Salesforce search returns no matching record, Always: new Salesforce record is created for every screenpop. Depends on Salesforce Object API Name and New Salesforce Record Field Mapping options.",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "no_matching_record, always",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.search-key-regex",
			"display_name": "RegEx to Match UserData",
			"type": "config",
			"default_value": "^cti_",
			"description": "Specifies a regular expression pattern used to match one or more UserData keys. The values for these keys are used to build the search and screen pop expression in Salesforce. If this option is not defined, the adapter uses the existing 'cti_' prefix logic",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A regular expression that matches a UserData key.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "screenpop.transfer-object-key",
			"display_name": "Object ID UserData key",
			"type": "config",
			"default_value": "id_transfer_object",
			"description": "Specifies the custom UserData key the adapter should use for the object ID of the focused page in Salesforce",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A valid key",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.inbound-voice.subject",
			"display_name": "Templates Salesforce Inbound-Voice Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.outbound-voice.subject",
			"display_name": "Templates Salesforce outbound-voice Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.transfer-voice.subject",
			"display_name": "Templates Salesforce transfer-voice Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.chat.subject",
			"display_name": "Templates Salesforce chat Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.email.subject",
			"display_name": "Templates Salesforce email Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.openmedia.subject",
			"display_name": "Templates Salesforce openmedia Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "templates.salesforce.internal-voice.subject",
			"display_name": "Templates Salesforce internal-voice Subject",
			"type": "config",
			"default_value": "false",
			"description": "Specifies the custom template the adapter should use when creating the subject field in a Salesforce activity",
			"version": "9.0.000.95",
			"category": "crm-adapter",
			"constraints": {
				"data_type": "A string with custom template variables wrapped in { and }",
				"required": false,
				"dynamic": true
			}
		}
	],
	"version": "9.0.000.98"
}
This page was last edited on September 16, 2022, at 17:11.
Comments or questions about this documentation? Contact us for support!