What determines the JSON structure of an OmniScript aside from header data?

What determines the JSON structure of an OmniScript aside from header data?

• A. The structure of the OmniScript elements
• B. Data sources used
• C. The OmniScript version
• D. The user permissions

Answer: (A)

The shape of the non-header JSON in an OmniScript comes from how the script is built—the arrangement and types of the OmniScript elements themselves define the data structure that gets produced. Each element contributes a piece of the output: screen fields map to properties, decisions and flows determine nesting, and data actions or DataRaptor mappings shape how data is grouped or nested (for example, lists become arrays, sub-flows become nested objects). In short, the script’s element tree and their data mappings establish the payload layout. Data sources influence what data is available or retrieved, and permissions can affect what data can be seen, but they don’t define the overall skeleton of the JSON output. The version may add features, but the fundamental structure still follows the element arrangement and mappings.

The shape of the non-header JSON in an OmniScript comes from how the script is built—the arrangement and types of the OmniScript elements themselves define the data structure that gets produced. Each element contributes a piece of the output: screen fields map to properties, decisions and flows determine nesting, and data actions or DataRaptor mappings shape how data is grouped or nested (for example, lists become arrays, sub-flows become nested objects). In short, the script’s element tree and their data mappings establish the payload layout.

Data sources influence what data is available or retrieved, and permissions can affect what data can be seen, but they don’t define the overall skeleton of the JSON output. The version may add features, but the fundamental structure still follows the element arrangement and mappings.