Use Vault Path property to define category

[Maarten65]

In Vault objects have a property called path. I like to use the property in a rule when determin which category the part is.

For example:

If path contains "LIBRARY" category_name = "Library parts"

If path contains "DESIGN" category_name = "Design parts"

If path contains "Content Center Files" category_name = "CC parts"

In this way a user only has to place the part at teh right location on disk. During initial check in it will get the correct category automaticly.

[xavier_dumont1]

Hello,

Any news regarding this? It's really a major issue (in my opinion) regarding assigning a specific lifecycle for Content Center Files.

Actually the solution bellow is not a good one regarding custom parts from Content Center and Frame parts.

https://www.youtube.com/playlist?list=PL9A6632DDBF5C9661

Thanks in advance

[ryan]

This functionality needs to be added to vault.  Anyone who has ever tried to implement vault across multiple divisions in a company can speak to how important this functionality would be.

Vault allows us to display the "Path" as column in the UI, so why no love to use it within a categorization rule?

While using templates with a custom iProperty and/or Data Standard help, there are many situations where it does not - categorization by path would be the cleanest solution.

P.S. Depending on the customer and their folder structure, this may also help another issue I have with deploying vault across multiple divisions which is the ability to distinguish the "type" of DWG file. 

-Ryan

Ryan Small

SolidCAD (Autodesk Reseller)

[ihayesjr]

The Vault Data Standard feature can be used to accomplish this.

[ThomasRambach]

Why can't this functionality be part of the core product?

[cbenner]

@ThomasRambach 

Have you checked to see if this is in the Ideas forum yet?  Are you a beta member?

NEVER MIND!

Read back to the beginning.  I get it now.

[ThomasRambach]

I haven't seen anything of the if, then else nature for this. @cbenner 

[Maarten65]

The request wasn't really solved.

Using the data standard isn't a nice way to work with vault, I think personally.

Beside the creation and management of the scripts to all clients, updating to a new release of Vault can generate extra work as well. If they don't work fine, you have to solve it yourself. Hints and how-to are given by multiple sources but you have to solve it yourself. 

It should be a feature inside Vault, not in an add in.