FireWorkflow Activity

Using the  FireWorkflow activity, a named workflow can be started. The activity interface is similar to the subflow activity, but the workflow fired is a separate event.

The FireWorkflow activity is different from the SpawnWorkflow activity because it does not iterate over records.

The FireWorkflow activity processes inputs, passes them to a new workflow, and then fires the workflow. The fired workflow runs as an independent workflow and does not return any output to the caller. The following are the main features of the FireWorkflow activity:

• Bypasses workflow selection business rule
• Supports in-memory workflow execution
• Does not support sequencing, that is, no registration order or registration keys
• Supports failover and restart
  Failover may generate duplicate events. Failover is handled as follows:

  • Before firing the FireWorkflow activity, an implicit checkpoint is added to ensure that the workflow is committed before the activity. For more information on the checkpoint workflow, refer to CheckpointWorkflow Activity.
  • The configuration property Save state before sending workflow message (com.tibco.cim.optimization.process.savebeforesend) is added in Configurator. If you set it to true, the workflow state that is created before sending the message is persisted to the database. Else, the workflow state is persisted before the workflow execution starts, based on the in-memory status of a workflow.
  • Failover marker is created before the workflow initiation and set it as completed.
  • On re-executing the workflow after failover.