Jump to: navigation, search

interaction-bar.enable-quick-access

Section: interaction-workspace
Default Value: true
Valid Values: true, false
Changes Take Effect: When application is started or restarted.


Specifies whether interaction windows are docked or undocked.

  • true: Interaction windows are docked to the interaction bar. Use the interaction-bar.quick-access-modes option to specify pinned or floating mode.
  • false: Interaction windows are undocked from the interaction bar (pre-8.5.0 legacy mode).

Note: In legacy mode, the Main Window layout is the same as when Quick Access is enabled: the interaction bar is located on the right of the Team Communicator control (instead of below it, as in the 8.1.4 release), and the Supporting Views are accessible from the ‘hamburger’ menu (instead of the toolbar buttons, as in the 8.1.4 release).

contact.editable-attributes

Section: interaction-workspace
Default Value: $All$
Valid Values: A comma-separated value list of Attribute Value names that correspond to contact field names, for example: LastName, FirstName, PhoneNumber, EmailAddress.
Changes Take Effect: When the application is started or restarted.
Dependencies: contact.displayed-attributes
Introduced: 8.5.101.14

The list of Contact attributes that can be changed by Agent. 'Contact - Can Edit Contact' privilege must be granted. A comma-separated value list of Attribute Value names that correspond to contact field names: either $All$ or one or more of the values that are defined by the contact.displayed-attributes option. If this option is left blank (""), no fields are editable.

accessibility.<media-type>.focus-on-interaction-toast

Section: interaction-workspace
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next interaction.
Introduced: 8.5.101.14
Related Options: accessibility.focus-on-interaction-toast

Specifies that all Interaction Notification views for the <media-type> receives the focus when they are displayed. When a value for this option is set, this option overrides the accessibility.focus-on-interaction-toast option. This option does not rely on the accessibility.visual-impairment-profile option; therefore, it applies to all configured agents, not just visually impaired agents.

accessibility.focus-on-interaction-toast

Section: interaction-workspace
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next interaction.
Introduced: 8.5.101.14

Specifies that all Interaction Notification views receive the focus when they are displayed. This option does not rely on the accessibility.visual-impairment-profile option; therefore, it applies to all configured agents, not just visually impaired agents.

display-format.agent-name

Section: interaction-workspace
Default Value: $Agent.FullName$|$Agent.UserName$
Valid Values: A string that contains a compilation of characters and field codes from the following list: $Agent.FullName$,$Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$.
Changes Take Effect: Immediately.


Defines the display format of other agents tby specifying a string that contains the following field codes: $Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$.

general.configuration-object-collection-cache-timeout

Section: interaction-workspace
Default Value: 0
Valid Values: Any positive integer value.
Changes Take Effect: When the application is started or restarted.
Introduced: 8.5.101.14
Related Options: teamcommunicator.list-filter-showing

Specifies the amount of time, in hours, to keep the list of objects in a local cache file before requesting it again from Configuration Server. Once the timeout is expired, Workspace request the objects from Configuration Server the next time that Team Communicator is initialized, such as at the next session login if Team Communicator is already initialized for the current session. The value 0 means that no local cache is created. This list of objects is loaded and cached based on the value of the teamcommunicator.list-filter-showing option.

general.configuration-agent-collection-loading-method

Section: interaction-workspace
Default Value: read-objects
Valid Values: One value from this list:read-objects,brief-info
Changes Take Effect: When the application is started or restarted.
Introduced: 8.5.101.14
Related Options: display-format.agent-name, teamcommunicator.list-filter-showing

Specifies the method that Workspace uses to retrieve the collection of agents from Configuration Server. This retrieval happens when the teamcommunicator.list-filter-showing option contains the value Agent. Choose the method that best meets your business requirements, system environment, and scale constraints:

  • read-objects—This is the legacy agent-retrieval method. This method returns the list of agents according to the "read" permission of the current agent. For each retrieved agent this method returns the full agent data from Configuration Server, including annex structure, in an uncompressed format. The bandwidth consumed can be much larger than the other retrieval methods.
  • brief-info—For each retrieved agent, this method returns only a subset of the agent data. This can result in significant network bandwidth optimization, as well as a decrease of the load on Configuration Server. Configuration Server ignores the "read" permissions of the current agent when returning the list of object; therefore, the Team Communicator provides access to all the agents of the Tenant. This methods does not provide access to the field EmployeeID; therefore, when displaying search results in Team Communicator, the value $Agent.EmployeeID$ is ignored when it is specified in the display-format.agent-name option.

