New CIs are not created when creating Assets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 08:14 AM
We used to have automatic creation of computer CIs whenever we created a new computer asset on the alm_hardware table. I just noticed this stopped a while ago and I can't find the cause. The "Create CI on insert" business rule is active:
The assets in question use the "Computer" model category. The category is set to the CI class cmdb_ci_computer
But creating new assets does not create a CI as you can see here:
Any idea why?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 08:52 AM
Were those assets created using Import Set? If that is the case, then check whether 'Run Business Rules' is enabled.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2025 04:29 AM - edited 04-09-2025 04:30 AM
They were created directly by going to the asset table and clicking the "new" button.
That's not how we usually do it (a workflow runs a script that creates them) but I did it manually this time to rule out errors in the script.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2025 09:34 AM
Hello @Jens Mogensen
These are OOB Business Rules and as suggested you should check if import had business rules checked. Or if any other script is running on that table which is setting the "setWorkflow(false)" - check in any other business rule on that table or any server update.
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY