You use this function to verify the variables up to a particular action. A breakpoint, which is assigned to an action, stops the transaction after the action's input links are executed but before the action is executed.
For more information, see Transaction Debugging.
If an action has a breakpoint, it is displayed as an icon in the action block. If you rename an action, the associated breakpoint becomes an orphan.
You can create the following types of breakpoints:
Always
Suspends the transaction's execution.
Disabled
Does not suspend the transaction.
On True
If the expression is true, suspends the transaction.
On Change
If the expression value changes, the breakpoint activates.
The system does not run breakpoints for a secondary transaction that is called by the main transaction that you are running. The system only processes the breakpoints for the primary transaction.
Breakpoints are user-specific; therefore, another user cannot see your breakpoints.
You cannot export a transaction with its breakpoints.
To add a breakpoint to an action, click the action with your secondary mouse button, and choose Create Breakpoint.