#

# LogiView

## How to Test a Decision Table

| ### What to do:
| As a prerequisite for this example, you must have added the decision table DocuDT as described in "How to add functions and commands". Additionally, you should create a trace file and enable the Debug Mode ("How to Definie Default Values").
| ### Syntax Check
| When saving entries, the syntax of used commands/functions is checked. Additionally, the program evaluates if a variable or procedure definition conflicts with previously assigned decision tables exists. In case of an error the error message detailing the type of error is displayed in the message bar. Additionally, a selection menu is opened where the user can choose to either correct the error OR keep the command / procedure as is (e.g. in case of a variable definition).
| Once the decision table is created, you may test run it.
| ### Test run of a decision table
| Switch to the Logic Models/Procedures form.
| Use the search function to display the DocuProcedure.
| Click the button Processing.
| In addition to program output (e.g. from 'put' commands) program information is displayed in the message bar after the execution. In this example, this is the line: "Decision table / procedure "DokuVerbund/Doku/Prozedur" completed successfully." In case of an error, an error message is displayed.
| Additionally, a trace file will be available after the run-time execution of a decision table. This file can be used to check the results of functions and commands.
| ### Trace File
| In order to run the trace file, call up the Trace Log function in the Manager > Macro > LogiView > Trace protocol menu.