Contents

Overview
A general description of how the Farlon UCC Desktop is configured.
The XML configuration file
The syntax and contents of the XML configuration file.
Shortcut keys
A description of how to define keyboard shortcuts used in the XML configuration.
Actions
A description of actions that can be used in tool buttons and workflow events.
Inserting runtime data
A description of how to insert values from calls, phone book entries etc. in URLs.
Object field names
A description of all the available fields that can be accessed on various objects.
Filter expressions
How to configure automatic distribution of Farlon UCC Desktop to agents PCs.
Automatic update
How to configure automatic distribution of Farlon UCC Desktop to agents PCs.
Debugging
How to inspect UCC traffic.


Configuration reference

The Farlon UCC Desktop can run as a standalone application, or fetch its configuration from a centralized location if two or more application instances are going to share settings like logout and not ready reasons.

During installation you can specify a file path or URL to where the application can find its XML configuration. If you want to change the path after installation reinstall or change the “ConfigUrl” setting in the applications .config file.

You can also specify the configuration file to use, as a command line parameter to the exe file.

The XML configuration file is a document that can be a physical XML file on a file share, on a web site or be generated on the fly by a ASP or PHP web page.

The file path or URL to the configuration file can get certain information inserted to enable groups to share the same configuration file.

Insertion variables
{{ UserDomainName }} User domain name
{{ UserName }}  User name 
{{ Version }}  Application version 
{{ LanguageId }}  User language id (4 hex digits) 

 

Example URL:

http://www.mydomain.com/desktopconfig.aspx?domain={{ UserDomainName }}&user={{ UserName }}&appversion={{ Version }}&language={{ LanguageId }}

The configuration XML is read once during startup and at each login. If the application is unable to read the startup configuration file, the user is notified with a pop up message.

If a “LoginConfigUrl” setting has been specified in the startup config XML file, an attempt to load extra information is performed after a successful login.

On the LoginConfigUrl you can specify additional insertion variables:

Insertion variables
{{ AgentInstrument }} The instrument(extension) of the logged in agent.
{{ Settings.<setting name> }} The settings values specified in the Settings section in the configuration file.
{{ Agent.<field name> }} The fields available on the Agent object. For more information, see the Object field names chapter.
{{ Agent.Team.<field name> }} The fields available on the Team object. For more information, see the Object field names chapter.

 

Example URL:

http://www.yourdomain.com/desktopconfig.team.aspx?agentId={{ Agent.AgentId }}|Unknown& teamId={{ Agent.Team.Id }}

If the application is unable to read the login configuration file, the user is notified with a pop up message (can be suppressed).