The Element Name property must be unique within the OmniScript and any included reusable OmniScripts.

The Element Name property must be unique within the OmniScript and any included reusable OmniScripts.

• A. It is displayed only in administration screens
• B. It must be unique within the OmniScript and included reusable OmniScripts
• C. It is displayed during runtime
• D. It must not include non-ASCII characters

Answer: (B)

The Element Name acts as the unique identifier the runtime uses to reference that element in bindings, data references, and actions across the OmniScript and any included reusable OmniScripts. When you combine scripts, every element needs to be distinctly addressable; if two elements shared the same name, the runtime wouldn’t know which one to resolve, leading to binding conflicts or incorrect data flow. Therefore, ensuring the Element Name is unique across the entire OmniScript and any reused components is essential. The other options don’t capture this behavior—the name isn’t just about display in admin screens or runtime visibility, and while there may be character rules, the critical requirement is uniqueness across the composed scripts.

The Element Name acts as the unique identifier the runtime uses to reference that element in bindings, data references, and actions across the OmniScript and any included reusable OmniScripts. When you combine scripts, every element needs to be distinctly addressable; if two elements shared the same name, the runtime wouldn’t know which one to resolve, leading to binding conflicts or incorrect data flow. Therefore, ensuring the Element Name is unique across the entire OmniScript and any reused components is essential. The other options don’t capture this behavior—the name isn’t just about display in admin screens or runtime visibility, and while there may be character rules, the critical requirement is uniqueness across the composed scripts.