Migrate to version v3 of a translator configuration

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read

    • Implement the contract with subflows using complex objects in the input and output fields for dynamic translation of text.

    Before you begin

    Role required: admin
    For a translator configuration that you added to integrate with a translation service provider of your choice, implement Integration Hub subflows with complex objects in the input and output fields. These subflows are required to interact with the translation service provider for the following tasks:
    • Translate the input text
    • Detect the language of the input text

    For information on implementing these subflows, see Integrate with a translation service provider.

    About this task

    After an upgrade to Washington DC, the version of all translator configurations that are available by default but not customized is automatically updated to v3. The corresponding subflows have complex objects in the input and output fields.
    However, you should migrate to version v3 for the following translator configurations:
    • Translator configurations that are available by default but customized in New York
    • Translator configuration that you added to integrate with a translation service provider of your choice

    Procedure

    1. Navigate to All > Dynamic Translation > Translator Configurations.
    2. Select a translator configuration.
    3. In the Translator Configuration form, update these fields.
      Table 1. Translator Configuration form fields
      Field Description
      Active Activates the translator configuration to integrate with Dynamic Translation.
      Version Version of the contract used in subflows. Select v3.
      Choose a translate subflow Integration Hub subflow with complex objects in the input and output fields to translate the input text.
      • For the translator configurations that are available by default but customized, select Translate Text [translate_text_v3].
      • For the translator configuration that you added to integrate with a translation service provider of your choice, select the subflow that you implemented with complex objects. The contract now supports multiple texts in a single method call.
      Choose a detect subflow Integration Hub subflow with complex objects in the input and output fields to detect the language of the input text.
      • For the translator configurations that are available by default but customized, select Detect Language [detect_language_v3].
      • For the translator configuration that you added to integrate with a translation service provider of your choice, select the subflow that you implemented with complex objects. The contract now supports multiple texts in a single method call.
      Mark as default for translation Marks the translator as the default configuration for dynamic translation of text.
      Mark as default for detection Marks the translator as the default configuration to detect language of the input text.
    4. Click Update.