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:
-
You are not permitted to edit VI-Key comments in the source code or to delete them because they label each code block and are needed for backing up scripts in the database.
-
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.
Example:
$FK(UID_Person).IsExternal:Bool$ is converted into GetTriggerValue("FK(UID_Person).IsExternal").Bool when it is loaded
-
In the Designer, you can use the Script Editor to create scripts. Enter the name of the script in the Script Editor and a skeleton script body. This you can export to the script library where you can edit the script with the System Debugger.
-
In the Designer, you can created templates, formatting scripts, methods, and table scripts. You can edit these elements with the System Debugger after you have exported them to the system library.
Related topics
Use database query and object action logging in the System Debugger to look for errors and optimize scripts during development. The processing time and the command that was run are logged.
Table 142: Functions for logging database queries and object actions
|
|
Starts recording. |
|
|
Stops recording. |
|
|
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.
Detailed information about this topic
To test a script
-
In the System Debugger, select the desired script in Scripts view.
-
Enter value for the script parameters as required.
-
Check the options for running the script.
-
Run in debug mode: Jumps into the source code. This allows you to use all Visual Studio debugging options.
-
Define base data: The Base and Value variables of the script base class can be pre-allocated as input parameters to be used in the script.
Example:
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 run within a transaction with subsequent rollback or whether the script is run immediately against the database.
-
Select Start.
The script starts running. After the script has run, the result and the processing time of the script is displayed.
TIP: To find scripts more easily, you can use the following functions in the Scripts view.
-
In the Find script field, enter the string to filter on.
-
Modified scripts are marked with a * in the System Debugger.
-
To find all modified scripts, click 
and apply the Changed scripts menu item.
Related topics
