About Working Under a Change Action

You must have one of the following roles to start, suspend, resume, or stop working under a change action:

• Leader role, or an equivalent app-specific role, and a license for Configuration Engineer or Change Manager
• Collaborative Industry Innovator role and assignment as the owner or a contributor to the change action

Objects that are created while working under a change action are change-controlled by default. They are under strict change control. All of the child objects created below them are also change-controlled by default. You must make all changes to objects under strict change control using the change action listed in the Change tab of the object's properties.

Objects that are created when you are not working under a change action can be enabled for change control by any user with the Leader role or an equivalent app-specific role, and who is also licensed for Change Manager or Configuration Engineer. Once you enable change control for these objects, they are under unified change control. You can make changes to an object under unified change control by selecting any change action in the In Work state to work under. After you make the first change to an object that is under unified change control, all subsequent changes to that object must be made under that same change action until the change action is Released.

After you select a change action in the In Work state to work under, most actions that you perform are logged in the Realized Changes tab of the change action. The change action under which changes are being logged is displayed in the Change tab when you view the object's properties. You can see under which change action changes to an object are currently being logged by clicking in the object's properties.

Some actions, such as adding a document to another object as a specification or removing it, are not tracked in the Realized Changes tab of the change action.