Siebel Business Process Designer Administration Guide for Financial Services > Designing Workflow Processes > Working with Stop Steps >

Defining a Stop Step

It is recommended that the Stop step be used only in Workflow Processes invoked from a script.

To define a stop step

  1. Make the appropriate process active by selecting it in the All Processes view.
  2. Navigate to the Process Designer view and double-click the Stop icon to access the details view.
  3. NOTE:  To add a Stop step to the workspace, drag and drop the Stop icon from the palette to the workspace.

  4. Enter a name for the step.
  5. Enter a description of the purpose of the step.
  6. Select an error code.
  7. NOTE:  To define a custom error message, select an error code starting with WF_ERR_CUSTOM. The error message displayed will be %1. To define the text of the custom error message, enter an input parameter with the name %1, and then enter the text of the message in the value field for input arguments.

  8. If you need to define input arguments for this step, continue to Defining Stop Step Input Arguments.

Defining Stop Step Input Arguments

NOTE:  No picklist is available for Input Argument Name. The input arguments for a Stop step are the substitution variables in the error message. Substitution variables are identified by a "%". To define the substitution value, enter the substitution variable in the input argument name, such as "%1".

To define input arguments for a stop step

  1. With the appropriate name displayed in the Stop applet of the Stop view and the Input Arguments applet active, choose Edit > Add New Record.
  2. Enter a name for the input argument.
  3. This should be the substitution variable appearing in the error message.

  4. Choose an input argument type. The choices available are:
  5. If the input argument type selected is Literal, enter a value.
  6. If the input argument type is Process Property, select a property name and a property data type.
  7. If the input argument type is Business Component, select the applicable business component name and business component field.
  8. If the input argument type is Expression, enter the expression in the value field.
  9. Enter any appropriate comments.

 Siebel Business Process Designer Administration Guide for Financial Services 
 Published: 22 May 2003