Translating Application Definitions

This chapter provides an overview of PeopleSoft application definition translation processes and discusses how to:

• Use the Translation Designer.

• Translate definitions.

Understanding Application Definition Translation

If you are running PeopleSoft applications with a multiple language user interface, you should translate any customizations you make to the product using PeopleTools into each of the languages that you are using. PeopleTools provides a full suite of tools to help you translate the application user interface; these are the same tools that PeopleSoft uses internally to provide the translations we ship on the global multi-language CDs.

The main definitions requiring translation in order to provide a fully multilingual user interface are pages and fields. However, PeopleTools allows the translation of many other definitions; everything that the end user sees via the PeopleSoft Pure Internet Architecture can be translated into multiple languages.

You can translate PeopleTools definitions using Application Designer, PeopleSoft Tree Manager, or the translations utilities. The translations utilities are a particularly powerful option for translating fields, translate values, and hard-coded text on pages (that is, text that is not derived from the field description). Given the definitional approach to PeopleTools applications, however, the order in which you translate objects is critical in order to obtain the most leverage from your translation work.

Using Translation Designer

The Translation Designer within Application Designer provides an efficient mechanism for translating PeopleSoft pages, which are the highest volume and highest profile definitions.

Page definitions include:

• Field labels.

• Page text (not derived from field labels).

• Translate values (which normally appear either as radio button labels or as values in drop-down lists).

Translation Designer facilitates translations with an easy-to-use grid where you can view the base language text and enter a translation simultaneously, enabling translators to review their translations side-by-side instead of simply overwriting source text with a translation.

This section discusses how to:

• Open Translation Designer.

• Use Translation Designer display options.

• Work in Translation Designer.

Opening Translation Designer

Translation Designer shows all the translatable definitions in your current Application Designer project, along with their base language and translated text.

The grid contents are based on the Application Designer project that is open when Translation Designer is started. This association with Application Designer projects is a handy mechanism for organizing your translation effort. However, it also means that, to use Translation Designer, you must have a project open, and it must contain one or more pages. If you modify the project, Translation Designer won’t pick up the new objects in the project until you save the changes and refresh.

To open Translation Designer:

1. Set your language preference to the target language.

   Because you use the Application Designer to access Translation Designer, set your language preference using PeopleSoft Configuration Manager.

2. Open Application Designer.

3. Create or open the project containing the definitions to be translated.

   It makes sense to use projects with the non-base language versions of any pages. That way you’re sure to include all definitions on the pages. If you are creating a new project, you must save it before opening Translation Designer. Keep the number of pages in the project being translated to a minimum, as all the fields and other translatable definitions on each page in the project are loaded into memory when Translation Designer starts. A project with a lot of pages may take some time to open due to the sheer volume of fields on the page. Try to keep the number of pages in a project to be translated using Translation Designer under 20.

4. Open Translation Designer.

   • To translate the pages in your project, from the Tools menu select Translate and choose Translate Page Definitions.

     This is the most versatile option because it shows you all translatable definitions that are associated with a page. You can use it to translate field labels, panel text (not derived from field labels), and translate values—all in one grid.

   • To translate only the fields in your project, from the Tools menu select Translate and choose Translate Fields.

     This option lets you translate fields that are directly included as definitions in your project. Fields that are part of records or pages in your project are not included unless they are also explicitly included in your project as fields.

   • To translate only the translate values in your project, from the Tools menu select Translate and choose Translate Xlats.

     You can also access all of these commands in the popup menu that appears when you right-click in the project workspace.

     After you select one of the translate options, Translation Designer appears in the object workspace.

     Depending on which translation grid you opened, different translatable definitions from the active project appear in the grid. All definitions are arranged hierarchically: pages (if included) are at the top level; fields are at the next level; and field labels, panel text, and translate (xlat) values are at the lowest level.

     Use standard tree controls to expand and collapse the view in order to display definitions at different levels. You can also collapse or expand all levels of the tree by right-clicking on the tree node and selecting the appropriate option from the popup menu.

5. (Optional) Arrange the window to maximize Translation Designer.

   If you want more space for the translation grid, maximize the Application Designer window and then maximize Translation Designer within the window. For even more space, hide the other frames in the Application Designer window. To toggle the display of the project workspace, from the View menu select Project Workspace, or press Alt+0 (zero). To toggle the display of the output window, from the View menu select Output Window, or press Alt+1.

See Also

Setting Up Language Preferences for Microsoft Windows-Based PeopleTools

Using Translation Designer Display Options

This section discusses how to:

• Use the information bar.

• Expand and collapse nodes.

• Choose which rows to view.

• Resize columns and rows.

Using the Information Bar

Across the top of the translation grid, an information bar displays helpful information about the project. The target language, current project, and current viewing option (all, translated, untranslated, or modified) are set in italic.

On the left side of the bar, you can see the hierarchical organization that is used to display definitions in the grid: pages (at the highest level), fields (at the next level), and translatable definitions—field labels, page text, and translate values—at the lowest level.

Each definition is color-coded to remind you with which definition type you’re working.

• Fields: blue.

• Field labels: light purple.

• Page text (not derived from a field label): dark purple.

• Translate values: green.

Further, the following graphical cues help you understand the display:

• All fields on the page are displayed, even if they are hidden fields.

• The default label ID appears in italics, but not boldface.

• Any label ID that is used but that is not the default label appears in boldface italics.

• Page text from hyperlinks is displayed.

• If the same field has multiple label IDs on the same page, it appears only once for that page.

In this example, notice that there is a group box with page text that is not derived from a field label. The ADDRESS_TYPE field has a set of associated translate values. All other translatable definitions are field labels.

Notice also that the default label ID is italicized but not bold, while any non-default label IDs used are in bold italics. This is apparent when you look at the ZIP field, which has two labels. The other field labels appearing in the grid are associated with the field, but not used on the page being translated; they are displayed primarily so the translator can see the context in which they are translating the label and ensure consistency of terminology across labels.

Expanding and Collapsing Nodes

The left side of the translation grid is a hierarchical tree control that displays all the definitions on the page.

To expand the entire tree structure, from the View menu select Expand All. To collapse the entire tree structure, from the View menu select Collapse All. Right-clicking anywhere in the grid displays a popup menu that contains these options. Another option on the popup menu, Expand Current Definition, expands the selected definition by one level.

Choosing Which Rows to View

Right-click anywhere in the translation grid to see a popup menu that lets you choose which rows are displayed in the grid:

Keep in mind that the options you select in the popup menu work together. If you select Expand Current Object while Untranslated is activated, you might not see anything. This means that everything in the current definition is translated.

Resizing Columns and Rows

