Jump to: navigation, search

general.writable-downloaded-attachment-file-types

Section: interaction-workspace
Default Value: No default value
Valid Values: A comma separated list of valid file extensions, such as xlsx, png, and so on.
Changes Take Effect: At next attachment download.
Introduced: 8.5.118.10

Specifies the list of attachment file types that when they are opened are writable on the hard drive of the agent workstation once they are downloaded from UCS.

general.restricted-attachment-file-content-types

Section: interaction-workspace
Default Value: No default value
Valid Values: A comma-separated list of restricted file formats from this list: exe, zip.
Changes Take Effect: At the next attachment upload or download.
Introduced: 8.5.115.17

Specifies the list of attachment file types for which agent operations, such as Attach, Open, Save, and Save All, will be blocked. File types are recognized by binary content, unlike the file extension used in Template loop detected: Template:Optionslink and Template loop detected: Template:Optionslink options. Following file formats are supported: Windows/DOS executable file and PKZIP archive file. Microsoft Office document files having extension '.docx', '.xlsx' have format PKZIP. If the file format 'zip' is specified in this option, the file will be rejected. The content type of the attachments added by inserting a Standard Response into an interaction is not validated by the Workspace logic controlled by this option.

general.non-unicode-connection-encoding

Section: interaction-workspace
Default Value:
Valid Values: .Net Name of Code Page Identifier
Changes Take Effect: When the application is started or restarted


Specifies the code page encoding that is used to connect to back-end servers that do not rely on Unicode communication (all back-end servers except UCS). The possible values can be obtained from the ".Net Name" column of the Code Page Identifier that is defined in the following document: http://msdn.microsoft.com/en-us/library/windows/desktop/dd317756(v=vs.85).aspx

When this option is empty, the applied encoding corresponds to the language for non-unicode programs, which is also known as the system-locale of the agent Workstation.

general.gad.attached-data

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


Specifies whether attached data keys are added. If this option is set to true, Workspace adds to the attached data the equivalent of GAD Keys. In the case in which routing base is used, Workspace adds the following keys: GD_TransferTargetType,GD_TransferTargetId

general.configuration-update-notification

Section: interaction-workspace
Default Value: All
Valid Values: A comma-separated value list of one or more items that are to be notifed: None, All, ThisAgent, ThisApplication, ThisTenant, Transactions, Persons, Skills, AgentGroups, DN, BusinessAttributes, BusinessAttributeValues, Script
Changes Take Effect: When the application is started or restarted.


Specifies the list of Configuration Server objects that require notification when there is an update.

Note: for legacy purposes, the value ThisAplication is also supported. This value was introduced erroneously in Workspace 8.1.

general.configuration-transaction-cache-preload

Section: interaction-workspace
Default Value:
Valid Values: A comma-separated value list of valid Transaction object names or $All$
Changes Take Effect: When the application is started or restarted.


Specifies the list of Transaction objects of type 'List' that are loaded and cached at login time.

  • If $All$ is configured, all the Transaction objects of type 'List' that are contained in the Agent’s Tenant and on which the Agent has Read Access, are pre-loaded at login time.
  • Pre-loading these objects means that dynamic access to Configuration Server during the critical phase of interaction notification is not required.

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-business-attribute-cache-preload

Section: interaction-workspace
Default Value: No default value
Valid Values: A comma-separated value list of valid Business Attribute object names or $All$.
Changes Take Effect: When the application is started or restarted.


Specifies the list of Business Attribute objects that are loaded and cached at login time.

  • If $All$ is configured, all the Business Attribute objects that are contained in the Agent’s Tenant and on which the Agent has Read Access, are pre-loaded at login time.
  • Pre-loading these objects means that dynamic access to Configuration Server during the critical phase of interaction notification is not required.

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.

General options

Tip
For the most up to date Workspace Desktop Edition configuration options, see the Genesys Configuration Option Database.
This page was last edited on June 27, 2024, at 13:46.
Comments or questions about this documentation? Contact us for support!