Does CI identification rules apply when creating an CI manually from an Asset?

Morten Steenbac · ‎08-21-2017

When creating an Asset manually and a related CI is automatically created, is the identification/reconciliation process involved to check for duplicates.

Or is it only during Discovery?

Community Alums · ‎08-25-2017

Morten,

No. CI Identification rules are not used for the automated creation of a CI with an Asset record. It is designed to just create a new CI record.

Asset management processes should be creating the CI first. In a proactive manner. Then discovery sources should be updating that CI record (preferably using the Identification and Reconciliation engine).

When items are brought into ServiceNow from your discovery source, then one of two things happens:

A matching CI is found and updated. This happens when the Asset created the CI first or if the CI was discovered previously.
No match is found and a new CI is created. Based on the Model Category, a corresponding Asset record is also created. If you are adding asset details later, you should update this automatically created Asset record (coalesce if you are importing Asset data).
1. If you do not want to automatically create an Asset (because the Asset record should exist first), you can enable the Enforce CI verification option on the Model Category. This prevents the Asset creation until you either verify that you want an Asset or Merge the CI with an existing CI (perhaps something was off and it did not properly merge). This gives you more control about how Assets and CIs are coordinated.
2. If you do not want to automatically create an Asset (because you do not purchase a specific Model or the Model is virtual), you can set the Asset tracking strategy on the Model record to not create Assets.

Sorry, this is probably a lot more detail than you were looking for here, but Assets are meant to be created first, so there is not identification done when the corresponding CI is created. If the CI is already there, you should be updating an existing Asset instead of creating a new Asset, so you really should be identifying that on the Asset side.

Ben

View solution in original post

Community Alums · ‎09-19-2017

Rodelio,

So if you change the Assigned to on the Asset, it does not change the Assigned to on the CI and vice versa? If this is the problem, it is likely related to the Business Rules that make this happen as above. That would be the first place I would check. Did the Business Rules get modified, deleted, or deactivated?

Ben

rodeliodoria · ‎09-19-2017

I am not a 100% sure. Do you think you can provide a screenshot of your business rule? Is this business rule on the asset or CI? I will do a quick compare and see if that might be the issue for me.