This new attribute allows
a user to:
a configuration manager to:
More: check the User guide
domainsare manageable as any Typology
Other possibilities which might be useful for some organization, but won't be defined as part of the standard Datamodel:
They could be developed as an extension
Basically, a new tab will be displayed on objet having that attribute and that tab will contain a dashboard displaying data specific to that particular objet.
codeis any field of the object
Example of an OQL within a Dashboard Attribute on Organization class. :
SELECT UserRequest AS u WHERE u.agent_id = :current_contact_id AND u.status NOT IN ("closed", "resolved") AND u.org_id = :this->id
This list of User Requests is dynamically based on the
current user (an option which was already available in Menu Dashboard) and the
displayed organization (This is new and specific to Attribute Dashboard)
This new type of Attribute allows to replace many lines of code written to display related objects with special filtering, with multiple lists. Once replaced, their customization is much easier and safer, as it relies on XML instead of PHP, and it can be enhanced as soon as new dashlets are added to your iTop (for example a Calendar View Dashlet).
This Dashboard even if not customizable by the users, will be editable by iTop administrators, who can design and test it with real data, before copying the resulting XML in an extension or in the ITSM Designer as the Dashboard
You can specify on a class, uniqueness rules, to prevent duplicate entries.
Employee number, but this rule only applies to your company, then you define the scope of the rule to be “Only Persons of organization XXX”
namemust be unique.
name + brand_idmust be unique.
org_id + employee_numbermust be unique only if employee_id is defined.
org_id + first_name + nameshould be unique (warning only).
Two new types of Trigger have been added to cover Notification needs on situation such as Update or Delete of an object. For the Update trigger, the list of fields which are monitored for a particular trigger can be specified.
Those triggers are called in all cases of update/deletion, not only when done on the Console and the Portal(s), but also through DataSynchro and API REST.
Be aware that if you set a TriggerOnUpdate on class
Team for field
:this→attribute_codeand it contains the value after the change.
Trigger on Updateset 'email_asynchronous' ⇒ 'true', in the Configuration File, as a CSV import, a bulk update can generate a lot of emails and impact the performances
Trigger on update is not triggered on those type of Attribute: