McDewey

To prevent reporting problems, define your reason codes consistently on both Finesse and the platform (Unified CCE or Unified CCX). For example, if you create a not ready reason code in Finesse with a code of 413 and a label of “Meeting”, but create a not ready reason code in Unified CCE with a code of 413 and a description of “Lunch Break”, the Unified CCE report shows “Lunch Break” for any agent who selects that code. For more information about predefined reason codes for Unified CCE, see the Cisco Unified Contact Center Enterprise Reporting User Guide (http://www.cisco.com/en/US/products/sw/custcosw/ps1844/products_user_ guide_list.html). For more information about predefined reason codes for Unified CCX, see the Cisco Unified Contact Center Express CTI Protocol Developer Guide. System reason codes are defined by Unified CCE and Unified CCX. These reason codes are used by Finesse but not listed in the ReasonCode APIs. Note The ReasonCode object is structured as follows: <ReasonCode> <uri>/finesse/api/ReasonCode/{id}</uri> <category>NOT_READY|LOGOUT</category> <code></code> <label></label> <forAll>true|false</forAll> <systemCode>true|false</systemCode> </ReasonCode> ReasonCode APIs ReasonCode—Get The following GET APIs allow an administrator or an agent to get a copy of the ReasonCode object. https://<FQDN>/finesse/api/ReasonCode/<id> URI: https://finesse1.xyz.com/finesse/api/ReasonCode/45 Example URI: Administrators and agents can use this API. Security Constraints: GET HTTP Method: — Content Type: XML Input/Output Format: — HTTP Request: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 237 Cisco Finesse Configuration APIs ReasonCode APIs