01. On Step 2 a Text element named contactEmail captures an address. A later Integration Procedure Action's Send JSON passes a parameter sourced from email, but the IP consistently receives a null for it even though the user typed a value.
What is the most likely cause?
a) The Text element lacks a required flag, so its value is not written.
b) The IP's invoke mode is Fire and Forget, so no value is passed.
c) The Send JSON maps a node path that does not match the element's actual data JSON node name.
d) A Conditional View hid the element, so it never captured a value.
02. After several records are updated, an Integration Procedure's own Preview returns the new values, but the OmniScript that calls it at runtime keeps showing the old values.
What is the most probable cause?
a) The OmniScript action's Response JSON Path is mapped to a node that no longer exists after the update
b) The OmniScript is running an older, still-active version of the script
c) The running user does not have field-level access to the updated fields
d) The Integration Procedure is returning a cached response, so the updated records are not re-read
03. Two FlexCards sit on the same page. When the user saves an edit on Card A through an Update action, Card B must re-query and display the new value.
How should the developer wire this behavior?
a) Card A fires an event when the Update action completes, and Card B listens for that event and reloads its data.
b) Card A's Update action is pointed directly at Card B so that the saved value is written straight into Card B's own separate data JSON.
c) Both cards are combined into a single state, so that saving on one re-renders the other.
d) Card B repeatedly polls Card A's data JSON on a timer and re-renders itself whenever it detects that a value there has changed.
04. Users keep seeing the old behavior of an OmniScript even though a developer edited it this morning and saved the changes on a new version.
What is the most likely cause?
a) Because edits are queued, OmniScript edits take effect only after the next Salesforce release
b) A saved OmniScript cannot be changed once it has first been activated
c) The component cache clears only when the browser is reinstalled
d) The new version was never activated, so the previously active version is still the one being served
05. An OmniScript step shows no data from its Integration Procedure Action. Running that same Integration Procedure in its own Preview with identical input returns the correct JSON.
What is the right next isolation step?
a) Inspect the OmniScript action's Response JSON Path, because the data returned but is not being mapped into the OmniScript data JSON
b) Re-run the Data Mapper Preview, because an empty step result must come from the underlying query returning no matching rows
c) Raise the Integration Procedure's cache duration, which does not isolate the fault, and retry the OmniScript
d) Open the browser network tab, because a blank step is always a failed client-side server call
06. Inside one FlexCard component, a summary view and a detail view are built as separate cards. A button must switch the user from the summary to the detail view in place — without leaving the page or opening an overlay.
Which action accomplishes this?
a) A Flyout action that opens the detail view as a modal overlay on top of the summary.
b) A Fire Event action published so that a separate listener card swaps the displayed view.
c) A Navigate action, which routes the user to the detail card's own record page.
d) A Card action, which flips to the detail card in place.
07. An Integration Procedure runs several server reads that do not depend on one another. The developer wants each read to start without the procedure waiting on the previous read response, while still using every read response later in the procedure.
Which invoke mode should the reads use?
a) Non-Blocking, so a read does not hold up the procedure yet its response remains available
b) Chainable, so each read can be called by another procedure
c) Default, so a read does not start until the previous one completes
d) Fire and Forget, so the reads all run without waiting and each of their responses is still returned
08. In an Integration Procedure, a Data Mapper Extract sits inside a Conditional Block. For the current input the block's condition evaluates to false. A later Set Values element reads a node that the Extract would have populated.
What is the result?
a) The Extract still runs anyway, because a Conditional Block only hides its output rather than skipping execution
b) A Loop Block, not the Conditional Block, supplies a default placeholder value for the skipped node
c) The Extract does not run, so its node is absent and the Set Values reads empty for it
d) The procedure stops with a fatal error because the expected node is missing
09. A field on a FlexCard is blank. Its value should come from an Integration Procedure that itself calls a Data Mapper. The developer wants the fastest way to find the layer where the JSON first becomes wrong.
Which approach isolates the failing layer most reliably?
a) Rebuild the FlexCard's merge fields and re-activate the card to refresh it
b) Open the browser network tab, read the raw server response, and work upward through each component until the blank field reappears
c) Run each layer's own preview from the bottom up (the Data Mapper Preview, then the Integration Procedure Debugger, then the FlexCard), stopping at the first layer whose output JSON is wrong
d) Clear the Integration Procedure's cache (its session, org, and platform layers), then reload the FlexCard in the app
10. In an OmniScript Preview, a field bound to a Data Mapper Extract Action response shows blank. The developer must determine whether the Data Mapper itself returns the value or the OmniScript drops it in the response mapping.
Which step best isolates the layer at fault?
a) Add a Set Errors action to surface the missing value.
b) Run the Data Mapper's own Preview with the same input.
c) Open the browser console to look for client-side script errors.
d) Re-activate the OmniScript in case a stale, inactive version is running.