Skip to main content

Change Actions

About Change Actions​

Change Actions are used to track changes and release content in 3DExperience. If an object in 3DExperience is under "Change Control", this means a Change Action is required to release the content. Change Actions (CAs) may be orchestrated with Change Requests and/or Change Orders, which will be elaborated on in future sections.

Creating Change Actions​

Change Actions can be created in 3DSpace or in the Dashboard. Both create the same underlying data object, but they do look different. Depending on your business's processes, you may use one or the other exclusively. Below are trainings for each one. Note that in the future, Dassault will no longer support 3DSpace, so it is recommended to use the Dashboard widget if possible!

Creating in Dashboard (Preferred):

Change Execution

Creating in Space (Not Preferred, but still Supported):

Collaboration and Approvals

Adding Content to Change Actions, via Proposed or Realized Changes​

There are two ways to release content via a Change Action. If your company utilizes Work Under to track changes against engineering content, use Option 1 described. If your company does not utilize Work Under, and instead adds the already updated content to the CA for approval/release, use Option 2.

  1. Add the released, impacted content to the CA and determine the modification necessary. Then utilize Work Under to make changes to the new revision/branch created by the CA
  2. Manually create the new revision/branch of content. Add the already updated, unreleased content to the CA Proposed Changes for approval and release.

Using Realized Changes as a Releasing Mechanism Using Realized Changes and Work Under When utilizing Work Under, the Proposed and Realized Changes tabs serve different purposes. The Proposed Changes tab contains what needs to be updated, and the Realized Changes captures what was done to fulfill those requests. Each Proposed Change also has a place to document if the engineer addressed each line item (some may have ended up being unnecessary).

Using Proposed Actions as a Releasing Mechanism Proposed Actions for Releasing When adding content to Proposed Changes, you can either drag content into the Change Execution widget with the CA opened to Proposed Changes, or you can click the + button to search for content to add. The below video will demonstrate both methods. Always confirm that the Change Assessment is marked to move the content to Release.

Adding Applicability to Change Actions (i.e. Model Version, Manufacturing Plan, Date or Unit)​

Approving or Rejecting a Change Action Task​

Check out the Tasks training to learn how!