cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

PTC Respect Existing10.X Use Cases and Fundamentals with OIR when Making New Functionality for 11.X

PTC Respect Existing10.X Use Cases and Fundamentals with OIR when Making New Functionality for 11.X

Hello.

 

This is a Vote for Development to understand existing Use-Case (How something works now) when they make Changes at next major Release.  If a Behavior Changes they should have mechanism to allow older use-Case to still work.

 

Customer upgrades from 10.2 to 11.0 and has to deal with changing behavior introduced by PTC specifically around Rename, Save As, Auto-Associate not following Object Intialization Rules.  We as administrators give  clear expectations with OIR

 

Example 1: New 11.X Functionality in Auto-Associate has WIndchill Parts NOT following their OIR setting for Number Field.  For Example Part OIR is PreGenerated/Immutable OFF however NEW 11.X Auto-Associate Functionality makes the WTPart follow EPMDocument and populates with EPMNumnber.  In 10.X it would have shown (generated) and be replaceable.  Result New Functionality overwrites OIR.  PTC Gives an Org Level Preference "Force" but OIR are set at Context Level and so should the Preferences to correct any NEW Behaviors... OR Respect the OIR.

 

Example 2: Rename.  In 10.2 Number Field in Commonspace was Greyed Out.  In 11.X PTC decided to Fix Issue.. Developers do not appear to Respect Identity Attributes and existing Use-Cases.  By Fixing, they enable Number to be Modifable in Commonspace which is good for those that want that... but they did not give option for those who wanted to continue with the existing Use Case.

In this case our only option is to change Business Process, removing Modify Identity Access Controls for Groups, removing set state (or making a new state) from other who could set back to WIP to correct spelling errors but now risk changing Number of an object already sent to ERP System.