Jump to: navigation, search

options.record-location

Section: interaction-workspace
Default Value:
Valid Values: A valid file path to a host directory.
Changes Take Effect: When the application is started or restarted.
Dependencies: options.record-option-locally-only
Introduced: 8.5.112.08

In environments where the value of the options.record-option-locally-only is set to false, this option specifies the location where agent preferences are stored when an agent exits the application. If the value of this option is left empty, agent preferences are stored in Person's Annex in Configuration Server. The full path can also contain the following field codes: $Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$,$Env.X$ (where X is the name of the environment variable). Genesys recommends that you append the agent's Username to the specified path as shown above.

editor.user-agent-http-header

Section: interaction-workspace
Default Value: Mozilla/4.0 (compatible; MSIE 7.0)
Valid Values: A string representing a valid 'User-Agent' HTTP header according to RFC 1945.
Changes Take Effect: At next interaction.
Introduced: 8.5.112.12

Specifies the 'User-Agent' HTTP header value set in the HTTP requests used by rich text/HTML editor to download external images.

chat.auto-answer

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


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 Overriding Options by Using a Routing Strategy.

8.5.112.12

Workspace Desktop Edition Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
04/07/16 General X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • In scenarios where a conversation between a contact and an agent is silently monitored by a supervisor, the name of the contact now remains visible in the interaction view after the call is completed. Previously, when the contact released the monitored call first, the label unidentified was displayed in the Case header, and the list of parties engaged in the conversation was empty.
  • The controls that enable a supervisor to request the silent monitoring or coaching of the call currently handled by the selected agent is now correctly labelled Monitor > Current call or Coach > Current call. Previously, these controls were labelled Monitor > Unidentified or Coach > Unidentified.



Resolved Issues

This release contains the following resolved issues:


In scenarios where the value of the interaction-workspace\chat.auto-answer option is set to true for a supervisor, if the supervisor tries to barge in to an agent Chat session, the barge-in button now behaves as expected. Previously, the barge-in button did not refresh correctly after it was clicked, which could cause unexpected error messages. (IW-12664)


When an agent adds a new Outbound record, Workspace no longer sends the GSW_RECORD_ID attribute. Previously, when GSW_RECORD_ID had send_attribute configured while adding a new record, all alternate number recall records were marked as stale in the Outbound campaign. (IW-12643)


You can now use the interaction-workspace\editor.user-agent-http-header option to configure the User-Agent HTTP header value that Workspace sets in the HTTP requests used by the rich text editor to download external images belonging to HTML formatted email interactions. Previously, the User-Agent HTTP header was hard-coded to be Mozilla/4.0 (compatible; MSIE 7.0), causing download requests to be rejected by some web servers. (IW-12640)


The interaction-workspace\options.record-location option, which is used to specify the storage of the agent profile in a shared directory instead of the annex of an Agent object in Configuration Server, can now be used in environments where Workspace is started by specifying username, password, and configuration server connection URI as command line parameters. (IW-12631)


The formatting of outbound HTML email interactions created by pasting text formatted in Microsoft Word has been improved to ensure better line spacing of paragraphs. (IW-12618)


When handling pull- or push-preview interactions in environments where UCS is enabled, Workspace no longer sends invalid requests to UCS when the outbound call is placed by the agent. (IW-12502)


In scenarios where a conversation between a contact and an agent is silently monitored by a supervisor, the name of the contact now remains visible in the interaction view after the call is completed. Previously, when the contact released the monitored call first, the label unidentified was displayed in the Case header, and the list of parties engaged in the conversation became empty. (IW-12415)


In environments where Workspace is configured to display interactions in separate windows, the window size is now preserved. Previously, the window size might not have been preserved, depending on whether the right panel was open or closed at the time the window was closed. (IW-12390)




Upgrade Notes

No special procedure is required to upgrade to release 8.5.112.12.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 12, 2017, at 07:10.