/mcpFinesse Notifications in Third-Party Containers Strict requirements must be followed to leverage the Finesse Desktop notification framework on a third-party container. 1. Clients must add a specific Finesse gadget, which establishes the XMPP connection and publishes notifications to Finesse-specific OpenAjax topics 2. Third-party containers (that is, those other than the Finesse Desktop) must provide support for the OpenSocial Core Gadget Specification 1.1 to ensure that gadgets can subscribe to Finesse-specific notifications through the OpenAjax Hub. Finesse Topics A gadget that is within the Finesse environment has the ability to subscribe or publish to a set of Finesse Desktop topics via OpenAjax Hub. The following sections provide details for the available topics. Connection Information finesse.info.connection Topic Name Gadgets subscribe to this topic. Topic Type Gadgets subscribe to the finesse.info.connection topic to receive status information about the XMPP connection, which is automatically established by the Finesse Desktop or a Finesse Desktop gadget (within a non-Finesse container). Connection status information can be used to determine the state of the connection so that a gadget can act appropriately. Additionally, a resource ID is provided in the published data to allow the gadget to construct a subscribe request to the Finesse Web Services. Connection information is published every time there is a connection state change. The published data is a JavaScript object with the following properties: { status: string, resourceID: string } The status parameter describes the XMPP connection status. It can have any one of the following values: • connected • connecting • disconnected • disconnecting • reconnecting • unloading Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 396 Finesse Desktop Gadget Development Finesse Notifications in Third-Party Containers