Once connected, the breakpoints defined within microflows will automatically trigger the events that are trapped by Mendix Studio Pro. After triggering, the debugging tool within Mendix Studio and Mendix Studio Pro allows you to step through each microflow action, one action at a time, viewing the changing variables along the route.
For more information about how to use the built-in debugging functionality, see How to Debug Microflows in the Mendix Studio Pro How-to’s.
Developers can debug any deployed instance of a Mendix app running either locally, on premises, or in the cloud. Mendix Studio Pro’s built-in debugging tools allow it to connect to and authenticate with an app environment using the app instance’s URL and the credentials provided from within the Mendix Developer Portal.
A microflow can be extended with custom Java actions. To make sure these can also be debugged, the Mendix Runtime and Mendix Service Console have been integrated into Eclipse. If you run into an error in any of the Java actions, you can easily debug them utilizing Eclipse’s debugger.
When you start the debugger in Eclipse, the full Mendix application is started, and Mendix Studio Pro console logs all the relevant logging information. This makes the debugging experience seamless and fully integrated.
For further information, see How to Debug Java Actions Remotely in the Mendix Studio Pro How-to’s.