Sequence Reservations

Sequence reservations are used to reserve a range of sequences for a naming rule and a type within the name context of a scope, based on certain conditions. A user can add, edit or delete a sequence reservation.

A Sequence reservation definition stores the conditions in the form of clauses grouped to form a sequence reservation rule. Each sequence reservation rule can have multiple nested clauses grouped using logical operators.

To view the available sequences, select a scope to load the sequence reservation definition.

For example, SpecScope.

Select + Add to display the New sequence reservation window.

Complete the Name field. Then select Name Context, Naming Rule and Type to populate the fields.

Note:

The scope field is pre-populated and non-editable.

There is only one sequence reservation for each unique combination of "Scope + Name Context + Naming Rule + Type".

Sequence reservations are validated to prevent duplication of names already allocated for a combination of selected "Scope + Name Context + Naming Rule + Type". For example, Engineering: Nozzle.

It is mandatory to have at least one rule. A sequence reservation can have more than one rule.

To generate a rule, click + Add.

Complete the Max and Min fields which can be text or numeric depending on whether the naming rule primary sequence datatype is text or numeric.

A rule can be duplicated and rearranged using the up and down arrows or deleted using the bin icon.

Once saved, you are returned to the Sequence reservation definition window. You can select a scope to view the created sequence.

Note:

There are several clauses to each rule. If the conditions are not met, then the rule will not save. All the fields for each rule must be completed.

The Min and Max values cannot overlap within two different rules and must be sequential. For example, In Rule 1 Min = 1 and Max = 15. In Rule 2 Min = 16, Max = 20.A sequence reservation works on primary numeric sequences only and allows multiple levels of clause grouping.

The clauses can be formed using only the naming parts associated with the corresponding naming rule.

A sequence is controlled by the values of other naming rule parts, so it is mandatory that the naming rule has at least one value part. You must select a type before creating a Sequence reservation definition.

A new sequence reservation cannot be created if a naming rule does not have a type. A message is displayed indicating the naming rule has no type.