Role required: admin.

To debug a script, you can use a built-in debugger. 

We recommend debugging only on the system instances intended for developing and testing business solutions, where there is no sensitive data, to avoid its loss or corruption.

You can use the try... catch blocks for script debugging.

Before debugging, pay attention to the methods:

  • *.insert(),
  • *.update(),
  • *.updateMultiple(),
  • *.delete(),
  • *deleteMultiple() 

Escape these methods or remove them to prevent data corruption or loss.

Open any record form in this debugger by calling the Open in script item in the hamburger menu.

With this functionality, you can:

  • locate breakpoints within the script body.
  • comment some strings to skip one or more operations.
  • display the object value before inserting or updating.
  • display the variable value when executing.

It is recommended to use SimpleSystem methods to display values when debugging a server-side script:

  1. To display them on a client-side:
    1. ss.addInfoMessage(message)
    2. ss.addErrorMessage(message)
  2. To put them into the Main Log (sys_log) dictionary, which is intended as the main log storage:
    1. ss.info(message)
    2. ss.warning(message)
    3. ss.debug(message)
    4. ss.error(message)

Another way to open the debugger is the following:

  1. Navigate to System Definition → Server Scripts.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to save the script, or click Run to execute it without saving.

But use this way only on the instances that have no sensetive data.