# Configuring the Sibling Check Related Record State Change Entry Action (QMS)

The **Sibling Check Related Record State Change** entry action allows you to configure a lifecycle so that a record automatically moves forward when all "sibling" records from a related object are in a specific state. "Sibling" records are records for a single object that all have a relationship to the same record on a related object. For example, a group of _Investigation_ records that are all related to the same _Quality Event_ record. The sibling records can also be checked for specific field conditions before the state change.

This configuration option is ideal for investigations and CAPA actions where an organization wants the related quality event to change states once all investigations or actions are complete.


<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 entry action is only available for QMS and LIMS Vaults. As of 20R2.2, an <a href="/en/lr/64930/">entry action with similar functionality</a> is now available for all applications.</p>
    </div>
  </div>
</div>



## How to Set Up the Action

The following section covers details that are specific to this entry action. For general information on configuring entry actions, see [Configuring Object Lifecycles](/en/lr/30683/).

To configure this entry action:

  1. From **Admin** > **Configuration** > **Object Lifecycles**, open the lifecycle that applies to the "sibling" object.
  2. Click into the lifecycle state that you want all sibling records to be in when you change the related record state.
  3. Add the **Sibling Check Related Record State Change** entry action.
  4. Optional: Make the Sibling Check conditional based on a field that applies to the "sibling" object. Under **Field**, selecting a field, operator (like "equals"), and value. Only Yes/No (boolean) fields are available here.
  5. Under **[Sibling Object] State** (Investigation State, for example), select a condition like "All records equal" and the state you want sibling records to be in. This should match the state on which you're configuring the entry action.
  6. Under **Change State Of**, select the related object that you want to move to a new state. The object must be related through an outbound relationship, either _Parent_ or _Reference_.
  7. Select the **To** state for the related object.

## Example Configuration

VeePharm configures the **Sibling Check Related Record State Change** entry action for the _Investigation_ object. This entry action checks the state of investigations related to the same _Quality Event_ record.

Whenever an _Investigation_ record enters _Closed_ state, Vault looks at other _Investigation_ records where the same _Quality Event_ record is selected. If any of those records are not in _Closed_ state, nothing happens. If all related _Investigation_ records are in _Closed_ state, Vault executes a state change on the related _Quality Event_ record.

### Field Condition

VeePharm wants to modify the above configuration so that _Quality Events_ can close without certain optional _Investigation_ records being complete. To configure this, the Admin adds a new Yes/No field to the _Investigation_ object: _Required_. Then, the Admin updates the entry action on the investigation lifecycle's _Closed_ state to specify that _Required equals Yes_.

Now, whenever an _Investigation_ record enters _Closed_ state, Vault looks only at other _Investigation_ records where the same _Quality Event_ record is selected and where the _Required_ field is set to _Yes_. If any of those records are not in _Closed_ state, nothing happens. If all related _Investigation_ records are in _Closed_ state, Vault executes a state change on the related _Quality Event_ record.