Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:2000_concepts:0800_data_processing:0400_rule_debugger [2022/08/21 12:09] – ↷ Page moved from start:2000_concepts:0800_data_processing:0400_rule_debugger to docs:2000_concepts:0800_data_processing:0400_rule_debugger administrator | docs:2000_concepts:0800_data_processing:0400_rule_debugger [2025/06/12 03:58] (current) – Change to AwareIM aware_support3 | ||
|---|---|---|---|
| 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 [[HelpUsingExecutionLog|Rule Log]] that shows in detail what is going on in the system. Another tool that can be extremely useful is the Rule Debugger. The Rule Debugger is very similar to debuggers used to debug code, written in some programming language. The idea is that you can set one or more “breakpoints” on the lines of your code and the system “stops” when execution reaches the breakpoint. At this point you can inspect the data – local and global variables and so on. You can then continue one line at a time and see how your lines of code get executed. | + | 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: |
| - | In the Aware IM 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 | + | In the AwareIM |
| - | {{page>start: | + | {{page>docs: |