CIs are not created from asset records

Robert _ysakows · ‎10-30-2023

I am using LAB instance with HAM installed but can not get the CI to be created even though all settings seems to be ok (see screenshots). I've run the job 'Asset - Create asset delayed sync' several times with no effect. What I am missing?

Ashok Sasidhara · ‎10-30-2023

Check whether 'Create CI on Insert' business rule is active. If it is disabled, you need to set it to 'Active'.

View solution in original post

Ashok Sasidhara · ‎11-02-2023

'Asset - Create asset delayed sync' scheduled job does not create CIs. The purpose of this job is creation of assets when CIs are created.

It is controlled by the system property 'glide.create_alm_asset.async'. If the value of system property 'glide.create_alm_asset.async' is "false", asset is created immediately when the Configuration item is created. If the value is "true", asset creation is deferred when the Configuration item is created. In this case, Asset is created via the "Asset - Create asset delayed sync" schedule job.

View solution in original post

scottl · ‎11-26-2024

I have no idea why this was set as a solution to the problem, as this does not work as expected.

When set to false, the Asset is created as expected. But when done async. it fails to create the Asset via the scheduled job and gives an error "Asset creation failed".

scottl · ‎11-26-2024

It's a feature of SN, so you are forced to use HI support because an Enterprise level product uses their customers to do functionality testing.

All joking aside, there is clearly an issue and defect with this functionality as I have found the same issue.