To change the column width, place the cursor over the column divider on the information bar. When the cursor changes, drag the column divider to the desired position. You can resize only translatable columns; you cannot resize the columns that display the hierarchical tree of page definitions. Use the same technique to change row height.

Working in Translation Designer

This section discusses how to:

• Enter translations.

• Navigate in Translation Designer.

• Search and replace.

• Use Application Designer functionality.

• Integrate with other applications.

Entering Translations

The working area of Translation Designer consists of four columns of data:Base Long Name, Tgt Long Name (target long name), Base Short Name, and Tgt Short Name(target short name).

As the column names imply, the two base language columns display the base language labels for the definitions in the grid. To translate the labels, type the translation into the Tgt Long Name and Tgt Short Name fields.

The grid incorporates standard text editing functionality. Cut, Copy, and Paste operations are available under the Edit menu. To force a line break within a label (so that the text wraps on the page), press CTRL+ENTER.

The first time that you translate a particular field label, the same translation is entered into any other occurrence of that field in the current grid. This ensures consistency and saves time.

The grid automatically limits the length of the text you enter based on the maximum length of the fields. When you reach the maximum length, you cannot add any more characters.

As with any Application Designer definition, changes are not permanent until you save them.

Note. To save related language data, you must have values in all fields. You cannot partially translate a single PeopleTools definition. For example, if you translate the long name but not the short name for a field, the short name defaults to the base language short name, and this value is saved in the related language table. Similarly, if you translate some but not all translate values for a particular field, any untranslated values pick up the base language text, which is then saved to the related language table.

Navigating Translation Designer

Click to move to a cell or node in Translation Designer, or use the standard Microsoft Windows keyboard shortcuts:

• Press TAB or ENTER to move to the right; press SHIFT+TAB to move to the left.

• Use any of the arrow keys to move from cell to cell.

  For example, the UP ARROW key moves you to the cell above the current cell.

• To move from the text cells to the tree, press the LEFT ARROW key.

• To move from the hierarchical tree to the text cells, press TAB.

  You can use the RIGHT ARROW key only when there are text cells in the same row—that is, if the current node is a translatable definition.

• Use the UP ARROW and DOWN ARROW keys to move around in the hierarchical tree—for example, from a field to an adjacent field or to a page.

  To move to a lower level, first press TAB to move into the main Translation Designer. Then move up or down to the desired node. Then use the LEFT ARROW key to move back into the tree.

• If there are several pages in your project, scroll directly to the node for a particular page by right-clicking that page in the project workspace and from the menu select Translate and choose Translate Page Definitions from the popup menu.

Searching and Replacing

To search for a specific word within a single column:

• Place the cursor anywhere in that column, and select Edit, Find and Replace In Current Column.

  To search a column you cannot edit, from the Edit menu choose Find in Current Column.

• The Find and Replace dialog boxes provide standard search and replace functionality, including the Find Next, Replace, and Replace All buttons. In either dialog box, select the Match case check box if you want to enable case-sensitive searching.

• The Find option provides enables you to search up or down the column.

  When you reach the top or the bottom of the column, the search does not cycle back through the column. Therefore, if you want to search the entire column, ensure that you’re in the top row when you press Find Next.

• The Replace function always searches down the column.

  If you want to replace all occurrences in the column, ensure that you’re in the top row when you press Replace.

Using Application Designer Functionality

Because Translation Designer is integrated into the Application Designer, you can use all standard Application Designer features while Translation Designer is open. Some features that are particularly useful during translations are:

• Using the Find Definition References option to research where in the system a particular definition is used. To use this option, from the Edit menu select Find Definition References.

• Opening a translated page in order to realign translated definitions.

• Opening definitions to see the properties.

  Remember, as long as you’re logged on using a non-base language, modifying labels in the definition updates the related language tables, not the base language tables.

There are several ways to open a definition:

• Use standard Application Designer functionality to open the definition from the project window.

• From the File menu, select Open.

• Double-click or right-click the definition within Translation Designer and select View Definition from the popup menu that appears.

  When you have selected page text that is not associated with a field definition, the page itself opens.

If there is a version of the page for the user’s language preference, that version appears; if not, the base language page appears.

Note. Security controls access to different Application Designer definitions. If you cannot open a particular type of definition from within Translation Designer, you may not have the necessary level of access.

See PeopleTools 8.51 PeopleBook: Security Administration

Integrating with Other Applications

Because Translation Designer emulates a Microsoft Excel spreadsheet, you can use the standard Windows copy and paste tools to copy translations from Translation Designer into Excel or another Windows application. This is useful when running spell check against your translations or when saving your translations in a spreadsheet for offline review.

To copy the entire contents of the currently open Translation Designer into the clipboard:

1. Select the entire grid.

   From the Edit menu choose Select All or click in the top left cell of the grid border.

2. From the Edit menu select Copy.

Note. With Translation Designer, you can copy an entire grid to the clipboard, but you can paste only individual field values back into the grid. You cannot paste the entire grid into Translation Designer after reviewing it in another application.

Translating Definitions

This section provides an overview of the translation pages and discusses how to:

• Translate page objects.

• Translate messages.

• Translate menu and component objects.

• Translate business processes.

• Translate PeopleSoft Process Scheduler objects.

• Translate mobile data.

• Translate portals.

• Translate trees.

• Translate records.

• Translate queries.

• Translate strings.

• Translate Application Engine descriptions.

• Translate review page text.

• Translate application data.

• Translate connected query definitions.

• Translate HTML definitions.

• Translate Integration Broker definitions.

• Translate XML Publisher definitions.

• Translate ACE analytic model ID definitions.

• Translate Essbase cube definitions.

• Translate time zone labels.

Understanding the Translation Process

For definitions that cannot be translated via Translation Designer, PeopleTools contains several translation pages that are especially useful if the translator has limited experience using PeopleTools. A translator who has good technical skills and who is familiar with PeopleTools may prefer to translate using the design tools as described later in this chapter.

To locate the translation pages, select PeopleTools, Translations, Translate System Definitions. The translation pages will help you to translate system definitions,including records, menus, menu items, components, queries, and other definitions.

You should translate application definitions in the following order to ensure the least amount of duplication during your translation process:

1. Translate page objects, messages, and menu and component objects—in any order.

2. Translate business processes, PeopleSoft Process Scheduler, mobile pages, and portals—in any order.

3. Translate other definitions—for example, trees, queries, application data, HTML definitions, and so on—in any order.

Translating Page Objects

All page objects except the HTML definitions can be translated directly in Translation Designer. However, you can also translate page definitions, fields, and translate values directly in Application Designer if you are familiar with the designer tools. The following table lists the objects, base tables, related language tables, and tools used to translate page objects.

