What happens when an element is hidden in OmniScript?

What happens when an element is hidden in OmniScript?

• A. It is not shown to the user but still part of the script flow.
• B. It becomes editable but hidden from UI.
• C. It saves data in the database.
• D. It triggers a validation error.

Answer: (A)

Hidden fields in OmniScript are not shown to the user but still participate in the script flow. They exist in the script’s data model, can hold values produced or computed during the flow, and can be referenced for logic, mappings, or in Save steps. Because they’re hidden, there’s no UI for editing them. They don’t automatically persist to the database unless you map their values in a Save step, and being hidden doesn’t by itself trigger validation errors. So the key idea is that a hidden element remains part of the script’s data flow even though it isn’t visible in the UI.

Hidden fields in OmniScript are not shown to the user but still participate in the script flow. They exist in the script’s data model, can hold values produced or computed during the flow, and can be referenced for logic, mappings, or in Save steps. Because they’re hidden, there’s no UI for editing them. They don’t automatically persist to the database unless you map their values in a Save step, and being hidden doesn’t by itself trigger validation errors. So the key idea is that a hidden element remains part of the script’s data flow even though it isn’t visible in the UI.