Using iTop

Creating your iTop

iTop Customization

"How to" examples

User Interface

Automation & Ticket management

Portal Customization

:: Version 3.2.0 ::

(Re-)Define dictionary entries

Prerequisite: You must be familiar with the Syntax used in Tutorials and have already created an extension.

Change a label for a field, a button, a menu,...
Dictionary, XML
min version:


With this tutorial you will learn how to modify a label displayed somewhere in iTop and create new dictionary entries.

Check the reference for understanding Dictionary entries naming conventions

with the Designer

with an iTop Extension

Modify an XML entry

You want to change an iTop label.

First things to do is to find its code.

For generic labels, check those files your-itop/dictionary/, where xxx is:

  • ui for labels used in the User Interface (UI)
  • core for labels of field types and generic objects such as: History, Trigger-Action, DataSynchro, BulkExport,…

For a label related to a Datamodel class, its code will be in your-itop/datamodels/2.x/xxx/ where xxx is the module name which handle that class.

Once you have the code, you just need to redefine its value in a extension, as described below.
Note the _delta=“redefine” to replace the existing value and the _delta=“force” if you are not sure that there was previously an entry for that code.

In this example we will suppose that in your iTop, the “Requestor” of a UserRequest, should be called Beneficiary, so here is how to do this:

itop_design / dictionaries
    <dictionary id="EN US" _delta="must_exist">
        <entry id="Class:UserRequest/Attribute:caller_id" _delta="redefine">
        <entry id="Class:UserRequest/Attribute:caller_id+" _delta="force">
          <![CDATA[Choose the client person who will get the requested service]]>
The second entry, with the same code completed by a plus sign correspond to additional information, displayed for Attribute as a tooltip when moving your mouse over the field in read mode
The caller_id is a field of the Ticket class, but the above entry was made on UserRequest class, as a result on other Ticket sub-classes such as Incident or Change, this field will still be labelled Requestor.

New XML entry

Note the _delta=“define” to create a new entry, it will fail if that entry already exist.

itop_design / dictionaries
    <dictionary id="EN US" _delta="must_exist">
        <entry id="Class:Team/Attribute:dashboard" _delta="define">
Here we created an entry in the english dictionary.
Replace EN US by FR FR for French labels.

Duplicate the XML structure if you want to defined labels for multiple languages.

Check here for ISO country values. iTop supports any language, but natively includes only a few.

More on iTop translation

Using dictionary files

Instead of defining dictionary entries in XML, you may define them in php file, one per language. See here for an example of this method

3_2_0/customization/add-dictionay-entry.txt · Last modified: 2024/06/20 17:28 (external edit)
Back to top
Contact us