Cisco Finesse supports both HTTP and secure HTTP (HTTPS). Administrators can sign in to the Administration Console using HTTP or HTTPS. Agents and supervisors can sign in to the Cisco Finesse Agent Desktop using either HTTP or HTTPS.
Administrators can run the Cisco Finesse HTTPS Redirect CLI command to enforce HTTPS access for both the Administration Console and the Agent Desktop. For more information, see Cisco Finesse HTTPS Redirect.
This guide uses HTTP for all example URLs.
Conventions
This manual uses the following conventions:
Convention
Description
boldface font
Boldface font is used to indicate commands, such as user
entries, keys, buttons, and folder and submenu names. For example:
Choose
Edit > Find.
Click
Finish.
italic font
Italic font is used to indicate the following:
To introduce a new term. Example: A
skill group is a collection of agents who share
similar skills.
For emphasis. Example:
Do not use the numerical naming convention.
A syntax value that the user must replace. Example: IF
(condition, true-value, false-value)
A book title. Example: See the
Cisco CRS Installation Guide.
window font
Window font, such as Courier, is used for the following:
Text as it appears in code or that the window displays.
Example:
<html><title>Cisco Systems,Inc.
</title></html>
< >
Angle brackets are used to indicate the following:
For arguments where the context does not allow italic,
such as ASCII output.
A character string that the user enters but that does not
appear on the window such as a password.
Documentation and service requests
For information on obtaining
documentation, submitting a service request, and gathering additional
information, see the monthly What's New in Cisco Product
Documentation, which also lists all new and revised Cisco technical
documentation, at:
Subscribe to the What's New in Cisco Product
Documentation as a Really Simple Syndication (RSS) feed and set
content to be delivered directly to your desktop using a reader application.
The RSS feeds are a free service and Cisco currently supports RSS version
2.0.
Documentation feedback
You can provide comments about
this document by sending email to the following address: