Push Destinations

“Pushed” distribution of work items is supported. In a pushed distribution model, when a work item is generated, it is sent to a user as an email. The email contains the URL of the work item, which the user can click to open and process the work item.

Generally, work items are “pulled” when a user logs into the BPM application and accesses their work list — this “pulls”, from the TIBCO server, the work items that were sent to that user.

Users do not need to login to the BPM application to access a pushed work item, though they are required to authenticate themselves before they can open the work item.

A pushed distribution is useful for occasional users — for example, managers who only need to become involved in a process when some form of higher level approval is required. These users will typically not be logged into the BPM application all the time and so could otherwise miss the arrival of high-priority work items.

Note: If you use the presentation channel settings (push destinations) to deliver notification of work items via email, on the Work Resource tab for the user task, you must set the Distribution Strategy to Allocate to One rather than Offer to All. For example, if you have a performer field set to: resource(name='tibco-admin'), tibco-admin will receive an email notification of a work item only if the Distribution Strategy is Allocate to One.

Push destinations can be specified for:

  • Organizational entities - These specify the destination(s) to which work items sent to the organizational entity are to be pushed. You can specify one or more push destinations for each organizational entity. For information, see Editing Organizational Entity Push Destinations.
  • Resources - These specify the destination(s) to which work items that are sent directly to the resource are to be pushed. You can specify one or more push destinations for each resource. For information, see Editing Resource Push Destinations.