I just resolved this same type of error on my system. I'm using the Auto Dispatch module and we had a rule defined with a Class of "Ticket". The rule had an OQL query which looked at the service_id field which isn't available on the Change tickets in my environment.
The steps I take is to try and automate updates when possible using the Synchro features in iTop. For everything without an external datasource it is a combination of reminding "owners" through audit rules and the requirement of including iTop updates in the setup of these devices.
Hi Chevolec, The following might work for you though it shows all FunctionalCI's. I've got this as a stored query in iTop. Name: CMDB Changes Description: Show all FunctionalCI changes over the past 60 days Expression SELECT FunctionalCI, CMDBChange, CMDBChangeOp FROM FunctionalCI JOIN CMDBChangeOp ON CMDBChangeOp.objkey = FunctionalCI.id JOIN CMDBChange ON CMDBChangeOp.change = CMDBChange.id JOIN Organization ON FunctionalCI.org_id = Organization.id WHERE CMDBChangeOp.finalclass = 'CMDBChangeOpCreate'...
The REST API is pretty straight forward. as shown below. I believe there are quite a few examples on these forums and on Github of using the API using a few different methods. https://wiki.openitop.org/doku.php?id=2_4_0:advancedtopics:rest_json&s[]=rest For storing sofware configuration within iTop I'm assuing you'll want a new CI. https://wiki.openitop.org/doku.php?id=2_4_0:customization:datamodel Hope this gets you started..
Good luck with your BMC replacement. Here is a direct link to the iTop Customization documentation on getting the above modifications into an extension to make for seamless upgrades.
Good thought Gary. I just crafted up the following that I added to one of my "test" datamodels and there is a good chance I'll put it into production. I just got used to clicking the link on the caller just to pop up the contact info. It might be benefical to add this to the Ticket class. You'll probably need to modify the presentation rank as mine is heavily modified. <class id="UserRequest" _delta="must_exist"> <fields> <field id="caller_phone" xsi:type="AttributeExternalField" _delta="define">...
Has anyone ever attempted or thought of adding AttributeHierarchicalKey to the Location CI? Additionally it might be beneficial to also add a Location_Type ENUM. I haven't done it yet but very tempted to though figured I'd start here and see if it has been done before and with what kind of success.
Has anyone looked at the possibility of a KanBan type of view for Tickets and/or workorders in iTop? Just curious as I have a few teams which use Jira for development work and would like to manage their iTop Requests via a KanBan board. Using the dashlet-calendar example this doesn't seem to be too far fetched of an idea.