System Texts

The system-texts manager allows to adapt any text displayed in the system as required. System texts are managed in so-called "bundles". Each bundle contains a given system text in all platform languages.

Example: The term "Learning path" is to be replaced by "Course series". A search for the term "learning path" will return all bundles containing the term so they can be adapted to the customer's specific needs.

System texts and instructions for use can be defined. Instructions for use can simply be integrated into the existing system interface. System texts can only be integrated in isolated cases and for specific points via the configuration file.

These settings are relevant to the client context. By selecting the client, the changes will only apply to this specific client and will not affect other clients. The client context is also visible in the column "text context" of already changed bundles. Unchanged bundles are tagged with "Global". If the user wants to undo changes he can mark changed bundles and click on reset. Changed bundles will have the default value ("Global") again.

Functions of the system text manager

New

New system texts can be added here. A distinction is made between instructions for use and system texts.

New → Switching the display for online help bundles

Instructions for use are highlighted in the system by "i" icons. In the active administrator mode, empty instructions for use can also be displayed which are identified by a small red triangle in the top right hand corner. If a new instruction for use is created, this can be created in a pre-defined position where an instruction for use that has not yet been created was intended to be located. In addition, a bundle name must be assigned and at least one identifier must be specified. The bundle name is freely selectable. The identifier which serves to link the text with the corresponding place in the system, is displayed by clicking on an empty instruction for use below the "i". With text that already exists within an instruction for use, the identifier and bundle name are displayed in the first line. Any number of identifiers can be added. As a result, in all the places where the entered identifiers are used, the same instructions for use appear. New instructions for use can be created in all the available platform languages.

New → System wording

Using this option, new bundles can be created which are integrated via the configuration file and thus can be displayed on the screen. The bundle name is also assigned here and the bundle can be created in all platform languages.

Edit

Upon editing bundles, they are displayed in all available languages. When editing, one of the "standard wording", "customer wording" or "patch wording" texts can be adopted and can be used as the basis for further editing.

Editing → Identifier

The text of a bundle can be edited both for system texts and for instructions for use in equal measure. With instructions for use, the identifier can also be adapted independently from the text of the bundle. Additional identifiers can be added and can no longer be deleted.

Flag

Flag → Set flag

Flags serve as permanent identifiers of bundles. Line-by-line highlighting of bundles can only take place within a spreadsheet. Highlighting with flags can however be applied universally. If highlighting with flags was used, it is identified by an entry in the table in the "With flag" column. Before executing the function, any number of lines can be highlighted in the table. Bundles with flags can be exported separately.

Flag → Remove flag

Set flags are removed from the selected lines in the table.

Flag -> Remove all flags

By executing this function, the flags are removed from all bundles in the table. Thereby, it is irrelevant as to whether the lines are highlighted or are visible in the current spreadsheet.

Export

An easy way of updating existing system texts is provided by the export or import of bundles. Exporting results in TXT files which can be edited easily and re-entered into the system via import. For each platform language, one TXT file is created.

The exporting of bundles can be restricted so that not all bundles that have been created must be exported. The option exists of only exporting individual languages. In addition, it can be configured to show whether standard, customer or patch wording or active or amended wording should be exported. In addition, it can be also restricted as to whether all bundles or only those with flags should be exported. For back-up purposes, the option also exists to carry out a back-up of the active wording. When choosing this option, all other settings are ignored in the export input window.

Import

Upon importing, some requirements apply to the import files. The most convenient way to manage imports is to conduct them on the basis of previously exported files.

• The text file to be imported must have the coding UTF-8.

• The name of the import file needs to be in the format imp_countrycode_YYYYMMTT.txt (e.g. imp_br_YYYYMMTT.txt for British English or imp_en_YYYYMMTT.txt for American English).

• The import file is a line-oriented txt file, with tab stops serving to divide columns.

• For each dataset that is to be imported, one line contains the appropriate column information.

• Each line generally consists of bundle name/tab stop/bundle text/tab stop and is completed by a line break. Possible text between the second tab stop and the line break will be ignored.

• Only datasets for which the imported text differs from the changed text or - if no changed text exists - from the active text will be updated.

• If the imported text differs from the changed text but matches the active text, the changed text will be deleted.

• Datasets with unknown bundle names will not be imported.

• They must not contain any line breaks. If necessary, the line breaks must be entered with "<br>"!

The uploaded system texts need to be activated, just like with manual editing.

A backup is recommended before each import for backup purposes.

Activation

Bundles are not directly transferred to active wording but only marked as change. To transfer the amended text to the system and thus also to the customer wording, the "Activation" function must be carried out. The new active wording is visible on the new page without restarting the system.

Reset

If unintentional changes should be made and switched to active, the wording can always be switched back to the original state again. In the meantime, patch wordings that have been supplied are not deleted and are therefore taken into consideration. All customer wordings get lost when reset. For backup purposes, a backup can also be carried out before resetting. The functionality can either be carried out for all bundles or partially for the bundles highlighted in the table and bundles assigned with flags.

Administrator mode

If changes are made to bundles, then the corresponding bundle text can either be searched for directly in the search of the system text or be activated via the administrator mode for instructions for use or system texts.

Administrator mode → ISwitching the display for online help bundles

In non-activated administrator mode, only the instructions for use are displayed that contain text. On top of that, optional instructions for use are available in many places in the systems which are not seen however, because they do not contain any text. If the administrator mode is active, populated instructions for use appear with a small green triangle in the bottom left-hand corner, and empty instructions for use with a small red triangle in the top right corner.

Administrator mode → Switching the display for system text bundles

If system texts are changed, the corresponding wording can be searched for. As several bundles can exist with identical text, it must be checked which precise bundle must be changed. If the administrator mode for system texts is activated, only the bundle names are displayed all over the system interface. The bundle text remains hidden. In the administration area of system texts, bundle names can be searched for specifically.

Hint

These settings are relevant to the client context. By selecting the client, the changes will only apply to this specific client and will not affect other clients. The client context is also visible in the column "text context" of already changed bundles. Unchanged bundles are tagged with "Global".

If the user wants to undo changes he can mark changed bundles and click on reset. Changed bundles will have the default value ("Global") again.

Global Functions and Related Topics