After loading the system library, you can edit scripts, templates, formatting scripts, methods and table scripts in the System Debugger and test them.
Note the following:
When templates and formatting scripts are loaded, the $ notation is converted into a GetTriggerValue method call. All GetTriggerValue methods calls are converted into $ notation when the changes are saved in the database.
$FK(UID_Person).IsExternal:Bool$ is converted into GetTriggerValue("FK(UID_Person).IsExternal").Bool when it is loaded
Use database query and object action logging in the System Debugger to look for errors and optimize scripts during development. The execution time and the command that was run are logged.
Open the log dialog box by selecting View | SQL protocol.
Open the log dialog box by selecting View | Object log.
|Copies logged data to the clipboard.|
|Save logged data in a file.|
|Deletes the logged data.|
The System Debugger gives you the opportunity to test scripts, templates, formatting rules, methods and table scripts. Visual Studio debug and edit options are available to you.
To test a script
|Run in debug mode||Jumps into the source code. This allows you to use all Visual Studio debugging options.|
|Define base data||The variables Base and Value of the script base class can be preallocated as input parameters to be used in the script.
Base is initialized with a DB object key in order to use base.GetValue("column name").String.
|Transaction with rollback||Use this option to specify whether the script is executed within a transaction with subsequent rollback or whether the script is executed immediately against the database.|
The script starts executing. After the script has executed, the result and the execution time of the script is displayed.