McDewey

When the wrap-up timer expires, the user transitions to NOT_READY state. WORK_READY state applies only to Unified CCE deployments. A user transitions to WORK_READY state for the following reasons: • The user was in READY state before taking a call. • The user set a state of READY while in TALKING state. When the wrap-up timer expires, the user transitions to READY state. The following statements apply to a supervisor using this API to change the state of an agent or other supervisor: • A supervisor can only change the state of a user who is assigned to that supervisor's team. • A supervisor can only set the state of another user to NOT_READY, READY, or LOGOUT. • A supervisor can set the state of a user to LOGOUT only if that user is in READY, NOT_READY, RESERVED, RESERVED_OUTBOUND, RESERVED_OUTBOUND_PREVIEW, TALKING, HOLD, WORK, or WORK_READY state. • A supervisor can set the state of a user to NOT_READY only if that user is in READY, WORK, or WORK_READY state. • When a supervisor uses this API to set the state of a user to NOT_READY, a reason code must not be used. If a reason code is provided, Finesse rejects it and returns a 400 Invalid Input error. Finesse sends a hard-coded reason code to indicate that the state change was performed by the supervisor. Note https://<FQDN>/finesse/api/User/<id> URI: https://finesse1.xyz.com/finesse/api/User/1234 Example URI: Agents can only act on their own User objects. Supervisors can act on the User objects of agents who belong to their team. Security Constraints: PUT HTTP Method: Application/XML Content Type: XML Input/Output Format: <User> <state>READY</state> </User> HTTP Request: id (required): The ID of the user state (required): The new state the user wants to be in (for example, LOGOUT, READY, NOT_READY) Request Parameters: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 47 Cisco Finesse Desktop APIs User—Change Agent State