Siebel Reports Administration Guide > Developing Multilingual Reports >

Designing Multilingual Reports

Designing a multilingual report is essentially the same as that of any standard report. The only additional step is to externalize the user interface elements for localization in the desired languages. The same report executable obtains the language-specific strings from the localized text files based on user's specification. The following instructions will describe the details of the additional step for localization of user interface strings.

To design a multilingual report

1. Design a report in the default language, for example, ENU for English.

   For more information about the ENU directory, see About Language Extensions.

   To create this part of the design, perform the same procedures as described in Process of Creating a Custom Report With Actuate e.Report Designer Professional, where you use Siebel Tools to create the ROL file and Actuate e.Report Designer Professional to create the ROD and ROX files. When performing the procedures, make the following modifications:

   • Configure the report to run in Design mode. For more information, see Running a Report in Design Mode or Deployment Mode.
   • When you perform the build and run procedure, set ssLanguage to the default language. For example, ENU for English.

     Note that the report executable and the user interface file are generated. For example, CUACCSVC.rox and CUACCSVC.txt. This executable is for design time use only.

2. Localize the contents of cuaccsvc.txt into separate language specific files.
   1. Generate a cuaccsvc.txt file specific to each language.
   2. Place each of the language-specific .txt files in $\Siebel\Tools\RPTSRC\[LANGUAGE]\cuaccsvc.txt.

      For more information about the LANGUAGE directory, see About Language Extensions.

3. Configure the report to run in Deployment mode.

   For more information, see Running a Report in Design Mode or Deployment Mode.

4. Recompile the report to create the report executable for the runtime deployment by setting ssLanguage to FRA (French), DEU (German), JPN (Japanese), and so forth as needed.
5. Verify that the language specific labels are displayed in Actuate e.Report Designer Professional for each user-specified language parameter.

Running a Report in Design Mode or Deployment Mode

A report can be run in design mode or deployment mode. When run in design mode, user interface strings and data properties are externalized to an external file. Later, you can run a report in Deployment mode to verify localization.

After you have completed testing a multilingual report, make sure the report executable is created in Deployment mode.

To configure a report to run in design or deployment mode

1. After adding the ssReport component to the desired location in the tree in the Report Structure window, right-click ssReport, choose Properties, click the Methods tab, and then double-click Sub Start ().
2. Identify an appropriate location to insert a new line of code near the beginning of the existing code, such as replacing Insert your code here.
3. In the editing window, insert a line of code according to the mode in which you want to work, as described in the following table.

   Design Mode	Deployment Mode
   Set gExportUI to 1	Set gExportUI to 0

During development, you can switch between design mode or deployment mode by modifying gExportUI.