asset to CI sync - install_status on update of CI fails - Issue?

[cyked]

So there are tables of sync rules, with script includes doing the work, right?

On the Asset-CI hardware status mapping the mapping is, if a "both directions" rule is in place would be to keep the Asset's Asset Status and Substatus in sync with a CI's Hardware status and Substatus in sync?

The Asset- CI install Status mapping is to, when on a "both directions" rule to sync a change of Assets's State and Substatus to set the CI's install_status?

I'm seeing a breakdown when a CI is updated (both directions rule for Asset-CI hardware status mapping) the Asset is updated, but when the Asset is then updated, I do not see that the rule for Asset-CI Install status mapping is fired.   That is the install_status of the CI is ONLY updated if the Asset's State and Substate are updated.  

Is this expected behavior?

[Community Alums]

Is there a specific example you can describe so we can try to replicate?

[cyked]

I have a HI ticket open as well...

If you update a Hardware CI's HW status and substatus, the linked Asset's State and Substate are updated.   Install status is NOT updated on the CI. So... CI > Asset > CI.

If you update the state and substate of the asset, the HW state and substate of the Asset, the linked CI's HW status, substatus AND Install Status (all three) are updated.

This of course is valid if you have a rule to update Install Status.

From here: Asset and CI mapping

• The Install Status and Hardware Status fields of a CI are independent of each other. There is no correlation between them. A change to the Hardware Status field does not change the CI Install Status field and vice versa.

If they are independent, then WHY update install status when the Asset is updated, but not when you update the CI?   Update to CI updates Asset, so why not fire the same rule to update Install Status?

[Community Alums]

Drew,

First, on the Install and Hardware Status fields on the CI: I would select one to work with (my recommendation would be Install Status as it covers a broader range of CIs). Don't work with both as it will just cause confusion.

For the synchronization, I was asking for a specific example, because   Asset States and Substates only synchronize to Statuses where it makes sense. You can see these by navigating to Asset > Administration > Asset-CI Install Status Mapping. Click All in the breadcrumb trail to see the baseline items. This allows you to see the baseline synchronization so you can see what maps to what.

Ben

[cyked]

Hardware will have different statuses than non-hardware CIs.   A logical Application is not "In stock" for example.  

Because this was mucked up years ago, the solution we want to implement on Hardware would to have teams to Manage these three fields to keep the CI and Asset in sync

• Operational status
• Hardware status
• Substatus

Of course if you update the Asset the rules would go both ways.

Install status for Hardware would be read only on Hardware and used as a display.   This was more of a requirement because other teams using CMDB data are reliant on Install Status for the past few years.   If we break this, there may be significant work on their end to adjust.   And really, it may just come to that.  

In dev, I basically deleted all the OotB rules and we are working through our own for Asset Lifecycle Management based on what the Infrastructure teams want.   All the ruleles on both sync tabs are set to Both directions.   If you make an Asset In stock/Available, the CI is In stock/Available.

None of this really matters, even in my personal dev instance if you update the Asset, Install status on CI is updated, but if you make the update from the CI, it doesn't push that rule even if it exists.   Its the script include I imagine.