Check Lifecycle from Items in CO

[bruce.nyfeler]

For releasing an Item, you have to create a CO and then you can change the Lifecycle from the Item.

It doesn't matter if this is "Under Development" or "Production". Item Lifecycle can only be changed with CO. This controlls, that affected Items are properly changed and they are under control revision.

However, Busniess is busy.

It can happen, that you addd Task to Users, and add Items. Tasks can be controlled with Condition and Validation Scripts. If something is pending, a specific Workflow is not possible.

But now, it is pssible to go forward until the end without having a Lifeceyle on the Item. If you now "Release" the CO, you well get an Message that is usless for the User.
It failed; yes I can see it. The process is not going forward. Not very helpful. Only as Admin you can see in the Error Log, that it has failed because Lifecyle is missing.

It would be helpful, if a Workflow transition can check if a Lifecyle is null. 

User training is good, a smart Workflow checkt would be better.

[sven.dickmans]

PLM validates the lifecycle settings for all items of a Change Order before reaching the 'managed state' of the given workflow (which will actually perform the given lifecycle transitions). If the lifecycle is not set, there is a proper error message - not the one you encounter. It seems that there is an error in the script of the workflow transition that you performed. Which transition is causing this error? Did you modify the standard 'Change Orders WF Actions' script?

[bruce.nyfeler]

It is based on the orign. CO Workspace. Some changes are made in the  'Change Orders WF Actions' script.

Thanks for the meeting for this task.