/mcpConnectionReq Sending a "ConnectionReq" forces the Finesse Desktop to attempt to establish a XMPP connection with the Notification Service. This request can only go through if either no active connection currently exists or if the current connection is in the "disconnected" state. The gadget should publish the following object to the topic finesse.info.requests: { type: "ConnectionReq", data: { id: ID, password: password, xmppDomain: xmppDomain }, } The id and password parameters specify the ID and password of the XMPP user for which to establish an XMPP connection. The xmppDomain parameter specifies the domain of the XMPP server. SubscribeNodeReq Sending a "SubscribeNodeReq" request causes the managed XMPP connection to send an XEP-0060 standard subscribe request (described in About Cisco Finesse Notifications) to subscribe to the notification feed for the specified node. The response to this request is published on the response topic finesse.info.responses.{invokeID}, where the invokeID must be generated by the gadget to identify this unique request and subscription. For more details, see Finesse Responses. The Cisco gadgets use an RFC1422v4-compliant universally unique identifier (UUID) for this invokeID. To guarantee that the gadget receives the response, it must subscribe to the response topic (on the OpenAjax Hub) of its self-generated invokeID before sending the following object to the topic finesse.info.requests: { type: "SubscribeNodeReq", data: { node: "/finesse/api/Team/{id}/Users" // the node of interest }, invokeID: "xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx" } The node parameter specifies the node to subscribe to. The invokeID parameter is self-generated and is used to track this particular subscription. This parameter is also used as part of the OpenAjax topic to which the response of the request is published. UnsubscribeNodeReq Sending an "UnsubscribeNodeReq" request causes the managed XMPP connection to send an XEP-0060 standard unsubscribe request (described in section 7.1 About Cisco Finesse Notifications) to unsubscribe from the specified node. The response of this request is published on the response topic finesse.info.responses.{invokeID}, where the invokeID must be generated by the gadget to identify this unique request. For more details, see Finesse Responses. The Cisco gadgets use an RFC1422v4-compliant UUID for this invokeID. For more details, see the Finesse SDK. To guarantee that the gadget receives the response, it must subscribe to the response topic (on the OpenAjax Hub) of its self-generated invokeID before sending the following object to the topic finesse.info.requests: { Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 399 Finesse Desktop Gadget Development ConnectionReq