Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Control Types • HANA SQL Tips • TWBS CC Web Order Import Integration Information • Versago Release Notes • Setup • Introduction (Decisions) • sap_business_one_integration_for_sql_server_databases
bw:decision_tool

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
bw:decision_tool [2019/01/02 07:03]
_deletedUser4_ [Using the “Else” Decision Rule] 		bw:decision_tool [2022/08/02 15:17] (current)
akoehler
Line 1: Line 1:
-====== Introduction ======+====== Introduction (Decisions) ======
  
-This document describes the use of the Bizweaver Decision tool +This page  describes the use of the Bizweaver Decision tool
- +
-====== Audience ====== +
- +
-This document is intended for developers of Bizweaver workflows. +
- +
-====== Related Documents ====== +
- +
-The following documents contain additional information that may be helpful with the development of Bizweaver workflows. +
- +
-  * Bizweaver – Application Introduction +
-  * Bizweaver – Looping Tool +
- +
-====== General Workflow Step Information ====== +
- +
-  - Each workflow step must have a unique **Name**. +
-    - The application will assign a default name, but we recommend that you change the name to something that helps you understand the purpose of the step as it is used in other steps. +
-    - The name cannot have spaces or special characters other than and underscore (_) +
-  - Enter an optional **Description** to provide any additional information that may be helpful to understanding the step. +
-  - Press <**F4**> to find and use values from previous workflow steps.+
  
 ====== Decision Tool ====== ====== Decision Tool ======
Line 32: Line 13:
 The initial workflow is very simple. A SQLCommand query step retrieves a list of Business Partners from the SAP Business One database. The decision(s) are within a loop since we want to evaluate each record individually. The initial workflow is very simple. A SQLCommand query step retrieves a list of Business Partners from the SAP Business One database. The decision(s) are within a loop since we want to evaluate each record individually.
  
-{{:bw:image1.png|}}+{{  :bw:image1.png  |  }}
  
 Three values are included in the query: Partner Code and Partner Type. Our decision will be based on Partner Type, which can be one of three values: C, S, or L. Three values are included in the query: Partner Code and Partner Type. Our decision will be based on Partner Type, which can be one of three values: C, S, or L.
Line 44: Line 25:
 In this first example we will be branching to the SLQCommand step if the Card Type value = ‘C’. In this first example we will be branching to the SLQCommand step if the Card Type value = ‘C’.
  
-  - Drag the tool to be executed for the “true” decision step into the design area and configure it as needed. \\ {{:bw:image2.png|}}+  - Drag the tool to be executed for the “true” decision step into the design area and configure it as needed. \\ {{  
 + :bw:image2.png  |  }}
   - Drag a Decision tool into the design area.   - Drag a Decision tool into the design area.
       - At this point you can either enter the evaluation rule or close the Decision.       - At this point you can either enter the evaluation rule or close the Decision.
           - In either case you will need to link the Decision to its preceding step. \\ {{:bw:image3.png}}           - In either case you will need to link the Decision to its preceding step. \\ {{:bw:image3.png}}
   - If the application has not already done so, connect the Decision to the appropriate output step.   - If the application has not already done so, connect the Decision to the appropriate output step.
-  - Open the Decision tool and configure the evaluation expression that will lead to the output step. \\ {{:bw:image4.png}} \\ Be sure to pick the appropriate data Type for the value being evaluated.  \\ \\ The evaluation expression can be viewed in the “Branching Details” window of the Decision. This will also show you where the branch will go if the evaluation is true.\\ {{:bw:image5.png?}}+  - Open the Decision tool and configure the evaluation expression that will lead to the output step. \\ {{  
 + :bw:image4.png  }} \\ Be sure to pick the appropriate data Type for the value being evaluated.  \\ \\ The evaluation expression can be viewed in the “Branching Details” window of the Decision. This will also show you where the branch will go if the evaluation is true.\\ {{  :bw:image5.png?  }}
   - Drag a “Merge” tool into the design area.   - Drag a “Merge” tool into the design area.
   - Connect the Decision output step to the Merge tool.   - Connect the Decision output step to the Merge tool.
-  - Connect the Merge tool to the subsequent step in the workflow. \\ {{:bw:image6.png?}}+  - Connect the Merge tool to the subsequent step in the workflow. \\ {{  :bw:image6.png?  }}
  
 ===== Using the “Else” Decision Rule ===== ===== Using the “Else” Decision Rule =====
Line 60: Line 43:
 However, if you want a false evaluation to go to a specific step, an ELSE evaluation must be used. In this next example we want the flow to move to the “SQLCommand_getOtherName” step. Therefore, we have an explicit ELSE step to point the workflow in that direction. However, if you want a false evaluation to go to a specific step, an ELSE evaluation must be used. In this next example we want the flow to move to the “SQLCommand_getOtherName” step. Therefore, we have an explicit ELSE step to point the workflow in that direction.
  
-{{:bw:image7.png}}+{{  :bw:image7.png  }}
  
-{{:bw:image8.png}}+{{  :bw:image8.png  }}
  
 ===== “No Match” Situations ===== ===== “No Match” Situations =====
Line 72: Line 55:
 The previous examples illustrate a single evaluation criterion. In some cases, however, the evaluation may need to be more complex. In the following (simple) example we are reading a list of all the SAP Business One Business Partners. We then want to take an action if 1) it is a customer (CardType = ‘C’) and 2) their current A/R balance is greater or equal to 50,000. The evaluation will look like this: The previous examples illustrate a single evaluation criterion. In some cases, however, the evaluation may need to be more complex. In the following (simple) example we are reading a list of all the SAP Business One Business Partners. We then want to take an action if 1) it is a customer (CardType = ‘C’) and 2) their current A/R balance is greater or equal to 50,000. The evaluation will look like this:
  
-{{:media/image9.png?384x118}}+{{  :bw:image9.png  }}
  
   - **AND** and **OR** relationships are supported.   - **AND** and **OR** relationships are supported.
Line 79: Line 62:
   - When using a combination of AND and OR relations, the OR relationships are considered together.   - When using a combination of AND and OR relations, the OR relationships are considered together.
   - It may be necessary to try different combinations of AND and OR to obtain the desired result.   - It may be necessary to try different combinations of AND and OR to obtain the desired result.
 +
 +====== Decisions Variables ======
 +
 +^ Name           ^ Description          ^
 +| StepMessage         | During a failure the reason for failure will be populated here|
 +| StepStatus         | True or False        |
  
bw/decision_tool.1546430603.txt.gz · Last modified: 2019/01/02 07:03 by _deletedUser4_

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki