What is Revision Sequence Validation?

The Revision Sequence checking feature helps Document Controllers ensure that project members do not mistakenly supersede Register Documents with revisions that are out of sequence.

How can I turn Revision Sequence Checking on my Project?

To turn on Sequence checking;

1. Go to Configure

2. Modules

3. Publication Space

4. Click on the numbering tab

5. Select Enable

6. And select an option from the options shown below

What's the difference between "A-ZZ then 0-99" and "0-99 then A-ZZ"?

A-ZZ then 0-99
Selecting this option means that the Rev sequence check starts at A and matches all the way up to ZZ and then from 0 to 99

0-99 then A-ZZ

Selecting this option means that the Rev sequence check starts at 0 and matches all the way up to 99 and then A to ZZ

What is A.1 ... to A-Z then 0.1 ... 99 to 0-999?

Selecting this options means that A.1 is considered a lower revision than A followed by 0.1 and then 1,2 and so on.

As an example revision sequence that will match this option is

A.1

A.2

A.3

A

B.1

B.2

B.3

B

0.1

1

Who can Turn this Feature on?

You need to be a Project Administrator to be able to access the page to enable this feature.

When does it perform the Check?

The validation check is performed when you upload a file into the publication space and click upload

What information about my Register Document does it perform the check against?

When a user attempts to upload a new revision where the Revision code for this document is earlier AND the Revision Date is later than the Revision Code and Date of the latest revision on the Register a warning will be displayed as shown below.

In the example below the user has previously uploaded Revision D on the 16th of November

He has now attempted to upload Revision A on the 24th of November

Since this new documents revision is EARLIER in the sequence and uploaded at a LATER DATE than the latest currently on the Register, the system has detected an out of sequence revision.

What does the warning message mean?

Blue highlight tells you the details of the file you have just attempted to upload.

Red highlight tells you the details of the revision that your upload is conflicting with in terms of the revision code and date.

The rest of the message provides you with instructions on how to resolve this conflict.

How can I resolve this conflict and finish my upload?

If you are trying to upload an older revision please correct the revision date

If you are trying to make this revision the latest choose a higher revision code

What will happen if I upload with a revision of "-"?

If you upload a new document without a revision code in the file name; eg ARCH 101[-].pdf, the system will treat it as the start of the sequence

eg -, A, B,C,0,1,2,3,4)

Browselist - It will first perform a revision check against the document revision history and inform you about the conflicted revision.

Upload Manager - It will auto correct the revision details and upload it as the first in the sequence. See example below.

What will happen if I don't add a Revision and upload?

If you upload a new revision without a revision code in the file name; eg ARCH 101.pdf, the system will treat it as the start of the sequence

eg "" A, B,C,0,1,2,3,4)

i.e same as the Above question.

What about Revision that are from Mark ups (Document Review Workflows)?

If a revision exists in the Document history with a mark up specific code; eg ARCH 101[B-MU1], then the system will treat B as the code that it performs the revision sequence check