Migrate to version v3 of a translator configuration
-
- UpdatedAug 3, 2023
- 2 minutes to read
- Vancouver
- Dynamic Translation
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Implement the contract with subflows using complex objects in the input and output fields for dynamic translation of text.
Before you begin
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
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