What makes an OmniScript unique?

What makes an OmniScript unique?

• A. Name and Version
• B. Type, Subtype, and Language
• C. Data Structure only
• D. User Roles

Answer: (B)

An OmniScript is uniquely identified by the combination of its Type, Subtype, and Language. Type sets the broad kind of script, Subtype specifies the particular variant or scenario, and Language provides localization. Together they create distinct assets even when the underlying workflow is similar, allowing multiple language variants or scenario tweaks to exist side by side without confusion. Name and Version describe or manage the asset but don’t guarantee global uniqueness—two scripts can share a name or have the same version number in different contexts. Data Structure explains how the steps are organized, but it doesn’t distinguish identity across language or variant. User Roles control who can access the script, not what specific script it is.

An OmniScript is uniquely identified by the combination of its Type, Subtype, and Language. Type sets the broad kind of script, Subtype specifies the particular variant or scenario, and Language provides localization. Together they create distinct assets even when the underlying workflow is similar, allowing multiple language variants or scenario tweaks to exist side by side without confusion. Name and Version describe or manage the asset but don’t guarantee global uniqueness—two scripts can share a name or have the same version number in different contexts. Data Structure explains how the steps are organized, but it doesn’t distinguish identity across language or variant. User Roles control who can access the script, not what specific script it is.