# Enable Signal Review Scheduling

With the 26R1 release, for <a href="/en/gr/01233/">Veeva SafetyDocs</a> and <a href="/en/gr/753121/">Veeva Safety Signal</a>, Vault can now create _Signal Reporting Periods_ for a _Signal Product Profile_ based on a configured schedule. This automation reduces manual effort and tracking for routine signal surveillance reviews. After you have configured this feature, see the following articles for more information: 
* <a href="/en/gr/808068/">Manage Signal Product Profiles</a>
* <a href="/en/gr/979940/">Signal Review Scheduling</a>

## Update Object Layouts

Update the following <a href="/en/gr/26387/#how-to-access-page-layouts">object layouts</a>: 
* [_Signal Product Profile_][1]
* [_Signal Reporting Period_][2]

### Signal Product Profile {#signal-product-profile}

To update the _Signal Product Profile_ layout: 
1. Insert the _Schedule_ <a href="/en/gr/26387/#related-object">related object section</a>.
2. In the _Schedule_ section, <a href="/en/gr/26387/#how-to-add-object-fields">add</a> the following fields:
   * _Schedule_
   * _Schedule Start Date_
   * _Schedule Initiated By_
   * _Schedule Initiated Date/Time_
   * _Schedule Terminated Date/Time_
3. Set the _Schedule_ and _Schedule Start Date_ fields to required by hovering next to the fields and selecting the **Edit** icon. Then, select **Display As Required** and select **Done**.
4. In the _Signal Reporting Periods_ section, <a href="/en/gr/26387/#columns">edit the default columns</a> to include:
   * _Review Type_
   * _Start Date_
   * _End Date_
   * _Lifecycle State_
   * _Previous Signal Reporting Period_
   * _Next Signal Reporting Period_

### Signal Reporting Period {#signal-reporting-period}

To update the _Signal Reporting Period_ layout, in the _Details_ section, <a href="/en/gr/26387/#how-to-add-object-fields">add</a> the following fields:
* _Review Type_
* _Previous Signal Reporting Period_
* _Next Signal Reporting Period_

## Configure the Signal Review Actions on Signal Product Profile

To configure the _Schedule Signal Review_ and _Cancel Scheduled Signal Review_ actions, <a href="/en/gr/43127/#assign-actions">assign</a> the actions to the _Signal Product Profile_ object and add them as a <a href="/en/gr/59885/#define-actions">user action</a> to the applicable states of the _Signal Product Profile_ object lifecycle using the following table: 

| Condition Type          | Condition                 | Action                   | Action Label             |
| ----------------------- | ------------------------- |------------------------- |------------------------- |
| All conditions are met  | Schedule Initiated Date/Time > is blank | _Schedule Signal Review_ | `Schedule Signal Review` |
| All conditions are met  | Schedule Initiated Date/Time > is not blank | _Cancel Scheduled Signal Review_ | `Cancel Scheduled Signal Review` |

## Update the Signal Reporting Period Object Lifecycle

This section applies only to Vaults with Veeva Safety Signal enabled. For the _Signal Reporting Period_ object lifecycle, <a href="/en/gr/30683/#associate-state-type">associate</a> the _Queued_ state with the _Queued_ state type.

## Grant Permissions

Ensure your <a href="/en/gr/22824/#objectpermissions">permission sets</a> are updated to grant the appropriate level of access for users to objects and fields according to your organization's process. Manage object permissions from **Admin > Users & Groups > Permission Sets > [Permission Set] > Objects**.

We recommend granting the following object and field permissions:

<table>
    <thead>
        <tr>
            <th>Object</th>
            <th>Fields</th>
            <th>Object Permissions</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td><em>Schedule</em></td>
            <td>N/A</td>
            <td><ul>
                    <li><em>Read</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Schedule Component</em></td>
            <td>N/A</td>
            <td><ul>
                    <li><em>Read</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Schedule Recurrence</em> of type <em>Signal Product Profile Recurrence</em></td>
            <td>N/A</td>
            <td><ul>
                    <li><em>Read</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Scheduled Event</em></td>
            <td>N/A</td>
            <td><ul>
                    <li><em>Read</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Scheduler Exception</em></td>
            <td>N/A</td>
            <td><ul>
                    <li><em>Read</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Signal Product Profile</em></td>
            <td><ul>
                    <li><em>Schedule</em></li>
                    <li><em>Schedule Start Date</em></li>
                    <li><em>Schedule Initiated By</em></li>
                    <li><em>Schedule Initiated Date/Time</em></li>
                    <li><em>Schedule Terminated Date/Time</em></li>
                </ul>
            </td>
            <td><ul>
                    <li><em>Read</em></li>
                    <li><em>Edit</em></li>
                </ul>
            </td>
        </tr>
        <tr>
            <td><em>Signal Reporting Period</em></td>
            <td><ul>
                    <li><em>Review Type</em></li>
                    <li><em>Previous Signal Reporting Period</em></li>
                    <li><em>Next Signal Reporting Period</em></li>
                </ul>
            </td>
            <td><ul>
                    <li><em>Read</em></li>
                    <li><em>Edit</em></li>
                </ul>
            </td>
        </tr>
    </tbody>
</table>

[1]: #signal-product-profile
[2]: #signal-reporting-period