Does an OmniScript name need to be unique?

Does an OmniScript name need to be unique?

• A. No, it doesn't need to be unique.
• B. Yes, it must be unique.
• C. Only the first and last name must be unique.
• D. Uniqueness is determined by environment.

Answer: (A)

The key point is that the Name you assign to an OmniScript is a human-readable label, not a unique identifier used by the system. You can have more than one OmniScript share the same display name because each asset is distinguished by its internal ID and its location in the project, not by that label alone. When the platform runs or references an OmniScript, it relies on the asset’s unique identity behind the scenes, not the visible name you see in the designer. So, it’s not required to have a unique name, which is why the best choice is that the name doesn’t need to be unique. The other options don’t fit because the system doesn’t enforce global uniqueness for the OmniScript label, and uniqueness isn’t determined by environment.

The key point is that the Name you assign to an OmniScript is a human-readable label, not a unique identifier used by the system. You can have more than one OmniScript share the same display name because each asset is distinguished by its internal ID and its location in the project, not by that label alone. When the platform runs or references an OmniScript, it relies on the asset’s unique identity behind the scenes, not the visible name you see in the designer.

So, it’s not required to have a unique name, which is why the best choice is that the name doesn’t need to be unique. The other options don’t fit because the system doesn’t enforce global uniqueness for the OmniScript label, and uniqueness isn’t determined by environment.