|
Legacy Mode
|
Everything on the system behaves as it did in previous releases. Change associations continue to use the AddressedBy2 and FormalizedBy model.
This is the default mode for systems upgrading to Windchill 11.0 or later.
|
|
Mixed Mode
|
Windchill allows a combination of legacy and flexible change links:
• New change objects use the FlexibleChangeLink model. As a result, existing change association rules are enforced for new change objects.
• Change objects that exist prior to moving to Mixed mode are considered legacy objects. These objects continue to use the AddressedBy2 and FormalizedBy model.
• Any new objects created from a legacy change object continue to use the AddressedBy2 and FormalizedBy model.
This is the default mode for new Windchill 11.0 installations and later.
From here, you can use the FlexibleChangeConverter utility to convert eligible legacy change objects to the FlexibleChangeLink model.
If links have a role object that is not a flexible change item, they are not converted. All objects must be converted before moving to Flexible mode.
|
|
Flexible Mode
|
All new and existing change objects use the FlexibleChangeLink model.
Eventually, this will be the default mode for all new Windchill installations.
|
|
FlexibleChangeItem
|
|
To move to Flexible mode, all new and existing change objects must implement the FlexibleChangeItem class.
If your system includes objects that do not implement FlexibleChangeItem, then you can only use the FlexibleChangeConverter utility to generate a report and move to Mixed mode. You cannot perform any of the conversion commands.
Objects that do not implement FlexibleChangeItem. For example, any custom extensions of out-of-the-box change objects.
|
|
Eligibility for Change Management Object Conversion
|
|
Legacy change objects must pass a few criteria before they are eligible for conversion:
• The change object class must support flexible links (the FlexibleChangeLink class).
• The change object class must have a readiness delegate registered.
• All legacy change link classes must have a registered converter delegate.
There are converter and readiness delegates provided for out-of-the-box change objects and links. If you have custom change objects or links, see Convert Custom Links to Flexible Change Links.
|
|
Flexible Mode Limitations
|
|
Flexible mode has two limitations:
• Loading legacy data
• Importing packages that include legacy data
If your system is in Flexible mode and you must load or import legacy data, you can use the setMixed action to reset Windchill to Mixed mode.
To move back to Flexible mode, rerun the conversion utility actions.
|
|
Link Converter Rules
|
|
Link converter rule files specify how legacy links are duplicated as change process links.
You should review and configure these files to ensure the rules match your change association rules as closely as possible. For more information, see Configure Link Converter Rules.
If you have custom links, you must create a custom converter rule file. For more information, see Convert Custom Links to Flexible Change Links.
|
|
Summary Reports for Current Status
|
|
You can update reports that use the deprecated legacy links.
For more information, see Flexible Change Links for Query Builder.
|
|
Review Change Association Rules
|
|
PTC strongly recommends that any additional change association rules are established and stable before running the conversion utility. For more information, see Define Change Association Rules and Change Association Rules Table.
If your system has any link customizations, see Change Associations: Deprecated APIs.
|
|
Review Change Process Workflows
|
|
PTC strongly recommends that you review and update existing change process workflows.
For more information, see Change Workflow Closure.
|