Note. Don't be confused by the term translate value or translate table. The Translate table (PSXLATITEM) is a common prompt table used throughout PeopleTools and PeopleSoft applications that is used to store values for fields that don’t need individual prompt tables of their own. The Translate table is not used for translation purposes.

Translating Translate Values

To translate values from the Translate table in Application Designer:

1. Change the PeopleSoft Configuration Manager language preference to the target language.

2. Open Application Designer.

3. Open the field whose translate values you want to access.

4. From the File menu, select Definition Properties.

5. Access the translate values tab in the Field Properties dialog box.

   1. Click the Properties icon (or right-click in the field definition and choose Field Properties).

   2. Click the Translate Values tab (this tab is visible only for fields with a length of four or less).

      If the descriptions have not been translated, they appear in the base language.

6. Translate the descriptions into the target language.

   1. For each translate value, click the Change button to display the Change Translate Table dialog box.

   2. Translate the Long Name and Short Name fields.

      Don’t change any other fields.

   3. Click OK to accept the changes and close the dialog box.

7. Click OK to close the Field Properties dialog box.

8. Save the field.

Translating Messages

The following table lists the objects, base tables, related language tables, and tools used for translating message set descriptions and messages.

The Translate Messages page enables you to translate message set descriptions, messages, and detailed message explanations into a specific target language.

Access the Translate Messages page (PeopleTools, Translations, Translate System Definitions, Messages).

To translate messages:

1. Select a message set with which to work.

   Enter a Message Set Number in the field or click the Prompt button to search for a specific message set number.

2. Select messages within the message set with which to work.

   1. To select all messages within the message set, leave the Message Number field blank.

   2. To select a range of messages within the message set, enter the range in the Message Number fields.

3. Select the target language.

   1. From the Language Code drop-down list box, select a target language.

   2. Click the Get Messages button.

      The message set description you selected appears under the Message Set Number.

      The first message in the set or in the range you selected displays in the Messages section. The Base Message Text and Base Explanation fields display the message and its explanation in the base language.

      Use the arrow buttons or the First and Last links on the Messages bar to navigate to the messages retrieved.

4. Translate the message set description into the target language.

   1. Click the Information icon next to the Get Messages button. The Add Message Set page appears.

   2. Enter a Description in the target language for the message set.

   3. Enter a Short Description for the message set in the target language. The short description must be 10 characters or less.

   4. Click OK to return to the Translate Messages page.

5. Translate the message text and explanation into the target language.

   1. In the Target Message Text field, enter a translation in the target language for the information in the Base Language Text field.

   2. In the Target Explanation field, enter a translation in the target language for the information that appears in the Base Explanation field.

6. Click Save.

7. Repeat steps 6 and 7 for each message in the message set.

   On the Messages bar, use the Forward or Back arrows or the First and Last links to navigate to other messages within the set to translate.

Translating Menu and Component Objects

The following table lists the objects, base tables, related language tables, and tools used to translate menu and component objects.

This section discusses how to:

• Translate menu definitions.

• Translate menu items.

• Translate folder tabs in Application Designer.

• Translate folder tab labels using the translation utilities.

Translating Menu Definitions

Access the Translate Menus page (PeopleTools, Translations, Translate System Definitions, Menus).

The Translate Menus page enables you to translate the labels for a menu and menu group into a specific target language.

Note. In a portal, the names that appear in the menu are actually content references. You must translate these using the Translate Menu Items page.

To translate menus definitions:

1. In the Menu Name field, select the menu.

   Leave the Menu Name field blank if you want to select all the menus in the system.

   If you want to work on an alphabetical group of menu definitions, enter the first character (or characters) of the definition in the Menu Name field.

2. In the Target Language field, select the language into which you want to translate the menu definition.

3. Click the Get Menu button to bring the menu descriptions into the menu list.

4. Translate the menu label and menu group into the target language.

   The base language descriptions for each label appear on the left; enter the translations in the fields on the right.

   If you want to include accelerator keys for use with PeopleTools development environment navigation, position the accelerator key ampersand to the left of the character that will serve as the accelerator key for the menu or menu group.

5. Click the Save button.

Translating Menu Items

Access the Translate Menu Items page (PeopleTools, Translations, Translate System Definitions, Menu Items).

The Translate Menu Items page enables you to select a menu and then translate the set of labels for its menu bars and menu items into a specific target language.

To translate menu items:

1. In the Menu Name field, select the menu.

   Leave the Menu Name field blank if you want to select all the menus in the system.

   If you want to work on an alphabetical group of menu definitions, enter the first character (or characters) of the definition in the Menu Name field.

2. In the Target Language field, select the language into which you want to translate the menu definition.

3. Click the Get Menu Items button to bring the menus into the Menu Item List.

4. Translate the bar label and item label into the target language.

   The base language descriptions for each label appear on the left; enter the translations in the fields on the right.

   The translated menu bar label appears at runtime if the user’s language preference is set to the target language. It will also appear if one or more menu items that appear in the menu bar have a menu bar label translated into the target language.

   To include accelerator keys for use with PeopleTools development environment navigation, position the accelerator key ampersand to the left of the character that will serve as the accelerator key for the menu or menu group.

   After you translate a menu bar label and exit the field, you must select whether to use the same translation for all occurrences of the bar label:

   • Click Yes if you want the translation you just entered to be copied to each of the menu items in the list that share the same bar label. This is merely a data entry shortcut; no translations are saved until you explicitly click the Save button.

   • Click No if you want to leave some of the menu items untranslated.

5. Click the Save button.

Translating Folder Tabs in Application Designer

Folder tabs should be translated directly in the Translate Components page. However, if you are familiar with design tools you can also translate folder tabs directly in the Application Designer, Translation Designer.

Component definitions include two labels for each page in the component: an item label and a folder tab label. In the PeopleSoft Pure Internet Architecture, only one of these is visible to the user. If a folder tab label exists, it is used on the folder tab for the corresponding page; the item label is ignored. If no folder tab label exists, the item label is used as the folder tab label.

To translate folder tab labels in Application Designer:

1. Change the PeopleSoft Configuration Manager language preference setting to the target language.

2. Log in to the PeopleSoft system.

3. Open Application Designer.

4. Open the component definition.

5. Translate the item labels and folder tab labels into the target language.

   Edit the labels directly in the Item Label and Folder Tab Label columns on the grid.

   If the cell in the folder tab label column is blank, the item label appears in the folder tab.

   If there is both an item label and a folder tab label, be aware that only the folder tab label is visible in the PeopleSoft Pure Internet Architecture. The item label appears only on Microsoft Windows menus.

   For items that users access in Microsoft Windows menus, you may want to include ampersands within the item label text to create accelerator keys.

6. Save the component definition.

