You have created a Process Composer project and elements containing language-specific attributes.
You have opened the Process Development perspective in the Developer Studio and have expanded your project in the Project Explorer view.
When you model a process, language-specific content is automatically stored in a resource file. For different types of elements containing text, a corresponding resource file is created. These files are of S2X format and use the XLF file extension. To edit XLF files, you use the S2X editor in the SAP NetWeaver Developer Studio.
In SAP NetWeaver Business Process Management (BPM) translation is supported for the following elements:
Element |
XLF File |
Located in Node |
---|---|---|
Process |
<process name>.bpmn.xlf |
bpmn |
Task |
<task name>.task.xlf |
tasks |
Function |
<function name>.function.xlf |
functions |
Ruleset/Flow Ruleset |
<ruleset/flow ruleset name>.function.xlf |
functions |
Event Trigger |
<event trigger name>.eventdef.xlf |
triggers |
Reporting Data Source |
<reporting data source name>.eventdef.xlf |
reporting |
You have to translate only attributes that are flagged with yes in the Translate column of the S2X editor.
The XLF files contain the texts in the language that you determined when you created the Process Composer project. For every language version other than this original language, you create a copy of the XLF file and enter the language-specific translations. Languages other than the original language are referred to as source languages.
Translated texts are included in the build when you build your project and are displayed at runtime after you deploy the project to the application server. For example, you can see translated task attributes when you log into the Universal Worklist (UWL) to execute a task. Displaying the translated text depends on the language defined for the user with which you log into the UWL.
If no translation is available, the task is displayed in the original language.