Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| 2000_concepts:0800_data_processing:0400_rule_debugger [2026/08/13 00:53] – ↷ Page moved from docs:2000_concepts:0800_data_processing:0400_rule_debugger to 2000_concepts:0800_data_processing:0400_rule_debugger localdev | 2000_concepts:0800_data_processing:0400_rule_debugger [2026/08/13 03:43] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Rule Debugger ====== | ====== Rule Debugger ====== | ||
| - | If your business rules do not perform as expected you may need to use special tools to find out what’s wrong. One of such tools is the [[docs:2000_concepts: | + | If your business rules do not perform as expected you may need to use special tools to find out what’s wrong. One of such tools is the [[2000_concepts: |
| In the AwareIM Rule Debugger you can set breakpoints on business rules wherever those rules are used - for example, rules of a process, rules of a business object, notification and so on. Whenever AwareIM executes these rules the system will stop and show you the current Context, the stack and the log up to this point. You can set breakpoints not only on rules but on actions of the rules. | In the AwareIM Rule Debugger you can set breakpoints on business rules wherever those rules are used - for example, rules of a process, rules of a business object, notification and so on. Whenever AwareIM executes these rules the system will stop and show you the current Context, the stack and the log up to this point. You can set breakpoints not only on rules but on actions of the rules. | ||
| - | {{page>docs: | + | {{page>: |