Contact Us 1-800-596-4880
  1. Homepage
  2. Automation Workshop (1.0.0)

  3. Lab 3: Implementation - Debug your process

Lab 3: Implementation - Debug your process

Prerequisites

Before starting

If you have not completed the previous Module/Lab then you should import the solution into your RPA Builder to ensure that you begin this Lab from the right place.

Yes, I want to import the previous Lab solution

No, I managed to finish it. Let’s start with this Lab!

Importing previous Lab solution

You should have the Google Drive link sent to you along with the credentials and other workshop material. This drive contains the solution for all Labs. If you do not have access, ask the instructor.

  1. From the Windows box, download the Module_2_Lab_2_completed.crpa file referred to the solution of the previous Lab.

  2. Open RPA Builder and open the project you want to overwrite with the Lab solution. Make sure you open YOUR project not to overwrite other’s.

    module01 lab03 001

  3. Once opened, click the Import Project option under the File menu:

    module01 lab03 002

  4. Click Yes in the confirmation dialog, locate your just downloaded .crpa file and click Open to import it.

You can now continue with the Lab.

Step 1: Testing options for an Automation Process

When you develop an Automation process where you will be executing multiple steps and following multiple flows, it is critical to have a clear view of what’s going on during the development phase.

MuleSoft RPA offers a number of capabilities or best practices for this purpose:

  • Use the Message Box step that can be used to display variable values or other helpful information during the execution of an activity.

  • Test an indivual activity by using the Run Workflow button of such activity:

    module2 lab06 001

  • Run the whole process with the Run Process button located on the process canvas:

    module2 lab06 002

  • Check the execution log for a run activity

    module2 lab06 004

  • Debug (with breakpoints) an activity

    module2 lab06 003

On this Lab, we will cover the debug capabilities.

Step 2: Set a breakpoint

When you plan to debug an activity, you have the option to set one or multiple breakpoints in any of the activity’s steps.

To do so, simple right click on any activity and use the Set Breakpoint option.

For this Lab purpose, we will use the Check Email process activity.

  1. In RPA Builder double click the Check Email activity to open its properties & steps

  2. Right click on the, i.e., Reset newMailAvailable step and select the Set Breakpoint option:

    module2 lab06 005

  3. Once you set a breakpoint on an activity, the breakpoint mark is set to easily identify the breakpoint’ed steps:

    module2 lab06 006

  4. You can easily remove a breakpoint on a step by clicking on the Delete Breakpoint option.

    module2 lab06 007

    Do not remove the breakpoint as we will be using it in the next step!

Step 3: Debug a process

  1. With the activity opened (and with at least one breakpoint set in any of its steps), simply click the Debug Workflow button:

    module2 lab06 008

  2. RPA Builder will be minimized as when we run the activity or process. But the Workflow Debugger is displayed on this ocasion.

    The Workflow Debugger window will show the steps hierarchy on the left, marks such steps with a breakpoint (with the breakpoint mark) and a pointer showing the execution step where the debugger is stopped.

    module2 lab06 009

    Please, note that the debugger stops AFTER the activity has been executed.

    On the right hand side, information about the executed step is displayed such as: status of the execution, variable old and new values (if applies), timestamp, etc:

    module2 lab06 010

  3. While the execution is stopped, you have different options available:

    module2 lab06 011

    From left to right:

    • Repeat the already executed step

    • Edit the step configuration (such edit will only be applied for the debug session) and repeat the step

    • Continue the process (the execution will continue until the next breakpoint or until the end)

    • Single step: execute the next step and pause the execution

    • Stop the execution of the process

    Regardless of the result of the last step executed, you can change such it (OK or Error) using the Runstate dropdown menu:

module2 lab06 012

  1. Keep pressing the Single step button to debug the rest of the steps. Pay attention to the result of each of the steps.

Take me to the TOP