If a user defined suffix has been added to a clause (the original or first added clause), and additional instances of that same clause are added to the specification, the platform will use dynamic suffix identification to ascertain if the suffix of the original or first added clause may form part of a logical sequence.


The subsequently added instances of the same clause will then either, have a suffix added based on the next logical value in the ascertained sequence, or simply have a sequential identifier of (A), (B), (C) and so an added to the end of the existing suffix value.


If the system generated suffix is not appropriate and you wish to change it, this is easily done. Please see Suffixes and prefixes - Adding and Editing for more information.


Examples


Example of a logical sequence in a Uniclass Work Sections specification

In the example below a user has added a suffix of Style 101 to the first added wood window units clause in a Uniclass Work Sections specification, so when further instances are added to the specification the system generates a suffix automatically of Style 102 and then Style 103 and so on.


Example of a logical sequence in a CAWS Work Sections specification

In the example below a user has added a suffix of Style 101 to the wood windows clause in a CAWS Work Sections specification, so when the clause is duplicated the system generates a suffix automatically of Style 102 and then Style 103 and so on.

Example of a sequential identifier in a Uniclass Work Sections specification

In the example below a user has added a suffix of Generally to the wood window units, so when further instances are added to the specification the system generates a suffix automatically of Generally (A) and then Generally (B) and so on.