Skip to Main Content
Feature Request FR-3887
Product Area Developer Experience

4 Voters

Debug Levels for Dynamic Actions

christian.hasslbauer Public
· Jul 5 2024

Idea Summary
APEX client side debugging consists of evaluating the browser console log, where all executed Dynamic Actions create entries.

Complex pages with lots of Dynamic Actions get increasingly complex to debug. This can be made worse by the Global Page if it contains lots of standard functionality, which is of no interest while debugging individual page functionality. This can lead to a point where activating the standard debug level initates a deluge of mostly irrelevant log entries.

Linking Dynamic Actions to different debug levels would solve this problem.

Use Case
Applications with a great amount of standard functionality as Dynamic Actions in Global Pages could be made easier to debug on the client side by giving these Dynamic Actions  a higher debug level, like Application or Engine level. Dynamic Actions in complex pages could temporarily be changed to higher debug levels in order to exclude simple or looped functionality from logging.

Preferred Solution (Optional)
Dynamic Actions, maybe Actions also, get a new attribute that specifies the debug level necessary to create a browser console log. Info level (4) should probably be the standard value.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is unlikely to make its way into APEX.



  • vincent morneau Admin OP 13 days ago

    Hi Christian,

    I definitely see the value of this idea. However simple filters in the browser console might be sufficient to identify the relevant logs, and having a new attribute at the dynamic action level might be overkill for most use cases.

    When debugging something very specific, you can also consider adding breakpoints in your code, or adding your own console.log and turning off APEX debug if that's too much noise.