Translating Folder Tab Labels Using Translation Utilities

To translate folder tab labels using the translation utilities:

1. Select PeopleTools, Translations, Translate System Definitions, Components.

   The Translate Components page appears. The Translate Components page enables you to select a set of component definitions and then translate the labels for the pages that make up the component.

   There are two translatable labels for each page in the component: an item label and a folder tab label.

   In the portal, only one of these labels appears to the user. If a folder tab label exists, it is used on the folder tab for the corresponding page. The item label is ignored. If no folder tab label exists, the item label is used as the folder tab label.

   In Microsoft Windows, item labels become part of the navigational structure, so if the item label and folder tab label are different, they should both be translated. However, because folder tabs use the item label when the folder tab label is missing, it is common to have item labels only.

2. In the Target Language field, select the language into which to translate the component labels.

3. In the Component Name edit box, select a set of component definitions.

   Leave the Component Name field blank to select all the components in the system.

   If you want to work through the components alphabetically, enter the first characters of the component name in the Component Name field. If you want to translate a specific component, enter the component name into the edit box or click the Search button to prompt for a specific record.

4. Click the Get Component button to bring the components into the component list.

   If a component item has no folder tab text, the item label appears in the folder tab. In these cases, you can leave the translation for the folder tab text blank.

5. Translate the item label and folder tab into the target language.

   The base language descriptions for each label appear on the left; enter the translations in the fields on the right.

   If you want to include accelerator keys for use with PeopleTools development environment navigation, position the accelerator key ampersand to the left of the character that will serve as the accelerator key for the menu or menu group.

6. Click the Save button.

Translating Business Processes

Translate menus before business processes, PeopleSoft Process Scheduler, and portals because the terms are related.

The following table lists the objects, base table, related language table, and tool used to translate business processes:

This section discusses how to translate:

• Business process definitions (and their related objects).

• Component Interface messages.

• Business Interlinks.

• Activity definitions.

Note. PeopleSoft Business Interlinks is a deprecated product. This translation page currently exists for backward compatibility only. New integrations can be built using Integration Broker.

Translating Business Process Definitions (and Their Related Objects)

To translate business process definitions:

1. Set the language in PeopleSoft Configuration Manager.

2. Open Application Designer.

3. Open the Business Process Map.

4. Overwrite the English with the translation.

5. Save.

Translating Component Interface Messages

To translate component interface messages:

1. Select PeopleTools, Translations, Translate System Definitions, Component Interfaces.

   The Translate Component Interfaces page appears. The Translate Component Interfaces page enables you to select a component interface and then translate the description of the component interface into a specific target language.

2. In the Target Language field, select the language into which to translate the message set.

3. In the Name field, enter a component interface.

   Click the Search button to prompt for a list of component interfaces.

4. Click the Get Objects button to bring the component interface into the definition list.

   A set of component interface names appears in the Object List.

5. Translate the component interface description into the target language.

   1. Click the Update button to display the Add Message Set page.

   2. Enter descriptions for the message set in the target language.

   3. Click OK to accept the change and return to the Translate Component Interfaces page.

6. Click the Save button.

Translating Business Interlinks

The Translate Business Interlinks page allows you to translate Business Interlink descriptions.

Note. PeopleSoft Business Interlinks is a deprecated product. This translation page currently exists for backward compatibility only. New integrations can be built using Integration Broker.

To translate Business Interlink descriptions:

1. Select PeopleTools, Translations, Translate System Definitions, Business Interlinks.

   The Translate Business Interlinks page appears. The Translate Business Interlinks page enables you to select the base description of an interface object name and then translate the description into a specific target language.

2. In the Target Language field, select the language into which to translate.

3. In the IO Name field, enter an Interface Object name.

   Click the Search button to prompt for a list of interface object names.

4. Click the Get Objects button to bring the interface object names into the definition list.

   A set of interface object names appears in the Look Up List.

5. Translate the base descriptions into the target language.

   Enter descriptions for the interface object name in the target language.

6. Click the Save button.

Translating Activity Definitions

The Translate Activity Definitions page enables you to translate the short and long descriptions for a activity definition into a specific target language.

To translate activity definitions:

1. Select PeopleTools, Translations, Translate System Definitions, Activities.

   The Translate Activity Definitions page appears.

2. In the Activity Name field, enter the name of the activity to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Activity Name field blank if you want to select all object definitions in the system.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the activity definitions into the object list.

   A set of activity definitions appears in the Activity List based on the value you entered in the Activity Name field.

5. Translate the short and long descriptions into the target language.

   The base language descriptions for each activity appear on the left; enter the translations in the Target Description fields on the right.

6. Click the Save button.

Translating PeopleSoft Process Scheduler Objects

PeopleSoft Process Scheduler has three language-sensitive definitions:

• Process type definitions.

• Job definitions.

• Process definitions.

The following table lists where to translate PeopleSoft Process Scheduler objects:

To translate a PeopleSoft Process Scheduler Types, Jobs and Recurrences definitions:

1. Sign in to the PeopleSoft system using the target language.

2. Select PeopleTools, Process Scheduler to open PeopleSoft Process Scheduler.

3. Open the definition to translate.

   • To open a process type definition, select Process Type.

   • To open a job definition, select Job.

   • To open a process definition, select Recurrences.

4. Translate the descriptive text fields into the target language.

   Translate the Description field.

5. Click the Save button.

Translating Process Definitions

To translate process definitions:

1. Select PeopleTools, Translations, Translate System Definitions, Process Definitions.

   The Translate Process Definitions page appears. The Process Definitions page enables you to select a process name and type and then translate the long descriptions of the Process Definitions into a specific target language.

2. In the Target Language field, select the language into which to translate the Process Definitions.

3. Enter Process Name and process type into the appropriate fields.

   Click the Search button to prompt for a list of names.

4. Click the Get Objects button to bring the Process Definitions into the definition list.

   A set of Process Definitions appears in the Look Up List.

5. Translate the process definitions description into the target language.

   Enter descriptions for the process definitions in the target language.

6. Click the Save button.

Translating Mobile Data

This section describes how to translate:

• Mobile page names.

• Mobile page view labels.

• Mobile page items, such as fields.

Important! PeopleSoft Mobile Agent is a deprecated product. These translation pages currently exist for backward compatibility only.

Note. To translate mobile data, you must also translate the \bin\mobile\res\lang\mptext.properties file.

The following table lists where to translate mobile data.

See Modifying Text and Error Properties Files for New Languages.

Translating Mobile Page Names and View Labels

Use the Translate Mobile Page page to translate mobile page names and view labels.

Note. PeopleSoft Mobile Agent is a deprecated product. This translation page currently exists for backward compatibility only.

