CMDB Remediation Rules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2019 11:58 PM
Hi,
I have configured a CMDB orphan rule in the Health Dashboard identifying orphan MS SQL Database CIs in cmdb_ci_db_mssql_database if they do not have the CONTAINED BY relation to a MS SQL Instance CI in Fcmdb_ci_db_mssql_instance.
I now want to configure a CMDB Remediation Rule where it seems I have to create a workflow:
If I then click the magnifying glass next to 'Workflow' I get a pop-up allowing me to create a workflow:
Submitting that workflow brings me to the workflow canvas:
Now if I Publish that workflow and return to the create CMDB Remediation Rule form it has put the new workflow in the 'Workflow' field:
But if I try to Submit that it is blanked out:
And hitting the magnifying glass again doesn't show the published workflow (if I open the workflow editor directly I see the workflow as published).
The documentation how to create a CMDB Remediation Rule seems very sparse. Anybody having successfully created such a rule?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2019 12:11 AM
Hi,
looking at the error message, please try to change the name of the Workflow, it should NOT match anywhere.
Give a try and let me know.
Please, remember to mark Correct or Helpful if you find my response useful.
Cheers
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2019 02:04 AM
Does the table for the workflow have to match the task type on the rule, so should be "Orphan CI Remediation"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2019 02:12 AM
I'm adding the workflow with a unique name and it gives the error (same if I add it with the same name as the Remediation Rule I'm trying to create).
And adding the workflow on the same "Orphan CI Remediation" table also gives the same error and besides doesn't seem to make sense since it is not in that table I want the workflow to delete the orphan MS SQL Database CIs.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-18-2019 06:46 AM
running into a similar problem, has there been any update on what was the root cause of the issue?