Where can breakpoints be placed in OutSystems?

In OutSystems, breakpoints can indeed be placed in both client-side and server-side actions. This capability allows developers to debug their applications effectively by pausing execution at specific points, enabling them to inspect variable values, evaluate logic flow, and understand how data is being manipulated at runtime.

When using breakpoints, developers have the flexibility to set these markers in various parts of their application, such as:

• Client-side actions: These include screen actions or client actions that execute on the user's browser. By placing breakpoints here, developers can monitor the behavior of the user interface and the front-end logic.

• Server-side actions: These are the actions that run on the server, handling data processing, business logic, or external integrations. Setting breakpoints in server-side logic allows developers to check data flow and logic execution without affecting the client interface.

This comprehensive debugging capability enhances the development process by allowing a thorough examination of both client and server interactions, which is essential when troubleshooting complex applications. Options that limit breakpoints to either client or server side do not reflect the full capabilities provided by the OutSystems platform. Thus, placing breakpoints only in actions—regardless of their location—provides the necessary flexibility for effective debugging.