You can configure your Vault to translate data on supported QMS records when users change the lifecycle state of a record or run a user action. Quality Automated Language Translation expedites complaint intake and processing in order to ensure that complaints are triaged quickly.
Note: This feature leverages a language translation provider that does not save or use data from your Vault to enhance its translation service, track usage, or resolve issues. For a list of supported languages, see Supported languages and language codes.
Quality Automated Language Translation supports the following types of standard and custom fields:
- Long Text
- Rich Text
- Text
Supported Objects
Quality Automated Language Translation supports the following objects and object types:
- Complaint (all standard and custom object types)
- Complaint Intake (all standard and custom object types)
- Quality Event (Complaint and Medtech Complaint object types only)
Configuration Overview
To configure Quality Automated Language Translation:
- Configure translation fields on a target object.
- Create a Quality Language Translation configuration.
- Configure the target object layout.
- Configure the target object lifecycle.
- Configure user permissions.
- Optional: Update your configuration for the Record Checks and Suggestions features to support translation.
Configuring Target Object Fields
To configure a supported object for Quality Automated Language Translation, first create fields to store translated text for custom and standard fields that require translation, then assign them to the relevant object types. The Title and Description fields include the corresponding standard Title (Translated) and Description (Translated) fields, but you must activate them and assign them to object types.
We recommend configuring the Translate Record field to be required. If you configure this field to be required, you can optionally set a default value of No. You can configure the Translate Record user action to display only when this field is set to Yes, and the Translate Record entry action to run only when this field is set to Yes.
The Source Language Code and Target Language Code fields are used by Vault only and are automatically populated with the applicable language code when users select a language from the Source Language and Target Language object controls that display as drop-downs on the target object’s layout. The language code fields should not be added to the layout for the target object.
You can optionally configure the Source Language Code field to be required. However, if you leave it optional, when users save a record without selecting a language from the Source Language drop-down, the action detects the source language during translation. We do not recommend setting a default value for this field.
If you expect your target language to always be a language other than English, you can configure the Target Language Code field to default to that language. If the user does not select a language from the Target Language control before translating a record, this field defaults to English.
Creating a Quality Language Translation Configuration
To create a Quality Language Translation configuration:
- Navigate to Admin > Configuration > Quality Language Translations and click Create.
- Enter a Label.
- Enter a Description.
- Select a Source Object.
- Select a Source Object Type.
- Click Save.
Next, you must create Field Mappings within the Quality Language Translation configuration for all fields you wish to translate on the target object.
To create Field Mappings:
- On a Quality Language Translation configuration, expand the Field Mappings section and click Edit.
- Select a Source Field from the drop-down. This is the field to translate.
- Select a Target Field from the drop-down. The translated text will appear in this field. If you selected a Rich Text type field as the Source Field, only Rich Text type fields are available to select as the Target Field. If the Source Field is Text or Long Text, you can select any type of text field as the Target Field.
- Click the (+) icon to add another field.
- Repeat steps 2-4 until you have created all required Field Mappings.
- Click Save.
Viewing, Editing, or Deleting a Quality Language Translation Configuration
To view, edit, or delete a Quality Language Translation and its Field Mappings:
- Navigate to Admin > Configuration > Quality Language Translations.
- Click the Actions menu next to the applicable configuration.
- Select View, Edit, or Delete.
When you delete a Quality Language Translation configuration, Vault also deletes its Field Mappings. To delete a Field Mapping from a Quality Language Translation configuration, navigate to the configuration record, click Edit in the Field Mappings section, click the (-) icon next to the Field Mapping you wish to delete, then click Save.
Configuring the Target Object Layout
On the layout for the target object and object type, add the following:
- Recommended: Source Language object control. If you configured the Source Language Code field to be required, this step is not optional.
- Optional: Target Language object control. Since this control defaults to English if left blank, we recommend adding it to the layout only if you require records to be translated into a language other than English.
- Recommended: Translate Record field
- All translation fields that will display translated data
After adding all translation fields to the layout, create a layout rule to hide the translation fields when users are first creating a record. When creating the rule, use the Hide display effect and specify the fields to hide. Next to IF this Layout Rule Expression is TRUE, enter the following expression: DisplayMode()='CREATE'. Do not hide the Translate Record field.
Configuring the Target Object Lifecycle
To make the Translate Record action available to configure on an object lifecycle, you must first assign the Translate Record action to the target object. Next, add the Translate Record action as an entry action or user action to any state of the target object lifecycle.
When configuring the action as an entry action, you can specify Action Completion Notification Recipients who should be notified when the action completes with errors or fails. If your process includes reviewing the translated data on the record, you can optionally create a Translation Ready lifecycle state and add the Translate Record entry action to it. You can optionally configure a condition to ensure the record is translated only if the Translate Record field is set to Yes.
When configuring the action as a user action, you can optionally configure a condition to make the Translate Record action visible only if the Translate Record field on a record is set to Yes. To do this, for the Condition Type, select All conditions are met, then use the drop-downs below the Condition Type to create the phrase If Translate Record equals Yes. If Vault encounters an error when translating records via the user action, an error message displays to the user who ran the user action.
If Vault encounters errors when the Translate Record user or entry action runs, depending on the nature of the error, Vault may only partially translate the record if specific fields cannot be translated. In other scenarios, the entire transaction may fail, for instance when the user or entry action is configured with an inactive or deleted Quality Language Translation configuration.
Configuring User Permissions
You must grant users the following permissions to use Quality Automated Language Translation:
- Edit permission on the target object record, including the Translate Record field and all source and target translation fields
- View permission for the Source Language object control and the Target Language object control on the target object if you added these object controls to the target object layout
Configuring Record Checks & Suggestions for Translation
You can configure the Recurrence Check, Duplicate Check, and Quality Event Suggestions features to search translated fields. In addition to completing the other configuration steps in this article, you must update the relevant configuration record to add or replace text comparison fields with translation fields, or create new configuration records to use translation fields.
If your target language is English and you expect users to create some records in English, you can create an action trigger to copy source field values to target translation fields when the record’s Source Language and Target Language fields are both English.
Limitations
The following limitations apply to Quality Automated Language Translation:
- You can create one Quality Language Translation configuration per object type.
- You can create up to five Field Mappings per Quality Language Translation configuration.
- If the data in source or target translation fields exceeds 100,000 bytes, Vault displays a warning message and does not translate these fields. The remaining fields on the record are translated. Some Long Text and Rich Text fields may exceed this limit.
- Rich Text fields are not translated if the target language is a language other than English.
- Field Mappings cannot contain duplicate Source Fields or Target Fields.
- The Reason for Change Capture field is not supported for translation.
Related Permissions
To complete the steps in this article, you must have the following permissions:
| Permission | Access Details |
|---|---|
| Pages: All Automated Language Translations: View | Grants view permission for the Quality Language Translations list page |
| Admin: Configuration: Automated Language Translations: Read, Create, Edit, Delete | Grants read, create, edit, and delete permissions for Quality Language Translation configuration records and their Field Mappings |