To translate mobile page names and view labels:

1. Select PeopleTools, Translations, Translate System Definitions, Mobile Pages. The Translate Mobile Page page appears.

2. In the Mobile Page Name field, enter the name of the page to translate, or use the Lookup button to search for a page.

3. From the Target Language drop-down list box, select the target language.

4. Click the Get Mobile Page button. The page refreshes and the Mobile Page List displays.

5. Translate the Mobile page name:

   Note. If available, the descriptions that you can translate display next to the fields in the base language.

   1. In the Description field, enter a translation for the page description in the target language.

   2. In the Long Description field, enter a translation for the long description in the target language.

      Note. A default description in the target language may display in the field. If so, clear the field then enter a new description in the target language.

6. Translate the mobile page view labels:

   Note. If available, the descriptions that you can translate display next to the fields in the base language.

   1. Click the Mobile Page View Labels button. The Mobile Page View Labels page appears.

   2. In the Detail View Label field, enter a translation for the Detail View in the target language.

   3. In the List View Label field, enter a translation for the List View in the target language.

      Note. A default description in the target language may display in the field. If so, clear the field then enter a new description in the target language.

   4. Click OK.

7. Click Save.

Translating Mobile Page Items

To translate Mobile page items use the Translate Mobile Page Items page.

This section provides and overview of the Translate Mobile Page Items page and describes how to:

• Select a mobile page and mobile page item(s) to translate.

• Choose predefined field label descriptions in the target language.

• Specify static text for a field label description in the target language.

• Suppress the display of field descriptions.

Note. PeopleSoft Mobile Agent is a deprecated product. This translation page currently exists for backward compatibility only.

To select a mobile page and mobile page item(s) to translate:

1. Select PeopleTools, Translations, Translate System Definitions, Mobile Page Items. The Translate Mobile Page Item page appears.

2. In the Mobile Page Name field, enter the name of the page that contains the page items you want to translate, or use the Lookup button to search for the page.

3. From the Target Language drop-down list box, select the target language.

4. Click the Get Mobile Item button.

   The page refreshes and in the Mobile Page Items section, the first item associated with the Mobile page appears.

   Click View All, or the Show Previous and Show Next buttons, to navigate through the results.

To choose predefined field label descriptions in the target language:

1. Select a mobile page with which to work.

2. In the Label Type box click the RFT Long button or the RFT Short button.

3. Click View Labels. The corresponding predefined RFT long or RFT short translation displays in the Related Lang Short/Long/Text field.

4. Click Save.

To specify static text for a field label description in the target language:

1. Select a mobile page and mobile page item with which to work.

2. In the Label Type box, click Text.

3. Click the View Labels button. Notice the value in the Related Lang Short/Long/Text field clears.

4. In the Related Lang Short/Long/Text field, enter a translation in the target language.

5. Click Save.

To suppress the display of a field description:

1. Select a mobile page and the mobile page item with which to work.

2. In the Label Type box click the None button.

3. Click Save.

Translating Portals

The following table lists where to translate PeopleSoft portal objects:

To translate portal objects:

1. Select PeopleTools, Translations, Translate System Definitions, Portal Objects. The Translate Portal Objects page appears.

   The Translate Portal Objects page enables you to select a portal objects name and portal reference type and then translate the label and description of the portal into a specific target language.

2. In the Target Language field, select the language into which to translate the Portal Objects.

3. Enter the Portal Object Name and the Portal Reference Type into the appropriate fields.

   Click the Search button to prompt for a list of names.

4. Click the Get Objects button to bring the Portal Objects into the definition list.

   A set of portal objects appears in the Look Up List.

5. Translate the Portal Objects description and label into the target language.

   Enter descriptions for the portal objects in the target language.

6. Click the Save button.

Translating Trees

The following table lists where to translate tree definitions:

In PeopleSoft Tree Manager, you can translate the tree description and the labels of nodes that correspond to language-sensitive record fields.

The translated tree descriptions appear in PeopleSoft Tree Manager list boxes.

Descriptive labels on tree nodes are derived from description fields in the record associated with the node. If you double-click the tree node, PeopleTools transfers you to the page where the node's properties are defined. If the record is language-sensitive (that is, if it has an associated related language table), the tree nodes' descriptive text is language-sensitive and can be translated using this page in the same way that you translate other application data.

This section discusses how to:

• Translate trees.

• Translate the tree structure description.

Translating Trees

To translate trees:

1. Ensure you have the specific language installed.

2. Log in to the PeopleSoft system in the target language.

3. Select Tree Manager, Tree Manager.

4. Open the tree whose description you want to translate.

   Click on the root or children.

5. Click the Edit Data button (the pencil icon). The Tree Node page appears.

6. In the Description field, enter a translation in the target language.

7. Click OK.

8. Click the Save button.

Translating Tree Structure Descriptions

To translate the tree structure description:

1. Ensure you have the specific language installed.

2. Log in to the PeopleSoft system in the target language.

3. Select Tree Manager, Maintain Tree Structure.

4. Select the Structure ID to translate.

5. Open the tree whose description you want to translate.

   Click on the root or children.

6. In the Description field, enter a translation in the target language.

7. Click OK.

8. Click the Save button.

Translating Records

The following table lists where to translate record definitions:

To translate record descriptions:

1. Select PeopleTools, Translations, Translate System Definitions, Records. The Translate Records page appears.

   The Translate Records page lets you select a set of record definitions and then translate the short and long descriptions for those records into a specific target language.

2. In the Target Language field, select the language into which to translate the record descriptions.

3. In the Record field, select a set of record definitions.

   Leave the Record field blank if you want to select all record definitions in the system.

   If you want to work through the records alphabetically, enter the first characters of the record name in the Record field. If you want to translate a specific record, enter the record name in the Record field or use the Search button to prompt for a specific record.

4. Click the Get Record button to bring the record descriptions into the record list.

   A set of record definitions appears in the Record List field based on the value you entered into the Record field.

5. Translate the short and long descriptions into the target language.

   The base language descriptions for each record appear on the left; enter the translations in the fields on the right.

6. Click the Save button.

Translating Queries

The following table lists where to translate queries:

To translate queries using the Translate Query utility:

1. Select PeopleTools, Translations, Translate System Definition, Queries. The Translate Query page appears.

   The Queries page enables you to translate query descriptions, heading labels, and query prompt descriptions into a specific target language.

2. In the Target Language field, select the language into which to translate the query descriptions and labels.

3. In the Query Name field, select a query.

   Leave the Query Name field blank if you want to select all the queries in the system.

   If you want to work through the fields alphabetically, enter the first characters of the query name in the Query Name field. If you want to translate a specific query, enter the query name in the Query Name field, or click the Search button to prompt for a specific record.

