I have created a custom change notice and change task workflow in my Windchill instance. The two workflows are based on the OOTB configurations for change notices and change tasks. When my change task gets to a state of "Implementation" the user can respond to a task put into their workspace with a vote of "Production". This will set the state of the change task to a state of "Production". The workflow for the change task is "Executed" at this point. The workflow for the change notice stops at the "Set Change Notice Resolution Date" task. In the process manager, this task is highlighted green and "Running". By looking at the change notice, I can see that a date has been attributed to the "Resolution Date" attribute. But when I check to see if the activity has any errors against it in the "Process Manager", there are messages saying that "Resolved is not a valid state in the Life Cycle Template". The next activity in my change notice workflow is the "Set State Resolved" activity. It looks like the issue resides with this task, not the "Set Change Notice Resolution Date" task.
I do have a state of "Resolved" in my change notice life cycle but I do not have a "Resolved" state in my change task life cycle. It appears as if the change notice workflow is trying to also set the state of my "Change Task" to "Resolved". But, I have no need for it to do this. I cannot see any config in the life cycle's or workflow's that prove this is the case but I'm wondering if it is behaving in this way as the change task is a child of the change notice. Can anybody explain how my issue can be overcome or why the system is behaving in this way?
