# Configuring Quality Event Suggestions (QMS)

Quality Event Suggestions allows users to streamline prioritization and categorization during the triage stage of a quality process, which can reduce cycle times and assist with workflow routing. You can execute the _Generate Record Suggestions_ action to suggest field values for matching fields and related objects associated with _Deviations_, _Complaints_, or _Nonconformances_, and their associated _Quality Event_ counterparts.

## Configuration Overview

Complete the following steps to enable the Quality Event Suggestions feature: 

* Optional: [Configure automated translation](/en/lr/981284/#record-checks-suggestions) for [supported objects](/en/lr/981284/#supported-objects). Up to five text fields can be included in the similarity match.
* Add a _Record Suggestion Configurations_ component and use it to define the _Match Criteria_, field suggestions, and related record suggestions.
* Optional: [Enable an application setting][1] to give users the ability to specify terms that all matching records must contain.
* Configure the _Generate Record Suggestions_ action on the lifecycles associated with a supported object.
* Configure the _Record Suggestion_ (`record_suggestion__v`) object.

## Creating Record Suggestion Configurations

Admins can configure a _Record Suggestion Configurations_ component for each object or object type for which they want to allow suggestions.

To create a _Record Suggestion Configuration_:

1. Access the _Record Suggestion Configurations_ component under **Admin > Configuration > Application Configurations > Quality Configurations > Record Suggestion Configurations**. 
2. Define the _Match Criteria_ for the supported objects and object types. These criteria include the date range, exact match fields, text fields for key match terms, and lifecycle states to include.
3. Select up to five (5) active fields to capture the field suggestions that will be used for calculating the top five (5) used field values for a particular field on similar records.
4. Optional: If you want Vault to exclude alphanumeric values from system-generated match terms, select the **Exclude numeric suggested terms** checkbox.
5. Select up to three (3) active related objects associated with the primary object that will be used to calculate related record suggestions.
6. Ensure that the related objects have a join or child parent inbound relationship with the primary object. Reference objects are not supported.

## Enabling Match on All Terms {#all-terms-setting}

You can enable an application setting to give users the option to specify search terms that all matching records must contain when generating event suggestions. To do this, navigate to **Admin > Settings > Application Settings**, and enable the **Enable Match on All Terms in Record Check and Record Suggestions Actions** checkbox in the _QMS_ section.

<div class="note-border alert-important">
  <div class="alert alert-important" role="alert">
    <div><i class="far fa-exclamation-circle"></i></div>
    <div class="alert-text">
      <p><strong>Important</strong>: Once enabled, you cannot disable the <em>Enable Match on All Terms in Record Check and Record Suggestions Actions</em> setting.</p>
    </div>
  </div>
</div>



## Configuring the Generate Record Suggestions Action

Admins must configure the _Generate Record Suggestions_ user action on lifecycle states associated with a supported object.

To configure the _Generate Record Suggestions_ action:

1. Navigate to the **Actions** tab under **Admin > Configuration > Objects**.
2. Click **Create** and select the **Generate Record Suggestion** action. Do not select the _Available in All Lifecycle States_ checkbox.
3. Add the action to the appropriate lifecycle state for the supported object. 
   1. Access the lifecycle state and click **Edit** under **User Actions**. 
   2. Select the _Generate Record Suggestions_ action and the _Record Suggestion Configuration_.
   3. Optional: Select the **Allow user to override discovered match terms** checkbox to allow users to modify the _Match Criteria_ that Vault suggests.
4. Optional: Configure the _Generate Record Suggestions_ action via _Atomic Security: Actions_ to allow only certain roles to execute the action.

## Configuring the Record Suggestion Objects

Admins must configure the _Record Suggestion_ (`record_suggestion__v`) object for the _Deviation_, _Complaint_, and _Nonconformance_ objects. Admins also can add the _Record Suggestion Item_ (`record_suggestion_item__v`) and _Record Suggestion Item Detail_ (`record_suggestion_item_detail__v`) objects to the _Record Suggestion_ object page layout.

## Related Permissions

Admins require the following permissions to configure Quality Event Suggestions:

* _View_, _Edit_, _Create_, and _Delete_ permissions for the _Record Suggestion Configurations_ component.
* Permissions for _Admin: Objects_ and _Admin: Object Lifecycles_.

Users require the following permissions to use Quality Event Suggestions:

* For field suggestions, users require _Edit_ permissions on the object, the field, and the field in the lifecycle state based on their role.
* For related record suggestions, users require _Create_ permissions on the related join object, _Read_ permissions on the second parent object record referenced in the join object, and _Edit_ permissions for _Atomic Security: Relationships_ for the join object in the lifecycle state.

[1]: #all-terms-setting