Workflow for library parts using VDS and Vault

Workflow for library parts using VDS and Vault

t_booijink
Participant Participant
203 Views
3 Replies
Message 1 of 4

Workflow for library parts using VDS and Vault

t_booijink
Participant
Participant

Hi all,

 

We're transitioning to Vault Professional along with a new ERP system, which gives us an opportunity to refine our workflow. We already have a custom VDS configuration that allows us to categorize parts using dropdown selections. Now, we want to implement a similar workflow for creating library parts.

 

The challenge we're facing is that library parts can't be checked in directly since they are outside the working folder. In the past, we first saved them in the working folder and then manually moved them to the correct library folder. While this method works, we’d like to automate the process as much as possible—especially since our dropdown selections already determine the correct library folder path.

 

I attempted to automate this using an iLogic rule and the AddFile Vault function, but as documented, this approach does not preserve relationships.

I’m curious to hear how others have tackled this workflow issue. Any insights or suggestions would be greatly appreciated!

 

Kind regards,

 

Thomas

0 Likes
Accepted solutions (1)
204 Views
3 Replies
Replies (3)
Message 2 of 4

Markus.Koechl
Autodesk
Autodesk
Accepted solution

Are you talking about Inventor Libraries (not the content center files)? From a Vault perspective, we recommend no longer saving custom content into the .\Library\<subfolders>... path, rather than a sub-structure within the workspace. The inventor concept of having these libraries in the project somehow provides write-/change protection for end users in an open file system. A Vault environment can handle access control more flexibly and elegantly. E.g. you can integrate your libraries like this: 

MarkusKoechl_0-1741859135258.png

Different access controls for library editors and consumers drive everything you need without switching projects or moving files. VDS fully supports property editing following this approach.



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes
Message 3 of 4

t_booijink
Participant
Participant

Hi Markus,

 

Alright, thanks! Makes sense, so our "Library" folder should become a normal folder and should reside in the working folder? And then with permissions we should "protect" it against unwanted writes?

 

Thanks in advance for the help.

 

Kind regards,

 

Thomas

0 Likes
Message 4 of 4

Markus.Koechl
Autodesk
Autodesk

Hi Thomas, I answer both questions with "Yes".

 



Markus Koechl

Solutions Engineer PDM, Autodesk Central Europe
0 Likes