Starting with "Vault-Revision-table" in a running system

Starting with "Vault-Revision-table" in a running system

MarkusGreifeneder3360
Advocate Advocate
586 Views
1 Reply
Message 1 of 2

Starting with "Vault-Revision-table" in a running system

MarkusGreifeneder3360
Advocate
Advocate

Hi,

we revised drawing using the Vault Revision, but we didn't use a Job-Client (Revision info was written by hand in titleblock)

Now we want to synchronize the inital release date and Initial releaser (according to DIN) to Title block and "Vault-Revision-table")

 

When setting up the "Vault-Revision-table" with 5 rows, of course all old Revision get printed on drawings.

Of course all old revisions are shown without Revisiontext and Editor.

 

How to solve this issue?

 

Workaround1:

Generate new revision-scheme and set for all "old" drawings (=> thousands of drawings have to be modified and the actual Revision has to be set)

 

Workaround2:

Reduce the lines of the "Vault-Revision-table" to 1.

Very few information is shown on the "Vault-Revision-table"  also for new drawings with several revisions

 

 

 

0 Likes
587 Views
1 Reply
Reply (1)
Message 2 of 2

Anonymous
Not applicable

The Vault system properties "Initial Approver" and "Initial Release Date" could be your answer.  These values are are assigned the first time a file is released, and can never change.  The "Initial Approver" value is the user name of the person who changed the state, and the "Initial Release Date" is the date and time of when that state change happened.

 

Instead of putting them in a rev table, they could be added to the title block.

 

First, map the properties to the file, note that it is one way only; Vault to file. (I used drawing properties instead of model, if you wish the properties to come from the model to the drawing, change the provider.)propdef.png

 

The data as it already exists in Vault:

propvalues.png

 

Added the mapped properties in the title block:

propmapping.png

 

And the result:

propindwg.png