Genpact Cora Knowledge Center


Multilingual Configuration


Cora SeQuence supports multiple languages. With minimal effort, you can configure a Flowtime environment in any supported language. Multilingual support enables you to translate the following metadata values:

  • Activity Alias
  • Activity Description
  • Workflow Alias
  • Workflow Description
  • Message Subject
  • Message Body
  • Expression Value

NOTE: Translating a workflow should be the last step of the workflow development process.

Supported Languages

Cora SeQuence supports several languages out-of-the-box. You can configure additional languages with minimal effort.

  • Dutch
  • English
  • French
  • Hebrew
  • Portuguese
  • Spanish

Create and Translate the Resource File

You need to perform several procedures to prepare your workflow for translation.

  1. Create the resource file.
  2. Configure the workflow in App Studio
  3. Translate the workflow metadata

Create the resource file

The first time you perform the workflow translation procedure, sCora SeQuence creates a directory and a language-specific resource file for the workflow. 


C:\Program Files\PNMsoft\Shared Resources\Resources\<Your Workflow Name> directory

Resource File

<Your Workflow Name>.TEMPLATE.resx

You will make all future modifications to this file. For example, if you designed a workflow in English, and want to translate the workflow to French, copy the template file and rename it to <Your Workflow Name>.fr-FR.resx.

NOTE: fr-FR is the target language culture, and as such is hierarchically structured. For more details on the CultureInfo Class, see

Configure the workflow in App Studio

There are several parameters in the Globalization section of the Properties panel that require configuration and resolution before you translate the workflow.  To access the parameters, navigate to App Studio > Properties panel > Globalization section. To enable these features, set the Localizable parameter to True.

Formatting defines how dates and numbers display. Formatting is determined by one of the   following.
  • Enforce a format: select a culture from the drop-down menu.
  • Thread   of the application: selection (auto) from the drop-down menu.
The language is  determined by one of the following:
  • Enforce a language: select a culture from the drop-down menu.
  • Thread   of the application: selection (auto) from the drop-down menu.

Translate the workflow metadata

  1. Open the workflow in App Studio.
  2. Navigate to App Studio > Properties panel > Globalization section, and set the Localizable parameter to True.
    You must perform this configuration every time you add a new activity to the workflow. After you add the new activity, set the Localizable parameter to False and then set it back to True.
  3. (Optional) Edit the resource file name to reflect the translation target language.
  4. Open the resource file in a text editor and translate the content of the Value column.
    Visual Studio offers a convenient Excel-like experience.
  5. Perform IISReset to implement the modifications.

Workflow Runtime Expressions

Runtime Cora SeQuence expressions is an efficient tool for retrieving any information you need related to the runtime context. For more information, see Understanding Expressions.

Runtime expressions enable users to retrieve data from the workflow resource file. You can use expressions to define default values, business roles, and much more, by using the following expression: rt.GetResourceString(<key from resource file>). For example, to return the localized workflow alias: rt.GetResourceString("ApprovalKey")

When you use Runtime expressions make sure that all available languages have a resource file. For example: <sq8:Label runat="server" Text='<%$sq8: rt.GetResourceString("Request_Form_Comment") %>' />.

You can also use <%$ Resources: MyResourceFile, LabelText %> to hold the expressions. If you do this, you will have to maintain the translations in two locations.

Create or edit a runtime expression

  1. In App Studio, right-click the activity you want to edit and select Edit.
  2. In UX Studio, click the arrow next to a form field and click <New field...> to access the data field window.
  3. Select a data field that you want to edit.
    As an example, we are going to assign a default value for the RequestDate field in the form.
  4. In the Properties panel, click the ellipsis button next to the Default Value field.
  5. Assign a default value for the RequestDate field.
    For our example, we are going to assign the default value as the current day.
  6. Click Validate.

Create a Multilingual Form

  1. In Visual Studio, create a resource file for the language that you want to create for the form.
    Example: MyResourceFile.resx
  2. Add values to the resource file, in which the key is the value used in the form's markup and the "value" is the display value in runtime.
  3. Translate the resource file to the new language, and name it with a corresponding extension.
  4. Copy the resource files to the application's App_GlobalResources directory.
    The App_GlobalResources directory is located in the application root directory. For example, in the default Flowtime installation, the path is: C:\inetpub\wwwroot\Workflow Runtime\App_GlobalResources. If this directory does not exist, you need to create it.
  5. In your forms, use the key as we show it in the exmple below.
    <sq8:Label runat="server" Text="<%$ Resources: MyResourceFile, LabelText %>" />

Cora SeQuence Flowtime Behavior

Follow this procedure to change the display language in Flowtime.

In Flowtime, click the Settings icon > General Settings, and select a language.

Translate Flowtime Categories

  1. Create a .resx file for each language that you want to translate the categories into.
    The file should include the tranlsated alias and description for each category. For example, if you want to translate the categories into French, the file should be The keys in the file would be CategoryName_Alias and CategoryName_Description. If one of the categories is Retail Banking, this is what the file would look like.
    <data name="Retail Banking_Alias" xml:space="preserve">
      <value> Retail Banking Fr</value>
    <data name=" Retail Banking _Description" xml:space="preserve">
      <value> Retail Banking Description Fr</value>
    <data name="[CategoryName2]_Alias" xml:space="preserve">
      <value>Category 2 Fr</value>
    <data name="[CategoryName2]_Description" xml:space="preserve">
      <value>Category 2 Description Fr</value>
  2. Create a folder named Portal in Shared Resource\Resources\Sequence.
  3. Put the category translation .resx files in the Portal folder.