Why Action Flow Debugging?
Studio enables you to add a set of tasks and actions that can be used on the happening of an event. There would be times when you have a host of actions and then when designing your app you feel the need to investigate where you are missing a step or what could be causing the error or a deviation from the expected results. We have thus introduced the Action Flow Debugging feature which enables you to add breakpoints and even conduct a step-by-step analysis of the action blocks.
Where is Action Flow Debugging?
The Action Flow Debugging is available in the Preview mode of your app. Whenever you take a preview to test your app, you can see the Bug Icon in the right-hand corner of the screen.
How do you use the Action Flow Debugging feature?
Once you have designed your app, you would be taking a preview to ensure that the app is working as expected. So now if you go to the Preview you will notice a BUG icon on the right-hand side of the screen.
Click the Bug to start debugging. It opens the Action Flow Listing. Select the Screen you wish to investigate. Here note that the different action events added to the screen are listed out.
You can mark the breakpoint for the action events of the respective button that you want to investigate. Simply click to add the breakpoint. A red mark appears against them indicating the breakpoint added.
The debugger starts when you click the action button and the task starts executing. You can see that the different tasks in the Action flow are listed out. While debugging you can manage the breakpoints and execute them all together or step by step as per your investigation needs.
The Debugger is basically distributed into four sections; Action Blocks, Input, and Output and Watchlist.
The Action block lists out all the tasks or Action blocks in the action event. If you want to investigate the specific task for the output and the values returned you can add breakpoints to the specific action in that action block as well.
The Input Section displays the input provided during execution. You can see the Input Parameters, Executes When and the Environments it is allowed to execute.
Depending upon the action block you would have some output. In this example the value is the RowID being returned hence the output block shows output data accordingly. It will vary depending upon each action. In case there is no output data or value returned, but the action is completed successfully without errors, the Output block displays this message as seen below.
Watchlist allows you to add a control or variable to keep track or watch on its values
Simple click + (add) to add the items from the list of variables and controls.
After you have added the breakpoints in the Action flows of any of your apps, they would persist even during the next time you take a preview or run the app. So you need not have to go through the same process over and over again.
The Action Flow Debugging is a very easy and handy method to investigate and debug your apps to make them error-free and functioning as expected. In case you have any thoughts, suggestions, or feedback? We’d love to hear from you. Head to our forum to share in our Suggestions Section.