In Decisions 3.5 Unit Test utility is separated from the Debugger. User is able to Test Flow/Rule and see if it is executing correctly in the Debugger or create Unit Tests to apply custom Rules to the...
This document demonstrates advanced techniques of using Unit Test utility in Decisions Designer. To start with Unit Test utility please go through Unit Tests Overview (Simple Flow) document first. This...
Flows can span multiple systems, such as POP, IMAP, Application Servers, and Database Servers, and may or may not involve an end user. A flow can run an approval process, check or send email, handle an incident, or turn on a server. To ensure the flow runs without errors and has no performance issues, debugging is highly recommended throughout the development stages.
When debugging a flow, it is sometimes useful to create debugging steps, which can provide information about or gather data from a certain step in the flow before the flow has finished running. Debugging steps can record information in system logs, output the current step's flow data, output a message, or output a string.
The Flow Debugger is the platform's environment for testing and debugging flows before putting them into production. When testing, it may be necessary to temporarily halt the flow's progress so that data can be analyzed mid-flow.
Exception handling is the process of responding to the occurrence, during computation, of exceptions – anomalous or exceptional events requiring special processing – often changing the normal flow of program execution.