Bizweaver provides a method to trigger a workflow from a Post Execute SQL stored procedure (for example SAP SBO_SP_PostTransactionNotice) in an SAP database (SQL or Hana). From the SAP stored proc, trigger instructions are inserted into a Bizweaver staging table and then immediately into a queue via a 'listener' (installed with Bizweaver) as a trigger request. Based on the target workflow's availability, the listener processes the request, triggering the workflow via the Bizweaver Commander.

All trigger set-up, management, and monitoring can be done via the Bizweaver user interface without the need to manually add or change SQL code in SAP.

Triggers are created from the workflow design window.

1. The workflow must be saved before the first trigger for the workflow can be saved
2. Select Trigger Set-up from the menu bar
3. In the trigger set-up fly-out panel complete these five required fields: Trigger Name, Connection, Procedure, Document, Action (one or more Actions may be selected)
4. Optionally add any parameters the trigger request will need to pass into the workflow. The parameter name is any user-defined variable in the Bizweaver workflow. The parameter value is any field name from the table underlying the selected source system (SAP) document.
5. Save the workflow

When the five required fields plus optional parameters are entered and the workflow is saved, Bizweaver:

1. Creates a staging table in the SAP database (connection assigned in the trigger setup)
2. Automatically inserts the SQL code that initiates the trigger into the SAP stored procedure.

The code inserted into the SAP stored procedure is surrounded by comments and is easy to identify by the trigger ID. It should not be tampered with. When the SAP stored procedure is called (ex. SAP SBO_SP_PostTransactionNotice), resulting from an action in SAP, a record is inserted into the staging table including the SAP document SQL table name and DocEntry value.

Example of the trigger SQL code that gets inserted into the SAP stored procedure:

The workflow is triggered by the listener, which performs these actions:

• Copies trigger records from the staging table in SAP (if the trigger is enabled in Bizweaver) to the request queue table in Bizweaver
• Clears trigger records (for both enabled and disabled triggers) from the staging table after enabled triggers are successfully copied to the request queue
• Checks the status of the workflow the queued trigger is targeting
• Triggers the workflow if it is available (not running)
• Goes to the next trigger request in the queue

The details of saved trigger set-ups can be viewed, and the triggers enabled/disabled or deleted as follows:

1. With the set-up information populated in the fields, in the upper right corner click the lightbulb to enable/disable, or the trashcan to delete the set-up. Saved triggers can be deleted this way too, but the deletion from the database will not happen until the workflow is saved.

1. Click View Workflow Triggers at the bottom of the trigger set-up panel
2. Or, select Triggers from the workflow window View menu
3. Click the lightbulb to enable/disable, or the trashcan to delete the trigger

1. Select Triggers from the Bizweaver main View menu
2. Click the lightbulb to enable/disable, or the trashcan to delete the trigger

More than one trigger can be configured for a workflow.

1. Select Trigger Set-up from the main menu
2. Click the + icon in the upper right corner of the set-up panel
3. Enter the set-up information for the trigger
4. Save the workflow

Saved and unsaved triggers (including those where the setup is incomplete) are available in memory while designing the workflow. These can be accessed via the … icon in the upper right corner of the trigger set-up panel. However, the workflow cannot be saved with incomplete trigger set-ups. Bizweaver will require incomplete set-ups to be completed or removed before the workflow can be saved.

1. Select Trigger Set-up from the main menu
2. Click the … icon in the upper right corner of the set-up panel
3. Click on any of the trigger set-ups listed in the floating (modeless) window. The trigger set-up will load in the trigger set-up panel
4. Make any changes

As of the 2.9.x release, saved triggers can not be modified. The trigger must be deleted via the user interface and a new one created.

A view to queued trigger requests is provided as a tab in the workflow and Bizwever main trigger listing windows.

When you can see trigger requests in the request queue window, they will reflect one these statuses:

• Pending (status code = 0)
• Sent (status code = 1)
• Cancelled (status code = 3)
• Completed (status code = 4)
• Error (status code = 4)

You have the ability to put a Hold (see the above screenshot) on processing queued requests. Clicking Hold allows trigger requests to queue but prevents them from triggering workflows until Resume is clicked.

The details of a queued trigger request can be accessed by clicking the … icon next to a request in the request listing.

In test mode, for triggers with parameters, the user will need to provide mock parameter values.

Upon running a test, a dialog is presented to select the saved trigger set-up (there could be more than one for a single workflow) and provide values for the configured parameters.