Default Behavior for Engineering Changes

When an Engineering Change is created for an object, a default state-blocking route is created. This behavior can be changed by customizing the trigger.

Engineering Changes are designed to use Route Templates as the Reviewer List and Approval List. ENOVIA Business Process Services uses the tasks/assignees defined in the Route Template to create a state-based route. For the Reviewer List, the route must be completed for the Engineering Change to be promoted from the Review to the Approved state. For the Approval List, the route must be completed for the Engineering Change to be promoted from the Formal Approval to the Complete state.

If you do not want ENOVIA Business Process Services to create default routes with no tasks/assignees, you must define custom triggers. For reference, these are the ENOVIA objects that control this functionality:

The Reviewer List uses:


  • JPO: emxCommonEngineeringChange
  • Method: createRoute
  • eService Trigger Program Parameters Object:
    • Name: PolicyEngineeringChangeStateEvaluatePromoteAction
    • Revision: CreateReviewerRoute

The Approval List uses:


  • JPO: emxCommonEngineeringChange
  • Method: createApprovalRoute
  • eService Trigger Program Parameters Object:
    • Name: PolicyEngineeringChangeStateValidatePromoteAction
    • Revision: CreateApprovalRoute

See Designing Triggers for details on creating custom triggers.