Description:
This step translates the text into the selected language using Azure ML.
Inputs
- textToTranslate – Text to translate
- selectFromLanguage – Select source language
- selectToLanguage – Select target language
- varGlobalToStoreValue – Variable or global to hold the result
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “clsAzureMLLanguageTranslatorDef” example.
- Create a new process definition named “clsAzureMLLanguageTranslatorDef” and open it in designer mode.
- Drag a "clsAzureMLLanguageTranslator" step to the canvas.
- Connect the dots between the “Start” and “clsAzureMLLanguageTranslator” steps, as shown above.
- Define a variable or a global to store the result.
-
Click the "clsAzureMLLanguageTranslator" step to configure its "Required" properties. Provide a name for the step. Enter the text to translate. Select the target language from the drop-down list. Provide a variable or global reference to store the result. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- Click the "clsAzureMLLanguageTranslator" step to configure its "Optional" properties. Select the source language from the drop-down list, or let the application auto-detect it using the default setting. Click the Save button.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.
- To complete the configuration, go to Status > Settings > Configuration > Azure ML settings. A sample image is provided for reference.
- Save the process definition, create a new instance, and execute it. The step should translate the text into the selected language and store the result in “variable. result” as configured.
Definition Sample:
You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.
Click here to download the sample file.