Windchill upgrade to 13 - conversion to flexible objects.

[Theodore_7]

One of our clients is planning an upgrade to Windchill 13. They need to make sure that all legacy change objects are converted to flexible change objects. They have run the conversion tool, which converted about 2000 change objects. However, there are 400 legacy change objects that are not eligible for conversion. These change objects are change requests and change notices that are still running without having a resolution date set yet. According to the documentation (article CS425124) they need to "complete all tasks associated to each change object so that Resolution Date is set automatically". The problem is that our client is just not possible to complete all tasks on those 400 change objects. What is the best approach or workaround to resolve this issue and proceed with the upgrade?

[Jimwang]

Open a technical support case via PTC eSupport to get support for it

[avillanueva]

So these are active change objects still in process? Is there a possibility that you can keep track of them, close the workflow and resume a new workflow once the conversion is complete? Is there anything common about them that is causing an issue? 

[mmeadows-3]

Change processes must be closed or meet other specific criteria for the flexible change conversion to work.

https://www.ptc.com/en/support/article/CS302277

Most customers close the existing change and open a new one that is flexible.  Then they can convert the closed ones without issue.

The system should have been set to mixed mode back when Windchill was upgraded to 11.x.  If it was and these are really long running changes, then your best option it to meet one of the acceptance criteria in that article.  Given the number of them, maybe someone out there has written a customization to 'duplicate' open change objects?

If these are faster turnaround changes, then maybe set to flexible in production and give it a month for the majority of the 400 open changes to cycle through.

[Theodore_7]

Thank you for your reply,

Yes it was in mixed mode and yes those were really long running changes created with custom workflows, something that i understand is pretty common for big companies.

That's why I thought that PTC would have a better solution in place than asking the client to complete all tasks..

Anyway the client decided to follow this path as the solution to write a custom readiness delegate is not guaranteed to work.

[BenLoosli]

Late to the thread as I have been on vacation.

What version of Windchill were they converting from? When I did our upgrade from 12.0.2 to 13.0.2, I had to do a 12.1.2 intermediate step to get the links converted because we had old change objects from 11.0 or 11.1 hanging around. Had to go to 12.1.2 to get the required states added to the right files. They had to be added in the Type Manager UI and not from the RB files in order for the convert tool to read the information properly. They could only be added after 12.1.2 as that is where the ability to add them in the UI was added.

Hope you got everything converted okay.