Data Management Capabilities > Managing Change > Change Management Administration > Change Association Rule Administration > Flexible Change Link Conversion > FlexibleChangeConverter Utility
  
FlexibleChangeConverter Utility
Use the FlexibleChangeConverter command-line utility to convert legacy change objects and links to the flexible model.
* 
Before using this utility, review the information outlined in Preparation and Planning for Flexible Change Conversion.
1. Open a Windchill shell.
2. Using administrative credentials, execute the following command:
java wt.change2.flexible.FlexibleChangeConverter -action <action_name>
The following actions are available. When performing conversion actions, the amount of time the action takes to complete depends on the number of change objects in Windchill.
report
Mode
Legacy
Mixed
Flexible
Actions
Generate a report file with information on the current state of various objects related to flexible change conversion.
Notes
For more information, see FlexibleChangeConverter Report.
setMixed
Mode
Legacy
Flexible
Actions
Set the change association mode to Mixed.
Notes
For more information, see Change Association Modes.
convertLinks
Mode
Legacy
Mixed
Actions
Create flexible change links that duplicate existing legacy change links.
Notes
The flexible change links created by this action are not activated. As a result, if you modify any converted objects or links, you must run the convertLinks action again.
* 
This action might take several hours to complete on systems with a large number of change objects.
convertAllObjects
Mode
Mixed
Actions
Convert all legacy change objects to flexible change objects.
Deactivate legacy change links.
Activate the duplicated flexible links created when executing the convertLinks action.
Notes
Flexible change objects implement the FlexibleChangeItem class.
* 
If the utility encounters any errors, the action fails and no change object are converted.
Due to the resources required, you must run this action when the system is offline.
convertEligibleObjects
Mode
Mixed
Actions
Convert eligible legacy change objects to flexible change objects.
Deactivate legacy change links.
Activate the duplicated flexible links created when executing the convertLinks action.
Notes
Flexible change objects implement the FlexibleChangeItem class.
* 
If the utility encounters any errors, the action skips the problematic object and continues processing eligible change objects.
This action might take several hours to complete on systems with a large number of change objects.
setFlexible
Mode
Legacy
Mixed
Actions
Set the change association mode to Flexible.
Notes
You cannot complete this action until all legacy change objects have been converted.
3. If you encounter errors, you can access a log file in the following location:
<Windchill>/logs/flexChangeConverterLogs
FlexibleChangeConverter Report
You can generate a report by executing the following command in a Windchill shell:
java wt.change2.flexible.FlexibleChangeConverter -action report
The output displays the location of a report file, which provides the following information:
Current mode
The first line identifies the current change association mode.
For more information, see Change Association Modes.
Legacy change object classes
The second line identifies any legacy change object classes.
A class is considered a legacy change object class if it does not implement the FlexibleChangeItem class.
If any legacy change object classes are found, the system cannot convert to Flexible mode.
Link converter delegates
Converter delegates are registered for legacy change link classes and used in the process of creating corresponding flexible links.
Each legacy change link type must have a registered converter delegate. If you are only using out-of-the-box change links, then the conversion delegates are provided.
If you have custom change links, see Convert Custom Links to Flexible Change Links.
Change object readiness delegates
Readiness delegates are registered for change object classes and used when determining if a change object is ready to be converted.
Out-of-the-box change objects classes have two readiness registered delegates: ResolutionDateReadinessDelegate and WorkflowReadinessDelegate. Only one delegate needs to pass for the object to be eligible for conversion.
Each change object type must have a registered readiness delegate. Delegates can be registered to parent classes to cover multiple change object types.
If you have custom change objects, or want information on modifying the out-of-the-box delegate behavior, see Convert Custom Links to Flexible Change Links.
Number of change links and objects
The report provide the following numbers to help with the conversion process:
Flexible change links
Unconverted legacy change links
Flexible change objects
Legacy change objects eligible for conversion
Legacy change objects not eligible for conversion
Each segment indicates how the number is distributed among link and object types.
Legacy change objects not eligible for conversion
The last section of the report is a list of legacy change objects that are not eligible for conversion.
The identity of the change object is provided, including the object type, number, version, and context.