Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Providing Multilingual Support for Task Forms

Providing Multilingual Support for Task Forms

You can create task forms that support different languages. To do so, you create a new task form, plus a default properties file and additional properties files for each language supported. The steps to accomplish this support are described below.
To Create a New Task Form and a Default Properties File:
  1. Create a new task form, described in Creating an Process Central Task Form.
  2. In the
    Create Form
    dialog, select the Externalize Strings check box.
  3. Select the dialog button next to Property File.
  4. Name the new properties file. Do not include an underscore in the name.
  5. Browse to the forms folder to store the file.
When you select to externalize strings, the following events occur:
  • Schema elements in the form are generated by identifier rather than by name to allow for runtime replacement of strings found in a properties file
  • A new link is added within the task form to indicate multilingual support:
    <link rel="i18n" charset="UTF-8" type="text/plain" href="../myTaskForm.properties" />
  • The list of schema elements is added to the properties file as a key-value pair. The value of each key is the English wording.
  • The properties file that you create is the default externalized strings file. It is for the en_US language.
For Each Additional Supported Language:
  1. Make a copy of the default properties file and paste it into the project
    form
    folder.
  2. Name the copied file with the syntax shown below. Note that you must use the exact same name for each file, followed by an underscore, followed by an ISO 639 Code for the Representation of Names of Languages.
    Syntax
    myFile_[ISO639Code]_{optional locale code}.properties
    Examples
    myTaskForm_fr.properties
    myTaskForm_fr_CA.properties
  3. Open the file in a text editor and replace the English values with another language.
Note
: You can also add multilingual support for a task's presentation elements, namely the Subject and Description. For details, see Adding MultiLingual Support for Task Subject, Description, and Display Name.
See also Deploying a Task Form and Properties Files.


Updated March 30, 2020