Released Items vs Released Files

[Anonymous]

After years of running 100% WIP, thanks in part to some early producststream scarryness, we're getting ready to transition to using some of the tools/features within the vault. Particularly we're looking at releasing items and implementing the ECO tools (thru the thin client).

Quick workflow questions for those of you that release items and or files thru the vault.

Files -

What's the point of releasing files when you can release items?

All of our files, except for the select few that I've been testing with, do not belong to any lifecycle definition, will that cause problems?

For that matter, what's the point of file lifecycle definitions?

Items -

I think that part of the intended workflow is that all library part items should be released, permenantly. That correct?

Anyone want to take the time to describe their item release workflow for me, as an example of what/what not to do?

Thanks!

Eric

Inventor 2014 Pro 64bit Build 246 SP2
Vault 2014/15 Pro Admin Update 1
Windows 7 Ultimate 64bit
Intel Xeon E5-2643 @ 3.30GHz
32GB RAM
Nvidia Quadro K5000

[Anonymous · Accepted solution]

I agree, the items are still a bit clunky. Too late for us though, we're stuck with them till the end. I did figure a workaround for item revisions, I'm just ignore them. I'm going to have our ERP link stop looking at the item system level REVISION property (which is only editable thru manual and lifecycle changes) and have it start looking at the item REVISION NUMBER property instead which is mapped to live file data and updates with the Item.

[Anonymous]

For now our link to ERP is going to be entirely a manual process but I like your approach to Item revisions and I plan on going that route if I set up an ERP link in the future.

[patric_fischer]

Hello wkoehn,

It seems you find a way to work with revision and state that are aligned between files and Items. Can you give us more information on your settings? Thanks

[nucleusgmbh]

Hi, I know this thread is pretty old but I'm facing exactly the same problems and I haven't seen a real solution yet.

We are using Vault Pro 2021 but I don't think it has changed a lot.

Generally we are having the same problems as @Anonymous  :

I have the feeling that the whole workflow is much smoother by using file life-cycle.

I totally like the idea of using items but I think there should be a revision-No on a DWF drawing and I don't find a way to have this without making 20 handstands.

To be honest how does anybody else handle this problem? Don't you put revision-tables on your drawings? Don't you use revision-No on your drawings?