4. Click the Get Query button to bring the query descriptions into the query list.

   A set of query descriptions appears in the field Query List based on the value that you entered in the Query Name field.

5. Translate the base language descriptions into the target language.

   The base language descriptions appear on the left; enter the translations in the fields on the right.

6. Translate query field headings and prompt names.

   Click the Show Item Details button to display the Query Headings page.

   By default, field headings in queries are derived from RFT Long or RFT Short field descriptions, which means that they are automatically language-sensitive (provided that the field descriptions have been translated). Query prompt names are similarly derived from the prompt table description. The Query Headings page appears any field heading labels and prompt descriptions that are not derived from field or table descriptions, that is, descriptions that have override text in the query definition.

   Translate the description text for the field headings and prompt descriptions in the fields, and then click OK to accept the change and return to the Translate Query page.

7. Click the Save button.

See Also

Enterprise PeopleTools 8.51 PeopleBook: PeopleSoft Query

Translating Strings

The following table lists where to translate strings:

Translating String Definitions into a Non-Base Language

To translate string definitions into a non-base language:

1. Select PeopleTools, Translations, Translate System Definitions, Strings. The Translate Strings page appears.

2. In the Program ID field, enter or search for a program ID.

3. From the Language Code drop-down list box, select the target language.

4. Click the Find Strings button.

   The page refreshes and displays the first of all strings for the program ID.

   Click the View All link or use the Show Next and Show Previous arrows to navigate through the results.

5. In the String Text field, enter the a translation for the string that displays directly above the field.

   There are three situations in which you can translate strings IDs.

   • The string ID matches a field name in the database whose labels have been translated. In this case, you can use the Translate Strings page to choose among any of the labels of that field or static text for the string label. If none of the labels is appropriate for this context (or they are too long) then you can select Text as the label type and enter the translation. It is preferable that, whenever possible, you use field labels.

   • The String ID matches a field name in the database whose labels have not been translated. In this case, the message “Untranslated Field” displays in red. This message means that there is a field in the database with the same name as the string ID, but it has not been translated, so you cannot use the translated labels for the string. In this situation, you must translate the field first and then return to the Translate Strings page and select the label that is more appropriate for the string.

   • The string ID does not match a field name in the database. In this case, you may not select a label type. Text is the only option.

6. Click the Save button.

See Also

Using the Strings Table for Language-Sensitive Text in Reports

Translating Application Engine Descriptions

The following table lists where to translate Application Engine definitions.

Translating Application Engine Programs

To translate Application Engine programs:

1. Select PeopleTools, Translations, Translate System Definitions, Application Engine Programs. The Translate Application Engine Programs page appears.

   This page enables you to translate Application Engine program descriptions into a specific target language.

2. In the Target Language field, select the language into which to translate.

3. In the Program field, select an Application Engine program.

   Leave the Program name field blank if you want to select all the programs in the system.

   If you want to work through the fields alphabetically, enter the first characters of the program name in the Program field. If you want to translate a specific Application Engine program, enter the program name in the Program field, or click the Search button to prompt for a specific record.

4. Click the Get Objects button to bring the program name and base descriptions into the object list.

   A set of base program descriptions appears in the Object List field based on the value that you entered in the Program field.

5. Translate the base language descriptions into the target language.

   The base language descriptions appear on the left; enter the translations in the fields on the right.

6. Click the Save button.

See Understanding Application Engine.

Translating Review Page Text

Most page text is derived from language-sensitive field descriptions. Text derived from field descriptions is translated automatically when you clone the base language page definition (provided that the field descriptions have already been translated). However, page control definitions give you the option to override the field description with a text description.

If you use Translation Designer to translate pages, you can translate all such override text right along with labels that are derived from field descriptions. This feature of Translation Designer helps to ensure that the entire page gets translated.

PeopleSoft also provides a Page Text inquiry page that identifies override text in pages to help you identify areas where you may have missed translating. You can translate the override text in the target-language page definition in Application Designer.

To check for override text in pages:

1. Select PeopleTools, Translations, Translate System Definitions, Review Page Text. The Review Page Text page appears. The Review Page Text page lets you generate a list of all override text (that is, text that is not derived from field descriptions) in a set of page definitions.

2. In the Page Name field, select a set of page names.

   Leave the Page Name field blank if you want to select all the pages in the system.

   If you want to work through the pages alphabetically, enter the first characters of the page name in the Page Name field. If you want to translate a specific page, enter the page name in the Page Name field, or click the Search button to prompt for a specific record.

3. In the Language Code field, select the language code of the page set.

   For example, if the Page Name field contains B, and the Language Code field contains French, the page set will consist of page definitions that begin with B and whose language code is FRA.

4. Click the Get Page Text button to display the overridden page text.

   A set of page definitions appears based on the settings in the Page Name and Language Code fields.

   For each page that appears in the list, the label text is the override text on the page. Looking at the label text, you can tell whether it has been translated. If it has not been translated, use Translation Designer to do the translation.

   See Using Translation Designer.

5. Click the Save button.

Translating Application Data

The Translate Application Data page enables you to translate system and customer data. This page does not allow you to translate managed objects.

Note. To use the Translate Application Data page you must be logged into the PeopleSoft Pure Internet Architecture in the base language.

Before you can translate application data, you must enable access to the Translate Application Data page. This section describes how to:

• Enable access to the Translate Application Data page.

• Translate record fields or ignore record fields for translation.

Enabling Access to the Translate Application Data Page

To enable access to the Translate Application Data page:

1. Select PeopleTools, Security, Permissions & Roles, Permission Lists.

   The Permissions List page appears.

2. Select a permission list that is assigned to your user ID.

   The permission list displays.

3. Select the Pages page.

4. Click the Edit Components link for the Translate menu item.

   The Component Permissions list displays.

5. Click the Edit Pages link for the Translate Application Data item.

   The Page Permissions page appears.

6. Click the Select All button.

7. Click the OK button, click the next OK button, and then click the Save button.

8. Repeat steps 2 through 7 for other users or roles that need access to the page.

9. Select PeopleTools, Portal, Structure and Content.

10. Click the PeopleTools link.

11. Click the Translations link.

12. Click the Translate System Definitions link.

13. Click the Edit link for the Application Data item.

14. Clear the Hide in Navigation check box.

15. Save your changes.

Translating Application Data

Before you can translate application data, you must enable access to the Translate Application Data page.

See Enabling Access to the Translate Application Data Page.

To translate application data:

1. Select PeopleTools, Translations, Translate System Definitions, Application Data.

   The Translate Application Data page appears.

2. In the Record to Translate field, enter the base table name.

3. From the Target Language drop-down list box, select the target language.

