Idea ID: 1655870

Allow updates and add Enrichment Rules for Importing Actual Services to System Elements

Status : Declined
over 2 years ago

Currently it is impossible to update the Actual Service, Service Components or System Element CIs coming from UCMDB into SMAX via a CSV import command.  However, the very obvious use-case is to add the 1st, 2nd, 3rd line support groups; to the Service CI, because this data does not come across from UCMDB. And then Owners can normally be set by a Rule, but these CI types don't support Enrichment Rules for the moment.

Updates on CSV import are only supported on a small selection of record types (device, license, infrastructure & peripheral, person, group). See: 1700_Admin/plfrmImportData.htm

This happens to be the same restricted list for Enrichment Rules. See: 1700_Admin/emEnrichmentRules.htm

The business case during migration is very obvious:

  1. When you start with thousands of services, currently someone needs to go and update them manually
  2. Or someone needs to write a Connect-IT, OO or other application script using REST-API.
  3. Importing a CSV file with the Groups would be much much easier and internal to SMAX.

The business case during maintenance exists too:

  1. Every reorganization requires shuffling groups in potentially hundreds or thousands of Service related CIs

It would also make the tool much more consistent if you could do update-imports and enrichment rules on all types of SACM entities: Actual Service, Service Components or System Element CIs.

If you agree, please vote for this!


Ben Rabau (for a Dutch Customer) 


  • Thank you for your idea. At this time, your idea hasn’t received enough community support and doesn’t align with our priorities so we are closing this idea. But we may review this again in the future. Thank you for your support and continue posting & voting on ideas to help make our products better.
  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team