Scopes

Scopes is an existing asset. It can be an Application, Project, Asset, or another defined context.

Create a new Scope

On the Home window, select Scopes to display a list of existing Scopes. Select a scope. For example, EPTScope.

This displays the Name contexts and Protection Strings for the scope.

Name contexts are a collection of rule sets and/or naming rules. It is a namespace to ensure that allocated names in a given set are unique.

Protective Strings are a Scope safeguard to ensure that name allocation requests are valid for their scope before they are processed. They serve as security keys for name allocation requests.

Note:
If one or more protection string is set, then a Name allocation request must provide a protection string for a scope. If not, it results in an unsuccessful name allocation.
It is not mandatory to define a protection string. If a protection is not defined then a request header can be omitted or an empty string value used as a replacement to ensure a successful response.

To create a new scope, select + Add. This displays a New scope window. Type the scope name and description.

For a new Name Context, select + Add to display the New name context window. Select Save.

This creates a new Name context.

Note: Protection strings are autogenerated.

Enhanced uniqueness check

In New name context form, the Prevent Duplicate Names option enables you to generate unique names within the same Name context.

This option enforces stricter control over name allocation, ensuring that no duplicate Fully qualified names (allocated name combined with invisible name part values) exist within the same name context. It guarantees that two Fully qualified names in the same context will always be unique, irrespective of their types or the naming rules applied.

Note:
The Prevent duplicate name is checked only during the creation of the name context and cannot be modified once tagging is done.