There is no lifecycle state to roll back to (Item state is Released)

[Maxim-CADman77]

Autodesk Vault Pro 2014 SR1 SP1.

Attempt to execute action/command "Roll Back Lifecycle State Change" to Item "B11NET11113" the only revision "0" of which is in Released state fails for the reason "There is no lifecycle state to roll back to".

How could this be possible?

Don't all Items have WIP state prior to be Released?

[cbenner]

In theory, unless your files are set to a specific lifecycle state on creation.  For example if you have it set up to Release a file on it's first check in... there would be no WIP to go back to.

[Maxim-CADman77]

I'm talking about lifecycle of Items (not files).

Could item be initially created in Released state?

[cbenner]

For Item this doesn't seem likely..... not sure what you're seeing.  It does sound odd at best.

[Maxim-CADman77]

Should I prove that I do have situation posting screenshot here?

[cbenner]

Screenshots are always helpful.  I don't disbelieve you by the way, I just have no idea what would cause this.  Maybe one of the Adesker Vault gurus will have a thought.

[Maxim-CADman77]

...not sure it would add anything to my textual  description ... anyway ..that is how it looks for me:

[cbenner]

Just had a thought... do you use ECO's?  If so, do you have this checked?

[Maxim-CADman77]

Not sure to understand you correctly.

Option "Restrict Item Lifecycle Changes to Change Orders" is OFF at
"Change Orders" tab of Vault Settings.

The issued Item doesn't have anything present at "Change Order" tab (on
Preview Pane) either.

[cbenner]

Ok,... that isn't the problem then, If that box was checked it would not let you roll back the state without an ECO.

[Maxim-CADman77]

BTW, do you know what is the steps to roll back Item state with the
option enabled?

[cbenner]

With the option enable, do you mean with that check box checked, requiring the use of an ECO?  I don't think you can roll these back without the Administrator doing it. 

I guess a good question would be, why are you rolling them back?  Were they changed by accident?  If so, then using Change Orders might help to prevent that.  If users cannot change the lifecycle state without an ECO, they would be less likely to change them unless they are certain they need to be changed.  My opinion.

[Maxim-CADman77]

In fact user would like to fix silently Item that get issued with this
defect - Units property value Item behaves wrong if Inventor
localization
ehaves-wrong-if-Inventor-localization/td-p/5017026>

[cbenner]

You can Change State (not roll back) without bumping the revision if that's the concern.  When you change state from Released to WIP there is a check box for Skip Revision Bump.  Good for quick changes that do not need a revision level change.  

[Maxim-CADman77]

Thanks for the suggestion.

I know about this possibility. But having several Item revisions with
same number is against our corporate policy.

[herrerh]

For your Item Lifcycle rule of WIP to Released, is that set to bump the revision?

-Hywell

[Maxim-CADman77]

No. We auto-bump revision only during Released->WIP.

[Maxim-CADman77 · Accepted solution]

Looks like Item Purge command is responsible for this - http://help.autodesk.com/view/VAULT/2014/ENU/?guid=GUID-C3165C15-A4DF-4510-816F-A9B012413546

But then the command is very-very rough because unlike File Purge command it gives no any flexibility...

Thus user chould always chooce between keeping all the Item history and size of database (ability to purge historical versions of files that are blocked due to be linked to some historeical versions of Item).

[Maxim-CADman77]

Seems nothing can be done about it in the 2014 release (hope somebody could check if something was improved regarding this in 2015).
Have created the idea - http://forums.autodesk.com/t5/Vault-IdeaStation/Make-Purge-Item-Command-flexible-alike-Purge-command...

[YounesYammouri]

Hi Maxim,

just to recap and make sure I got you right:

You would like to rollback lifecycle State change of an Item from Release State to Work in Progress.

If this is the case today the Rollback Lifecycle State change can only be applied to an Item in Work in Progress state which has been at a certain time released. Please check also Vault help for that:

http://help.autodesk.com/view/VAULT/2015/ENU/?guid=GUID-A83D54E2-423A-450E-A6A5-4C6AEAD86F72

You can roll back an item that:

• is in the Work in Progress (WIP) state to the previous released version
• has been released to the last lifecycle state of either Work In Progress (WIP) or In Review

Rolling back an item from WIP to the previous released state deletes the current revision of the item.

The lifecycle of an item cannot be rolled back if:

• the item is in the Obsolete state
• doing so would create an invalid BOM
• there is no previous lifecycle state
• the item history was created during a change order that is now cancelled or closed

Your feedback to allow a rollback also from any state (e.g. release state) to a previous valid (e.g. Work in Progress) state is much appriciated. Please make sure to add this as an Idea in the Idea Station forum.

Younes Yammouri

Autodesk Product Manager