McDewey

Gadgets subscribe to the finesse.containerservices.workflowActionEvent topic to receive workflow action events to run as a result of workflow evaluations. Third-party gadgets subscribing directly to the OpenAjax Hub for the Workflow Action Event topic might cause the Finesse Workflow Engine to lose its subscription and no longer be able to run workflow actions. Third party gadgets should instead implement something like the following: Note var _containerServices = finesse.containerservices.ContainerServices.init(); _containerServices.addHandler("finesse.containerservices.workflowActionEvent", function(data) { // Perform logic on "data", which is a WorkflowActionEvent object }); The published data is a JavaScript object with the following properties: { uri: string, name: string, type: string, params: [ { name: string, value: string, expandedValue: string } ], actionVariables: [ { name: string, node: string, type: string, testValue: string, actualValue: string } ] } Description Field In the uri, the id maps to the primary key of the WorkflowAction entry. uri The name of the workflow action. name The type of workflow action. Possible value is BROWSER_POP. type List of Param subobjects (see below). params List of ActionVariable subobjects (see below). There can be at most 5 Action Variable subobjects assigned to a workflow action. actionVariables The Param subobject uses the following fields: Description Field The name of the parameter. name The value of the parameter. value The value of the parameter with variables substituted with their values. expandedValue Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 401 Finesse Desktop Gadget Development Workflow Action Event