Debugging Best Practices

Question 1

Where are the outputs from gs.debug(), gs.print(), gs.info(), and gs.log()?

Answer 1

These can be found in the Debug Log

System Diagnostics > Session Debug > Debug Log

Question 2

Which debug outputs are available in all scopes and which are not available in scoped applications?

Answer 2

gs. print() and gs.log() are not available in scoped applications
gs. debug() and gs.info work in all environments

Question 3

What does “Debug Business Rule” do?

Answer 3

System Diagnostics > Debug Business Rule displays messages about business rules. These messages indicate which business rules are being run and when they are started (==>), finished (<==), or skipped (===). If a business rule is skipped, the failed condition is displayed.

Question 4

What does Debug Security Rules do?

Answer 4

System Security > Debug Security Rules places a debug icon on each field of a form. Point to the icon to see if there are any debug messages for the associated element. Click the icon to expand details about read and write access. This module is very helpful when you are using ACLs to control access to records and fields. The debug security rules have enhanced functionality, allowing you to view a context parameter.

Question 5

When you activate a server-side debugging module, it remains active until one of the following occurs:

Answer 5

• You activate the Stop Debugging module, located in System Security.
• You log out from the instance.
• The session expires (for example, the session times out).
• You close the browser.