Additional Asset Hardware Substate

[djparkie]

I'm having difficulties adding a Substate to an asset with State of "In use" which is OOTB. My Substate record is in place on sys_choice with the relevant dependency value set correctly. However, when selecting "In use" I cannot get Substate out of read-only.

I thought there was some UIP or CS at play, but couldn't find anything. Then thought it was related to Asset CI Install Status Mappings. I tried to create an entry for my new Substate but didn't make any difference.

I think I'm missing something simple; can someone help me understand what is making Substate read-only for some values but editable for others?

[Alberto Consonn]

Hi,

I suggest you to read carefully the following thread:

https://community.servicenow.com/community?id=community_question&sys_id=13629b61db101fc01dcaf3231f96...

If I have answered your question, please mark my response as correct and/or helpful so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you

Cheers
Alberto

[Alberto Consonn]

Any update on this?

If I have answered your question, please mark my response as correct and/or helpful so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you

Cheers
Alberto

[djparkie]

Thank you - I have read and understood. However, I am not enlightened to understand why my Substate is read-only. I have created an additional mapping, set the CI status and Sync direction. So, my combination is Asset State = In use, Substate = Available, and mapped to CI Status = Installed. Sync is Asset to CI.

Still the Substate field remains read-only when selecting Asset State of "In use".

[djparkie]

Solved it - UI Policy on alm_asset. Short Description - Make substatus readonly when not required. Obvious really.