Asset and CI sync functionality in Asset Management

[Sunny45]

Hello 

I have noticed below which is OOB. Not sure if this is normal behavior? 

1) When Asset side state changes to In Maintenance, CI side changes as well to In Maintenance  : Good

2) When Asset side state changes back to In Use, CI side changes as well to Installed : Good 

3) When CI side changes to In Maintenance, Asset side doesn't change  : Bad

4) When CI side changes back to Installed, Asset side doesn't change state : Bad

I am seeing that there is record for In Maintenance sync is in both direction in Asset CI State mapping table.(snap below) 

As per this all 4 scenario should work, but only 1, and 2 are working and 3, 4 are not. 

Please advise or am I missing something?. Do I need to make some changes?

Thanks

.

[Sunny45]

[Tim Deniston]

A change to the Status field on a hardware CI does not push its value to the Asset's State field... for Hardware CIs (or any child of cmdb_ci_hardware), the 'Hardware Status' field on the CI should be used. It's very confusing, but it's how it works. Use the table at "Asset > Administration > Asset-CI Hardware Status Mapping" to determine the right sync values (alm_hardware_state_mapping). 

You will want to adjust your CI list views to show the correct fields. 

[Sunny45]

Thanks Tim

I see your point. It is really kind of confusing for me as a beginner. So if I change Hardware Status on CI side it does change on Asset side and vise versa. 

So if you can help me, can you please guide me for following requirement?

 I need to create 1 new status (Unknown) on CI side and asset side so that, they are always in sync. What steps should I take beginning with create new choice? 

Creating new choice also can be challenging. It can be created on alm_hardware or alm_asset. 

Please help me out through the steps.

Thank you very much.

[Tim Deniston · Accepted solution]

One good thing is that the Hardware Asset (alm_hardware) table inherits the State values from Asset (alm_asset). So, you just need to add the Unknown value once for Asset. 

I think these would be the right steps:

1. Create the "Unknown" value in the choice list for Asset > State
1. Label: Unknown
2. Value: [your choice, but it should be an available number, like 0 or 12 or 13]
2. Create the "Unknown" value in the choice list for Configuration Item > Status (install_status)
1. Label: Unknown
2. Value: Use the same one as before
3. Create the "Unknown" value in the choice list for Hardware (cmdb_ci_hardware) > Hardware Status (hardware_status)
4. Create an Asset-CI Install Status Mapping record that maps the State field on the Asset to the Status field on the CI. Set it to go both ways.
5. Create an Asset-CI Hardware Status record that maps the State field on the Asset to the Hardware Status Mapping field on the CI. Set it to go both ways. 

[Sunny45]

Perfect Tim,

That makes perfect sense. So when I trigger change from CI side, I need to trigger status change on Hardware status and not on install status. That is what it makes it to run.

Thanks.

Suraj