Article - CS302277
Information about readiness delegates used by the "FlexibleChangeConverter" in Windchill PDMLink
Modified: 11-Nov-2025
Applies To
- Windchill PDMLink 11.0 to 13.1
Description
- Information about readiness delegates used by the FlexibleChangeConverter
- what makes a Legacy change object eligible to be converted when running the convertLinks tool
- How does the FlexibleChangeConverter determine which objects are eligible for conversion
- Some objects are not getting converted when running the FlexibleChangeConverter
- Encountered a flexible link issue while running Windu pre-upgrade mandatory tasks. ConverLinks log reports too many change objects to complete manually one by one - how to resolve it through customization.
- How to interpret entries like below in convertLinks.log after running convertLinks action of FlexibleChangeConverter utility:
The following is a list of legacy change objects that are not eligible for conversion:
Identity: "Change Request - xxxx"
Reasons:
Change object does not have a resolution date: "Change Request - xxxx"
Change object has a running workflow that does not handle closure: "Change Request - xxxx"
- After run command java wt.change2.flexible.FlexibleChangeConverter -action convertLinks, it shows error
Determining eligibility for change object class: wt.change2.WTChangeIssue
The following is a list of legacy change objects that are not eligible for conversion:
Identity: "DefectCase - PR61362"
Reasons:
Change object is not administratively locked and will continue with other readiness checks to determine state of conversion.: "DefectCase - PR61362"
Change object does not have a resolution date: "DefectCase - PR61362"
Change object has a running workflow that does not handle closure: "DefectCase - PR61362"
This is a printer-friendly version of Article 302277 and may be out of date. For the latest version click CS302277