You are browsing the documentation for iTop 2.6 which is not the current version.

Consider browsing to iTop 3.2 documentation

What's new in iTop 2.4


This new feature is targeted for iTop installations with multiple years of data, performance issue and a requirement to keep even the old data accessible online. It enables flagging old data as archived which is equivalent to a “soft delete”. Archived data look like truly deleted, also they can be seen again with a special console mode.

How does it work


This new feature allows to

  • identify obsolete objects,
  • highlight this status with icon and tag when listing and displaying those objects,

  • improve impact analysis accuracy by ignoring obsolete objects.
  • hide obsolete objects from displayed list, if requested by the user

Check details here


This feature was enhanced to remove some of the known limitations.

What's possible now on Ticket

  • User is forced to change the agent during a re-assign transition, but not in any place else.
  • agent is
    • read-only in assigned state,
    • hidden in any state before
    • mandatory in ev_assign transitions.

What's possible on any class with lifecycle

  • Force a field to be documented when going from a particular state to another, but for any other transition ending on the same final state, do not prompt for that field.
  • Force a field to be documented in a transition, but then be read-only in the final state.
  • Force a field to be documented in the portal on a transition, while it is not mandatory on the console
  • Force a field to be hidden on the portal on a transition, while it is prompted in the console

How does it work


  • You can set attachment in read-only mode based on object states in portal and/or console. Example, preventing a portal user to add an attachment on a closed ticket.

Enhanced portal

Introduced in 2.3.0, the Portal gets mature with multiple enhancements:

  • Filter Brick extension is now included to the core application.
  • Create Brick now supports abstract class.
  • Manage Brick displays object count on each tab.
  • Browse Brick offers a new Mosaic mode:

 Tree mode has an optionnal description, improving readability and filter efficiency

  • Multiple enhancements on Forms, such as: opening mode, display mode, use of dictionary entries,…
  • New forms per transition, redefining the displayed/required fields.
  • Hiding/enabling transitions by user profile.

More details here

Importing Images and Files

It is now possible to import Images and Files attributes through CSV import, convenient for loading images for the Mosaic mode of the portal.

More details here

Console Look & Feel

We have revisited the layout used to display and edit an object in the console:

  • Aligned labels to the left
  • Set the same width for each field in edit mode
  • Put Text and HTML attributes under their label, using the full width of the column.
  • Offer a full screen mode for Text attribute as we have for HTML

  • Add an horizontal scroll-bar when the window is not large enough to display the object
  • Fix bugs by which fields were getting out of the frame.


  • Creating an object from another one in view mode: New Configuration parameter allow_menu_on_linkset to enable “Actions” menus in read mode on LinkedSet attributes.
  • New placeholder $current_user->friendlyname$ on Notification to reference the user having done the change which has triggered the Action.

New in 2.4.1

  • Enable HTML editor and support of must_change flag for CaseLog on transitions.
  • In console, align layout of Display and Modify of an object to take all available space, have equally sized columns and automatic columns resizing when the window is resized.

2_6_0/release/2_4_whats_new.txt · Last modified: 2020/02/05 11:42 (external edit)
Back to top
Contact us