/mcptype: "UnsubscribeNodeReq", data: { node: "/finesse/api/Team/{id}/Users", subid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" }, invokeID: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxy" } The node parameter specifies the node to subscribe to. The subid parameter specifies the subscription to remove, which is uniquely identified by the invokeID that was used in the subscribe request. The invokeID parameter is self-generated and is used as part of the OpenAjax topic to which the response of the request is published. Finesse Responses finesse.info.responses.{invokeID} Topic Name Gadgets subscribe to this topic. Topic Type Responses to requests are published to these channels. When a request is made, the gadget generates and specifies a unique invokeID as part of the request. This invokeID is used as the trailing token in the topic to which the response of the request is published. Because this topic is only used to communicate the response of a single request and never used again, be sure to unsubscribe from the topic as part of the callback handler in the subscribe request. For example: // Generate invokeID and construct request var UUID = _util.generateUUID(), data = { type: "ExampleReq", data: {}, invokeID: UUID }, // Subscribe to the response channel to ensure we don't miss the response OAAsubid = gadgets.Hub.subscribe("finesse.info.responses."+ UUID, function (topic, data) { // Unsubscribe from the response topic to prevent memory leaks // Do this before processing the response in case the processing throws an exception gadgets.Hub.unsubscribe(OAAsubid); // Process the response here }); // Publish the request after we have registered our response callback on the response topic gadgets.Hub.publish("finesse.info.requests", data); Workflow Action Event finesse.containerservices.workflowActionEvent Topic Name Gadgets subscribe to this topic. Topic Type Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 400 Finesse Desktop Gadget Development Finesse Responses