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 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. For example, SpecScope.

To create a new Sequence reservation:

1. Select + Add.

   

2. Complete the Name field.

3. Finally, select Name Context, Naming Rule and Type from the dropdown lists, to populate the fields and display a new sequence reservation.

   

   Note:
   A user can add, edit or delete a sequence reservation.
   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".
   It is mandatory to have at least one rule. A sequence reservation can have more than one rule.
   A rule can be duplicated and rearranged using the up and down arrows or deleted using the bin icon.

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.

To generate a sequence reservation rule:

4. Select a sequence in Sequence reservations to display the Sequence reservation definition window. For example, Seqst1.

   

5. Select + Add.

6. Complete the Max and Min fields with text or a numeric datatype.

   This depends on if the naming rule primary sequence datatype is text or numeric.

   

7. Select Save.

   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.
   Rule conditions support the Less Than, Less Than or Equal To, Greater Than, and Greater Than or Equal To operators for numeric values only.
   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.
   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.