8.5.101.14

Workspace Desktop Edition Release Notes

Release Date Release Type Restrictions AIX HP-UX PA HP-UX IPF Linux Solaris Windows
08/28/14 General X

Helpful Links

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Workspace Desktop Edition.

  • Workspace can now render HTML text that is included in a fieldset HTML tag. Previously, all text included in a fieldset tag was ignored.
  • Team communicator performance, network bandwidth, and Configuration Server load optimization. The following configuration options have been added to support this feature:
  • In multi-site SIP Server environments designed with complex trunk structures, Workspace now properly displays the agent identifier in the conference according to the value specified by the display-format.agent-name configuration option. This capability requires SIP Server version 8.1.101.30 and that the value of the sip-enable-call-info SIP Server option is set to true. Previously in this kind of environment, some conference participants might have been displayed with technical strings instead of actual names.
  • Support for the localization of display names for DN object aliases, Business Attributes, and Action Codes by using new and enhanced display-format.* configuration options.
  • The width of the Standard Response table columns is now saved in the agent settings so that it can be restored the next time that the view is displayed, either during the same agent session or at the next agent login.
  • You can now control whether the Interaction Notification toast receives the focus when it is displayed. This feature enhances accessibility in environments that use screen reader applications; when an Interaction Notification is displayed it is read by the screen reader. The following configuration options have been added to support this feature:
  • Virtualization support is extended to Citrix XenDesktop 7 and XenApp 7.
  • Support for the customizing of display names for configuration objects by using new and enhanced display-format.* configuration options.
  • Workspace deployment can be configured so that agents cannot reject ClickOnce upgrades at login time. This can be specified in the Deployment Manager Configuration.
  • Specify which contact attributes can be edited by agents by using the contact.editable-attributes configuration option.
  • E-mail printing capability has been extended to the following views:
    • My History
    • Contact History
    • Workbins

Corrections and Modifications

This release also includes the following corrections or modifications:


It is now possible to add attachments to e-mail interactions in legacy window mode (where the value of interaction-bar.enable-quick-access is set to false). (IW-9686)


The Advanced Search now works correctly in the Standard Response view. Previously, when an "All Keywords" search was performed with only Responses Names, no results were returned. (IW-9661)


Workspace no longer closes unexpectedly while identifying the contact (main) party in a SIP Voice call. (IW-9654)


All tool-tips can now be localized by using the dictionary file. The ToolTip attribute has been added as a dictionary key and the Team Communicator now considers localization dictionaries for tooltips. (IW-9633)


The name of the agent is now correctly displayed to supervisors for monitored (coached) calls. Previously in this scenario, the contact's number was displayed instead of the name of the agent. (IW-9632)


The chained records list of Outbound Records is now correctly displayed in both the Interaction Bar and the Interaction Window. (IW-9569)


Agents no longer receive a timeout error when they try to reschedule a push preview record after reconnection of Interaction Server. (IW-9252)


External messages are now displayed and Agents can enter text in the SMS input field when handling a transferred SMS Session. Previously in this scenario, agents were not able to enter a message unless the contact sent an SMS first if the transcript contained external messages. (IW-9240)


In Business Continuity environments where Workspace is configured with preferred and peer Configuration Server Proxy pairs that are configured with multiple ports, Workspace is now able to properly connect to the non-default port of those configuration servers. (IW-9228)


The following value for the display-format.interaction-<media>-name is no longer supported in the metadata: $Interaction.Id$. This parameter is for system use only. (IW-8857)


This page was last edited on September 12, 2017, at 14:51.
Comments or questions about this documentation? Contact us for support!