New Vault Properties for Title Block Mapping

[cadfish1]

Per Brian Shanen's recent blog article, he states that are new vault system properties that can provide administrators the ability to map critical release process data to title blocks. Brian doesn't state how this is done in Inventor nor can I find help on this matter. Does anyone else know how?

Thanks in advance.

http://underthehood-autodesk.typepad.com/blog/2010/04/new-vault-properties-for-title-block-mapping.h...

[Anonymous]

Hello. That's a good question. There are a few
things that you have to understand in order to do this. The first is creating
custom properties on an Inventor file and adding those properties to your title
block. If you need help on this part let me know and I'll add more detail. For
now I will assume you've created the custom property on a file and linked it to
your title block.

In the Autodesk vault client, you can navigate to
the Property Definition dialog and select any of the 4 system properties
mentioned in Brian's article. Edit the property and select the mapping tab. In
the mapping tab, add a mapping by navigating to the file that contains the
custom property and selecting the property. Now that you've done this, when
these properties are changed, the value will be mapped to the
file and then shown on your title block.

Regards,

Adam 

style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">

"cadfish1" wrote in message
href="news:6392189@discussion.autodesk.com">news:6392189@discussion.autodesk.com...

Per
Brian Shanen's recent blog article, he states that are new vault system
properties that can provide administrators the ability to map critical release
process data to title blocks. Brian doesn't state how this is done in Inventor
nor can I find help on this matter. Does anyone else know how?

Thanks
in advance.


href="http://underthehood-autodesk.typepad.com/blog/2010/04/new-vault-properties-for-title-block-...

[cadfish1]

I should have mentioned this before but my Vault Pro client is not connected to the vault server because I'm having some difficulty installing 2011 therefore I can't get to any data so I flying blind at this point.

I do know how to point a Textbox in the title block definition to a file property. I didn't know that these new vault system properties are mapped to custom file properties in Inventor.

It dawned on me that any property available for edit in iProperties (tabs: Summary, Project, Status, Custom) are modifiable in Inventor if the user is not logged on to Vault. So someone could potentially change the values of these new custom properties then make prints for manufacturing. I don't care if these new vault system props are custom or standard props in iProperties but it would be great if they could be protected somehow from user changing from iProperties. In other words, only Vault can change them. They would have to be in a list in Inventor "Format Text" dialog so the admin could point towards this data in a title block but in any case if they were protected against direct (iProperties) manipulation then it can be considered to be a digital signature. This would allow us to go paperless! This may not be workable because copying files becomes an issue because the new file would contain digital signatures. Just thinking out loud.

Thanks for the help Adam.

[Anonymous]

My pleasure.

In regards to protecting the properties, the mapping that you would create
from this system property can only be a write property. That is to say that
it will never be read into the vault. That might help a little. Any time the
file is downloaded from Vault it will lay down the correct value.

Adam

"cadfish1" wrote in message news:6392439@discussion.autodesk.com...
I should have mentioned this before but my Vault Pro client is not connected
to the vault server because I'm having some difficulty installing 2011
therefore I can't get to any data so I flying blind at this point.

I do know how to point a Textbox in the title block definition to a file
property. I didn't know that these new vault system properties are mapped
to custom file properties in Inventor.

It dawned on me that any property available for edit in iProperties (tabs:
Summary, Project, Status, Custom) are modifiable in Inventor if the user is
not logged on to Vault. So someone could potentially change the values of
these new custom properties then make prints for manufacturing. I don't
care if these new vault system props are custom or standard props in
iProperties but it would be great if they could be protected somehow from
user changing from iProperties. In other words, only Vault can change them.
They would have to be in a list in Inventor "Format Text" dialog so the
admin could point towards this data in a title block but in any case if they
were protected against direct (iProperties) manipulation then it can be
considered to be a digital signature. This would allow us to go paperless!
This may not be workable because copying files becomes an issue because the
new file would contain digital signatures. Just thinking out loud.

Thanks for the help Adam.

[cadfish1]

That works fine assuming a vault interface is how manufacturing gets ALL its prints. We are not paperless here (yet). We require stamps (approved for use) and signatures on hardcopies. Engineers make all the prints for manufacturing and the engineer usually uses Inventor to make the prints. If the digital signatures and dates (Vault system props) in the title block are pointing towards file properties that can be changed directly in Inventor and then printed then we can use them as a digital signature (unprotected - untrusted).

[Anonymous]

The problem that you are talking about is a problem with access.
Anytime someone can download and open a file they can change it and even
print it out. It is not possible to stop someone from doing this.

Lets say for a second that we could prevent a user from changing the
iprops in Inventor whenever a file was not checked out. What would stop
them from checking out the file, making changes, printing it, and then
doing an undo checkout?

Its just not possible to stop people from being people. What we do offer
are tools to help make sure that data is up to date.

--

Mikel Martin
Autodesk Data Management
Applications Design Lead