About Gadget Development

When developing a gadget that uses the Web Client API, it must run in the context of the Openspace session, call the action (passing any parameters that are required) and, if required, support managed events.

  • At runtime, the deployed gadget runs in the context of the current Openspace session and hence no separate login is required to invoke the BPM services. However, you must provide the service URL of the BPM node where you want to call the service. However, you only need to provide this once, as the service URL can be used again.
  • Call the action, passing any parameters that are required. For a complete list of actions and parameters, see Web Client API Service.
  • If you want your gadget to support the publishing of managed events, you must enable managed events, see Enabling Managed Events.

For a summary of all the public services provided by TIBCO Openspace, and links to detailed documentation generated from the individual APIs, see Web Client API Service.