Managing multiple languages

Follow the following steps to manage templates in multiple languages or in a language that is not the 'master' language defined on the customer code:
 
(1)    When we define a form template we need to go through 2 steps:

a.       Run the form wizard in a ‘master language’

b.      Run the form wizard again in the target language


So the form template should be defined in 2 languages.

 

(2)    You can determine the language of the form template and select the correct one using the form-level  ‘Template’ user-exit. So, for example, here you can select the form language based on the language of the logged in user.

 

1:
2:
3:
4:
5:
6:
7:
8:
9:
DATA: l_spras TYPE spras.

     CALL METHOD /flm/core3=>get_logon_language
       EXPORTING
          im_user = im_user
       RECEIVING
          re_lang = l_spras.

ex_toption = l_spras  D


(3) The Action list at the bottom of the form always considers the language of the logged in user.

  • Customer-defined actions should be translated in table /flm/factt
  • In order to maintain these translations, use the menu path from SPRO: Cross-Application Functions / General Application Functions / Forms LiveCycle Manager / Initialize Customer Code / Define Form Actions
  • Then select the entry you want to translate and use the menu path Goto / Translation

(4) Three actions are delivered for forms at initial status:

  • D – Save to Draft
  • L – Delete Form
  • 99 – Save as Template action

(5) In order to translate those into other languages, we provide domains /FLM/DRAFT, /FLM/DELETE and /FLM/SAT   so the translation can be managed as a repair in SE11.

 

The Define Template Option allows new template options to be created for each language.

 

 

When creating a new form Template in the Form Wizard, the Template option is selected for each language. Subform and field Captions for HTML templates and Excel uploads can be maintained for the language of the Template Option.

 

 

Stelo Apps

 

Within Stelo generate apps the handling of multiple language is managed using standard UI5 i18n files. A sample is shown below which includes the generated entries for the app title and description used in the Fiori launchpad.

 

1:
2:
3:
4:
5:
6:
7:
8:
9:
      # **********************************************
      # Customer Start

      # Customer End
      # **********************************************

      #FLP Support
      appTitle=Travel to Work Loan
      appDescription=Travel to Work Loan

 

        If a user logs in with any language Fiori will automatically look for a i18n file for that language and use the equivalent values.