Manage onboarding of new CIs

[daniellethomson]

I work for a very young company that it just developing out ITSM processes. Currently, we manage onboarding new CI's through email and our ITSM Manager manually adds the CI to ServiceNow. I have been looking into options of using interceptors but see this OOO option adds the CI immediately without a formal review/approval process.

How does your company manage the onboarding of additional CIs?

[vibee]

One way to onboard new CI's. Especially in a mass load is to use transform maps and data imports. That is what I have done with adding new CI's in to the CMDB module. But this loads the CI's without approvals.

If you want approvals, you will have to add in a workflow for when the CI is added to the table.

Set it for, once the CI is saved, it goes for approval, and then once approved is set to a 'published' state.

[daniellethomson]

Thanks Vibee,

I didn't think I could run approvals on the onboarding of a CI. I don't see a way I can add a related link for approvals on the form.

[vibee]

One way is to add in a state field onto the CI form. I'm not sure if your CI's follow a state like build- decommission, etc type of state.

You can add in a set of states such as: Submitted - Published- Approved(In use) - Closed(decommissioned)

Then set a workflow to push the CI through the different states. When first onboarded, it's in published. The workflow will trigger an email for approval once it is in 'Published', once it is approved, the state will change to 'approved' and then once the CI is ready to deactivated, you can set it to send for another approval if need be, based on your processes.

That is how I would do it, if approvals are needed through ServiceNow. You can change the names of the state based on your needs, and the number of states. This is just an idea on how it can be done in my opionion.

There are of course, a lot of different ways to do this. The best part is you get to use your creative juices to play around until you find what works