Differences

This shows you the differences between two versions of the page.

--- bw2:bizweaver_trigger [2023/04/11 11:15]
mfoster [Executing Workflows from SQL Using Direct Connection (Trigger)]
+++ bw2:bizweaver_trigger [2024/09/09 13:27] (current)
dlee [Executing Workflows from SQL Using Direct Connection (Trigger)]
@@ Line 1: / Line 1: @@
-======Executing Workflows from SQL Using Direct Connection (Trigger)======
+======Called from SAP Business One (Trigger)======
 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.
@@ Line 16: / Line 16: @@
 </WRAP>
 <WRAP center round important 80%>
-Once a Bizweaver user-defined variable has been assigned and saved as part of a trigger, it can not be deleted. To delete or change the variable (using the variable tool), the trigger must first be deleted.
+Once a Bizweaver user-defined variable has been assigned and saved as part of a trigger, it can not be deleted. To delete or change the variable (using the variable tool), the trigger must first be deleted. Triggers are very disposable. Deletion simply removes the code for that trigger from the SAP proc and it's very easy to add a new trigger.
 </WRAP>
 {{:bw2:add_trigger_2.png?800|}}
+{{ :bw2:triggers.mp4 |}}
 === What's going on behind the scenes when a trigger is created? ===
 When the five required fields plus optional parameters are entered and the workflow is saved, Bizweaver:
-  - Creates a staging table in the SAP database (connection defined in the trigger setup)
+  - Creates a staging table in the SAP database (connection assigned in the trigger setup)
   - Automatically inserts the SQL code that initiates the trigger into the SAP stored procedure.
 <WRAP center round info 80%>Bizweaver creates only one staging table per SAP database.</WRAP>
-This code 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, then if the SAP document and action match those in the trigger SQL code, a record is inserted into the staging table. If trigger parameters were configured, then the values for those are also inserted with the record in the staging table. The parameter values are obtained from the SAP document SQL table using the SAP DocEntry key passed into the stored procedure by SAP.
+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.
 <WRAP center round important 80%>Do not tamper with the SQL code Bizweaver inserts into the SAP post-execute stored procs</WRAP>
@@ Line 42: / Line 43: @@
   * 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)
+  * Triggers the workflow if it is available (not running), fetching parameters values for SAP using the SAP document table name and DocEntry value
   * Goes to the next trigger request in the queue

Wiki

User Tools

Site Tools

Differences

Page Tools