# Configuring Change Action Paths & Steps

_Change Action Paths_ allow Admins to configure a _Change Control_, _Quality Event (Change Control_ object type only), or _Change Plan_ to organize _Change Actions_ in sequential _Action Steps_. QMS will automatically start _Change Actions_ in the order based on their sequencing in the _Change Action Path_'s configuration. 

## Accessing Change Action Path Configurations

To view and edit _Change Action Path_ configurations, navigate to **Admin > Configuration > QMS Action Path Configurations**.

## Configuration Overview {#configuration-overview}

The following list is an overview of how to configure change action paths and steps:

* If the relevant **Parent Object Type** is not already configured, create the related <a href="/en/gr/32857/">object types</a> layout needed for your path before you begin configuration. Custom _Parent Locked States_ should also be configured before creating a change action path.
* If your organization uses _Change Action Paths_ and also copies _Change Controls_, _Quality Event Change Controls_, or _Change Plans_ to create new object records, the _Action Path ID_ field on these objects should have the _Do not copy this field in Copy Record_ attribute enabled.
* **Create a Change Action Path**. _Change Actions_ are child actions that govern the steps needed to implement a change. The change control to kick off a subset of Actions. 
* **Create _Action Steps_ in the _Change Action Path_**. Click into each stage to define the specific change actions that belong to each step. When those actions are complete, the _Change Control_ is moved forward to kick off additional actions or approval workflows.
* **Add the _Add Action Path_ event action to the parent object's lifecycle**. Configuring the _Add Action Path_ event action adds the _Change Action Path_ to the parent object's lifecycle, ensuring _Change Actions_ start in the lifecycle states specified in the _Change Action Path's_ configuration.
* **Assign an _Action Step_ to a _Change Action Template_**. Users can assign an _Action Step_ to a _Change Action Template_, which then assigns _Change Actions_ created from a template to that _Action Step_ in a _Change Control_ or _Change Plan_.

## Creating Change Action Paths {#create-change-action-paths}

To create a _Change Action Path_:

1. From the **QMS Action Path Configurations** page, click **Create**. 
2. Enter a **Label** and **Name** for the _Change Action Path_. 
3. Use the **Status** selector to make the field active or inactive. 
4. Optional: Enter a **Description**.
5. Optional: Select **Yes** or **No** for the **Hide Other Actions** option to hide or display the _Other Actions_ section on a _Change Control_ record. Users utilize this section to add _Change Actions_ outside of _Action Steps_.
6. Optional: Select **Yes** or **No** for the **Allow Change Actions to be added to In Progress Action Steps** option. Once enabled, users can add _Change Actions_ to an _In Progress_ _Action Step_.
7. Select the **Parent Object** in the drop-down.
8. Select the **Parent Object Type** in the drop-down. Learn more about <a href="/en/gr/32857/">object types</a>.
9. Select **Change Action** as the **Action Object**.
10. Select one or more **Parent Locked States**. If a parent object is in any of these states, it will not be moved.
11. Click **Save**.

## Defining Change Action Steps {#define-change-action-steps}

To create _Change Action Steps_:

1. From the **QMS Action Path Configuration** page, select a _Change Action Path_. Under _QMS Action Step Configurations_, click **Edit**.
2. Enter a **Label**.
3. Select the **Parent Start State** from the drop-down. When parent objects reach this state, actions in the included action states will be moved to the _Action Start State_.
4. Select the **Action Start State** from the drop-down. Actions in the included action states will be moved to this state when the parent reaches the _Parent Start State_.
5. Select the **Included Action States**. Actions must be in the included action states to be moved to the _Action Start State_ when the parent reaches the _Parent Start State_.
6. Select the **Action Finished States**. This is the terminal state for actions in this step.  When all actions are in this step, the parent will be moved to the _Parent Finish State_.
7. Select the **Parent Finish State**. This is the destination state for the parent object when all actions have moved to one of the _Action Finish States_.
8. Optional: Move the **Display Order**.
9. Optional: Under **Default Fields to Display**, click **Edit** to set the default columns and column order to display for _Action Steps_.
10. Click **Save**.

All actions within a step can be executed in parallel, while actions in subsequent steps remain in the initial state.

## Creating an Add Action Path Event Action

After creating a _Change Action Path_, you must add it to the parent object's lifecycle.

To do this, <a href="/en/gr/51700/#object-event-actions">create</a> the _Add Action Path_ event action on the _Create Record_ event on the parent object lifecycle. When creating the event action, from the _Action Path_ drop-down, select the _Change Action Path_ you created for the parent object.

## Assigning Change Action Templates to Action Steps

<a href="/en/gr/726155/">_Action Steps_</a> help organizations execute _Change Actions_ in a particular sequence. Users can assign an _Action Step_ to a _Change Action Template,_ which then assigns _Change Actions_ <a href="/en/gr/57968807/">created from a template</a> to that _Action Step_ in a _Change Control_ or _Change Plan_.

Before _Change Action Templates_ can be assigned to an _Action Step_, Admins must add the _Change Action Template Action Path & Step_ control to a section in the _Change Action Template_ object layout. Once the _Change Action Template Action Path & Step_ control has been added to the object layout, users can assign a _Change Action Template_ to an _Action Step_. Once a _Change Action_ is created from the _Change Action Template_, the template's _Action Step_ is assigned to the _Change Action_.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: When an <em>Action Step</em> (such as Pre-Implementation) is already <em>In Progress</em> or <em>Closed</em>, users cannot create a <em>Change Action</em> from a <em>Change Action Template</em> for that <em>Action Step</em>.</p>
    </div>
  </div>
</div>



### Limitations 

* _Quality Event_ object types are limited to the _Change Control_ object type. 
* A path can have up to five _Action Steps_ for each _Change Action Path_. 
* A path can only be saved if there is at least one _Change Action Step_. 
* A path cannot have more than one _Change Action Step_ with the same _Parent Start State_. 
* A _Change Action Template_ can only be assigned to one path.
* If parent objects are in a _Locked State_, they will not be moved.

## Related Permissions 

Only Admins can configure _Change Action Paths_ and _Change Action Steps_. The following permissions affect your users ability to configure _Action Paths_ in your Vault.

|Type|Permission|Controls
|--- |--- |--- |
|Security Profile|Objects: Change Action: Object Control Permissions: Valid Action Step Column|Ability to view the _Valid Action Step Column_ on the _Change Action_ object.|
|Security Profile|Objects: Change Control: Object Control Permissions: Action Step.|Ability to view the _Action Step_ section in the _Change Control_ object.|
|Security Profile|Objects: Change Plan: Object Control Permissions: Action Step|Ability to view the _Action Step_ section in the _Change Plan_ object.
|Security Profile|Objects: Quality Event: Object Control Permissions: Action Step|Ability to view the _Action Step_ section in the _Quality Event_ object.|
|Security Profile|Admin: View Admin Information|Ability to view the _Admin_ tab collection.|