Change Order lifecycle state and itemstate

[Anonymous]

Our company has recently started to discuss a upgrade from 2012 to 2016 version. Finally... But when starting testing of changeorder routing and item life cycle we find some problems.

It is really a mess trying to figure out the lifecycle state for the item when putting the item throug a eco. In 2012 we also had some problems getting to the final result but is should be possible to do it way more easy than the current solution.

Why should we bother using the Item life cycle definistion when we mark that the item should follow the eco state.

My idea is to make a lifecycle definition for the eco. and when you put the items into the eco then they follow the eco state.... propably a bit difficult to understand.

Autodesk has a lot of good solutions compared to dashauld solid works and PDM works enterprise. but regarding state changes on items/files using an eco it should be possible to do it easier and more simple like the PDM works enterprise.

https://www.youtube.com/watch?v=nPZBLM63RIA

[Senthil_Kumar]

Thanks for sharing your Idea. We use this forum to guide product development and help users in the best way we can based on voting. We occasionally merge Ideas or archive old ones to keep the forum working properly- it ensures there is room for people to review new Ideas and that the most relevant and meaningful ones can gain votes. We’re archiving this Idea because it's been on the board for well over a year and hasn't received many votes from the community. If you want to raise it again and try to gain more support, you're welcome to do so. We’ve found that pictures and mock-ups can help get concepts across and win more votes from other users. If you have questions or see a connection between this Idea and others, let us know. - Vault product team