Using a workflow On CMDB

[ychick]

Has anyone ever used a workflow on the cmdb_ci table to get approval for a CI prior to setting it to active? I got requirements yesterday stating that there should be an approval process for CIs but not sure what effects may arise. I see that on the workflow properties I can pick cmdb_ci but just curious if anyone ever tried.

[myee]

From a platform perspective, there is nothing that is stopping you from using a workflow on a CI. From a process best practice perspective, I would advise against it. Management of CIs (add/modify/delete) is typically handled through the Change Management process. A better route would be to utilize your change management workflows (may have to create a specific workflow for CIs) and have Change Management integrate with the cmdb_ci table. If you really think about it, if you are "adding a CI", all you really are doing is making a Change.

[tsho]

I totally agree with Michael. CMDB merely reflects what is currently in the environment. When you set a CI to active, there should be an associated RFC for that CI to go live. The Change Management process is your approval process. ServiceNow has a couple of features you may want to look into to dovetail Config process with Change. The Proposed Change feature allows Change requester to input CI changes. The Baseline Diff allows you to associate RFC to a change from the baseline.

- Teresa

[ychick]

Both the replies are quite helpful. I may be coming back with some follow-ups. Thank you.