4. Optionally, click the Filter with SQL? link to select the record fields to translate.

5. Click Search.

   When you click Search, the page appears the related language record, the number of rows or values found, and the first of all key names and key values for the table. For each value, the translatable fields display in the Base Text column in the base language of the database. The Lang Text fields display translations for the fields, if they exist. Use the View All link or the Show Previous and Show Next arrows to navigate through the results retrieved.

   Note. The following information describes how to work with all rows in a record or specific rows in a record.

   • To work with all rows in a record, click Search.

   • To select specific rows in a record, click the Filter with SQL? link.

     A WHERE clause page appears that provides you with an area to enter an SQL statement that will filter the record data. Enter a WHERE clause to filter the data.

     The field names that you can use in the WHERE clause display in the Record Fields box. To expand the list, click the View All link.

     After you enter a WHERE clause, click OK to return to the Translate Application Data page. Click Search.

6. Translate or ignore the record fields.

   Some related language tables contain fields that should never be translated. You can choose to translate the record fields or tell the system to ignore them for translation.

   • To translate a field, in the Lang Text box, enter a translation for the item in the Base Text field.

   • To ignore a field for translation, check the Ignore? box next to the Lang Text box. The following message displays:

     Ignoring field: Translations for this field will be overwritten with base⇒
      language values, proceed? (102,83)
     
     By ignoring this field, any translation for this field will be overwritten with⇒
      the base language values. Do you want to proceed?
     

     Click Yes.

     Note. This message displays the first time you check the Ignore? box for a translatable field. If you check this box again for the same field, the message will not display and the system copies, in the base language, the text in the Base Text field over to the Lang Text field. This text will appear in all rows in the table. Therefore, do not use the Ignore? option to simply copy the information in the Base Text field to the Lang Text box. To remove an entry in the Lang Text box made under these circumstances, clear the Ignore? box and delete the entry.

7. Click Save.

Translating Connected Query Definitions

The following table lists the objects, base table, related language table, and tool used to translate connected query definitions:

The Translate Connected Query Definitions page enables you to translate the short and long descriptions for a connected query definition into a specific target language.

To translate connected query definitions:

1. Select PeopleTools, Translations, Translate System Definitions, Connected Query Definitions.

   The Translate Connected Query Definitions page appears.

2. In the Connected Query field, enter the name of the connected query to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Connected Query field blank if you want to select all object definitions in the system.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the connected query definitions into the object list.

   A set of connected query definitions appears in the Connected Query List based on the value you entered in the Connected Query field.

5. Translate the short and long descriptions into the target language.

   The base language descriptions for each connected query appear on the left; enter the translations in the Target Description fields on the right.

6. Click the Save button.

Translating HTML Definitions

You typically translate HTML definitions when they contain hard-coded text. Most HTML definitions should contain JavaScript and references to the Message Catalog only, and therefore don’t require separate translation. However it is possible to hard-code text into HTML definitions which may require translation using this method.

To translate an HTML definition:

1. Change the PeopleSoft Configuration Manager language preference to the target language.

2. Login to the PeopleSoft system.

3. Open Application Designer.

4. Open the HTML definition.

   Choose File, Open and select the HTML definition you want to open.

5. Edit any language-sensitive text in the HTML object.

6. Save the HTML object.

Translating Integration Broker Definitions

The following table lists the objects, base table, related language table, and tool used to translate Integration Broker objects:

PeopleTools features one page for each Integration Broker object that you can use to translate object descriptions into a specific target language.

Note. The following steps for translating Integration Broker objects apply to all of the objects in the preceding table.

To translate a Integration Broker object:

1. Select PeopleTools, Translations, Translate System Definitions.

   The Translate System Definitions menu appears.

2. Select one of the following menu items to translate the corresponding Integration Broker object descriptions:

   • Message Definitions

   • Queues

   • Routings

   • Service Operation Handlers

   • Service Operations

   • Service Operation Versions

   • Services

   The corresponding translation page appears.

3. Based on the object descriptions that you are translating, do the following:

   Object Descriptions to Translate	Action
   Message Definitions	In the Message field, enter the name of the message definition to translate or use the Look up button (Alt+5) to select a specific definition.
   Queues	In the Queue Name field, enter the name of the queue to translate or use the Look up button (Alt+5) to select a specific definition.
   Routings	In the Routing Name field, enter the name of the routing to translate or use the Look up button (Alt+5) to select a specific definition.
   Service Operation Handlers	In the Operation field, enter the name of the service operation handler to translate or use the Look up button (Alt+5) to select a specific definition.
   Service Operations	In the Operation field, enter the name of the service operation to translate or use the Look up button (Alt+5) to select a specific definition.
   Service Operation Versions	In the Operation field, enter the name of the service operation that contains the version to translate or use the Look up button (Alt+5) to select a specific definition.
   Services	In the Service field, enter the name of the service to translate or use the Look up button (Alt+5) to select a specific definition.

   Note. Leave the field blank if you want to select all object definitions in the system.

4. In the Target Language field, select the language into which to translate the object definitions.

5. Click the Get Objects button to bring the object definitions into the object list.

   Note. If no descriptions exist in the base language, no results are returned.

6. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translations in the Target Description fields on the right.

7. Click the Save button.

Translating XML Publisher Definitions

The following table lists the objects, base table, related language table, and tool used to translate XML Publisher objects:

This section discusses how to translate the descriptions for:

• XML Publisher data source definitions.

• XML Publisher report definitions.

• XML Publisher template definitions.

In addition to translating the descriptions for these definitions, you can also translate the "translatable units" for report templates.

See Maintaining Template Translations.

Translating XML Publisher Data Source Definitions

The Translate XML Publisher Data Source Definitions page enables you to translate the description for a XML Publisher data source definition into a specific target language.

To translate XML Publisher data source definitions:

1. Select PeopleTools, Translations, Translate System Definitions, XMLP Data Sources.

   The Translate XML Publisher Data Source Definitions page appears.

2. In the Data Source Type field, enter the name of the XML Publisher data source type to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Data Source Type field blank if you want to select all object definitions in the system.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the XML Publisher data source definitions into the object list.

   A set of XML Publisher data source definitions appears in the Data Source List based on the value you entered in the Data Source Type field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating XML Publisher Report Definitions

The Translate XML Publisher Report Definitions page enables you to translate the description for a XML Publisher report definition into a specific target language.

To translate XML Publisher report definitions:

1. Select PeopleTools, Translations, Translate System Definitions, XMLP Report Definitions.

   The Translate XML Publisher Report Definitions page appears.

