Issue with Domain Specific Choice Lists

[Chris Sanford1]

I am trying to configure domain specific incident categories on the 'category' field. I have pre-existing global domain choices, and then added a new one in a specific domain. None of my choices are inactive. For an incident in the specific domain, I expected to see all the global ones, as well as the domain specific choice. However this does not seem to be the case. I only see the new choice in that specific domain, and the global ones appear on all of the other domains except that one.

According to ServiceNow's documentation on this subject at https://docs.servicenow.com/bundle/kingston-platform-administration/page/administer/company-and-doma..., I found the following paragraph:

From what I can tell this appears to be a false statement. I confirmed in my out of box developer instance the same behavior. Am I missing something here?

[lalit007]

sys_overrides field is not present on sys_choice table because choices are data not process, but work as process (exception to data). So if you create choice in child domain (override), parent domain choices will not be visible.

[Deepak Ingale1]

Just to correct, sys_choice is still configuration and not a data since it gets captured in an update set. Anything which OOB gets captured in an update set is "configuration"

[lalit007]

Straight from Servicenow docs.... Exceptions to data separation In general, data defined at a higher level in the domain hierarchy is not visible at lower levels in the hierarchy. However, the following records behave like policies: Form sections Options in a choice list When defined at a higher level in the hierarchy, these records are visible in child domains. What do you say now??

[Deepak Ingale1]

Okay,

1) Anything which gets captured in an update set is configuration

2) Rest is data

[Deepak Ingale1]

BTW, from DB point of view, everything is data