- CMDB
- Ticketing
Introduced by iTop 2.4, the Data Model now includes an obsolescence notion defined per class of object, to improve user experience by highlighting / hiding obsolete objects.
Object defined as obsolete are flagged in the console to make this aspect obvious, by graphical icon and tag.
On a list:
On an object:
On a list of linked object:
Obsolete objects are ignored by Impact Analysis
Before iTop 2.4.0:
After:
Based on user preference, objects which are defined as obsolete, are removed from displayed lists in the iTop console.
An obsolete object details is displayed regardless of user preference.
The same Farm
as above displayed for a user, requesting to not display obsolete objects:
obsolescence_flag
show obsolete data
before!
obsolescence_date
won't be documented unless the iTop cron is running. obsolete
or inactive
,obsolete
closed
more than 15 months ago, (in 2.4.x only, was removed in 2.5.0)status='inactive'
status='obsolete'
status='inactive'
status='inactive'
status='inactive'
its DBServer is obsolete
status='inactive'
its Middleware is obsolete
status='obsolete'
status='inactive'
status='inactive'
status='obsolete'
its Web server is obsolete
status='inactive'
status='obsolete'
status='inactive'
Licence is not perpetual and end date defined and exceeded by more than 15 months
status='inactive'
its Device is obsolete
Licence is not perpetual and end date defined and exceeded by more than 15 months
On all end-user devices use the same logic defined on Physical Device: status='obsolete'
status='obsolete
'status='obsolete
'its Virtual Machine is obsolete
status='obsolete
its Datacenter Device is obsolete
its Storage System is obsolete
status='obsolete'
its NAS is obsolete
status='obsolete'
status='obsolete'
its Tape Library is obsolete
status='obsolete'
status='obsolete'
status='obsolete'
status='obsolete'
status='obsolete'
None, due to performance issue, if based on current date, it is never cached and recomputed all the time
obsolescence condition
is an OQL statement, using any field of the class, including those of type AttributeExternalField<obsolescence _delta="redefine"> <condition><![CDATA[status='inactive']]></condition> </obsolescence>
undefined
(= no value = ISNULL), is not considered as obsolete by default.
If you want to have undefined
status considered as obsolete then use this condition:
<obsolescence _delta="redefine"> <condition><![CDATA[status='inactive' OR ISNULL(status)=1]]></condition> </obsolescence>
Based on object status:
<classes><class id="Organization"><properties><obsolescence><condition> <![CDATA[status = 'inactive']]> </condition></obsolescence></properties></class><classes>
Based on object status combined with status of a parent if parent exists :
<classes><class id="Hypervisor"><properties><obsolescence><condition> <![CDATA[status = 'obsolete' OR (server_id != 0 AND server_id_obsolescence_flag)]]> </condition></obsolescence></properties></class><classes>
Combination of status and delay:
<classes><class id="Ticket"><properties><obsolescence><condition> <![CDATA[operational_status='closed' AND (close_date < DATE_FORMAT(DATE_SUB(NOW(), INTERVAL 15 MONTH),'%Y-%m-%d 00:00:00') OR (ISNULL(close_date) AND last_update < DATE_FORMAT(DATE_SUB(NOW(), INTERVAL 15 MONTH),'%Y-%m-%d 00:00:00')))]]> </condition></obsolescence></properties></class><classes>