# Translating Checklist Designs

To easily add multiple localized sections, questions, and answers at once, export and import tools are available from the **Actions** menu on a _Checklist Design_ record. The exported translation file is a CSV that you can edit in Excel, any text editor, or translation software. You can also manage checklist translations in the <a href="/en/gr/537448/#managing-checklist-translations">Visual Checklist Designer</a>.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The <em>Checklist Design</em> should be created in your Vault’s base language. We do not recommend changing a Vault’s base language if checklist translations already exist.</p>
    </div>
  </div>
</div>



## Supported Fields for Checklist Design Translation

Only text fields (excluding Long Text or Rich Text) are currently supported for checklist design translation. For more details, refer to the following table:

|Object|Supported Fields|Unsupported Fields|
|--- |--- |--- |
|_Checklist Design_|`name__v`|`welcome_email_subject__sys`<br/>`welcome_email_text__sys`<br/>`welcome_notification_text__sys`|
|_Section Design_|`name__v`<br/>`description__sys`<br/>`header__sys`||
|_Question Design_|`question_text__sys`<br/>`question_help_text__sys`|`name__v`|
|_Available Answer Design_|`answer_text__sys`|`name__v`|

## Exporting Checklist Design Translations {#export}

To export a CSV file for translations:

1. Navigate to **Business Admin > Objects > Checklist Designs** and select the _Checklist Design_ record for the checklist you want to translate.
2. From the **Actions** menu, select **Export Translations**.
3. Select the language you're translating to and click **Continue**. Only languages available in your Vault (excluding its <a href="/en/gr/13309/#base">base language</a>, as Checklist Design text should be created in the Vault's base language) are displayed in the picklist. If you select more than one language, the download will be a .zip file containing separate translation files for each language.
4. In the downloaded translation file, you can view all the fields available for translations and any existing translations for the selected language.
5. Update existing translations or enter new translations for new values in the _Translated Value_ column.
6. When done, save the file. If editing in Excel, it is important that you only execute _Save_ on the file and do not use _Save As_ to save the file as a CSV file in a different location or save it as a native Excel file. To move or rename the file, use your operating system, rather than Excel's _Save As_ option.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: For any rows where the <em>Translated Value</em> field is left blank, no translation will appear in Vault for that field. This also applies if a field that previously had a translation is left blank. However, if an entire row is missing, its translation text value will remain unchanged.</p>
    </div>
  </div>
</div>



At present, if you export a translation file for an aggregate checklist, only the _Checklist Design_'s _Name_ field is available for translation. You must ensure that the _Checklist Designs_ comprising the aggregate checklist are translated individually.

### Bulk Exporting Checklist Design Translations {#bulk-export}

You can also export translation files for multiple _Checklist Design_ records at once in much the same way as exporting a single translation file. Instead of navigating to a specific _Checklist Design_ record, you can begin a bulk export from the **Actions** menu in **Business Admin > Objects > Checklist Designs**.

The steps are the same as above, except that you will be prompted with a _Select Checklist Design_ dialog where you can choose which _Checklist Design_ records you would like to translate. In this dialog, you can search for specific records or apply filters to narrow the list of records. By default, the following filters are applied:

* _Lifecycle State_ in _Draft_ or _Approved_.
* _Translated Checklist_ equals _Yes_.

You can remove these filters if desired.

## Importing Checklist Design Translations {#import}

To import an updated translation file:

1. Navigate to **Business Admin > Objects > Checklist Designs** and select the _Checklist Design_ record for the checklist you have translated.
2. From the **Actions** menu, select **Import Translations**. You can only import a translation file if the _Checklist Design_ record is in the _Draft_ state. This option may be unavailable if the record is in the incorrect lifecycle state.
3. Select the updated translation file and click **Submit**. Vault applies any new translations immediately. Rows without any changes are ignored – that is there only for reference.

### Bulk Importing Checklist Design Translations {#bulk-import}

As with exporting, you can bulk import checklist design translation files from the **Actions** menu in **Business Admin > Objects > Checklist Designs**. When bulk importing, you may include translations for multiple _Checklist Design_ records in the same CSV.

### About CSV File Validation

During import, Vault validates the CSV file and reports any errors in order based on the rows in which they appear. The following circumstances may cause import errors:

  * The file is not a CSV or does not have the .csv file extension.
  * The file is empty or contains only column headers.
  * The file size exceeds 1GB.
  * The file has missing or extra columns.
  * The file has blank or invalid column headers.
  * The file has an invalid language value. For example, the language code is inactive in your Vault, is the Vaults base language, or does not match any Vault language.
  * The file contains extra rows. This may occur if a multiple-choice answer or optional text field value was deleted in Vault but is still present in the translation file.
  * A value in the file exceeds the text character limit for its respective field.
  * The file includes invalid row values such as unsupported fields or invalid objects.

## Managing and Approving Checklist Design Translations {#managing-approving-checklist-design-translations}

When a checklist translation is successfully imported, Vault creates a _Checklist Design Translation_ record as a child of the _Checklist Design_ record and _Checklist Field Translation_ records as children of the _Checklist Design Translation_, which house the actual translated text for each field. When a _Checklist Design Translation_ record is created, Vault also sets the _Translated Checklist_ field of the parent _Checklist Design_ record to _Yes_. Admins can use the _Checklist Design Translation_ record to track and manage the translation status of the checklist design for a specific language. This includes moving the translation's lifecycle state from _Draft_ to _Approved_ or vice versa. Translations must be approved before they will be visible to users in the checklist.

_Checklist Field Translation_ records also contain a _Question Reference Document Translation_ object type that allows you to upload translated reference documents. You can then add reference documents in the translated language to the checklist.

Before a _Checklist Design_ record can be approved, all of its child _Checklist Design Translation_ records must be approved. While the _Checklist Design_ record is in a stable state, you cannot make changes to or add new _Checklist Design Translation_ records.

When translations are available, they are also included when executing the following actions:
  * <a href="/en/gr/52824/#new-version">Create New Version</a>
  * <a href="/en/gr/52824/#copying-checklist-design">Deep Copy Checklist Design</a>
  * <a href="/en/gr/50438/">Upload Design Configuration</a>
  * <a href="/en/gr/50438/#exporting-checklist-designs">Export Checklist Design</a>

[1]: #managing-approving-checklist-design-translations