Follow the steps below to use the Procedure Debugger to debug a procedure.
Note: Procedure Debugger will save the Target User, Watch List, and Break Points from the previous Debugging session.
Navigate to Settings > Applications > App Designer > Procedures, then select the Debugger:
Search for a Target User who will encounter and cause the procedure to execute.
Select the User
Select the procedure(s) you want to debug. The workspace updates to reflect the procedure selected.
Check the code block(s) to apply a break point.
Repeat step 5 for any other code block that you want to add a break point.
Note: You must apply a breakpoint to the block of code that contains the variable you want to add to the Watch List.
Select a block that has a break point to add a variable to the watch list
Select the search area and a list of relevant parameters and variables appears. Select one and click Add
.png?sv=2022-11-02&spr=https&st=2026-03-10T14%3A32%3A45Z&se=2026-03-10T14%3A43%3A45Z&sr=c&sp=r&sig=5YVGsXwhVQdFy9Ofaghjk5mjUXG1xcR7iTrqtuCZ6fo%3D)
.
Repeat steps 7 & 8 to add variables to the Watch List for any other code block that has a break point.
Click Start. The Debugger remains in this loading state until the procedure is triggered in eCASE
Notes:
Wait 15 seconds before you trigger the event/procedure
You only have one minute to trigger the event/procedure before the debugger stops collecting data.
Log-in to home as the user selected in step 3 and fulfill the requirements for the procedure to be executed. Make sure you leave the Procedure Debugger open and running in another window or tab.
12.Once you have triggered the procedure navigate back to the Procedure Debugger to see the execution paused at the break point with the value of the variable listed.
Click Continue to move to the next breakpoint or complete the execution of the code.
Note: You have one minute to Continue the execution of the code or the Debugger will stop and eCASE will resume the execution of the code.
Once the code has finished executing and there is no more break points the page will continue loading for another minute looking for other procedures to execute, then the Procedure Debugger will stop.
