Skip to main content
Skip table of contents

Debugging Rules in AppBase Studio

AppBase developers dedicate a substantial amount of time to crafting and debugging rules. Recognizing the critical role of rule development in application success, AppBase 7.1 R3 introduces a significant overhaul of the rule debugger, designed to elevate user comfort and quality.

This latest iteration boasts a meticulously redesigned user interface optimized for clarity and efficiency. Intuitive navigation and streamlined workflows empower developers to delve deeper into rule logic more easily, fostering a more productive and enjoyable debugging experience.

Furthermore, AppBase 7.1 R3 introduces many functional enhancements to the rule debugger, further augmenting its capabilities. These advancements include:

  • Enhanced breakpoints: Developers now benefit from more granular control over rule execution, enabling them to set breakpoints at specific points within a rule, facilitating pinpoint debugging.
  • Improved variable inspection: A redesigned variable inspector provides a comprehensive and readily digestible view of rule variables, allowing developers to analyze their values and identify potential issues effortlessly.
  • Streamlined logging: Enhanced logging functionality offers developers a more detailed and insightful view of rule execution, providing valuable context and facilitating the identification of subtle bugs.
  • Expanded documentation: Comprehensive documentation provides developers with readily available resources to explore the full potential of the revamped rule debugger, maximizing its efficiency and effectiveness.


This procedure explains how to debug a business rule manually.

  1. Navigate to Business Rules → Rules to open the rules window.
  2. Click the Debug button next to the name of the rule. The debugger will open in a separate tab.

  3. The debugger is divided into three areas:
    1. Rule parameters
    2. Rule code
    3. Rule results

  4. Provide the parameters needed to execute the rule and click the Run button.
  5. The result will be shown in the bottom pane, Rule Result.
  6. You can make modifications to the code (body) and click the Save body button to update the rule.
  7. In some scenarios, you must clear the cache before running the rule for testing by clicking the Save body & Clear Cache button.
  8. Click the Go Back button when done to close the debug tab.

There can be only one instance of the rule debugger for each rule. If you try to reopen a debugger rule, the previously opened debugger becomes active.

New Functionalities

Save body & Run button: The rule’s body is saved, and then the rule is executed automatically.

Rule code formatting: Format the rule code (automatic indent). Click the brackets icon ({}) at the bottom.

Rule result formatting: Manually format the rule results in JSON. Click the brackets icon ({}) at the bottom.

Rule execution logs: If the AppBase is configured and enabled to save logs to the ELK stack, the rule debugger shows the logs of the rule's execution.

IMPORTANT Meaning that the logs are indexed with a delay.

Log filtering: The following switches are used to filter logs.



Show Critical logs

Show Error logs

Show Warning logs

Show Information logs

Show Debug logs

Show Trace logs

Show log records with normalized rule body only. All other filtering parameters will be ignored

Show the log of the current run only

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.