EBS-TranslationToolEN

Entersoft Business Suite^® | Entersoft CRM^®

The data translation process – User guide

Identity

Document version 1.0.0

Software version 4.0.44.0

Last Update May 2016

Copyright

© Copyright 2012 - 2016 Entersoft S.A. All rights reserved.

No part of this work may be reproduced, transmitted, stored, or used in any form or by any means, without the prior written permission of the publisher.

Regarding the present content …

• It may be altered at any time.
• It serves exclusively informative goals.
• No guarantee whatsoever is handed out for the possible existence of mistakes or the wrongful use or non-wanted results produced by the use of processes hereby followed and recommended.

Table of = Introduction =

The data translation tool enables you to manage translation needs of different objects. This document describes all the actions required to create objects that must be translated in different cultures. The following topics are covered:

• ODS multilingual tables
• Table translation
• Custom, multilingual report development

ODS multilingual tables

Language definition

Table data translation requires first to define the languages that you need to perform translation. You can do this task using the ODS tool as follows:

• Use the button located to the right hand side toolbar to navigate to languages tab page

• Using the add action you can select the language that you need to perform translation

When a language is selected the following dialogue appears:

Using the above dialogue you may set the fallback level of the language. In this context, in case where the translation of a field is null then the system will return the translation of the fallback language. You may set more than one fallback languages. The fallback level is always <> 0 and the order is descending. Moreover, you may set the image of the selected language. The system provides an image repository with the most common languages image under the category ‘4. Languages’.

• You may override the name of the selected language
• Publish language definition using the relative action as shown below

Publication process will update the table ES00ZDataLanguage that contains the languages defined using the steps mentioned above.

Multilingual table definition

In order to define which tables you need to translate the following steps must be followed:

• Select the table subpage using the action button located to the right hand side toolbar
• You can translate any table you need, zoom, entity master or detail table. In this context, you must select the table you need its data to be translated using the context action as shown below. For example, you need to translate the zoom table ESGOZBusinessUnit:

The system shows the following multilingual table:

Using the ‘Select’ action you can define which fields of the selected table you need to be translated. The system shows the available string-text fields that can be translated:

Continue the above process for every table that you need to translate.

• Publish multilingual tables using the relative one click publish action. The publication process will generate the following:
  • A multilingual table for each table that must be translated. The name of the table is generated as follows: Translated table name + Multilingual, e.g. ESGOZBusinessUnitMultilingual
  • A view per each translated table and language. The name of the view is generated as follows Translated table name + ISO name of the selected culture (language), e.g. ESGOZBusinessUnitEN. The structure of the view is the same as the table structure. The view returns the records of the translated table having the translated columns that you have chosen for translation using the above steps. The translation of a column is returned based on the fall back levels you have defined. For example, if you have defined 2 fall back levels then the translations of the field is returned based on the rule translation = coalesce (selected language , fall back level 1 language, fall back level 2 language, base record column data).
  • A multilingual view per each translated table. The multilingual view returns the records of the translated table having the translated columns that you have chosen for translation but for all languages you have defined.

Editing multilingual tables

You can edit at any time the specification of an existing multilingual table in order to enhance its definition related to the translated columns or/and adding a performance index.

In order to do this, you have to change the ODS view to multilingual tables using the drop down selector on the right hand side.

To edit a multilingual table select a row and then edit using the relative action. When you have completed the changes you need to perform on click publish action to generate the changes to the DB schema.

Translating tables

Translating zooms

In order to translate zoom tables you must navigate to central configuration and select the zoom that you have chosen to translate its data.

You can perform translation by selecting the context action ‘Data translation’ located in the submenu ‘Actions’ of the toolbar of the configuration page.

Using the translation modal dialog you have to select the translation language first if you have defined more than one translation languages. The grid displays all the fields that you have selected for translation in the relative ODS definition. When you have completed the translation then you must save the changes.

You may also perform on the spot translation. In this context, when a translated field is in focus an action button is displayed as shown below:

Using the action button you can translate the data content for each language defined in the ODS.

Translating entity tables

You can translate entity records by selecting the relative action ‘Data translation’ located on the submenu ‘Actions’ of the main toolbar of the entity UI form.

If you have selected more than one entity table to be translated you have to choose first the table using the relative drop down selector. Moreover, you need also to select the language if your ODS language definition includes more than one languages.

The grid displays all the fields that you have selected for translation in the relative ODS definition. When you have completed the translation then you must save the changes. You may also perform on the spot translation in the same way as mentioned in section 3.1.

Import / Export Translations

You can use export/import services to create Excel files that can be sent to a translator to perform translation. Using export service you may select for the ODS languages you need. In this context, the system will produce an excel for selected language.

Import / Export services are available from UI form actions and Scroller relative actions

If you need to translate multiple entity records you may select a list (Scroller) that is used to manage these records. For the selected records (multi select), use the relative export action to create one or more export file depending on the selected records. If the translated entity includes more than one translated tables then an excel is produced per language and table.

Translation User Authorization

You may define which users are authorized to perform translation using the central authorization system as shown below:

Developing a multilingual report

You can create a multilingual report using the EBS query builder as follows:

• The main query must use the multilingual view(s) generated by the ODS publish services. The multilingual view is named using the name of the table that has been defined as multilingual with suffix MultilingualView, e.g. ESTMTaskMultilingualView. It is reminded that the structure of the view is the same as the original table having translated the columns that you have chosen.
• The query must have as parameter the language that you need to present the result set. The parameter must be defined in the where clause using the equal operator. Moreover, the parameter must be defined as query parameter as shown below:

PDF Version