Custom decisions are built as stored procedures. They use similar logic to the GOTO function covered in the Scripting section of the on line help but if the stored procedure is written to return wither a true or a false then the step number is not required and users can use decision steps to manage the step flow.  They are covered in detail on the Custom Decision Scripting forms

 

When the user clicks on the New button in the Decision window and selects Custom Decision, the following form appears. In order to select a custom decision, simply click on the drop down and select the name of an existing standard decision.

 

There is no need to define a Message for this decision since the decision will not return any error messages.

 

Selecting a Custom Decision

 

It is possible to build the stored procedure without referring to any previously scanned steps however, if values from previous steps are required (as is generally the case) it is strongly recommended to pass the step values to the stored procedures as parameters rather than finding the data manually.

 

Step Mapping

Once the parameters are mapped to the steps the decision defined for that step is shown in the grid. Only one decision is supported per step. The result of the decision is either True or False. The Decision Step configuration uses this information to sequence the user through the steps