Change Status old revision

[guillermo.martinezC6FK8]

Good Morning,

I have a Part in Revision 0 (Staus Release) and this part in other assembly, but the before Revision "A" is in "Work in progress".

When I try change the status to Release in this asseblie. I cann´t do this change because I have the Part of revision A in "Work in Progress"

Is it possible change the status in old revision for change the status assemblie?

Thank you

[Gabriel_Watson]

This is most likely an issue with your template having a different revision scheme than your Vault revision scheme. You start the part as Rev A WIP and when released it adopts Vault's revision scheme that is numerical.
You may need to simply update your templates to start as Rev 0 WIP, and you can't really fix the previous version in Vault by editing the property, unless you Roll Back Lifecycle State (warning: save a copy of the latest version before rolling back, as it will erase the tip version).

[CStilesCARE]

Just to confirm I understand your issue:

1. Your active assembly contains "Part" Rev A and a separate assembly contains "Part" Rev 0 (same part, different revision).
2. You are attempting to release your current assembly while it still has "Part" Rev A, but Vault won't let you.

If that's correct, then my first question is, why are you not using the most recent version of "Part" (Rev 0) in both assemblies? Archiving purposes? There should only ever be a single active revision of any component at one time. If multiple need to be used simultaneously, they should be separate components with separate numbers.

That being said, if you have a need to change this assembly state, you can either change it to a lifecycle that allows the change without requiring components to be released, or alter the current lifecycle transition rules to allow it.

[guillermo.martinezC6FK8]

My active assembly contains "Part" Rev 0, this Part in this revision the status is Release.

But the before Revision A is in the status "Work in progress". Yes I did change the revision without change the status (bad).

Now, when I want to change the status to the assemblie, Vault sow me "Restrictions: Revision A of "Part..." is not released." 

The Revision A is before to 0.

[CStilesCARE · Accepted solution]

Ahh, ok. Yeah, I'm not exactly sure why Vault has this issue sometimes. If this isn't likely to be an issue for you going forward, you (or someone with Vault Admin permissions) could just edit the lifecycle transition rules to eliminate the requirement for all previous revisions of components to have released status.

If you're hesitant to change the active Lifecycle transition rules, another option is to create a new Lifecycle (maybe copy the current one) with altered transition rules specifically for cases like this where you don't need or want that limit enforced.

There might be an easier way to fix it than this, but I'm drawing a blank at the moment! 

[guillermo.martinezC6FK8]

Thank you, for this solution.

In this case was the best. 

When I upload the file, I changed the revision because the file has xxxx-R4, for example.

When you change the revision to 4, the first revision, in my case "0" is in "Work in progress". This is the problem, Vault not change the old Revision in Release.

When I tray Change the Assembly, this part have this "problem"

[CStilesCARE]

Not a problem. Glad we were able to help you out here.

The only thing I can think of which "might" work would be to bait-and-switch Vault by just creating a version of the file with the revision number that's "missing" a released state, releasing that, then immediately changing back to WIP, checking out and changing revision number back to what it's supposed to be.

If the model needs to "match" the old revision, then you could even switch-out the model file for the old one for that version, then switch back after.

I'm not sure why Vault even has a Lifecycle requirement option for checking whether all previous versions of a component have released status, since that has little bearing on the current version, and I can't think of any "nice" way to fix that issue if it comes up... I'm sure there are relevant use cases for it, but they seem niche so I don't see why it was set as a "default" option for lifecycle transitions.

[kpk7VYPK]

Hi, I cant seem to see this option for not checking previous versions are released. I am using Vault 2024. Can you help?

[CStilesCARE]

Hi @kpk7VYPK! I can sure try to help.

In this case, I think the original issue was that Vault was preventing an assembly from being changed to "released" because not all of the components used in it were already "released". In order to change this, you need to have sufficient admin access in order to alter the Lifecycle Definition that is causing you trouble.

Assuming you're using Vault 2024 Professional, you do have the required access to modify Lifecycle Definitions, you'll have to navigate to the appropriate "Transition" that is giving you trouble (ex: "Work in Progress" to "Released"), and edit it, then look for the "Actions" section and see what checkboxes are checked which mention checking for various things to be "released".  See the snip below for an idea of what that section looks like.

Note that THIS WILL CHANGE IT FOR EVERYONE, not just you, so make sure that you won't get in trouble for making the changes.

You can get to this screen via the following steps from the main window.

• Tools Menu  >  Administration > Vault Settings > (Vault Settings Window Opens)
• Behaviors Tab >  Lifecycles and Revisions Section > Lifecycles... > (Lifecycle Definitions Window Opens)
• Select desired Lifecycle 'X' to check/change > Edit Button (up top) > (Lifecycle Definition 'X' Window Opens)
• Select "Released" State in lower left > Transitions Tab (lower right) > "Work in Progress" to "Released" or other desired transition (Make sure the arrow is pointing towards "Released") > Edit Button > (Transition Window Opens)
• Select "Actions" Tab > Edit checkboxes as desired

[kpk7VYPK]

Perfect. Thanks.