Live OmniScript data, structure and remote action calls, in a Chrome DevTools panel.
Debugging an OmniScript is not a friendly experience. The data is in there somewhere,
the remote actions happen out of sight, and a Data Mapper can fail while the response
comes back as a cheerful HTTP 200. This adds a DevTools tab that just shows it.
What it does
Data — the live payload as a collapsible tree, highlighting what changed as you click through the script.
Structure — every element the script is built from, with its current value, required and conditional markers, and visibility rules as readable expressions.
Remote actions — every Apex call the page makes, with Data Mappers and Integration Procedures named by bundle or key, batched calls split apart, and errors flagged even inside a successful response.