Debugging BPMs

Debugging a BPM

1. Log in to the application designer by referring to Logging In to the Application Designer.
2. In the navigation pane, choose BPMs.
3. Move the cursor to of the corresponding BPM, and choose Edit.
4. To simulate BPM interactions, click to run the BPM from the design page.

   After the simulation, verify the the results to ensure they align with your expectation.

5. Click Tracer in the upper right corner of the design page.
6. On the log tracer page, view details about each step in the BPM, for example, check whether variables are transferred as expected.
   Figure 1 Log tracer
   

   The log tracer page is divided into two sections: a search box and a log tracing table.

   • Search box
     Figure 2 Search box
     
     • BPM switchover: allows you to filter BPMs by start time. The tracing information is stored for 30 minutes.
     • Search box: allows you to search BPMs using the tracing information.
     • Download button: allows you to download and save the complete logs as a file to your local PC.
   • Table: records BPM process logs with timestamps, module types and names, element types and names, and operation descriptions. During subprocess execution, the module reflects the subprocess details.

7. If the result does not meet your expectation, return to the BPM and repeat 4.

Common Errors

• Incorrect variables

  Verify input parameter types match definitions and convert types if needed.

• Incorrect variable structures

  Ensure input parameter structures (such as attribute name or value type) match the target. For extensive JSON errors, use JSON viewers or formatters to compare.

• Unspecified branches and unexpected termination

  Ensure a default branch is set in exclusive gateways to prevent process termination when all conditions are unmet. The process ends implicitly when no next steps are defined.