Jump to: navigation, search
(Created page with "=options 9.0.000.31= <pre>{ "parameters": [], "version": "9.0.000.31" }</pre> Category:V:HTCC:8.5Source")
 
Line 1: Line 1:
 
=options 9.0.000.31=
 
=options 9.0.000.31=
 
<pre>{
 
<pre>{
−
"parameters": [],
+
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "from 0 to MAXINT",
 +
"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.",
 +
"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].",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value from 500 through 50000.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "system.feedback.log-size",
 +
"display_name": "The feedback log size.",
 +
"type": "config",
 +
"default_value": "1000",
 +
"description": "Specifies the number of characters from the last Log to send with the feedback.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value greater than or equal to 0.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
 +
"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.",
 +
"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'. 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).",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.<media-type>.queue",
 +
"display_name": "Workitem - Routing Based Queue",
 +
"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.",
 +
"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": "Workitem - Routing based actions",
 +
"type": "config",
 +
"default_value": "OneStepTransfer",
 +
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"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": "Workitem - Routing based targets",
 +
"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.",
 +
"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 the inactivity timeout, the agent session is ended. A value of 0 disables the inactivity timeout. Warning: After the timeout occurs, the Worksapce login dialog should be blank; however, if the agent has allowed the browser to remember his or her password, then the login dialog will still be populated with the agent's credentials. For security, agents should not allow web browsers to remember their login credentials.",
 +
"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.",
 +
"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.",
 +
"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": "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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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'.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value greater than 0.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "main-window.window-title",
 +
"display_name": "Window Title",
 +
"type": "config",
 +
"default_value": "&#36;Window.Title&#36;",
 +
"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;.",
 +
"category": "interaction-workspace",
 +
"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;.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "ContactInteractionDetailView,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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView,...",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "views.HistoryInteractionDetailsRegion.activate-order",
 +
"display_name": "Default view in Region HistoryInteractionDetailsRegion",
 +
"type": "config",
 +
"default_value": "ContactInteractionDetailView,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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView,...",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "views.WorkbinInteractionDetailsRegion.order",
 +
"display_name": "Views order in Region WorkbinInteractionDetailsRegion",
 +
"type": "config",
 +
"default_value": "ContactInteractionDetailView,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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView,...",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "views.WorkbinInteractionDetailsRegion.activate-order",
 +
"display_name": "Default view in Region WorkbinInteractionDetailsRegion",
 +
"type": "config",
 +
"default_value": "ContactInteractionDetailView,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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,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.",
 +
"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.",
 +
"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": "KnowledgeView,CoBrowseView,WebActivityView,ContactView,SRLView",
 +
"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.",
 +
"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'): KnowledgeView,ExtensionSectionName,CoBrowseView,WebActivityView,ContactView,SRLView,...",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "views.CaseSideRegion.activate-order",
 +
"display_name": "Default view in Region CaseSideRegion",
 +
"type": "config",
 +
"default_value": "ContactView,SRLView,KnowledgeView,CoBrowseView,WebActivityView",
 +
"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.",
 +
"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,KnowledgeView,CoBrowseView,WebActivityView,...",
 +
"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.",
 +
"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\\*#/]*&#36;",
 +
"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.",
 +
"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})&#36;",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid 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": "Sspecifies 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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, Dnd, NotReadyReason, AfterCallWork, 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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, NotReadyReason, AfterCallWork, 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.",
 +
"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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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'. 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.",
 +
"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.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'. 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.",
 +
"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'. 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).",
 +
"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><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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A string that represents an attached data key.",
 +
"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",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"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>.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "interaction-bar.quick-access-modes.<media-type>",
 +
"display_name": "Quick Access Modes <media-type>",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "interaction.disposition.use-attached-data",
 +
"display_name": "Disposition uses attached data",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies that attached data can be added to the interaction in UserEvent. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid Business Attribute name.",
 +
"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.",
 +
"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.",
 +
"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": "Disposition cache timeout delay",
 +
"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.",
 +
"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.",
 +
"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": "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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "(&#36;Contact.FirstName&#36; &#36;Contact.LastName&#36;{{!}}&#36;Interaction.MainParty&#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;'.",
 +
"category": "interaction-workspace",
 +
"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).",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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. Do not enable this option if the privilege.sipendpoint.can-use privilege is granted.",
 +
"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.",
 +
"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 &#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)). English is the default language, and will always be available.",
 +
"category": "interaction-workspace",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "chat.nickname",
 +
"display_name": "Agent Nickname",
 +
"type": "config",
 +
"default_value": "&#36;Agent.UserName&#36;",
 +
"description": "Specifies the agent's nickname that is used during chat sessions (displayed to the customer) by a string that can contain regular characters and field codes. This option can be overridden by a routing strategy as described in the Configuration Guide.",
 +
"category": "interaction-workspace",
 +
"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;.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid name of a Script of type Interaction Queue.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "The name of a valid Business Attribute.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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 &#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:'.",
 +
"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": "&#36;FullHeader&#36;",
 +
"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:'.",
 +
"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: &#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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "\\\"response:\\\" followed by the response path to the standard response",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Any valid character string.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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>",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.voice.routing-points",
 +
"display_name": "Voice - Routing Points",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of call number names in the following format: &#36;dn_name@switch&#36;",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.voice.routing-based-actions",
 +
"display_name": "Voice - Routing based actions",
 +
"type": "config",
 +
"default_value": "MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer",
 +
"description": "Specifies the list of Routing Based Actions that an agent may perform.",
 +
"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": "Voice - Routing based targets",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid object types from the following list: Agent, RoutingPoint, TypeDestination, OutboundRecord, Contact",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.voice.make-call-caller-id-business-attribute",
 +
"display_name": "Voice - 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.",
 +
"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": "Voice - 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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "voice.caller-id.key-name",
 +
"display_name": "Caller ID - Attached Data Key",
 +
"type": "config",
 +
"default_value": "IW_SelectedCallerId",
 +
"description": "Specifies the key name of the attached data that contains the selected caller id information.",
 +
"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": "Voice - Single Step Conference enabled",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.voice.single-step-transfer-enabled",
 +
"display_name": "Voice - Single Step Transfer enabled",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.voice.consultation-enabled",
 +
"display_name": "Voice - Consultation enabled",
 +
"type": "config",
 +
"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
 +
"description": "Specifies the list of targets enabled in Team Communication for a consultation.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.voice.make-call-enabled",
 +
"display_name": "Voice - 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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "intercommunication.chat.queue",
 +
"display_name": "Chat - Routing Based Queue",
 +
"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.",
 +
"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": "Chat - Routing based actions",
 +
"type": "config",
 +
"default_value": "InitTransfer,OneStepTransfer",
 +
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"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": "Chat - Routing based targets",
 +
"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.",
 +
"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": "Email - Routing Based Queue",
 +
"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.",
 +
"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": "Email - Routing based actions",
 +
"type": "config",
 +
"default_value": "OneStepTransfer",
 +
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"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": "Email - Routing based targets",
 +
"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.",
 +
"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": "Workitem - Routing Based Queue",
 +
"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.",
 +
"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": "Workitem - Routing based actions",
 +
"type": "config",
 +
"default_value": "OneStepTransfer",
 +
"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
 +
"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": "Workitem - Routing based targets",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "personal, campaign",
 +
"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.",
 +
"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 Outbound Campaign functions",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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).",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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, specifies if WWE should attempt to automatically set channel back to its previous state once it is back in service.",
 +
"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, specifies the amount of time (in second) to set channel back to its previous state once it is back in service when voice.restore-state-on-back-in-service.is-enabled is true.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer from 0 through 10.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "standard-response.categories",
 +
"display_name": "Categories to display from Standard Response Library",
 +
"type": "config",
 +
"default_value": "&#36;All&#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.",
 +
"category": "interaction-workspace",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "Enalbes agents to use the voicemail functionality. This privilege is required to control and monitor voicemail boxes.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer",
 +
"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.",
 +
"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.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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "presence.evaluate-presence",
 +
"display_name": "Evaluate Presence",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Specifies whether the presence (availability) of an agent or agent group (when configured) is shown in Team Communicator in the search results.",
 +
"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'.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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, 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.",
 +
"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.",
 +
"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).",
 +
"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.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}&#36;.",
 +
"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}&#36;.",
 +
"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}&#36;.",
 +
"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}&#36;.",
 +
"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 (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.",
 +
"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 (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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
 +
"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. Virtual agent groups are not supported. This option is overridden by the permissions.agent-group.restrict option.",
 +
"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. Virtual agent groups are not supported.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.cache-timeout-delay",
 +
"display_name": "Cache timeout delay",
 +
"type": "config",
 +
"default_value": "0",
 +
"description": "Specifies the delay, in seconds, before the cache of the result of a Universal Contact Server request is cleared.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer from 1 through 3600. 0 to deactivate it",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "contact.lookup.<media-type>.enable",
 +
"display_name": "Enable <media-type> Contact Lookup",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "contact.lookup.<media-type>.enable-create-contact",
 +
"display_name": "Enable <media-type> Contact Creation on Lookup",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"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.",
 +
"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.",
 +
"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 Diplayed 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.",
 +
"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-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.",
 +
"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.",
 +
"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.",
 +
"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-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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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>",
 +
"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,&#36;OtherMedia&#36;",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated value of valid media type names or &#36;OtherMedia&#36;.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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'.",
 +
"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'.",
 +
"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'.",
 +
"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'.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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",
 +
"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 GWS server to be used for communication by Screen Recording Client",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "Template For 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 the Interaction Queue view.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A comma-separated list of attached data, for example: From,Subject,Received",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.monitor-dashboard.can-use",
 +
"display_name": "Can use the Dashboard",
 +
"type": "config",
 +
"default_value": "true",
 +
"description": "Enables the Dashboard tab.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "privilege.workbin.can-search-my-workbins-trees",
 +
"display_name": "Can Search Workbin",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables agents to search for workbins in the navigation tree of the My Workbins View.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Select a value from the following list: agent,call",
 +
"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.",
 +
"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",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "An integer value from 2 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).",
 +
"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'. If SIP Endpoint is enabled, the login.prompt-place option must be set to false.",
 +
"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.",
 +
"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.",
 +
"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'.",
 +
"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'.",
 +
"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.",
 +
"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 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).",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A correct uri",
 +
"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, 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).",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Any valid host name (either with or without a Fully Qualified Domain Name) or IP Address.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "sipendpoint.register-interval",
 +
"display_name": "Register Interval",
 +
"type": "config",
 +
"default_value": "1500",
 +
"description": "Specifies the interval, in milliseconds, between each register on Genesys Softphone.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid integer",
 +
"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 'failed on check if endpoint' is active allowed.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid not ready reason",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "sipendpoint.enable-webrtc-auth",
 +
"display_name": "Enable WebRTC Auth with OAuth 2 protocol",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Specifies whether the Softphone authenticates using the OAuth 2 protocol.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "webrtc.service-urn",
 +
"display_name": "WebRTC Server URN",
 +
"type": "config",
 +
"default_value": "No default value",
 +
"description": "Specifies the URN that should be based on the following pattern: WEBRTCGATEWAY_SERVER:WEBRTCGATEWAY_PORT?sip-proxy-address=SIPPROXY_SERVER:SIPPROXY_PORT. Replace WEBRTCGATEWAY_SERVER with the hostname where the WebRTC Gateway is deployed, and PORT with the HTTPS port of the WebRTC Gateway. Also, replace SIPPROXY_SERVER and SIPPROXY_PORT (optional) with the connectivity parameters of the SIP Proxy that need to be contacted by the WebRTC Gateway to register this DN.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "A valid URN.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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 associated with the expression.phone-number option.",
 +
"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 associated with the expression.email-address option.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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 Click to Dial in email associated with the expression.identify.phone-number option.",
 +
"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'.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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'.",
 +
"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'.",
 +
"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'.",
 +
"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'.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-monitor-<media-type>",
 +
"display_name": "Can Monitor Generic Chat",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables a supervisor to monitor generic chat interactions.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "true, false.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "privilege.teamlead.can-coach-<media-type>",
 +
"display_name": "Can Coach Generic Chat",
 +
"type": "config",
 +
"default_value": "false",
 +
"description": "Enables a supervisor to coach generic chat interactions.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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'.",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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",
 +
"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.",
 +
"category": "interaction-workspace",
 +
"constraints": {
 +
"data_type": "Comma-separated list of fonts from the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "editor.default-font",
 +
"display_name": "Default font",
 +
"type": "config",
 +
"default_value": "Roboto",
 +
"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.",
 +
"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.",
 +
"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.",
 +
"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": "security.web-content.sandbox-rights.default-authorizations",
 +
"display_name": "List of default sandbox rights authorization options for the embedded Web Application in INTERNAL 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 mode (based on iframes), in order to remove restrictions and enable features.",
 +
"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 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",
 +
"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 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.",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A comma-separated list of file extensions that represent file types that are to be restricted.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
},
 +
{
 +
"id": "attachment.<media-name>.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 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.",
 +
"category": "workspace-service",
 +
"constraints": {
 +
"data_type": "A comma-separated list of file extensions that represent file types that are to be restricted.",
 +
"required": false,
 +
"dynamic": true
 +
}
 +
}
 +
],
 
"version": "9.0.000.31"
 
"version": "9.0.000.31"
 
}</pre>
 
}</pre>
−
 
