Single-stepping through your code

Single-stepping is useful to determine whether the functions and actions within a rule are operating as intended. As you step through each line, you can see the actions that are returned as True (check mark) and False. (exclamation point).

If an action returns false, you can look in the batch log to see why the action returned false. (See Examining log files from the Test tab.)

Remember:

If all actions within a function return True, Datacap skips any remaining functions in the current rule.
If an action returns False, Datacap skips any remaining actions within that function and starts the next function (if there is one).

The Test tab provides UI controls (enabled with tooltips) for stepping through code:

UI control	Description
Step in	Steps into the next line of code. If the next line calls a rule or function, Step in opens the rule or function and halts inside it. If the next line is an action, Step in opens the action and you must click it again to close the action. For example, if a process is halted at a function, use this control to step into a function and start each of its actions.
Step/Step over	Starts the next line of code and any lower-level functions and actions, and then stops. If the next line is an action, Step over works like Step in and opens the action. For example, if a process is halted at a function, use this control to start the function, including all of its actions.
Step out	Steps through the next line of code. If the next line is a rule or function, Step out works like Step over and starts any lower-level functions and actions. If the next line is an action, Step out starts and closes the action.