Did you miss our iTop 3.2 webinar? Watch the replay now!

Thank you for your engaging questions during the webinar!

We've compiled all the answers from the session for you to review.

Newsroom, notifications and user interface

Are the notification triggers configurable? For example, can they be used on created classes with new person/date fields?

Generic triggers in iTop include the creation, updating, and deletion of object characteristics. Some triggers are related to workflows (transitioning from one state to another) or can be introduced by external modules. Any event can be associated with a trigger in iTop.

What about sending invitations, are the fields customizable?

It is possible to rely on any date field of the trigger object (this field is configurable)

Will these "standard" notifications be automatically delivered with the installation of version 3.2?

There are already a number of notifications available upon installing iTop, and we are currently working to enhance these sample data.

Is it possible to create a trigger for a checked box and notify someone when a box is checked?

Checkboxes are not standard elements in iTop. However, by using a "yes/no" enum, it is possible to trigger an action when the value of any field changes.

How do invitations work with an Outlook calendar?

The process is similar to that of Gmail. The invitation is the same as one sent by a person via their email address. You simply need to accept or decline it for it to appear in the calendar. The same goes for updates.

Is it planned to allow a user to unsubscribe from calendar notifications for tasks?

This is not feasible for obvious practical reasons: a calendar invitation is intended to reserve a time slot in a calendar for resources that need to perform a task (change, intervention, etc.). The user always has the option to decline this invitation.

However, if the user only wants to be informed about a task, we recommend using notifications instead of calendar invitations.

Does the search offered to the user in the portal only cover their tickets (for example, the tickets where they are the caller)? Is it contextual to the user?

The portal search is restricted to the scope associated with his profile. Therefore, he will only be able to search within the tickets related to his scope.

Does the new web page design consider accessibility (compliance with RGAA), for example, for visually impaired users?

As explained during the webinar, the ergonomics of the iTop back-office console include numerous enhancements for visually impaired users, in compliance with the WCAG guidelines.

If I remember correctly, there is no user provisioning function when SAML authentication is used, why not implement it? It would also be useful to automatically sync your profile picture.

It is not implemented at the moment due to the complexity of configuring each SAML identity provider, as we have created a generic interface for SAML, whereas the one set up for OpenID or OAuth is tailored to each provider.

If Assign to Me is integrated into 3.2, will it be necessary to uninstall the extension? Review the associated configuration file?

There is no specific action required as iTop always installs the latest version of the module, which is included in iTop 3.2. However, to maintain a "clean" iTop, you can uninstall the old module after the migration.

To check what is no longer needed, it is possible to conduct a migration audit. For this, you can contact our support team.

Is it not possible to upgrade directly from 2.7 to 3.2? Are we always required to go through 3.0 and then 3.1 before reaching 3.2?

It is possible to make a direct transition from 2.7 to 3.2, which generally proceeds very smoothly. However, we remind you that there is no common PHP version between 2.7 and 3.2, so we encourage you to install a new VM, transfer the backup to it, and then proceed with the 3.2 installation.

You can refer to the migration notes.

For the migration from 2.6 to 3.2, can you remind me of the deadline? And is there any support planned?

As outlined in the iTop maintenance calendar, iTop 2.6 STS (Short Term Support) has not been supported since the end of 2021. Therefore, we encourage you to migrate to iTop 3.2 as soon as possible.

If you are a Combodo customer, migration assistance is included in your subscription contract.

We are currently using version 3.1.0-3 with a functional Case Exchange 2.2.3 for our exchanges with the Service Now of our IT managers. Will version 3.2 still be compatible with Case Exchange Base 2.2.3 Stable?

iTop 3.2 will indeed be compatible with Case Exchange Base 2.2.3

iTop 3.2 will indeed be compatible with Case Exchange Base 2.2.3

MySQL 5.7 is compatible up to iTop 3.2.

For performance reasons, we do not recommend using MySQL 8.

Since MySQL 9 was released during the development of iTop 3.2, we still lack sufficient experience to advise you.