Skip to main content

Developing an Application

 

OutSystems

Debugging Producer Modules

When you are debugging a producer Module the debugger will not stop in any breakpoints set in the consumer Module unless you also start a debug session in the consumer Module.

The procedure for debbugging producer Modules differs depending on the type of exposed Actions:

Public Client Actions or public Server Actions

Pre-requisites

Your consumer Module must fulfill the following conditions:

  • It must be a consumer of a Client or Server Action from the producer Module by referencing it.
  • The reference to the producer Module is up-to-date.
  • You have permissions to publish the consumer Module.

How to debug the producer Module

To debug the functionality being exposed in a public Action by the producer Module, follow these steps:

  1. Open the producer Module and set the entry Module for debugging to be the consumer Module. You can set the entry Module in the Debugger pane or in the Debugger menu, by choosing the "Select Entry Module..." option.

    Note: If the desired consumer is not in the list, check the pre-requisites listed above.

  2. Place breakpoints where you want the execution to stop. The execution will only stop on breakpoints of the producer Module.

  3. Start the debugger in the producer Module. If the producer Module is part of a mobile app, the consumer Module will automatically be opened; if it's part of a web application, you can open the consumer Module in a browser.

  4. Interact with the application to execute the functionality that calls the producer logic where the breakpoints are set.

Service Actions

Unlike public Server Actions, Service Actions run in the context of the producer Module; to debug a Service Action, follow these steps:

  1. Open the producer Module and set the Entry Module to (this module).

    You can set the entry Module in the Debugger pane or in the Debugger menu, by choosing the "Select Entry Module..." option.

  2. Place breakpoints where you want the execution to stop. The execution will only stop on breakpoints of the producer Module.

  3. Start the debugger on the producer Module.

  • Was this article helpful?