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

Adding Multilingual Support for Forms and Tasks

Adding Multilingual Support for Forms and Tasks

You can create request forms as well as task forms (for a People activity) that support different languages. To do so, you create a new form, plus a default properties file and additional properties files for each language supported. The properties file contains externalized strings for schema-based keyIdentifiers. The steps to accomplish this support for requests are described below.
For details on task forms, see Providing Multilingual Support for Task Forms in the
Human Tasks
topics elsewhere in this help.
Create a new request form and a default properties file:
  1. Create a new request form, described in Creating an Process Central Process Form.
  2. In the Create Form dialog, select the
    Advanced
    button.
  3. Select the Externalize String
    s
    check box.
  4. Accept the default name and location for the properties file, or select the dialog button next to Property File to name and store your file. Do not use an underscore in the name.
When you 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 form to indicate multilingual support:
    <link rel="i18n" charset="UTF-8" type="text/plain" href="myForm.properties" />
  • The list of schema elements is added to the properties file as a key-value pair.
  • The properties file that you create is the default externalized strings file.
For each additional language you want to support, do the following:
  1. Make a copy of the default properties file and paste it into the forms folder.
  2. Name the copied file with the syntax described in Naming Convention for a .properties File. Basically, 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.
  3. Open the file in a text editor and replace the existing values with another language.
To test your properties, specify a language when you login to Process Central. For example:
http://localhost:8080/activevos-central/login.jsp?lang=fr
See also I18N Functions.


Updated March 30, 2020