Using iTop

Creating your iTop

iTop Customization

"How to" examples

User Interface

Automation & Ticket management

Portal Customization

:: Version 3.2.0 ::

Force a field to be mandatory

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

Force a field to be provided
XML, PHP, Constrain, Portal
min version:

There are many ways to force a field to be provided, depending on what you want to achieve. Each technic is described in a separate tutorial, just follow the link which correspond to what you want to achieve.

The different technics will not work in all situations, for each technic, the tutorial will mention which modification will be controlled and which one will not. The possible ways for modifying an object are:

  • Console - object creation/modification form as well as bulk-modification form
  • Portal - object creation/modification form
  • CSV import - in the console and in command line
  • DataSynchro

The first series of tutorials explains how to make the PhysicalDevice “Location” field mandatory.

  1. Always mandatory for all sub-classes of PhysicalDevice.
  2. Always mandatory but only for a subset of the PhysicalDevice sub-classes.
  3. Mandatory for a given class, but only if the object respects a particular condition.

The second series of tutorials explains how to make the UserRequest “Service” and “Service subcategory” field mandatory or optional

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