−
[[Category:V:HTCC:8.5Source]]
 

Revision as of 15:14, April 5, 2019

options 9.0.000.31

{
	"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "from 0 to MAXINT",
				"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.",
			"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].",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 500 through 50000.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "system.feedback.log-size",
			"display_name": "The feedback log size.",
			"type": "config",
			"default_value": "1000",
			"description": "Specifies the number of characters from the last Log to send with the feedback.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than or equal to 0.",
				"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: Trace, Debug, Info, Warning, Error, Off.",
				"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.",
			"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'. 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).",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.<media-type>.queue",
			"display_name": "Workitem - Routing Based Queue",
			"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.",
			"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": "Workitem - Routing based actions",
			"type": "config",
			"default_value": "OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"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": "Workitem - Routing based targets",
			"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.",
			"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 the inactivity timeout, the agent session is ended. A value of 0 disables the inactivity timeout. Warning: After the timeout occurs, the Worksapce login dialog should be blank; however, if the agent has allowed the browser to remember his or her password, then the login dialog will still be populated with the agent's credentials. For security, agents should not allow web browsers to remember their login credentials.",
			"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.",
			"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.",
			"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": "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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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'.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value greater than 0.",
				"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$.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "$Window.Title$,$Application.Title$,$Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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": "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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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": "ContactInteractionDetailView,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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView,...",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.HistoryInteractionDetailsRegion.activate-order",
			"display_name": "Default view in Region HistoryInteractionDetailsRegion",
			"type": "config",
			"default_value": "ContactInteractionDetailView,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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView,...",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.WorkbinInteractionDetailsRegion.order",
			"display_name": "Views order in Region WorkbinInteractionDetailsRegion",
			"type": "config",
			"default_value": "ContactInteractionDetailView,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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,ContactInteractionNotePadView,StaticCaseDataView,...",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.WorkbinInteractionDetailsRegion.activate-order",
			"display_name": "Default view in Region WorkbinInteractionDetailsRegion",
			"type": "config",
			"default_value": "ContactInteractionDetailView,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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid view names from the following list (plus the custom views): ContactInteractionDetailView,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.",
			"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.",
			"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": "KnowledgeView,CoBrowseView,WebActivityView,ContactView,SRLView",
			"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.",
			"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'): KnowledgeView,ExtensionSectionName,CoBrowseView,WebActivityView,ContactView,SRLView,...",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "views.CaseSideRegion.activate-order",
			"display_name": "Default view in Region CaseSideRegion",
			"type": "config",
			"default_value": "ContactView,SRLView,KnowledgeView,CoBrowseView,WebActivityView",
			"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.",
			"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,KnowledgeView,CoBrowseView,WebActivityView,...",
				"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid 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": "Sspecifies 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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, Dnd, NotReadyReason, AfterCallWork, 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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of action names from the following list: Ready, NotReady, NotReadyReason, AfterCallWork, 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.",
			"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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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'. 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.",
			"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.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'. 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.",
			"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'. 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).",
			"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><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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A string that represents an attached data key.",
				"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",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"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>.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction-bar.quick-access-modes.<media-type>",
			"display_name": "Quick Access Modes <media-type>",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "interaction.disposition.use-attached-data",
			"display_name": "Disposition uses attached data",
			"type": "config",
			"default_value": "false",
			"description": "Specifies that attached data can be added to the interaction in UserEvent. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid Business Attribute name.",
				"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.",
			"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.",
			"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": "Disposition cache timeout delay",
			"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.",
			"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.",
			"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": "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.",
			"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.",
			"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.",
			"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.",
			"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$'.",
			"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": "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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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. Do not enable this option if the privilege.sipendpoint.can-use privilege is granted.",
			"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.",
			"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)). English is the default language, and will always be available.",
			"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.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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 used during chat sessions (displayed to the customer) by a string that can contain regular characters and field codes. This option can be overridden by a routing strategy as described in the Configuration Guide.",
			"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$.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid name of a Script of type Interaction Queue.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "The name of a valid Business Attribute.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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:'.",
			"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:'.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "\\\"response:\\\" followed by the response path to the standard response",
				"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid character string.",
				"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.",
			"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.",
			"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.",
			"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>",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.routing-points",
			"display_name": "Voice - Routing Points",
			"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.",
			"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": "Voice - Routing based actions",
			"type": "config",
			"default_value": "MakeCall,OneStepConference,InitConference,OneStepTransfer,InitTransfer",
			"description": "Specifies the list of Routing Based Actions that an agent may perform.",
			"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": "Voice - Routing based targets",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, RoutingPoint, TypeDestination, OutboundRecord, Contact",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.make-call-caller-id-business-attribute",
			"display_name": "Voice - 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.",
			"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": "Voice - 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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "voice.caller-id.key-name",
			"display_name": "Caller ID - Attached Data Key",
			"type": "config",
			"default_value": "IW_SelectedCallerId",
			"description": "Specifies the key name of the attached data that contains the selected caller id information.",
			"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": "Voice - Single Step Conference enabled",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.single-step-transfer-enabled",
			"display_name": "Voice - Single Step Transfer enabled",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.consultation-enabled",
			"display_name": "Voice - Consultation enabled",
			"type": "config",
			"default_value": "Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill",
			"description": "Specifies the list of targets enabled in Team Communication for a consultation.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.voice.make-call-enabled",
			"display_name": "Voice - 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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of valid object types from the following list: Agent, AgentGroup, RoutingPoint, Contact, TypeDestination, Skill.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "intercommunication.chat.queue",
			"display_name": "Chat - Routing Based Queue",
			"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.",
			"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": "Chat - Routing based actions",
			"type": "config",
			"default_value": "InitTransfer,OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"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": "Chat - Routing based targets",
			"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.",
			"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": "Email - Routing Based Queue",
			"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.",
			"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": "Email - Routing based actions",
			"type": "config",
			"default_value": "OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"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": "Email - Routing based targets",
			"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.",
			"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": "Workitem - Routing Based Queue",
			"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.",
			"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": "Workitem - Routing based actions",
			"type": "config",
			"default_value": "OneStepTransfer",
			"description": "Specifies the list of 'routing based' actions that an agent is allowed to perform.",
			"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": "Workitem - Routing based targets",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "personal, campaign",
				"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.",
			"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 Outbound Campaign functions",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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).",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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, specifies if WWE should attempt to automatically set channel back to its previous state once it is back in service.",
			"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, specifies the amount of time (in second) to set channel back to its previous state once it is back in service when voice.restore-state-on-back-in-service.is-enabled is true.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 0 through 10.",
				"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.",
			"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": "privilege.SRL.can-use",
			"display_name": "Can Use",
			"type": "config",
			"default_value": "false",
			"description": "Enables access to the Standard Response Library functions.",
			"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.",
			"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": "Enalbes agents to use the voicemail functionality. This privilege is required to control and monitor voicemail boxes.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer",
				"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.",
			"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.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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "presence.evaluate-presence",
			"display_name": "Evaluate Presence",
			"type": "config",
			"default_value": "true",
			"description": "Specifies whether the presence (availability) of an agent or agent group (when configured) is shown in Team Communicator in the search results.",
			"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'.",
			"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.",
			"category": "interaction-workspace",
			"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.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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, 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.",
			"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.",
			"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).",
			"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.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}$.",
			"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}$.",
			"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}$.",
			"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}$.",
			"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 (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.",
			"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 (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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of Agent Groups; empty means no exclusion.",
				"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. Virtual agent groups are not supported. This option is overridden by the permissions.agent-group.restrict option.",
			"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. Virtual agent groups are not supported.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.cache-timeout-delay",
			"display_name": "Cache timeout delay",
			"type": "config",
			"default_value": "0",
			"description": "Specifies the delay, in seconds, before the cache of the result of a Universal Contact Server request is cleared.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer from 1 through 3600. 0 to deactivate it",
				"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.",
			"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.",
			"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.",
			"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.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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.<media-type>.enable",
			"display_name": "Enable <media-type> Contact Lookup",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "contact.lookup.<media-type>.enable-create-contact",
			"display_name": "Enable <media-type> Contact Creation on Lookup",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"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.",
			"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.",
			"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 Diplayed 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.",
			"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-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.",
			"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.",
			"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.",
			"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-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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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>",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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'.",
			"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'.",
			"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'.",
			"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'.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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",
			"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 GWS server to be used for communication by Screen Recording Client",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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": "Template For 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 the Interaction Queue view.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A comma-separated list of attached data, for example: From,Subject,Received",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.monitor-dashboard.can-use",
			"display_name": "Can use the Dashboard",
			"type": "config",
			"default_value": "true",
			"description": "Enables the Dashboard tab.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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": "privilege.workbin.can-search-my-workbins-trees",
			"display_name": "Can Search Workbin",
			"type": "config",
			"default_value": "false",
			"description": "Enables agents to search for workbins in the navigation tree of the My Workbins View.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Select a value from the following list: agent,call",
				"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.",
			"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",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "An integer value from 2 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).",
			"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'. If SIP Endpoint is enabled, the login.prompt-place option must be set to false.",
			"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.",
			"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.",
			"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'.",
			"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'.",
			"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.",
			"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 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).",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A correct uri",
				"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, 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).",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Any valid host name (either with or without a Fully Qualified Domain Name) or IP Address.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.register-interval",
			"display_name": "Register Interval",
			"type": "config",
			"default_value": "1500",
			"description": "Specifies the interval, in milliseconds, between each register on Genesys Softphone.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid integer",
				"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 'failed on check if endpoint' is active allowed.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid not ready reason",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "sipendpoint.enable-webrtc-auth",
			"display_name": "Enable WebRTC Auth with OAuth 2 protocol",
			"type": "config",
			"default_value": "false",
			"description": "Specifies whether the Softphone authenticates using the OAuth 2 protocol.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "webrtc.service-urn",
			"display_name": "WebRTC Server URN",
			"type": "config",
			"default_value": "No default value",
			"description": "Specifies the URN that should be based on the following pattern: WEBRTCGATEWAY_SERVER:WEBRTCGATEWAY_PORT?sip-proxy-address=SIPPROXY_SERVER:SIPPROXY_PORT. Replace WEBRTCGATEWAY_SERVER with the hostname where the WebRTC Gateway is deployed, and PORT with the HTTPS port of the WebRTC Gateway. Also, replace SIPPROXY_SERVER and SIPPROXY_PORT (optional) with the connectivity parameters of the SIP Proxy that need to be contacted by the WebRTC Gateway to register this DN.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "A valid URN.",
				"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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 associated with the expression.phone-number option.",
			"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 associated with the expression.email-address option.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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 Click to Dial in email associated with the expression.identify.phone-number option.",
			"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'.",
			"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.",
			"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.",
			"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.",
			"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'.",
			"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'.",
			"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'.",
			"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'.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-monitor-<media-type>",
			"display_name": "Can Monitor Generic Chat",
			"type": "config",
			"default_value": "false",
			"description": "Enables a supervisor to monitor generic chat interactions.",
			"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.",
			"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.",
			"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.",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "true, false.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "privilege.teamlead.can-coach-<media-type>",
			"display_name": "Can Coach Generic Chat",
			"type": "config",
			"default_value": "false",
			"description": "Enables a supervisor to coach generic chat interactions.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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.",
			"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'.",
			"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.",
			"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.",
			"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.",
			"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",
			"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.",
			"category": "interaction-workspace",
			"constraints": {
				"data_type": "Comma-separated list of fonts from the following list: Serif, Sans-serif, Monospace, Cursive, Fantasy, Tahoma, Roboto.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "editor.default-font",
			"display_name": "Default font",
			"type": "config",
			"default_value": "Roboto",
			"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.",
			"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.",
			"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.",
			"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": "security.web-content.sandbox-rights.default-authorizations",
			"display_name": "List of default sandbox rights authorization options for the embedded Web Application in INTERNAL 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 mode (based on iframes), in order to remove restrictions and enable features.",
			"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 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",
				"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 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.",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A comma-separated list of file extensions that represent file types that are to be restricted.",
				"required": false,
				"dynamic": true
			}
		},
		{
			"id": "attachment.<media-name>.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 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.",
			"category": "workspace-service",
			"constraints": {
				"data_type": "A comma-separated list of file extensions that represent file types that are to be restricted.",
				"required": false,
				"dynamic": true
			}
		}
	],
	"version": "9.0.000.31"
}
Comments or questions about this documentation? Contact us for support!