McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 364

↗ View in doc context
page
364
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::348

<Update> <event>put</event> <source>/finesse/api/User/csmith</source> <data> <User> <dialogs>/finesse/api/User/1001001/Dialogs</dialogs> <extension></extension> <firstName>AGENT</firstName> <lastName>1001001</lastName> <loginId>1001001</loginId> <loginName>agent1</loginName> <pendingState></pendingState> <reasonCodeId>2</reasonCodeId> <ReasonCode> <uri>/finesse/api/ReasonCode/{id}</uri> <code>10</code> <label>Team Meeting</label> </ReasonCode> <settings> <wrapUpOnIncoming>OPTIONAL</wrapUpOnIncoming> <wrapUpOnOutgoing>REQUIRED</wrapUpOnOutgoing> </settings> <roles> <role>Agent</role> </roles> <state>LOGOUT</state> <stateChangeTime></stateChangeTime> <teamId>5000</teamId> <teamName>FunctionalAgents</teamName> <uri>/finesse/api/User/1001001</uri> </User> </data> </Update> Sample Notification Payload: • Addition of a user Addition of a user • Deletion of a user • State change • First or last name change • Role change • Pending state change Notification Triggers: Dialog Notification Finesse sends a Dialog notification when information (or an action) changes for a call to which the user belongs or when the user adds or removes a dialog. For the purpose of notifications, the fromAddress and toAddress parameters of the Dialog object are defined as follows: • fromAddress: The extension of the caller who initiated the original call. If an unmonitored caller placed the call, the fromAddress is the unmonitored caller's extension. If an agent placed the call, the fromAddress is the agent's extension. For an Outbound Option Dialer call, the fromAddress is the extension of the Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 348 Cisco Finesse Notifications Dialog Notification