13.2.4 Debugging Dynamic Actions

Learn how to debug dynamic actions in APEX.

Parent topic: Managing Dynamic Actions

13.2.4.1 About Debugging Dynamic Actions

Learn about debugging dynamic actions.

Debugging dynamic actions in APEX is slightly different than other debugging, because much of the processing done with the dynamic action framework is done on the client, not on the server. To debug dynamic actions, APEX outputs debug information to the browser's JavaScript console if your browser supports it (for example Firefox with Firebug installed shows the debug information in its Console pane). The debug information tells you when an action of a dynamic action fires, along with some additional information about the dynamic action, in the following format:

Dynamic Action Fired: [Dynamic Action name] ([Action name]) {JavaScript object containing all Dynamic Action information}

This format enables you to identify the dynamic action name, the action name which indicates which action is triggered, and the JavaScript object which contains a lot of information about the dynamic action, including the when element, the affected elements, the event object, and any data that may be associated with the dynamic action.

Parent topic: Debugging Dynamic Actions

13.2.4.2 Debugging Dynamic Actions

Debug an dynamic action by viewing the page in runtime and clicking Debug on the Developer toolbar.

To debug a dynamic action:

  1. Ensure the application containing the dynamic action has Debugging enabled. See Utilizing Debug Mode.
  2. Run the page containing the dynamic action.
  3. Open the browser's JavaScript console.
  4. From the Developer toolbar, find Debug.
  5. On the Developer toolbar, click Debug, Enable Debug. Use Enable Debug to specify the level of detail included when you click View Debug .

    Options include:

    • No Debug - Enables and disables Debug mode

    • Info (default) - The debug log contains the default or normal amount of information. This corresponds with a log level of 4 and a Debug URL argument of YES.

    • App Trace - The debug log contains messages up to level 6. This corresponds with a Debug URL argument of LEVEL6.

    • Full Trace - The log will contain the maximum amount of information. This corresponds with a Debug URL argument of LEVEL9. Full Trace can slow request processing but provides the most amount of detail.

    Since debug information is only output when running in Debug mode, leaving Debug mode switched on enables you to further test if dynamic actions are firing when you expect them to. For example if you have defined a dynamic action that fires when a certain item's value changes, change that item's value and the console shows the debug output if the dynamic action fires.

  6. On Developer toolbar, click Debug, View Debug.

    Clicking View Debug refreshes the page. If you have any dynamic actions that are set to fire on page load, you will see the debug output in the browser console.

Parent topic: Debugging Dynamic Actions