2. In the Report Name field, enter the name of the XML Publisher report definition to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Report Name field blank if you want to select all object definitions in the system.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the XML Publisher report definitions into the object list.

   A set of XML Publisher report definitions appears in the Report Definition List based on the value you entered in the Report Name field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating XML Publisher Template Definitions

The Translate XML Publisher Template Definitions page enables you to translate the description for a XML Publisher template definition into a specific target language.

To translate XML Publisher template definitions:

1. Select PeopleTools, Translations, Translate System Definitions, XMLP Template Definitions.

   The Translate XML Publisher Template Definitions page appears.

2. In the Template ID field, enter the name of the XML Publisher template definition to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Template ID field blank if you want to select all object definitions in the system.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the XML Publisher template definitions into the object list.

   A set of XML Publisher template definitions appears in the Template List based on the value you entered in the Template ID field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating ACE Analytic Model ID Definitions

The Translate Analytic Model page enables you to translate short and long descriptions for Analytic Calculation Engine (ACE) analytic model ID definitions into a specific target language.

The following table lists where to translate analytic model ID definitions.

To access the Translate Analytic Model page, select PeopleTools, Translations, Translate System Definitions, Translate Analytic Model.

To translate an ACE analytic model ID definition:

1. In the Model ID field, select the analytic model ID to translate.

   Leave the Model ID field blank if you want to select all analytic model ID definitions in the system.

   If you want to work through the records alphabetically, enter the first characters of the record name in the Model ID field. If you want to translate a specific record, enter the record name in the Model ID field or use the Search button to prompt for a specific record.

2. In the Target Language field, select the language into which to translate the record descriptions.

3. Click the Get Model ID button In the Record field, select a set of record definitions.

   A set of model ID definitions appears in the Analytic Model List based on the value you entered into the Model ID field.

4. Translate the short and long descriptions into the target language.

   The base language descriptions for each model ID appear on the left; enter the translations in the Target Description fields on the right.

5. Click the Save button.

Translating Essbase Cube Definitions

The following table lists the objects, base table, related language table, and tool used to translate Essbase cube definitions:

This section discusses how to translate:

• Cube connection definitions

• Cube dimensions

• Cube outlines

• Cube templates

Translating Cube Connection Definitions

The Translate Cube Connection Definitions page enables you to translate the description for a cube connection definition into a specific target language.

To translate cube connection definitions:

1. Select PeopleTools, Translations, Translate System Definitions, Cube Connection Definitions.

   The Translate Cube Connection Definitions page appears.

2. In the Essbase Connection ID field, enter the name of the cube connection to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Essbase Connection ID field blank if you want to select all object definitions in the system.

   Note. If you want to work through the records alphabetically, enter the first characters of the record in Essbase Connection ID field. If you want to translate a specific record, enter the record name in the Essbase Connection ID field or use the Search button to prompt for a specific record.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the cube connection definitions into the object list.

   A set of cube connection definitions appears in the Cube Connection List based on the value you entered in the Essbase Connection ID field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating Cube Dimensions

The Translate Cube Dimensions page enables you to translate the description for a cube dimension into a specific target language.

To translate cube dimensions:

1. Select PeopleTools, Translations, Translate System Definitions, Cube Dimensions.

   The Translate Cube Dimensions page appears.

2. In the Dimension Name field, enter the name of the cube dimension to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Dimension Name field blank if you want to select all object definitions in the system.

   Note. If you want to work through the records alphabetically, enter the first characters of the record in Dimension Name field. If you want to translate a specific record, enter the record name in the Dimension Name field or use the Search button to prompt for a specific record.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the cube dimension definitions into the object list.

   A set of cube dimension definitions appears in the Cube Dimension List based on the value you entered in the Dimension Name field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating Cube Outlines

The Translate Cube Outlines page enables you to translate the description for a cube outline into a specific target language.

To translate cube outlines:

1. Select PeopleTools, Translations, Translate System Definitions, Cube Outlines.

   The Translate Cube Outlines page appears.

2. In the Outline Name field, enter the name of the cube outline to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Outline Name field blank if you want to select all object definitions in the system.

   Note. If you want to work through the records alphabetically, enter the first characters of the record in Outline Name field. If you want to translate a specific record, enter the record name in the Outline Name field or use the Search button to prompt for a specific record.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the cube outline definitions into the object list.

   A set of cube outline definitions appears in the Cube Outline List based on the value you entered in the Outline Name field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating Cube Templates

The Translate Cube Templates page enables you to translate the description for a cube template into a specific target language.

To translate cube templates:

1. Select PeopleTools, Translations, Translate System Definitions, Cube Templates.

   The Translate Cube Templates page appears.

2. In the Template Name field, enter the name of the cube template to translate or use the Look up button (Alt+5) to select a specific definition.

   Leave the Template ID field blank if you want to select all object definitions in the system.

   Note. If you want to work through the records alphabetically, enter the first characters of the record in Template ID field. If you want to translate a specific record, enter the record name in the Template ID field or use the Search button to prompt for a specific record.

3. In the Target Language field, select the language into which to translate the object definitions.

4. Click the Get Objects button to bring the cube template definitions into the object list.

   A set of cube template definitions appears in the Cube Template List based on the value you entered in the Template Name field.

5. Translate the descriptions into the target language.

   The base language description for each object appears on the left; enter the translation in the Target Description field on the right.

6. Click the Save button.

Translating Time Zone Labels

There are two ways to translate time zone labels in PeopleTools:

• Using the Translate Application Data page.

• Using the Time Zone IDs page.

Translating Time Zone Labels Using the Translate Application Data Page

To translate time zone labels using the Translate Application Data page.

1. Ensure that the Translate Application Data page has been enabled.

   See Enabling Access to the Translate Application Data Page.

2. Select PeopleTools, Translations, Translate System Definitions, Application Data.

3. In the Record to Translate field, enter PSTIMEZONE.

4. From the Target Language drop-down list box, select the language into which to translate the time zone label.

5. Click the Save button.

Translating Time Zone Labels Using the Time Zone IDs Page

To translate time zone labels using the Time Zone IDs page:

1. Sign into the PeopleSoft system using the target language.

   Note. Alternatively, if you have enabled multi-language entry, then you can select the target language in the Data Language drop-down list box on the Time Zone IDs page.

2. Select PeopleTools, Utilities, International, Time Zones.

   The Time Zone IDs page appears.

3. Locate a time zone with which to work from the list.

4. In the Description field, enter a translated description for this time zone.

5. Optionally, in the ID for Standard Time field, enter a label for the time zone for when standard time is in effect.

6. Optionally, in the ID for DST field, enter a label for the time zone for when daylight saving time is in effect (if applicable).

7. Click the Save button.

Additional information on using the Translate Application Data page can be found in this PeopleBook.

See Translating Application Data.