What is special about the Requirement message type in OmniScript?

• A. It marks the element as optional
• B. It makes the element required and enforces error checking
• C. It triggers a warning banner
• D. It hides the element

Answer: (B)

The concept being tested is how validation works in OmniScript with the Requirement message type. Tagging a field with a Requirement makes it mandatory for the user to fill in. OmniScript then enforces error checking: if the user leaves that field empty, an inline error appears and you cannot proceed to the next step until a value is provided. It doesn’t make the field optional, it doesn’t trigger a separate warning banner, and it doesn’t hide the element. This behavior helps ensure essential data is collected before the flow continues.