/mcpFor nonvoice tasks, dialog actions result only in Finesse reporting the state to CCE. The application is responsible for enforcing that state within the application. For example, if a user pauses an email dialog using the Dialog - Take Action on Participant API, the dialog state PAUSED is reported to CCE. However, if the application still displays the user interface to work on the email, the agent can continue to work on the email. The application must enforce the PAUSED state by preventing agent from working on the email in the user interface. Important Notifications Finesse sends a Dialogs/Media notification when information (or an action) changes for a nonvoice task to which the user belongs. If a nonvoice dialog operation results in an asynchronous error, the error is returned in a Dialogs/Media notification. The notification includes the error type, error code, and error constant. The ErrorMedia parameter indicates the Media RoutingDomain to which the error applies. For an interruptible Media Routing Domain configured to accept interrupts, Finesse sends only a Media state change when an agent is interrupted in that MRD. It does not send Dialogs/Media notifications with the action list modified to reflect the fact that actions not permitted on the tasks in that media. The state change is the only indication to the Finesse applications that no actions are allowed on the interrupted dialogs. Important Interactions with Customer Collaboration Platform Finesse connects to Customer Collaboration Platform in order to resubmit tasks into the system for these reasons: • The agent transfers a task. • A task RONAs while waiting to be accepted by an agent. Finesse automatically resubmits the task to Customer Collaboration Platform. • An agent signs out with tasks. The agent was configured to transfer tasks on logout. Finesse automatically resubmits the task to Customer Collaboration Platform. The original dialog is closed with an appropriate disposition code, and the task is resubmitted as a new task request. For automatic task resubmissions due to RONA and agent logout, the Finesse server on which the agent was last signed in initiates the request. User APIs for Nonvoice Tasks Most User APIs are restricted to voice media. Several of them, described here, can be used with nonvoice media. User- Get List of Dialogs APIs You can use User - Get List of Dialogs (Nonvoice Only) to get a list of only nonvoice dialogs for a user. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 187 Cisco Finesse Desktop APIs User APIs for Nonvoice Tasks