Workflow Trigger Reference for Saltbox Core Connector
Workflow Triggers initiate workflows and are used to define the data supplied to a workflow. Supported trigger Data Types for this connector are outlined below.
Basic details are shown in the table below.
Trigger Source | Description | Version |
---|---|---|
Event Workflow Trigger |
This triggers when the specified event occurs. ex: a route-based action. This is an alternative to scheduled Workflow Triggers. | 10.0+ |
Generate an Empty Message |
Generate a blank message. This trigger message source may be used to schedule a workflow that doesn’t require starter data. | 11.9+ |
Trigger Sources
Event Workflow Trigger
Trigger Source | Description | Version |
---|---|---|
Event Workflow Trigger |
This triggers when the specified event occurs. ex: a route-based action. This is an alternative to scheduled Workflow Triggers. | 10.0+ |
An event trigger enables a workflow to be triggered from other workflows, or to be triggered using Saltbox API Gateway.
-
Trigger an event-based workflow from other workflows using one of the actions
Route Message
orRoute Message Synchronously
. -
Trigger an event-based workflow from a third-party system synchronously using Saltbox API Gateway.
General setup
Basic setup for a workflow that uses an Event-based trigger is as follows.
Go to the Workflow Trigger section and define the following:
-
Connector: Saltbox Core Connector
-
Connection Config: (leave blank)
-
Source: Event Workflow Trigger
-
Source Settings
- ID Path: (leave blank or set the desired value)
-
Raw Message Contents
-
Message Format: Select the expected message format, such as XML.
-
other settings may be left as default
-
Once settings are configured, *Save the Workflow Trigger. Restart the project engine if it was already started.
Action-triggered example
After a trigger has been set up as described in the General setup section above, another workflow may use one of the actions Route Message
or Route Message Synchronously
to trigger this workflow.
Edit the second workflow that will route messages to the previously-configured workflow.
In the second workflow, open Workflow Designer, then edit or add a Route Message
or Route Message Synchronously
action to the workflow. Configure this action to point to the event-based workflow name that was set up in General setup section above.
For example, if a workflow called “My Event Workflow” has been configured as an event-based trigger, and another workflow called “Traffic Director Workflow” needs to send messages to that event workflow, a Route Message
action will be added to the “Traffic Director Workflow” designer page, and will contain the details outlined in the following links.
See Saltbox Core Connector Actions - Route Message or Saltbox Core Connector Actions - Route Message Synchronously for more action setup examples.
API Gateway example
See Setting Up Saltbox API Gateway for a tutorial on getting started with API Gateway.
Step 3.1: Workflow Trigger setup outlines how to set up this trigger to accept calls from Saltbox API Gateway.
Generate an Empty Message
Trigger Source | Description | Version |
---|---|---|
Generate an Empty Message |
Generate a blank message. This trigger message source may be used to schedule a workflow that doesn’t require starter data. | 11.9+ |