- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi All,
I have got a requirement if the Asset Team is making a CI or a record in the Hardware (alm_hardware) state field to "Retired" then in configuration item (cmdb_ci) table the Operational status needs to be changed to Retired and vice versa if in the Hardware table the CI/Record is changed back to In use then in the Configuration Item table the operational status should change to "Operational".
My doubts are I have found a table by name Asset CI Install Status Mappings (alm_asset_ci_state_mapping). My question is:
- What is the significance of the table?
- Do I need to utilize and update this table for future reference as I can only see there are 47 records in the list view?
- Is updating the Table is a best practice?
- Is even updating the table required in this case?
Please help me with the requirement OR please share some links where I can go and check it
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @Harsh3842
This AssetCiSynchronization process is not that simple.
Until and and unless customization which has strong business justification is there then you can modify this process.
Because here if the change is not done carefully , it can break the synchronization process (bidirectional ASSET & CI sync process) and you will not get any support due to your customization until you are reverting to OOB.
Next coming to your requirement - " updating record in the Hardware (alm_hardware) state field to "Retired" then in configuration item (cmdb_ci) table the Operational status needs to be changed to Retired and vice versa"
Using BR on the CI table - you can achieve it , why you are changing syncing process?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Harsh3842
First I will suggest you to read this article though its a old one.
https://www.servicenowelite.com/blog/2013/12/20/how-to-sync-assets
- What is the significance of the table? Ans: ServiceNow Asset-CI Install Status mappings synchronize Asset States (e.g., In Use) with Configuration Item (CI) Install Statuses (e.g., Installed) to maintain data accuracy between ITAM and CMDB. Refer: https://www.servicenow.com/docs/r/it-asset-management/asset-management/t_CreateAssetandCIInstallStat...
- Do I need to utilize and update this table for future reference as I can only see there are 47 records in the list view? (If you have any custom state value of CI , in order to sync that custom state of CI with Asset, You need to create map here) Though OOB is always recommended.
- Is updating the Table is a best practice? No, until and unless you are getting any Customization requirement
- Is even updating the table required in this case? (question is not clear)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Tanushree Maiti ,
Thank you for your response. Regarding my question number 3 and 4
For question No.3 Is updating the Table is a best practice? - I have not understood it see what I now is that there is no custom field in the Hardware as well as in Configuration Item table although I have created a custom field in the Asset CI Install Status Mappings (alm_asset_ci_state_mapping) table by name "Operational Status" and it is only a custom field and nothing else.
For Question No.4 Is even updating the table required in this case? - let me clarify, the requirement that I want to do/achieve Does it have to do anything with this Asset CI Install Status Mappings (alm_asset_ci_state_mapping) table do I need to update the table? Is it Required to update the table for the requirement that I want to achieve? and if required to update the table, does it come under best practices to update the asset ci install status mapping table and also if I update the table does it going to help me in future/long run where i can go and check which CI are Retired OR Operational. I hope I am not confusing you.
Regards,
Harsh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @Harsh3842
This AssetCiSynchronization process is not that simple.
Until and and unless customization which has strong business justification is there then you can modify this process.
Because here if the change is not done carefully , it can break the synchronization process (bidirectional ASSET & CI sync process) and you will not get any support due to your customization until you are reverting to OOB.
Next coming to your requirement - " updating record in the Hardware (alm_hardware) state field to "Retired" then in configuration item (cmdb_ci) table the Operational status needs to be changed to Retired and vice versa"
Using BR on the CI table - you can achieve it , why you are changing syncing process?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Tanushree Maiti ,
Thank you for your suggestion. I wanted to confirm the requirement that I want to achieve does it involves Asset CI Install Status Mappings (alm_asset_ci_state_mapping) table OR Needs involvement of it. Thank you for your clarification.
I will write a BR and complete the requirement.
Regards,
