Asset CI synchronization

[SARAN_14]

Hi,

When a Discovery source updates the CI the corresponding Asset is not updated. When the system property 'glide.create_alm_asset.async' is 'false' the assets were updated by approx 1160 of 5000. When the system property 'glide.create_alm_asset.async' is 'true' only 2 assets were updated of 5000. I have to know why Assets were not updating even though the CIs were updated whenever the scheduled jobs for Discovery source runs.

Thanks,

Saran

[Niklas Peterson · Accepted solution]

Hi,

The glide.create_alm_asset.async property only controls creation of Assets based on CIs. If false Assets are created immediately and if true they are created asynchrous (with a delay). 

Updating a CI does not necessarily mean that the corresponding Asset needs an update. Only synchronized attributes that are updated on the CI will trigger an update on the Asset.

https://docs.servicenow.com/en-US/bundle/utah-it-asset-management/page/product/hardware-asset-manage...

Regards,

Niklas

[MarkyMark1]

Great information.   But this ties into to an issue I have with understanding the creation of assets. I have read many ServiceNow docs including the one you linked to but I'm still not clear on how this property and the scheduled job 'Asset - Create asset delayed sync' and the business rule, Create asset on insert, that runs on a CI insert.  The both create assets by different means but do they work together, should they both be enabled/active?   I just don't understand their relationship and the docs don't appear to explain.  

[SARAN_14]

Hi @MarkyMark1 ,

1. That property was used to create the asset in an interval of 15 minutes from the creation of CI (if it is set to true). The scheduled job mentioned will carry out the process of creating the assets.

2. If you set the property to false, the asset will be created immediately after the CI is created, it won't wait for the Scheduled job to create the asset.

3. The business rules were used to create the records in the asset and CI table as you mentioned, by deactivating those business rules you won't have the respective CI for the asset when you manually create the asset in the "alm_asset" table (or) a CI is discovered by the discovery source the CI will be created or updated but you don't have the asset record for that CI.

[Niklas Peterson]

Hi,

To my understanding they work together. The BR runs on insert of a CI if the asset attribute is empty and the CI class is not excluded from the BR. When running, the BR checks the property and if the property is false, it creates the Asset directly. If property is true, then is creates a queue record and then the scheduled job picks up the queue record and creates the Asset.

The BR is always needed and the scheduled job is needed if the property is true.

Regards,
Niklas