**Source URL:** https://safety.veevavault.help/en/lr/1275658/

# Enable Safety Case Translation Agent

With the 26R3 release, Veeva Safety introduces the Translation Agent in Vaults using Vault AI for Safety. This AI tool automates verbatim translation of text fields across the intake, case processing, and reporting workflows. The Translation Agent replaces inefficient methods such as manual translation and export to external services by automatically translating free-text reported fields into your organization's designated [working language][1]. This removes delay from getting started on _Inbox Item_ and _Case_ processing. In addition, designed for the translation requirements of regional authorities, such as the PMDA, the Translation Agent supports transmission compliance. 

Depending on your business needs, you can configure your Vault so users can manually run the agent when translation is needed, or automatically along your workflow. The Translation Agent performs:

* **Inbound Translation**: For _Inbox Items_ and _Cases_, the agent translates reported text on all supported text fields from the non-working language to your configured _Working Language_.
* **Outbound Translation**: You can configure up to 10 _Localization_ groups and define which fields the agent translates for the related _Localizations_. On _Localized Cases_, the agent translates text into the language required by the regional health authority.

The Translation Agent translates text verbatim without enhancements or change to the clinical meaning. When text exceeds a field's character limit, the agent makes non-substantive adjustments for small overages. Otherwise, Vault notifies users of fields that could not be translated. Global safety teams can use the agent as a tool of their quality control (QC) processes.

After you have configured this feature, see the following articles for more information:

* Perform Local Language to English Intake
* Prepare a Domestic Case
* Prepare a Localized Case

## Configure the Translation Agent
To configure the inbound and outbound settings for the Translation Agent:

1. Navigate to **Admin > Configuration**, and in the _Application Configurations_ section, select **Translation Agent**.
2. On the _Translation Agent_ page, select **Edit**.
3. In the _Inbound Translations: Inbox Item and Case_ section, select a [**Working Language**][1]. If you do not select a language, Vault applies English.
4. Add up to ten _Localization_ groups that will share the same configured fields for translation on _Localized Cases_:
    1. In the _Outbound Translations: Localized Case_ section, select **Add Localization**.
    2. In the _Add Localization_ dialog, select the _Localizations_, and then select **Done**.
    3. Expand the newly created _Localization_ group, and for each listed _Section_, select which fields are available for translation by the agent. You can configure any standard or custom non-rich text field. Leaving a section blank results in Vault translating no fields for that section. 
5. Select **Save**.

For any _Localizations_ not defined in a _Localization_ group, Vault translates all [supported fields][2].

### Edit Localization Groups

To change the _Localizations_ in a _Localization_ group: 

1. On the _Translation Agent_ page, select **Edit**.
2. Select the **Edit** () icon for the group. 
3. Update the _Localizations_.
4. Select **Done**. 

### Supported Working Languages {#languages}

The Translation Agent supports the following _Working Languages_ for translation on _Inbox Items_ and _Cases_:

* Arabic
* Bengali
* Chinese (Simplified)
* English
* French
* German
* Hindi
* Indonesian
* Italian
* Japanese
* Korean
* Portuguese
* Spanish
* Swahili
* Yoruba

### Supported Localized Case Fields {#localized-fields}

The Translation Agent supports translating any standard or custom non-rich text field. By default, when configured, the agent translates the following object fields into the target language required for regional submission:

* _Localized Case_
    * _Additional Pregnancy Related Information_
    * _Medical History Text_
    * _Reporter's Comments_
    * _Company Comments_
    * _CIOMS Remarks_
    * _Reporting Summary_
    * _Study Name_
    * _Study Name (Continued)_
* _Localized Case Contact_
    * _Additional Information_
* _Localized Case Product_
    * _Other Additional Information_
    * _Related Device Information_
    * _Product (Reported)_
    * _Product (Coded)_
    * _Registration Holder/Applicant_
* _Localized Case Product Dosage_
    * _Dose Text_
    * _Parent RoA Text_
    * _Patient RoA Text_
* _Localized Case Product Substance_
    * _Substance Name_
* _Localized Case Product Indication_
    * _Name (Reported)_
* _Localized Case Adverse Event_
    * _Event (Reported)_
* _Localized Case Cause of Death_
    * _Cause of Death (Reported)_
* _Localized Case Test Result_
    * _Test Name (Reported)_
    * _Comments_
    * _Result (Text)_
* _Localized Case Medical History_
    * _Condition / Procedure (Reported)_
    * _Comments_
* _Localized Case Drug History_
    * _Drug (Reported)_
    * _Indication (Reported)_
    * _Reaction (Reported)_
* _Localized Case Comment_
    * _Comments Text_
* _Localized Case Document_
    * _Attachment Description_
    * _Reference Text_
* _Localized Case Assessment Result_
    * _Method (text)_
    * _Result (text)_
    * _Source (text)_

## Update Object Layouts

To display the status of translations for users, add the _Translation Status_ field to the _System_ section of applicable layouts for the following objects:

* _Inbox Item_
* _Case_ (update only the layout assigned to the `case__v` object type)
* _Localized Case_

## Configure Translation Agent Actions

To support your business processes, you can configure the Translation Agent to run as a user action, an entry action, or a workflow action, as needed. Assign actions to objects as follows:

* _Translate Inbox Item_ to the _Inbox Item_ object
* _Translate Case_ to the _Case_ object
* _Translate Localized Case_ to the _Localized Case_ object

After assigning the action, add the action to the applicable _Inbox Item_, _Case_, and _Localized Case_ object lifecycles.

## Configure Agent User with Object Permissions

You must update the Case Translation Agent _User_ record to include a security profile and permission sets that grant the appropriate level of access to objects and fields according to your organization's process. To complete translations, we recommend granting the Case Translation Agent _User_ permission to _Read_ and _Edit_ the _Inbox Item_, _Case_, and _Localized Case_ objects. 

[1]: #languages
[2]: #localized-fields