McDewey

<Update> <event>put</event> <source>/finesse/api/Team/1004</source> <requestId>xxxxxxxxx</requestId> <data> <team> <uri>/finesse/api/Team/1004</uri> <id>1004</id> <name>Shiny</name> <users> <User> <uri>/finesse/api/User/1234</uri> <loginId>1004</loginId> <firstName>Charles</firstName> <lastName>Norrad</lastName> <pendingState></pendingState> <state>LOGOUT</state> <stateChangeTime>2012-03-01T17:58:21.123Z</stateChangeTime> </User> <User> <uri>/finesse/api/User/9876</uri> <loginId>9876</loginId> <firstName>Jack</firstName> <lastName>Brown</lastName> <state>NOT_READY</state> <stateChangeTime>2012-03-01T17:58:21.134Z</stateChangeTime> <ReasonCode> <uri>/finesse/api/ReasonCode/1</uri> <code>10</code> <label>Team Meeting</label> <category>NOT_READY</category> <id>1</id> </ReasonCode> </User> ... other users ... </users> </team> </data> </Update> Sample Notification Payload: • Agent name is changed for an agent who belongs to the team • Agent state is changed for an agent who belongs to the team Notification Triggers: Queue Notifications Finesse sends a queue notification every 10 seconds (if queue statistics change). Finesse sends notifications for this node only for a stand-alone Finesse deployment with Unified CCE. Notifications for this node are not sent for a coresident Finesse deployment with Unified CCX. Note XML Format: /finesse/api/Queue/{id} Node: /finesse/api/Queue/{id} Source: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 361 Cisco Finesse Notifications Queue Notifications