Unpacking of [ConfigurationItemXXX] has been initiated

[G24]

Hello.   When our users choose certain cmdb_ci values on the Incident form, they sometimes get a message saying:

"Unpacking of [ConfigurationItemXXX] has been initiated"

I have no idea what this means.  Where may I find documentation on these messages, please?  Thank you.

[Tony Chatfield1 · Accepted solution]

Hi, using Studio's code search functionality in a PDI, 'Unpacking of' returns a match for BR 'Sync Affected CI Dynamic Group '

/nav_to.do?uri=sys_script.do?sys_id=a77e5938231220101488dc1756bf65cc

This is an after BR running on insert for CIs Affected [task_ci] and looks to be related to dynamic CI groups.

Sandiego patch 2 releases note show there is a known issue with it running unexpectedly for incident, problem, change

San Diego Patch 2 (servicenow.com)

and this KB suggests it may also impact Utah.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1047919

The KB includes details of a fix\workaround.
If you have any issues, questions or concerns I would log a case in SNC Support.

[G24]

Hello, @Tony Chatfield1 Thank you for that!  May I ask a follow-up question related to SEARCH?

1) I did a Global Search, and that returned ZERO results as you can see here:

2) Then I searched "for text" in the Application Files (sys_metadata) table, and that returned only two, irrelevant, results:

3) Finally, after reading your response to my question, I did a Code Search in All Applications from Studio, and that DID FIND the relevant object:

I see that the Business Rule is in table sys_script, and that sys_script does derive from table "Application File" / sys_metadata (which I already searched) in step 2.

So my new question is Why did my search of the sys_metadata table NOT find this business rule???

As I'm typing this, it occurred to me to try this on a PDI...

So I just tried on my PDI (San Diego) and the object WAS FOUND from a search of sys_metadata:

Then I tried Tokyo, and the object WAS FOUND there also, in sys_metadata:

And finally, I tried Utah, and again the object WAS FOUND in sys_matadata:

So in conclusion, apparently something is wrong with the List View Search function on our specific Utah instance.  Baffled as to what that would be, but I guess I'll have to log a ticket with ServiceNow...

[G24]

@Tony Chatfield1 The 2nd link you posted did not work for some reason.  I think it has an extra comma at the end of it.  I think you were trying to post the following, thank you:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1047919 

[G24]

I updated the business rule to include more user-friendly info messages: