Hi,
I'm looking for a way to stop inserts to alm_hardware table if the related CI is virtual. I tried to do that via a business rule that already does the same for locations other than the pilot locations for our project (that works fine):
Unfortunately these filters don't work as expected for virtuals. Is it because not all classes are included separately? I tested on Windows Servers and perhaps the parent Server class filter is insufficient. On the other hand I also tested on Computers and it didn't work either.
Can this be achieved any other way? Perhaps I should just include the filter in the script?
Or should I rather change the Asset tracking strategy for the virtual CMDB models to 'Don't create assets'?
Hi @Pawel Kozlik ,
You can update the existing BR with condition. Lets say you dont want to create asset for Software class then you can add condition like below. you can keep on adding more class for which you dont wanna create asset.
Note: All CIs are not assets. That is why asset creation should be controlled using the relevant model category or model records as per ServiceNow best practices.
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay
-------------------------------------------------------------------------
HI,
You have to manage this with product Model, you can associate incoming CIs to virtual device category.
Thanks,
Ajit
