Was this helpful?
Start Step
Start is the first step in every process. Each process is required to have one, and only one, Start step. The Start step is added for you when you create the new process, but you have the option of changing any property of the step except its name.
Start Step Properties
Click and select the Start step to open the Step Properties tab. Specify the following step properties.
Name
Description
Name
Displays the step name. By default, it is Start and you cannot change this name.
Description
(Optional) Description for the step.
Enabled
Enables the step for execution. You cannot disable this step.
Error Handling
Select either of the following:
Stop Process - (Default) All the steps after the current step are skipped or the entire process is stopped (depending on how you have the error logging options set) if this step stops due to an error.
Ignore Error - The remaining steps in this process are executed even if this step stops due to an error. This is useful when you want to write a Decision step that can test for the error state of a previous step.
Note:  The Break after first error Logging Option on the Configuration tab overrides the Ignore Error option in the step level, hence when you set the Ignore Error option at step level, you should uncheck (disable) the Break after first error Logging option for the Ignore Error to be effective.
Script
Click Browse and select that script file that contains the expression that must be evaluated before the process begins. Alternatively, type the expression in the Expression box.
Expression
In the Expression box, type the expression that must be evaluated before the process begins.
Note:  You can also double-click the Start step or click Open. The EZscript Expressions window is displayed where you can type the expression.
Note:  You can specify an Expression or Script but not both.
To run an expression at the beginning of a process, add it to the Start step. This is useful in the following scenarios:
When you are setting a message object.
When you are using a function, such as FileWrite, to write to a message object.
Last modified date: 07/26/2024