Customizing iTop

By adding existing extensions

Check what exist and you may pick-up some in this list of published extensions and install them as documented.

Base knowledge on creating iTop extensions modules:

Refer to iTop customization mechanism to understand how to extend or modify iTop.
Start by this step by step example, to create your first extension.

Don't be afraid to write your first extension, even if you are not a developer.
Many customizations can be done without a single line of PHP code

Helper to create the mandatory files for a new extension.
Searching and manipulating objects API
Adding business logic on objects using CRUD events, which are called following CRUD sequence
Adding your own events: Events API - New in 3.1 - Methods versus events
Customizing the GUI with Interfaces API
For XML syntax: XML Data Model Reference and XML Portal reference .
For PHP code: iTop coding standards
For icons: FontAwesome v5

Get familiar with the tutorial syntax before reading below examples

Force a field to be mandatory - reworked in May 2025
- Only on a particular condition
- Only for a subset of final classes
Make a field read-only - reworked in May 2025
Hide cost for some users
Form Prefill:
- Prefill fields in an object creation form
- Prefill fields in a transition
- Prefill search criteria, when searching objects to link them to the current object
Check data integrity: - reworked in May 2025
- Ensure that End date is after Start date
- Ensure that a Location is filled when on Physical Device is on Production
- Prevent changes on LinkedSet: eg prevent consumptions exceeding stock - August 2024
- Prevent Person's organization change to break associated Portal user
- Prevent Users to create object of a class and limit them to modification only.
Define Obsolescence rules
Prevent duplicates

Only available since version 2.3, the enhanced Portal offers customization options

Examples of How to :