What is the purpose of the {Data} object in OmniScript testing?

• A. To log script events
• B. To store user credentials
• C. To configure integration endpoints
• D. To view JSON data in the OmniScript Designer

Answer: (D)

In testing OmniScript, the Data object represents the current runtime JSON payload that drives the script, so you can inspect exactly what data is flowing through as the script executes. This lets you see input values, how mappings transform data, and what the script outputs at each step, helping you verify that fields are read correctly and that conditional logic or loops produce the expected results. It’s a debugging aid that shows the real data structure the OmniScript is working with. The other options aren’t what the Data object is for: logging script events happens through logs or event tracing, storing credentials is a security concern handled elsewhere, and configuring integration endpoints is about connections and endpoints—not about viewing the data as it moves through the script. Viewing JSON data in the OmniScript Designer is exactly what the Data object provides, making it easier to validate data shape and content during tests.