Change state previous version

[ZC_10909252]

Version: Windchill 12.1

Use Case: User A changed the state of an object (version 1.7) from released to inactive, Then checked it out and made version 1.8 and set the state to released. User B does not have any access to see inactive objects. They had version 1.7 in their workspace before the change. When trying to add version 1.8 the received an error say that 1.8 could not be add because 1.7 was inaccessible.

Description:

I was able to go into the users workspace as admin and remove the inactive 1.7 version which resolved the issue, but I was not able to change the state of that older iteration as the set state option was missing from the menu.

Is there a way to allow the user to update an older version in their workspace that is at a state they do not have access to? Or is there a way to change the state of the previous 1.7 iteration back to a readable state for all users? 

[TDT]

Hi @ZC_10909252,

I don’t think this is supported out of the box.
However, you could try writing a utility that takes the 1.7 OID as input and uses RMI to update the object’s state.

[avillanueva]

Not the best way but if you delete latest iteration (saving off the 1.8 content), you then can revert to 1.7 and change the state. Repeat process to check out, iterate to 1.8 and set state to released again. 

Careful with states that do not allow at least read access. You can deny download but making the object at least readable will avoid most issues.

[TDT]

Hi @ZC_10909252,

The following article provides a workaround for setting the state on a non-latest iteration.

https://www.ptc.com/en/support/article/CS61713?source=bloop