Integrated language translation - Data
Interaction data translation
The integrated language translation feature also offers an Interaction data translation workflow for language translations within an Interaction. The workflow was built to enable configurability of which fields to be translated, where the translated values are stored within Medical Information Cloud, and which 3rd party service is used to complete the translation. Additionally, notifications can be configured to alert the content manager when translations have been completed by an integrated translation service.
Admins will also be able to configure translation services based on specific regions. For information on configuring vendor regions, visit Vendor Regions below.
Configuration requirements
Note
To configure the interaction data translation feature, you will need a language translation connector license. Please reach out to your Komodo Health representative for more information.
Note
This package will be installed automatically for V13.
Configuration steps
To configure:
Assign the appropriate permissions.
Set up translation mappings that enable manual translation.
Optionally, setup automated translations.
Permission sets
To configure and customize the Komodo Health integration, admin users must be assigned the Komodo Health Translation Admin (KomodoHealthTranslationAdmin) custom permission. This custom permission is included in the Komodo Health Translation Admin (KomodoHealthTranslationAdmin) permission set.
To add the correct permission set to a profile:
In the Quick Find box in Setup, search for and select Profiles.
Click Lightning Medical Information Agent.
Click Enabled Custom Permissions.
Click Edit.
Scroll down the Available Custom Permissions list and click mvn-komodohealth-vendor.mvn.Komodo Health Translation Admin.
Click the right arrow to add it to the Enabled Custom Permissions column.
Click Save.
Enable the translation vendor
To enable the translation vendor:
In Setup, navigate to Custom Metadata Types.
Click Manage Records next to Translation Vendor.
Click Edit next to KomodoHealth.
Ensure the Label and Translation vendor names are KomodoHealth.
Ensure the API Endpoint is populated with the correct API (https://translation.komodohealth.com).
Set the Enabled? (
mvn__CT_IsEnabled__c) value to true (checked).Click Save.
Vendor regions
Vendor regions determine the translation service the translation request is sent to based on the region associated with the data.
To create a Vendor Region:
Open the App Launcher to the left of the side of the page header.
Scroll down and click Vendor Region.
On the Vendor Region page, click New.
Complete the following fields:
Table 144. Vendor Region settingsField
Description
Values
Vendor Developer Name
The name of the translation vendor that will be used for the region.
Must match the value of the Translation Vendor Name field in the Translation Vendor (
mvn__CT_Vendor__mdt) custom metadata type.Region
The region that encompasses the area that will be serviced by the translation vendor.
Select the region to assign the vendor to.
Priority
The order in which this region applies.
Using numerical values, add the priority for the specified vendor region. The lower the number, the higher the priority.
Is Data Translation Enabled?
A checkbox that indicates if data translation is enabled for this vendor in this region.
This box must be checked to enable data associated with the selected region to be translated by the vendor.
Is Content Translation Enabled?
A checkbox that indicates if content translation is enabled for this vendor in this region.
This box must be checked to enable data associated with the selected region to be translated by the vendor.
Click Save.
Warning
A vendor region can be saved without selecting either translation checkbox. However, when neither data nor content translation is selected, no translation requests for that region will be sent to the selected translation vendor.
A vendor region can be defined for the same or overlapping regions to customize the translation routing process. Data can be routed to separate translation services for the same region by creating different vendor regions for each translation type. Vendor regions can also prioritize different translation services for overlapping areas.
Example vendor regions are shown below:
Field | Vendor Region A | Vendor Region B |
|---|---|---|
Vendor Developer Name | TransPerfect | AWS |
Region | Mexico | North America |
Priority | 1 | 2 |
Is Data Translation Enabled? | Selected | Selected |
Translation settings
Medical Information Cloud is shipping with the following default records in the Translation Setting (mvn__MED_Translation_Setting__mdt) custom metadata records. These metadata records can be edited as needed and new metadata records can be added if desired. These records allow you to configure which fields (source fields) will be translated and where they will appear (target field) on the record.
AE Narrative
PQC Complaint
Request Question
Request Response
Data translation field configuration
The metadata records associated with the Translation Settings (mvn__MED_Translation_Setting__mdt) custom metadata type define which specific object fields are automatically sent for translation upon record closure.
To create a new Translation Settings metadata record:
In the Quick Find box in Setup, search for and select Custom Metadata Types.
Click Manage Records next to Translation Setting.
Click New to create a new Metadata Record. Each record, when enabled, will automatically translate a defined field for every record of the defined object type.
Complete the following fields:
Table 146. Translation Settings fieldsField
Description
Required values
Label
Name of the custom metadata setting.
Must have a unique name.
Translation Setting Name
API name of the label.
N/A - Automatically populates based on the Label field.
Automated Translation
A checkbox that enables the automated translation upon closure of the record.
The box must be checked to enable automatic translation.
Warning
The label can be saved without checking the box; however, the data will not be translated.
Object Type
Drop down list of the available object types.
Select the object type that contains the data for the translation request.
Source Field
Drop down list of the available fields within the selected object type.
Select the field that contains the data for the translation request.
Source Region Field
The field that contains the region associated with the data.
The API name of the field that contains the region information associated with this source field.
Source Language Field
The field that contains the associated language code.
The API name of the reference field.
Target Field
Drop down list of the available fields to translate the data into.
Select the field for the translated data to be returned to.
Target Language
The language the data is translated into.
A Salesforce supported ISO language code.
Click Save.
Warning
A Vendor Region must be defined for the region associated with the translated data to route the translation request to the correct service.
Add the translation quick action button
The Translate quick action can be added to any record page. To do so:
From a record page (e.g., Requests), click the gear icon in the top right of the page and click Edit Page.
Click to select the highlights panel.
On the right side of the page, at the bottom of the list of Actions, click Add Action.
In the modal that appears, search for Translate and click to select it.
Click Done.
Click Save on the top right corner of the page.
Automated data translation
The metadata records associated with the Translation Settings (mvn__MED_Translation_Setting__mdt) custom metadata type define which specific object fields are automatically sent for translation.
To create a new Translation Settings metadata record:
In the Quick Find box in Setup, search for and select Custom Metadata Types.
Click Manage Records next to Translation Setting.
Click New to create a new Metadata Record. Each record, when enabled, will automatically translate a defined field for every record of the defined object type.
Complete the following fields:
Table 147. Translation Settings (mvn__MED_Translation_Setting__mdt) fieldsField
Description
Values
Label
Name of the custom metadata setting.
Must have a unique name.
Translation Setting Name
The API name of the label.
Automatically populates based on the Label field.
Automated Translation
The checkbox that enables the automated translation.
The box must be checked to enable automatic translation.
Note
The label can be saved without checking the box, however, the data will not be translated.
Object Type
A dropdown list of the available object types.
Select the object type that contains the data for the translation request.
Source Field
A dropdown list of the available fields within the selected object type.
Select the field that contains the data for the translation request.
Source Region Field
The field that contains the region associated with the data.
The API name of the field that contains the region information associated with this source field.
Source Language Field
The field that contains the associated language code.
The API name of the reference field.
Target Field
A dropdown list of the available fields to translate the data into.
Select the field for the translated data to be returned to.
Target Language
The language the data is translated into.
A Salesforce supported ISO language code.
Click Save.
A Vendor Region must be defined for the region associated with the translated data to route the translation request to the correct service.