Get started in five minutes

Open the panel, pick the script, turn Mask values on, learn what the three tabs are for and where the help is.

You have an OmniScript running in a Salesforce page, or open in a Designer preview, and you want to see what it holds and what it calls. This takes about five minutes.

Open the panel

1. Open Chrome DevTools on the page: F12, or Option+Cmd+I on a Mac.
2. Pick the {=} OmniScript tab, next to Elements and Console. If you cannot see it, it may be behind the » overflow at the end of the tab row.
3. If the page was already loading, reload it with DevTools open. The panel only reads the page while DevTools is open, so calls made during page load are missed otherwise.
4. In the top bar, pick your script from the list. If the panel says "No OmniScript found on this page", open a page that runs an OmniScript (or a Designer preview), let it load, and press Rescan. See Top bar and Rescan.

Turn on Mask values

Before you copy, save or export anything from a real org, tick Mask values in the top bar. Strings and numbers become placeholders in everything that leaves the panel; keys and structure stay. It is off every time DevTools opens, unless Mask values at start is ticked in Settings. See Mask values and Mask values at start.

Learn the three tabs

1. Data shows what the script holds right now, as a tree, updating while you click through it. Type in the filter box to find a key or a value. Tick Track changes to see what each step changes. See Data, Start here.
2. Structure lists every element of the script, joined to the live data. Click an element to read its value, properties, show rule and calls. Follow current step keeps the step the script is on selected. See Structure, Start here.
3. Calls lists the Data Mapper, Integration Procedure and Apex calls the page makes, with their input, options and output. A failed call is red and opens on its reason. See Calls, Start here.

Drag a tab to put the tabs in another order. See Tab order.

Find the help

1. Press ? in the top bar for the help. Every control has an entry, and the filter box at the top narrows them by words.
2. Right-click a button or switch, or press ? while it has focus, to open the entry for that control. See Help for a control.
3. The gear opens Settings, where the debug tools are too. See Settings.

A first question to try

Pick a field on your page and ask one of these:

• Why is this field hidden?
• Why can't I press Next?
• Why did this call fail, and what did it send?

A short tour of each tab appears the first time you open it. Turn the tours off from any card, or see them again from the end of Start here. See Tour.

Every control is described in the reference. More guides.