Best practice for a dynamic progress tracker (chevrons) on a record form (Classic UI)?

mandysander — Sun, 01 Mar 2026 03:32:32 GMT

I’m trying to replace a set of static chevrons on a record form with a dynamic progress tracker in the classic form UI (not Workspace).

What I need

A visual, chevron‑style progress indicator rendered directly on the record form.
Each step should show one of several statuses (Action Needed, Waiting/Pending, Complete for Now, Complete, Not Applicable).
Status is driven primarily by phrases in a field on the record (e.g., a “Sign‑Off Status” string generated by server logic), not just by the record state.

What I’ve tried

Formatter UI Macro
- Plain HTML renders fine.
- Client‑side scripts (<script>, GlideAjax, etc.) are unreliable or stripped.
- Jelly (<j:script>, <j:jelly>) consistently fails at runtime with
  “The prefix ‘j’ for element ‘j:script’ is not bound”, even though the macro saves.
UI Pages
- Work when accessed directly.
- Fail or render blank when embedded via iframe on a form (likely scope / ACL / rendering context issues).
GlideAjax + Script Includes
- Server‑side evaluator logic exists and works.
- Getting the results reliably into a formatter without hitting XML/Jelly issues has been the blocker.

The roadblocks

Formatter macros seem limited to HTML with no reliable server or client scripting.
Jelly works in some contexts but not consistently in formatter macros.
UI Pages introduce iframe and scope complications.

My question

Is there a recommended or simpler pattern for building a dynamic, multi‑step progress tracker on a classic form?
Am I fighting the platform by trying to do this in a formatter, and should this be done another way (UI Builder, Workspace, related list override, etc.)?
Are there known limitations or best practices for dynamic visual components like this on classic forms?

Any guidance on the right architectural approach (even if it means rethinking where/how this renders) would be hugely appreciated.

And yes, Microsoft Copilot wrote this question for me. I've been trying to use it and our internal version of chat GPT to help, but I feel like I'm going in circles.

Re: Best practice for a dynamic progress tracker (chevrons) on a record form (Classic UI)?

mandysander — Tue, 03 Mar 2026 19:00:43 GMT

For posterity...

What worked reliably on classic forms was a Formatter UI Macro that renders only HTML/CSS, with all logic done server‑side in a Script Include. The script include evaluates record fields and returns a simple JSON model of steps and statuses, which the macro renders via <g2:evaluate>. We avoided client scripts, Jelly tags, and UI Pages entirely, as they did nothing but cause problems. Treating classic formatters as server‑rendered, declarative UI only turned out to be the stable pattern.

question Best practice for a dynamic progress tracker (chevrons) on a record form (Classic UI)? in App Engine forum

Best practice for a dynamic progress tracker (chevrons) on a record form (Classic UI)?

Re: Best practice for a dynamic progress tracker (chevrons) on a record form (Classic UI)?