Rules for attributes mandatory when upgrade state

[ZANET]

I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.9

Hello,
Please, we use several states (design, prototype, and production) and we use partslink (parts with classification attributes).
How is it possible to ensure, when we upgrade from prototype to production, that we have a check that all classifications attributes are filed.
If it's not the case, stop the upgrade.
Thanks

[avillanueva]

Did you mean to use the word "upgrade"? That typically means Windchill version change. I think what you mean is promotion or change in lifecycle state. If the latter, you can build these checks into a promotion request workflow or a listener.  Attributes can be made mandatory such that at any point, they are required to be filled out. I see that you might want it non-mandatory early on but as it progresses, flip that. I do not think that can be done by lifecycle state which is why it needs to be built into your promotion workflows. This can be done in change notice workflow is that is your process to move states as well.

[ZANET]

You're right Avillanueva, I mean promotion in lifecycle state. I'm going to look for informations about promotion workflows.

You know how can I configure a promotion workflow?

thanks.

[avillanueva]

I would start by looking at online help documentation around workflows and workflow programming. Are you using the promotion workflow currently or are you just using set state? Workflows themselves are not hard to modify and edit but there is a ton of information and best practices out there. Skills needed for what you are asking for would be workflow customization which is Java programming and understanding the Windchill API. 

[ZANET]

Yes we are using promotion workflow.

[avillanueva]

General workflow programming is too large of a topic for a single post thread. I suggest if you do not already know, explore workflow design, especially conditionals and expression robots. Next I would look for knowledge base articles and other posts that have discussions of looking up attributes against the objects on the promotion notice. Since there can be multiple objects, you need to know how to navigate from the primary business object on the workflow, to the objects on the promotion notice and then it can apply your business rules against each one. Something to consider is a useful message back to a user when it fails a business rule so they know what to address. The result of a failed check would get kicked back to a user to address the issue and retry, a simple check loop.  I think that should close out this thread but I would expect more posts on topics above as you work on your solution.

[Fadel · Accepted solution]

you need some kind of business rules to do the validation on the attributes , see https://www.ptc.com/en/support/article/CS301629 , https://www.ptc.com/en/support/article/CS156636, https://www.ptc.com/en/support/article/CS361541