What is the best practice for mass update state from INWORK to RELEASED of parts/doc belonging to an assembly?

[M.RehanYousufQu]

Hi,

What best practice one should do for mass update state from INWORK to RELEASED of parts/doc belonging to an assembly?

I see many options and looking at the different UI pages came up with the following: Appreciate feedback in this regard.

UI Page	Check-Out State	How to start	Multiple Objects	Dependencies	Access for Set State permission
Detail Page	Must be checked in	Action menu	N/A	No collector	Yes
Folder View	Must be checked in	Add to Workspace / Action menu / New promotion request	Yes for editing multiple object but No for doing set state on multiple objects.	Objects must be associated or dependent part/doc	Yes
Product Structure Browser	Must be checked in	Add to Workspace / Action menu / New promotion request	N/A	No collector	Yes
Search Results	N/A	Add to Workspace	N/A	No collector	Yes
New Promotion Request	Must be checked in	Action menu	No	Objects must be associated or dependent part/doc	Yes
Lifecycle / Workflow	Must be checked in	Lifecycle based	N/A	No collector in UI but can collect related part/doc programmatically	Yes
Revise	Must be checked in	Action menu	No	Objects must be associated or dependent part/doc	Yes

Regards,

- Rehan

[JarrettOberg]

Hi Rehan,

Excellent job in summing up some of the methods.

There is another method that may work for you. In some of the later maintenance releases we have added a utility that can perform these updates.

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS13365

See the Windchill Online help section entitled "Running the Life Cycle Template Command Line Utility" for more information on its use

Good Luck,

Jarrett