Supervisors can now view the recent call history of an agent on an assigned team from the Team Performance gadget. Select the team of the agent, click on the agent from the list. You can view call details like start time of the call, duration, type etc.

You cannot select any other agent or choose another team while the recent call history of the selected agent is being loaded. However, you may change an agent's state or monitor an agent's call during this time-frame.

Supervisors can now view the recent state history of an agent on an assigned team from the Team Performance gadget. Select the team of the agent, click on the agent from the list. You can view agent state details like start time of the call, agent state, reason, and duration of the call.

You cannot select any other agent or choose another team while the recent state history of the selected agent is being loaded. However, you may change an agent's state or monitor an agent's call during this time-frame.

Agents and Supervisors can make calls from Ready State.

Finesse desktop layout.xml provides an additional attribute to specify alternate hosts from which gadgets can be loaded. This is to ensure that the Finesse desktop is fully functional even if the primary servers on which the gadgets are hosted are unavailable.

As an Agent or Supervisor, you can view your call history by clicking on the 'My History' tab. You can view call details like start time of the call, duration, type etc.

The Finesse Administrator can differentiate between system reason codes and custom reason codes in the Not Ready and Sign Out Reason code gadgets. The Type column can be sorted to display both reason codes (System or Custom) in the Finesse Admin Console. System reason code "labels" can be edited and saved but the global attribute and "code" cannot be edited. Admin cannot create or update a new Reason Code that conflicts with a predefined Reason Code already present in the system.

By default, in the Team performance gadget, supervisors will not be able to view logged out agents. To view both logged in and logged out agents, click the Include logged out agents checkbox.

The Queue Statistics gadget is enabled by default as part of Cisco Finesse new installation for Unified CCE. When performing a system upgrade from Cisco Finesse 11.5(1), the desktop custom layout needs to be modified by the administrator for the Queue Statistics gadget to be displayed on the Agent and Supervisor desktop.

Secondary call ID is added in the additional element of the primary dialog API for consult, transfer and conference calls scenarios.

Dynamic Live Data gadgets (identified by the "type=dynamic" URL parameter) in the supervisor desktop layout can have only a single viewID URL param configured. This enables you to view call history and state history on the desktop correctly.

When upgrading from a previous Cisco Finesse version to 11.6(1), you can manage reason code conflicts so that reports reflect accurate reason codes after upgrade.

When performing a system upgrade in a Unified CCE deployment, if the predefined system reason codes already exist in the system as custom reason codes, they need to be modified with new values to avoid conflict post upgrade.

Toaster notifications are enabled by default after a fresh installation of Cisco Finesse. Use CLI commands to disable, enable and check the status of the toaster notifications. You can set the duration (timeout in seconds) of the toaster notification.

Cisco Finesse 11.6(1) supports TLSv 1.2. For Cisco Finesse 11.6(1) to be backward compatible with earlier Unified CCE versions, TLSv 1.0 and 1.1 protocols must be enabled. Run the following CLI command:

set tls client min-version

This command allows you to set the minimum TLS version to 1.0 or 1.1 in the client that can be used for outbound SSL connections. Restart the system for the changes to take effect.

Note	When you update the TLS minimum version from TLSv1.2 to TLSv1.1 or TLSv1.0, restart Cisco Finesse. In a multi-node Cisco Finesse deployment, run this CLI command on all the nodes of the cluster starting from the publisher. Restart all the nodes after executing the CLI command.