# Configuring the Check Sibling Records Entry Action

The **Check sibling records before updating related record** 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.

This configuration option is ideal for actions where an organization wants the related record to change states once all actions are complete.



## 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 **Check sibling records before updating related record** entry action.
  4. Under **All sibling records in lifecycle state**, select one or more lifecycle states of records that you want to check.
  5. Under **Related Object**, 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_.
  6. Select the **Target State** for the related object.
  7. Click **Save**.

## Example Configuration

VeePharm configures the **Check sibling records before updating related record** entry action for the _Investigation_ object in a Quality Vault. 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.