Jump to: navigation, search

main-window.window-title

Section: interaction-workspace
Default Value: $Window.Title$
Valid Values: $Window.Title$,$Application.Title$,$Application.Name$,$Agent.UserName$,$Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId$.
Changes Take Effect: Immediately.


Defines the title of the Main Window that appears in the Windows Task Bar by specifying a string that contains the following field codes:

$Window.Title$,$Application.Title$,$Application.Name$,$Agent.UserName$, $Agent.LastName$,$Agent.FirstName$,$Agent.EmployeeId

If all field codes are empty, the following field codes are used:

$Window.Title$

main-window.bypass-auto-hide-conditions

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

In environments where an agent is granted the privilege to auto-hide the main window, the value of this option can be set to true when it is necessary to bypass the default control that disables the Workspace auto-hide function when a third party auto-hide window is reported as already present by the Windows Operating System. This is useful in a Citrix XenApp environment where Workspace is running as a Seamless Window.

main-window.auto-hide-display-delay

Section: interaction-workspace
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: At the next interaction.
Introduced: 8.5.136.07

When the Main Window - Can Auto-hide the Main Window privilege is granted, this option specifies the duration, in milliseconds, for which the Main Window remains hidden before being displayed when the mouse is at the top of the screen. The value 0 means specifies the minimum value.

Main Window options

Tip
For the most up to date Workspace Desktop Edition configuration options, see the Genesys Configuration Option Database.

Related Resources

The following topics discuss the implementation of these options:

This page was last edited on July 21, 2020, at 18:27.
Comments or questions about this documentation? Contact us for support!