When deploying rules and logic from your application, the process functions smoothly until an issue arises that requires debugging of the rules and logic.
The challenge with conventional rules engines is that debugging rules and logic inside of the application environment is not feasible. Typically, this requires running the application, attaching it to a debugger, and then diagnosing the rules and logic. This approach is not always practical or possible.
However, in the FlexRule authoring platform, it is possible because you can simply load your rules and logic and start debugging them line-by-line and do not need any extra attach application. It means the user can view the details of each logic during the execution and go through them one-by-one to see the individual result and the details of each rule. Debugging the model gives the flexibility to user to find the bugs in the model and inspect all the parameters and value in the execution context.
Book a Custom Demo
Advanced highlighter and Parameters window:
Highlighter shows you with a yellow highlight and a yellow arrow which steps you are debugging, and the green highlight shows the already satisfied conditions. There are arrows on the top toolbar that help the user move to other rules and logic and manage debugging. To see the debugging tutorial check this resource hub page.
And YES! You can start debugging your flow, right from the Designer. Also, the breakpoint is another feature you can use it during the debugging. Breakpoints mark where FlexRule Designer should pause your logic, allowing you to examine parameters and values.
Happy debugging rules and logic!
Last updated August 19th, 2024 at 11:53 am Published February 22nd, 2014 at 05:38 pm
