Blank Asset records being created

[LG2]

Hi,

We are looking to create asset records via a wizard so users have a nice pretty front end to play with - at the moment it's only passing basic info as we're testing the concept.

Asset gets created via record generator in the wizard - not a problem - and we have a new field called "u_wizard" to identify that is where is comes from.

We then have updated the OOB Business Rule which creates a CMDB entry so that it doesn't run when u_wizard = true

We then have our own script which creates the CMDB entry if u_wizard is true.

So far, so good works a treat... creates the Asset how we want it, then creates the linked cmdb record how we want it...

Except when the CMDB is created, it then goes off and creates a new, completely blank Asset record (we know it is done after the CMDB because of the date/time stamp).

We've tried temporarily disabling the two OOB Business rules which run on CMDB table which create assets:   Create Asset on Insert, Create Asset on Model change.     Still we get a blank asset?     There are no custom BRs which create assets which run on the cmdb table.

Any ideas before we get splinters from head scratching?

thx

[Michael Fry1]

Create Asset on Insert is the business rule that creates an Asset when a new CI is created. If you've turned that off, and it's still creating, turn Debug on and look through the entries to see what's happening.

[LG2]

thanks Michael, we did run the debug log before and it didn't bring back anything blindingly obvious (to me anyway)

I've attached a summary of what we got when we ran it again - it seems to run our create CI custom script (line 23-34) and in that it skips create asset on insert (line 33) - I can't see any other create asset type business rule getting triggered?

There is a reference to Create CI on insert again in lines 74-77, but it's not creating duplicate CIs, it's creating blank asset.

[Community Alums · Accepted solution]

Easiest way to prevent Asset creation from the CI would be to enable "Enforce CI Verification" on your Model Categories, but I have to ask:

What are you doing differently in your CI creation process that is different than the built in process to do this? Why did you decide to work the process this way?

[LG2]

Thanks Ben - we'll take a look at that next week when my colleagues wake up.

For some reason, it wasn't working the OOB way with the wizard - which is probably another discussion in itself...     and we're doing a wizard because they want something "easy for end users to use and not get wrong".... again, probably another can of worms!