When building an application for use within many countries around the globe, it's essential to be able to translate your application to be localized to the user's location. Descope makes translating the text within your flows a breeze by offering translation via connectors or manual overrides. When using a connector to translate a Descope flow, you can override the translation response from the third-party service to meet your needs.

This guide will cover an overview of localization configuration; however, we have dedicated knowledge base articles for utilizing connectors such as Google Cloud or AWS Translate.

Configuration Overview

To configure the localization of a Descope flow, navigate to the Localization section within the Descope console. Once here, you can select the applicable flow you want to localize from the dropdown, then click Configure Localization.

Start localization of a flow within Descope.
Once you have clicked Configure Localization, you will be prompted to select the connector, source language, and target languages.

Localization modal within Descope for initializing of translation of a flow.
When you select the dropdown for Connector, you can choose manual or one of the connector instances if you have configured per this guide.

Selecting a configured connector for localization of a flow in Descope.
After selecting Done, you will see a page similar to the one below. You can change the settings from the previous modal by clicking the settings icon at the top right. You can also import and export the translations via the arrows icon. You can also select the checkbox to View overrides only to show only the overridden items on the right-hand side for the selected language.

Selecting a configured connector for localization of a flow in Descope.

Manual Localization

After selecting the manual option for localization, you will see a screen like the example below. You can then manually override the translations per language.

An example screen for manual localization of a flow within Descope.

Connector Based Localization

When configuring localization to utilize a connector like Google Cloud or AWS Translate, the localization will automatically be generated for the flow based on the returned translation. Below you can see an example configuration and the generated translation.

An example configuration of localization with a connector within Descope.

An example output of connector based localization of a flow within Descope.

Manually Overriding Connector Translations

When you configure localization with a connector, you can manually override the translation. When you override the translation, you will see the override highlighted like the below example.

An example of manually overriding connector based localization of a flow within Descope.