CMDB Remediation Rules

[klautrup]

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?

[Shelby Foister]

Has anyone heard or seen any resolution to this? I'm running into the same issue on all of my instances.

[LaurentChicoine]

The table of the workflow should be the associated remediation table so if your remediation rule is for the "Stale CI Remediation" task type, then the workflow should be running on that table. Same thing applies for other remediation task types.

[FYL]

Found the answer here https://hi.service-now.com/kb_view.do?sysparm_article=KB0725128

Do the following before Submitting the CMDB Remediation Rule 

**************************************************

Creation of the Workflow for "Reconcile Duplicate task" 
1) Click "New" to create a new Workflow. 

2) Fill in the form: 
a) for the option of "Table", select "Reconcile Duplicate Task" (reconcile_duplicate_task) 
b) For "If condition matches", select "None". 

3) [Ensure that the associated workflow remediates duplicate CIs.] 

4) Save and Publish the workflow. 

[Jeff133]

Did you get this to work? I want to create a workflow that will...

1. Select the duplicate record with the Newest Updated
2. Set it as the Master record
3. Set Status="Retired" on all duplicate records
4. Merge relationships from the duplicates to the Master

Is that possible?

These are the steps that I seem to perform manually many times each week.

[Henrik Jutterst]

Looking for the same feature as you describe.
Did you have any luck with this in a Workflow?