Skip to main content
B
BF_1381190014-Alexandrite
14-Alexandrite
October 10, 2025
Solved

Is it possible to stop the Change Notice Workflow Setting the State of the Change Task?

  • October 10, 2025
  • 1 reply
  • 481 views

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?

Best answer by BF_13811900

It appears the answer is in this article. Not the behavior I really want but I'm not sure how I can change the state the robot attempts to assign the change task to without having an impact on the state that other workflows that other workflows try to put change tasks on as a result of the inclusion of the ‘Set Change Notice Resolution Date’ robot.

 

https://www.ptc.com/en/support/article/CS102710?source=search

1 reply

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
October 10, 2025

Not sure if its there but in the change task workflow there is typically a sync robot in each workflow that waits for a change on one workflow to proceed ahead. Did you make any changes to those? 

B
BF_1381190014-AlexandriteAuthor
14-Alexandrite
October 10, 2025

My change task workflow contains one sync robot. I use this synch robot to detect when I have manually set the state of the change task to "Implementation". The synch robot identifies when this event occurs and then progresses to the next task in the workflow. The sync robot is behaving as I want it to in this workflow. So I have changed this robot but it is working as I want it to. I don't think the modification to this robot has any relation to my issue. My change notice workflow makes use of a "Synch on CA Complete" robot. I have not made any changes to the configuration of this robot and it is identical to the OOTB version. The expression in this robot makes reference to a change activity state called "Complete". I do not use a state called "Complete" in my change activity life cycle. But, I have defined my "Production" state as being a value for "Completed States" in the type and attribute management facility for the change activity object. Consequently, it seems as if the "Synch on CA Complete" is recognizing that my change activity is complete when it gets set to a state of "Production". The workflow progresses past the "Synch on CA Complete" with no issues and as I would expect.

B
BF_1381190014-AlexandriteAuthorAnswer
14-Alexandrite
October 10, 2025

It appears the answer is in this article. Not the behavior I really want but I'm not sure how I can change the state the robot attempts to assign the change task to without having an impact on the state that other workflows that other workflows try to put change tasks on as a result of the inclusion of the ‘Set Change Notice Resolution Date’ robot.

 

https://www.ptc.com/en/support/article/CS102710?source=search

    Terms & ConditionsCookie settingsAccessibility statement