# Configuring Cascading State Changes for Content Plans (RIM)

To help your users manage complex content plan hierarchies, new Vault implementations on or after the 19R3 release include a configuration to move ascendant _Content Plan_ records to a new lifecycle state when descendant records move to new states. For example, Vault can move ascendant _Content Plan_ records to an active _Draft_ lifecycle state when a _Content Plan Item_ record moves from _Inactive_ to _Draft_ as an alternative to inactivating or deleting sections not in use. This article discusses how to set up this configuration in Vaults created before 19R3.

Much of the configuration described here leverages the _Content Plan Hierarchy State Change_ system action. This action is asynchronous, meaning it runs in the background without preventing users from continuing their work. See [Managing Content Plans with a Lifecycle](/en/lr/45365/#content-plan-state-change) for details about how this action can operate independently.

<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>: This feature is only available on RIM Submissions Vaults.</p>
    </div>
  </div>
</div>



## Configuration to Activate Ascendant Records {#activate-ascendant-records}

In this configuration, Vault moves ascendant _Content Plan_ records to an active _Draft_ lifecycle state when a descendant _Content Plan_ or _Content Plan Item_ record moves from _Inactive_ to _Draft_. When configured:

*  Moving an inactive _Content Plan Item_ record to the _Draft_ state activates the immediate parent _Content Plan_ record but does not activate sibling _Content Plan Item_ records or parent _Content Plan_ records at other levels of the hierarchy.
* Moving an inactive _Content Plan_ record to the _Draft_ state activates any parent _Content Plan_ records in the hierarchy, as well as each parent's child records, without activating sibling _Content Plan_ records.

### Configuration Overview

1. Add [new lifecycle states][8] to the _Content Plan_ and _Content Plan Item_ object lifecycles.
2. Create [new object workflows][9].
3. Set up [entry actions and user actions][10] on the _Content Plan_ and _Content Plan Item_ object lifecycles.


#### Adding New Object Lifecycle States {#activate-lc-states}

Navigate to **Admin > Configuration > Object Lifecycles**. Ensure that both your _Content Plan_ and _Content Plan Item_ lifecycles include _Inactive_ and _Draft_ states already. If they don't, add those first.

[Add the following new active states](/en/lr/30683/#define-states) to the _Content Plan_ and _Content Plan Item_ object lifecycles:

|Lifecycle|State Label|Records in this state become inactive|Description|
|--- |--- |--- |--- |
|Content Plan Lifecycle|Activate Parent (Intermediate)|No|Intermediate state used to initiate the state change from _Inactive_ to _Draft_ on _Content Plan_ parent records. Vault enacts this state in conjunction with the _Activate Section_ state to activate all descendant records.|
|Content Plan Lifecycle|Activate Section (Intermediate)|No|Intermediate state used to initiate the state change from _Inactive_ to _Draft_ for all of the _Content Plan_ record's descendants. Vault enacts this state in conjunction with the _Activate Parent_ state to activate ascendant parent records in the hierarchy.|
|Content Plan Item Lifecycle|Set Parent to Draft (Intermediate)|Yes|Intermediate state used to initiate the state change to _Draft_ on _Content Plan_ parent records.|

#### Creating Object Workflows {#activate-workflows}

Navigate to **Admin > Configuration > Workflows** to [add the following new workflows](/en/lr/33550/ ):

|Workflow Label|Object Lifecycle|Allow auto-start from entry action and event action|Workflow Steps|
|--- |--- |--- |--- |
|Change Content Plan to Draft|Content Plan Lifecycle|Yes|Add a _State Change_ step and set the **Next State** to **Draft**.|
|Change Content Plan Item to Draft|Content Plan Item Lifecycle|Yes|Add a _State Change_ step and set the **Next State** to **Draft**.|

#### Setting Up Entry Actions & User Actions {#activate-actions}

Set up the following [entry actions](/en/lr/59885/#entry-actions) and [user actions](/en/lr/59885/#user-actions) on the _Content Plan_ object lifecycle:

<table class="wbord">
  <tr>
    <td>
      <p>
        <strong>Lifecycle State</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Type</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Conditions</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="2">
      <p>
        Activate Parent (Intermediate)
      </p>
    </td>
    <td rowspan="2">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Parent</strong>
      </p>
      <p>
        Change State To: <strong>Activate Parent (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record&#8217;s State: <strong>Draft</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan to Draft</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="4">
      <p>
        Activate Section (Intermediate)
      </p>
    </td>
    <td rowspan="4">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plan</strong>
      </p>
      <p>
        Change State To: <strong>Activate Section (Intermediate)</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plan Items</strong>
      </p>
      <p>
        Change State To: <strong>Draft</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object:<strong> Parent</strong>
      </p>
      <p>
        Change State To: <strong>Activate Parent (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record&#8217;s State: <strong>Draft</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan to Draft</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Draft
      </p>
    </td>
    <td>
      <p>
        Entry Action
      </p>
    </td>
    <td colspan="2">
      <p>
        On the <em>Draft</em> state, delete all existing entry actions related to changing parent or child states.
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Inactive
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Activate Section (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Draft</strong>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Draft</em> user action
      </p>
    </td>
  </tr>
</table>

Set up the following [entry actions](/en/lr/59885/#entry-actions) and [user actions](/en/lr/59885/#user-actions) on the _Content Plan Item_ object lifecycle. Configure these in the order they appear in the table below.

<table class="wbord">
  <tr>
    <td>
      <p>
        <strong>Lifecycle State</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Type</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Conditions</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="2">
      <p>
        Set Parent to Draft (Intermediate)
      </p>
    </td>
    <td rowspan="2">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plan</strong>
      </p>
      <p>
        Change State To: <strong>Activate Parent (Intermediate)</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan Item to Draft workflow</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Inactive
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Parent to Draft (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Draft</strong>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Draft</em> user action
      </p>
    </td>
  </tr>
</table>

## Configuration for Backwards State Changes

When a content plan section reverts to a lower state, for example, when it moves from the _Baselined_ state back to the _Draft_ state, the section's parent records should no longer be in the _Baselined_ state. This section includes configurations for applying backwards state changes up the content plan hierarchy.

If your Vault has custom configurations for the _Content Plan_ object lifecycle or lifecycle states, you may need to make additional changes to your configuration.

### Baselined or Locked to Draft Configuration

In this configuration, Vault moves ascendant _Content Plan_ records to an active _Draft_ lifecycle state when a descendant _Content Plan_ or _Content Plan Item_ record moves from the _Baselined_ or _Locked_ state to _Draft_. When configured:
*  Moving a _Content Plan Item_ record from the _Baselined_ or _Locked_ state to the _Draft_ state cascades the _Draft_ state to its ascendant parent records in the hierarchy without updating sibling _Content Plans_ or _Content Plan Items_.
*  Moving a _Content Plan_ record from the _Baselined_ or _Locked_ state to the _Draft_ state cascades the _Draft_ state to its descendant records and any ascendant parent records that are also in the _Baselined_ or _Locked_ state.

#### Configuration Overview

1. Add [new lifecycle states][14] to the _Content Plan_ object lifecycle.
2. Set up [entry actions and user actions][15] on the _Content Plan_ and _Content Plan Item_ object lifecycles.

#### Creating New Lifecycle States {#baselined-to-draft-lc-states}

[Add the following new active states](/en/lr/30683/#define-states) to the _Content Plan_ lifecycle:

|Lifecycle|State Label|Records in this state become inactive|Description|
|--- |--- |--- |--- |
|Content Plan Lifecycle|Set Parent to Draft (Intermediate)|No|Intermediate state used to initiate the backwards state change to Draft on Content Plan parent records. Vault enacts this state in conjunction with Set Section to Draft (Intermediate) state to set all descendant records to Draft.|
|Content Plan Lifecycle|Set Section to Draft (Intermediate)|No|Intermediate state used to cascade the backwards state change to Draft for all Content Plan descendant records. Vault enacts this state in conjunction with the Set Parent to Draft (Intermediate) state to set the record's parents in the hierarchy to Draft.|


#### Setting Up Entry Actions & User Actions {#baselined-to-draft-actions}

Set up the following [entry actions](/en/lr/59885/#entry-actions) and [user actions](/en/lr/59885/#user-actions) on the _Content Plan_ object lifecycle:

<table class="wbord">
  <tr>
    <td>
      <p>
        <strong>Lifecycle State</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Type</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Conditions</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="2">
      <p>
        Set Parent to Draft (Intermediate)
      </p>
    </td>
    <td rowspan="2">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Parent</strong>
      </p>
      <p>
        Change State To:<strong> Set Parent to Draft (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan to Draft</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="4">
      <p>
        Set Section to Draft (Intermediate)
      </p>
    </td>
    <td rowspan="4">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plans</strong>
      </p>
      <p>
        Change State To: <strong>Set Section to Draft (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft, Inactive</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plan Items</strong>
      </p>
      <p>
        Change State To: <strong>Draft</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft, Inactive</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Parent</strong>
      </p>
      <p>
        Change State To: <strong>Set Parent to Draft (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft, Inactive</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan to Draft</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Baselined
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Section to Draft (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Draft</strong>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Draft</em> user action
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Locked
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Section to Draft (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Draft</strong>
      </p>
      <p> Note: This replaces the existing <em>Change State to Draft</em> user action
      </p>
    </td>
  </tr>
</table>

Set up the following and [user actions](/en/lr/59885/#user-actions) on the _Content Plan Item_ object lifecycle:

| Lifecycle State| Action | Action Type | Action Conditions|
|--- |--- |--- |--- |
| Baselined | User Action | Change State to | Select the **Set Parent to Draft (Intermediate)** state <br> <br> Action Label: **Change State to Draft** <br> <br> Note: This replaces the existing _Change State to Draft_ user action |
| Locked | User Action | Change State to | Select the **Set Parent to Draft (Intermediate)** state <br> <br> Action Label: **Change State to Draft** <br> <br> Note: This replaces the existing _Change State to Draft_ user action |

### Locked or Published to Baselined Configuration

In this configuration, Vault moves ascendant _Content Plan_ records to an active _Baselined_ lifecycle state when a descendant _Content Plan_ or _Content Plan Item_ record moves from the _Locked_ or _Published_ state to _Baselined_. When configured:
*  Moving a _Content Plan Item_ record from the _Locked_ or _Published_ state to the _Baselined_ state cascades the _Baselined_ state to its ascendant parent records in the hierarchy that are also in the _Locked_ or _Published_ state without updating sibling _Content Plans_ or _Content Plan Items_.
*  Moving a _Content Plan_ record from the _Locked_ or _Published_ state to the _Baselined_ state cascades the _Baselined_ state to its descendant records and any ascendant parent records that are also in the _Baselined_ or _Locked_ state.

#### Configuration Overview

1. Add [new lifecycle states][11] to the _Content Plan_ object lifecycle.
2. Create [new object workflows][12].
3. Set up [entry actions and user actions][13] on the _Content Plan_ and _Content Plan Item_ object lifecycles.

#### Creating New Lifecycle States {#locked-to-basedlined-lc-states}

[Add the following new active states](/en/lr/30683/#define-states) to the _Content Plan_ lifecycle:

|Lifecycle|State Label|Records in this state become inactive|Description|
|--- |--- |--- |--- |
|Content Plan Lifecycle|Set Parent to Baselined (Intermediate)|No|Intermediate state used to initiate a state change to the previous _Baselined_ state on _Content Plan_ parent records. Vault enacts this state change in conjunction with the _Set Section to Baselined (Intermediate)_ state to move descendant records to _Baselined_.|
|Content Plan Lifecycle|Set Section to Baselined (Intermediate)|No|Intermediate state used to initiate a state change to the previous _Baselined_ state for all _Content Plan_ descendant records. Vault enacts this state change in conjunction with _Set Parent to Baselined (Intermediate)_ state to move ascendant parent records in the hierarchy to _Baselined_.|
|Content Plan Item Lifecycle|Set Parent to Baselined (Intermediate)|No|Intermediate state used to initiate a state change to the previous _Baselined_ state on the _Content Plan Item_ record's parents in the hierarchy.|

#### Creating Object Workflows {#locked-to-basedlined-workflows}

Navigate to **Admin > Configuration > Workflows** to [add the following new workflows](/en/lr/33550/ ):

|Workflow Label|Object Lifecycle|Allow auto-start from entry action and event action|Workflow Steps|
|--- |--- |--- |--- |
|Change Content Plan to Baselined|Content Plan Lifecycle|Yes|Add a _State Change_ step and set the **Next State** to **Baselined**.|
|Change Content Plan Item to Baselined|Content Plan Item Lifecycle|Yes|Add a _State Change_ step and set the **Next State** to **Baselined**.|

#### Setting Up Entry Actions & User Actions {#locked-to-basedlined-actions}

Set up the following [entry actions](/en/lr/59885/#entry-actions) and and [user actions](/en/lr/59885/#user-actions) on the _Content Plan_ object lifecycle:

<table class="wbord">
  <tr>
    <td>
      <p>
        <strong>Lifecycle State</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Type</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Conditions</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="2">
      <p>
        Set Parent to Baselined (Intermediate)
      </p>
    </td>
    <td rowspan="2">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan to Baselined</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Parent</strong>
      </p>
      <p>
        Change State To: <strong>Set Parent to Baselined (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft, Baselined</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="4">
      <p>
        Set Section to Baselined (Intermediate)
      </p>
    </td>
    <td rowspan="4">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plans</strong>
      </p>
      <p>
        Change State To: <strong>Set Section to Baselined (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Inactive, Baselined</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Items Plans</strong>
      </p>
      <p>
        Change State To: <strong>Baselined</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Inactive, Baselined</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan to Baselined</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Parent</strong>
      </p>
      <p>
        Change State To: <strong>Set Parent to Baselined (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft, Inactive, Baselined</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Baselined
      </p>
    </td>
    <td>
      <p>
        Entry Action
      </p>
    </td>
    <td colspan="2">
      <p>
        On the <em>Baselined</em> state, delete all existing entry actions related to changing parent or child states.
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Locked
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Section to Baselined (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Baselined</strong>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Baselined</em> user action
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Published
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Section to Baselined (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Baselined</strong>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Baselined</em> user action
      </p>
    </td>
  </tr>
</table>

Set up the following [entry actions](/en/lr/59885/#entry-actions) and [user actions](/en/lr/59885/#user-actions) on the _Content Plan Item_ object lifecycle:

<table class="wbord">
  <tr>
    <td>
      <p>
        <strong>Lifecycle State</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Type</strong>
      </p>
    </td>
    <td>
      <p>
        <strong>Action Conditions</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td rowspan="2">
      <p>
        Set Parent to Baselined (Intermediate)
      </p>
    </td>
    <td rowspan="2">
      <p>
        Entry Action
      </p>
    </td>
    <td>
      <p>
        Change related object lifecycle state
      </p>
    </td>
    <td>
      <p>
        Related Object: <strong>Content Plan</strong>
      </p>
      <p>
        Change State To: <strong>Set Parent to Baselined (Intermediate)</strong>
      </p>
      <p>
        Conditions On Related Records: <strong>Yes</strong>
      </p>
      <p>
        Condition: <strong>Exclude related records in the following lifecycle states</strong>
      </p>
      <p>
        Related Record's State: <strong>Draft, Baselined</strong>
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Start Workflow
      </p>
    </td>
    <td>
      <p>
        Start Workflow: <strong>Change Content Plan Item to Baselined</strong> workflow
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Locked
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Parent to Baselined (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Baselined</strong>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Baselined</em> user action
      </p>
    </td>
  </tr>
  <tr>
    <td>
      <p>
        Published
      </p>
    </td>
    <td>
      <p>
        User Action
      </p>
    </td>
    <td>
      <p>
        Change State to
      </p>
    </td>
    <td>
      <p>
        Select the<strong> Set Parent to Baselined (Intermediate)</strong> state
      </p>
      <p>
        Action Label: <strong>Change State to Baselined</strong>
      </p>
      <p>
      </p>
      <p>
        Note: This replaces the existing <em>Change State to Baselined</em> user action
      </p>
    </td>
  </tr>
</table>

### Draft to Baselined Configuration

In this configuration, moving a _Content Plan_ record from the _Draft_ state to the _Baselined_ state cascades the _Baselined_ state to all of the _Content Plan's_ active descendant records, but not to its parent records. This configuration uses the [_Content Plan Hierarchy State Change_ action](/en/lr/45365/#content-plan-state-change) so that Vault can change the state of the records asynchronously.

To configure this, update the existing _Change State to Baselined_ [user action](/en/lr/59885/#user-actions) on the _Content Plan_ object lifecycle:

|Lifecycle State|Action|Action Type|Action Conditions|
|--- |--- |--- |--- |
|Draft|User Action|Content Plan Hierarchy State Change|Next State: **Baselined**<br><br> Exclude States: **Inactive, Locked** <br><br> Action Label: **Change State to Baselined** <br><br> Optional: Select **Prevent action if one or more items are being processed** <br><br> Note: This replaces the existing _Change State to Baselined_ user action.|

### Baselined to Locked Configuration

This configuration cascades the _Locked_ state to all of the _Content Plan_'s active descendant records, but not to its parent records. This configuration uses the [_Content Plan Hierarchy State Change_ action](/en/lr/45365/#content-plan-state-change) so that Vault can change the state of the records asynchronously.

To configure this, add or update the following [user action](/en/lr/59885/#user-actions) and remove the following [entry actions](/en/lr/59885/#entry-actions) on the _Content Plan_ object lifecycle:

|Lifecycle State|Action|Action Type|Action Conditions|
|--- |--- |--- |--- |
|Baselined|User Action|Content Plan Hierarchy State Change|Next State: **Locked** <br><br> Exclude States: **Inactive**<br><br> Recommended: Select **Prevent action if one or more items are being processed** <br><br> Action Label: **Change State to Locked**<br><br> Note: This replaces the existing _Change State to Locked_ user action.|
|Locked|Entry Action|N/A|Remove the existing _Change related object lifecycle state_ or _Change related object lifecycle state asynchronously (no limit)_ entry action that moved related _Content Plan_ records to _Locked_. <br><br> Remove the existing _Change related object lifecycle state_ or _Change related object lifecycle state asynchronously (no limit)_ entry action that moved related _Content Plan Item_ records to _Locked_. |

### Inactive Entry Action Configuration

This configuration cascades the _Inactive_ state to all of the _Content Plan_'s descendant records, but not to its parent records. This configuration uses the [_Content Plan Hierarchy State Change_ action](/en/lr/45365/#content-plan-state-change) so that Vault can change the state of the records asynchronously.

To configure this, add or update the following and [user actions](/en/lr/59885/#user-actions) and remove the following [entry actions](/en/lr/59885/#entry-actions) on the _Content Plan_ object lifecycle:

|Lifecycle State|Action|Action Type|Action Conditions|
|--- |--- |--- |--- |
|Draft|User Action|Content Plan Hierarchy State Change|Next State: **Inactive** <br><br> Optional: Select **Prevent action if one or more items are being processed** <br><br> Action Label: **Change State to Inactive** <br><br> Note: This replaces the existing _Change State to Inactive_ user action.|
|Baselined|User Action|Content Plan Hierarchy State Change|Next State: **Inactive** <br><br> Optional: Select **Prevent action if one or more items are being processed** <br><br> Action Label: **Change State to Inactive** <br><br> Note: This replaces the existing _Change State to Inactive_ user action.|
|Locked|User Action|Content Plan Hierarchy State Change|Next State: **Inactive** <br><br> Optional: Select **Prevent action if one or more items are being processed** <br><br> Action Label: **Change State to Inactive** <br><br> Note: This replaces the existing _Change State to Inactive_ user action.|
|Inactive|Entry Action|N/A| Remove the existing _Change related object lifecycle state_ or _Change related object lifecycle state asynchronously (no limit)_ entry action that moved related _Content Plan_ records to _Inactive_. <br><br> Remove the existing _Change related object lifecycle state_ or _Change related object lifecycle state asynchronously (no limit)_ entry action that moved related _Content Plan Item_ records to _Inactive_.|

## Configuration for Drag & Drop Document Matching

By default, Vault does not allow users to [drag and drop a document onto inactive content plan items](/en/lr/59502/#drag-and-drop). However, you can configure Vault to move the content plan item to an active lifecycle state before matching the document. You must update the cascade configuration in your Vault to support the ability to drag and drop documents to match them to inactive content plan items.

To update your configuration, add the **Cascade Activation** [state type](/en/lr/30683/#state-type) to the _Content Plan Item_ lifecycle and select the _Set Parent to Draft (Intermediate)_ lifecycle state. This will allow users to drag and drop a document onto an inactive _Content Plan Item_ to activate the record and its ascendant records. Ensure that there is an existing **Change State to** [user action](/en/lr/59885/#user-actions) on the _Content Plan Item_ lifecycle state you selected when setting up in the **Cascade Activation** state type.

 [8]: #activate-lc-states
 [9]: #activate-workflows
 [10]: #activate-actions
 [11]: #locked-to-basedlined-lc-states
 [12]: #locked-to-basedlined-workflows
 [13]: #locked-to-basedlined-actions
 [14]: #baselined-to-draft-lc-states
 [15]: #baselined-to-draft-actions
 [16]: #activate-ascendant-records