Enforcing Change Process for Development Parts

ECM replaces DECO (Development Engineering Change Order) in 2017x. However, some users who upgrade from a previous release may have DECO objects for parts that have not been released. Therefore, existing DECO objects that are connected to development parts are supported in 2017x and users may release parts attached to any existing DECO. Version 2015x does not support creating new DECO objects. Administrators can enforce change process created in ECM or DECO for development parts.

Change process can be controlled by setting this key to either true or false:

"emxTeamEngineering.TeamChange.Mandatory"

  • If this key is set to true, then change process is required for development parts:
  • If the key is set to false and the change process is connected to current or previous revisions, the change process is mandatory for development parts.
  • If the key is set to false and the change process is not connected to current or previous revisions, the change process is optional for development parts.