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).
Workspace Desktop Edition Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
The Quick Search List View now correctly displays search results for email address search strings that contain the hyphen character. Previously, if an agent searched for an email address that contained a hyphen, no results were displayed. (IW-11626)
Workspace now correctly supports the definition of table widths in the <table> tag for HTML formatted outgoing email interactions. Previously, the WIDTH keyword was dropped from the <table> tag after the HTML email interaction was sent, causing the HTML email interaction to not be displayed correctly in Microsoft Outlook or Microsoft Internet Explorer. (IW-11615)
If the legacy interaction display mode is enabled (the value of the interaction-bar.enable-quick-access is set to false), the size of interaction windows is now correctly managed when an agent shows or hides the Responses panel. Previously in this scenario, interaction windows were not correctly resized when the Responses panel was shown or hidden. (IW-11594)
When Workspace is configured to connect to a T-Server Hot Standby pair through TLS, the connection is now correctly set to the back-up T-Server. Previously in this scenario, the TLS connection to the back-up T-Server failed if it was not installed on the same host as the primary T-Server. (IW-11530)
In environments configured to use Kerberos Ticket to connect to Configuration Server, Workspace no longer tries to check the validity of the configured Service Principal Name against Microsoft Active Directory before using it to request a Ticket to the Microsoft security stack. Previously in this scenario, the validity check could fail in environments where the end user account and the Genesys server host were configured in distinct Domains; whereas, the Windows Kerberos environment was properly configured to support multi-domain authentication. (IW-11513)
The connection mechanism to Genesys back-end servers, such as Configuration Server, has been improved to better support difficult connection environments, such as those with workstation that run Microsoft ForeFront UAG, which affect the Windows network stack. (IW-10686)
No special procedure is required to upgrade to release 220.127.116.11.