Flexible Change Associations Migration Survey

[JeffZemsky]

Several releases ago, Windchill introduced the concept of “Flexible Links” that allows the network of Change Management objects to be configured based on the rules and practices of your company. Along with the introduction of this capability, a conversion tool has been provided that will migrate the existing “Legacy Links” to their corresponding “Associated Process” flexible link. The tool offers the ability to operate in a “Mixed Mode” so that the legacy objects can be completed in their workflows, or to operate in a “Full Flexible” mode by migrating all existing “Legacy Links” to their equivalent “Flexible Link”.

As we plan our next major Windchill release (estimated December 2021), we would like to eliminate the support for the “Legacy Links” completely. This would mean that all Change Management and Quality Management objects have been converted to the “Flexible Links” and the system is operating in a “Full Flexible” mode.

We'd like to hear from you.  We are running a survey for the next through May 31st to get feedback on where you are with your journey to Flexible Change Associations. 

Flexible Change Association Survey

Thank you for your support

[rhart]

I'm stuck at question 3 @JeffZemsky , how can I find out:

"What mode is your Change Management process operating in currently?

There's several Change Association Rules ...

[JeffZemsky]

@rhart  - if you run the FlexibleChangeConverter tool using the report option it will tell you which version you are running.  You can find more information here

FlexibleChangeConverter Utility

[rhart]

Thankyou for your answer @JeffZemsky , I ran the report but I'm still not completely sure of the answer.

Current Windchill mode: Mixed

No legacy change object classes were found.

Legacy change link classes and registered FlexibleChangeLinkConverterDelegate classes:
Class: wt.change2.AddressedBy2 Delegates: wt.change2.flexible.DefaultFlexibleChangeLinkConverterDelegate
Class: wt.change2.FormalizedBy Delegates: wt.change2.flexible.DefaultFlexibleChangeLinkConverterDelegate

Change object classes and registered FlexibleChangeItemReadinessDelegate classes for action convertLinks:
Class: wt.change2.WTChangeRequest2 Delegates: [wt.change2.flexible.AdministrativeLockReadinessDelegate, wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: wt.change2.WTVariance Delegates: [wt.change2.flexible.AdministrativeLockReadinessDelegate, wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Delegates: [wt.change2.flexible.AdministrativeLockReadinessDelegate, wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Delegates: [wt.change2.flexible.AdministrativeLockReadinessDelegate, wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: wt.change2.WTChangeOrder2 Delegates: [wt.change2.flexible.AdministrativeLockReadinessDelegate, wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: wt.change2.WTChangeIssue Delegates: [wt.change2.flexible.AdministrativeLockReadinessDelegate, wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]

Change object classes and registered FlexibleChangeItemReadinessDelegate classes for action convertReplicatedLinks:
Class: wt.change2.WTChangeRequest2 Delegates: [wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: wt.change2.WTVariance Delegates: [wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Delegates: [wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Delegates: [wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: wt.change2.WTChangeOrder2 Delegates: [wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]
Class: wt.change2.WTChangeIssue Delegates: [wt.change2.flexible.ResolutionDateReadinessDelegate, wt.change2.flexible.WorkflowReadinessDelegate]

Total number of flexible change links: 8,031

Total number of converted legacy change links: 0
Class: wt.change2.AddressedBy2 Total: 66 Count: 0 Percentage: 0%
Class: wt.change2.FormalizedBy Total: 24 Count: 0 Percentage: 0%

Total number of unconverted legacy change links: 90
Class: wt.change2.AddressedBy2 Total: 66 Count: 66 Percentage: 100%
Class: wt.change2.FormalizedBy Total: 24 Count: 24 Percentage: 100%

Total number of flexible change objects: 15,258
Class: wt.change2.WTChangeRequest2 Total: 6,868 Count: 6,799 Percentage: 98.99%
Class: wt.change2.WTVariance Total: 0 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Total: 6 Count: 6 Percentage: 100%
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Total: 6 Count: 6 Percentage: 100%
Class: wt.change2.WTChangeOrder2 Total: 6,436 Count: 6,367 Percentage: 98.92%
Class: wt.change2.WTChangeIssue Total: 2,111 Count: 2,080 Percentage: 98.53%

Total number of local legacy change objects eligible for conversion: 0
Class: wt.change2.WTChangeRequest2 Total: 6,868 Count: 0 Percentage: 0%
Class: wt.change2.WTVariance Total: 0 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Total: 6 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Total: 6 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeOrder2 Total: 6,436 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeIssue Total: 2,111 Count: 0 Percentage: 0%

Total number of administratively locked legacy change objects eligible for conversion: 0
Class: wt.change2.WTChangeRequest2 Total: 6,868 Count: 0 Percentage: 0%
Class: wt.change2.WTVariance Total: 0 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Total: 6 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Total: 6 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeOrder2 Total: 6,436 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeIssue Total: 2,111 Count: 0 Percentage: 0%

Total number of local legacy change objects not eligible for conversion: 169
Class: wt.change2.WTChangeRequest2 Total: 6,868 Count: 69 Percentage: 1%
Class: wt.change2.WTVariance Total: 0 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Total: 6 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Total: 6 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeOrder2 Total: 6,436 Count: 69 Percentage: 1.07%
Class: wt.change2.WTChangeIssue Total: 2,111 Count: 31 Percentage: 1.46%

Total number of administratively locked legacy change objects not eligible for conversion: 0
Class: wt.change2.WTChangeRequest2 Total: 6,868 Count: 0 Percentage: 0%
Class: wt.change2.WTVariance Total: 0 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.plan.CAPAActionPlan Total: 6 Count: 0 Percentage: 0%
Class: com.ptc.qualitymanagement.capa.request.CAPAChangeRequest Total: 6 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeOrder2 Total: 6,436 Count: 0 Percentage: 0%
Class: wt.change2.WTChangeIssue Total: 2,111 Count: 0 Percentage: 0%

No legacy change objects eligible for conversion have been found. Run the convertLinks action.

[JeffZemsky]

@rhart  based upon the results you are running in Mixed mode and have small number of Legacy links that will need to be further converted

[jbailey]

@JeffZemsky How do you run this when you are not using basic authentication?  With the Windchill shell commands there's a --javaargs command to pass... 

[shussaini]

Here is the extract from help center. hope this helps.

>>>

Command line java clients executed via the windchill script (or directly by calling java [classname]) may be unable to authenticate against more advanced authentication solutions, such as single sign-on. The Windchill server is a trusted server and a user name can be specified as a command line argument to execute the command as a particular user. When using the windchill script, the --javaargs argument can be used to specify this user: windchill --javaargs="-Dwt.auth.trustedAuth.username=username" <windchill java class>.

regards
~Syed

[avillanueva]

Has this pinned message outlived its usefulness?