If you add more than one instance of the same clause, the platform will use the suffix field of the subsequently added clauses to differentiate them from one another.
This suffix may be in one of three different formats, depending on the suffix of the original or first added clause:
- Adding a new sequential suffix of Type A, Type B, Type C and so on to subsequently added versions of the clause (where the original or first added clause does not currently have a suffix)
- Appending a sequential identifier of (A), (B), (C) and so on (where the original or first added clause currently has a suffix that does not appear to be part of a logical sequence)
- Incrementing an existing suffix to the next logical value in an ascertained sequence (e.g. Style 102 would follow Style 101, Set B would follow Set A etc.)
Example of a new sequential suffix in a Uniclass Work Sections specification
In the example below a user is adding further instances of the Clay bricks clause in a Uniclass Work Sections specification, the system generates a suffix automatically of Type A and then Type B for the second and third instance and so on.
Example of a new sequential suffix in a CAWS Work Sections specification
In the example below a user is duplicating the Clay facing brickwork clause in a CAWS Work Sections specification, the system generates a suffix automatically of Type A and then Type B for the second and third instance and so on.
The separate support article Adding additional clauses and systems when a user has edited the suffix provides additional examples for appended (A), (B) etc. type suffixes and incremented sequence suffixes.
The suffix of any clause (including system generated suffixes) can be edited if required. For more guidance on how to do this, please see the separate support article Suffixes and prefixes - adding and editing.