Idea Summary
When developers declare cross‑layer calls in APEX—such as JS calling PL/SQL Ajax processes, Dynamic Actions invoking server‑side code, or PL/SQL emitting client‑side scripts—there’s no quick way in the App Builder to locate the counterpart definition. This slows development and increases risk of errors.
Use Case
- JS invokes apex.server.process('MY_AJAX', …), but the corresponding Ajax Process is buried in the App Builder.
- A Dynamic Action executes PL/SQL code, but developers must manually find that server‑side process.
- PL/SQL can output JavaScript via htp.p('<script>…'), without navigation support to the JS logic.
Currently, developers must manually search across pages, dynamic actions, and shared components.
Preferred Solution (Optional)
Add clickable cross‑layer navigation in App Builder:
- JS → PL/SQL: recognize apex.server.process('NAME'), and display a link to the matching Ajax Process or PL/SQL block.
- Dynamic Action → PL/SQL: in “Execute Server‑side Code” actions, provide a “View PL/SQL” link opening the code block directly.
- PL/SQL → JS: detect htp.p('<script>…'), and support “Jump to client script” links.
UX Examples
- Hovering on apex.server.process('FETCH_DATA') shows “Go to Ajax Process: FETCH_DATA”—click to navigate.
- In Dynamic Action’s True action “Execute PL/SQL Code”, display an arrow icon that opens the PL/SQL editor.
- In a Process definition containing <script>…, include “View referenced JS” to jump to the client script.