Get old assembly version including dependants

[Jelvin_]

Vault 2018.2 Professional. Item workflow with associated file security for linked files.

Hi, I have a question regarding download/get of old assembly versions. See workflow below

Create Assembly 1 and check in with part 1 and part 2. All versions = 1

Make a change and check in Part 2 and NOT the assembly. Only part2 is version 2.

Is there a way to get the Original assembly (v1) as it was designed and checked in?

If i select the history tab and then get on Version 1 of TopAssy i get this result

Note that version 2 of the part is automatically selected if i include children.

Now to the funny part. If i create a new version of the top assy (a check out to generate new version is enough). And select get on version 1.

i get this result. Note part2 is downloaded as version 1

How is is possible to get two different results for version 1 of the assembly file? Is this as intended or is this a bug?

Could anyone please explain to me if there is a way to get the original checked in version 1 of the assembly WITHOUT first creating a second new version?

[gandhey]

Hello,

The 'latest' configuration of the assembly always refers to the 'tip version' (latest version) of the child components. This is what you see when you do 'Get' operation.

The assembly will show the 'As-stored' configuration (configuration at the time of check-in) when you have multiple versions for the assembly and when you are trying to Get/download the non-latest version.

In your case the Latest of assembly is version 1, the moment you checkout assembly the Version is bumped up (2) - note you do not need to checkin assembly to get to version2, you can see this in the History tab too.

First Get operation follows the 'Latest configuration'

Second Get operation, I believe you are doing on version 1 of the assembly (after checking it out) which is why you see the Part file version 1 in get UI. (this is As-Stored  OR checkin configuration)

Try doing Get on version 2 of assembly in your scenario to understand the difference.

Regards,

Yogeshwar

(Vault team)

[Jelvin_]

Thanks for your reply.

So if i understand correctly there is no way to distinguish between the latest and as stored version of an assembly if only one version of the assembly exists? (or if no later version of the assembly exists)

Lets put this into a user case.

Create assembly and assign topassy and parts to items.

Release entire item and child items as Revision A

• Top Assy Rev A (version 1)
  • Part1 Rev A (version 1)
  • Part2 Rev A (version 1)

Make a revision to Part2 only and release as Rev B

I can now view my TopAssy Item the difference between the latest and the A revision of the item.

Latest:

• Top Assy Rev A (version 1)
  • Part1 Rev A (version 1)
  • Part2 Rev B (version 3)

Version A

• Top Assy Rev A (version 1)
  • Part1 Rev A (version 1)
  • Part2 Rev A (version 1)

Unless i create a new version of my TopAssy iam. file (requires revision or quick change of associated item) there is no way for me to retrieve the item as designed and released in Revision A

Do i need to consider a different workflow (ie. file workflow with revisions and states) to solve this issue?

[gandhey]

Hello,

I hope you noted that the version is bumped up for the file/item as you Change the state (on file or Item respectively).

As i try to simulate your workflow, I can see that on ITEM.

Latest:

• Top Assy Rev A (version 2)
  • Part1 Rev A (version 2)
  • Part2 Rev B (version 3)

Version A (Work In Progress) Guess this is the one you are interested in.

• Top Assy Rev A (version 1)
  • Part1 Rev A (version 1)
  • Part2 Rev A (version 1)

Note the Item shows different versions for the TopAssy thus the difference seen is viable. But for the same assembly file you just have one version.

Regards,

Yogeshwar

(Vault team)

[Jelvin_]

Hi, Well yes it is true that the Item (or a file with a workflow enabled) does get a new version for each state. That does not mean that the associated file gets a new version each time the Item goes through a change.

I created a screencast to show to workflow and the issue I'm having. Hopefully it will make things a bit clearer

Thank you for your input.

https://autode.sk/2Ei14Yc

In the video, the last step is a quick change of the item. Open and check out of associated file. Update of item and release. After this procedure, which created a new version of the associated file, am i able to get the original version of released version A

[gandhey]

Hello,

That does not mean that the associated file gets a new version each time the Item goes through a change. --> That's correct.

File and Item are still explicit and need update separately to keep both in sync.

• File changes (structure/properties etc) to be passed on to Item -> user need to Update Item.
• Item changes (properties etc) to be passed on to File -> user needs to do Update Properties.

And just to highlight at the last step you are updating the Assembly file, which essentially is versioning up the assembly file

Regards,

Yogeshwar

(Vault team)

[Jelvin_]

Exactly.

I did the last step (quickchange state) to illustrate that if i create a new assembly file version, and then update the Item, it is now possible to get the original assembly revision A, A, A (version 1, 1, 1).

I would like to avioid having to make this step just to download an old version of an assembly

I just have to work my way around this problem. If i use revisions and states for files this is not an issue.

Thanks for your help,