Configuring Choice Lists in Domains

[asd13]

Hi all,

I'm configuring a some choices lists for fields in the cmdb_ci_server form in a domain separated environment.   Most choices apply to all domains so I was keeping them global or in a high-level process domain but there are a few specific to different customer domains.   I thought I could just add the additional (customer-specific) at the customer domain in the choice table and still be able to see global + domain-specific choices in the drop-down.

What I'm actually seeing is if there's any choices specified for a lower domain then SN displays those and excludes the higher or global choices.   This paragraph in the wiki seems to imply thats expected behaviour:

This logic applies to choice list values as a set. As soon as one choice list is found for the relevant table and field, then only that set of choices appears in the drop-down list.

http://wiki.servicenow.com/index.php?title=Domain_Separation_Setup#Creating_Domain-Specific_Choice_L...

Which doesn't seem that helpful - it basically means I have to replicate the common choices across all my customer domains or else define them high and let all customers see them - possibly using some client script shenanigans to dynamically build the choice list depending on the selected customer/domain.

Can anyone confirm this is the right behaviour or is there a magic property or way to make these cumulative down the hierarchy?

thanks

Dave

[Michael Fry1]

Works the same way for us. If you are putting choices in customer domains, the only way to get those choices is to be 'in' the right domain. That means enter Caller (populates Company) save that, then system should put you in that domain and thus you will get the right choice list.

[Deepak Ingale1]

Hi David,

When we implemented last time on Eureka version in domain separated environment, we had defined common choices at process domain. Those choices are then appeared to child customer domains as well.

After that, we had defined customer specific choices by going to respective customer domain. However, we have to configured additional choices by going to incident form (we had done that for incident categories btw), right clicking on category field and then selecting 'Configure Choice' option. What it did : It created a overrides on choice list fields and presented us the categories of process domain + addition child domain.

Are you trying to create it by the same way?

Once you define choices at customer domain, then if you add any other choice at 'process domain', it wont reflect in customer domain. You will have to again add it customer domain.

I haven't tested it on Fuji though.

[Mohammed Kemal]

Hi there,

I am adding a reply to this question as I feel this need an updated answer dating back 5 years but here is the current (2020) steps to work on the domain separation specifically to choices. 

The steps to create domain specific choices are the following:

1. Select the domain from domain picker where the choice should be added.
2. Right-click the choice field you want to customize and select Configure Choices.
3. Update or add choices.
4. Push changes through the normal change process such as update sets.

• If you adds a new choice from the global domain, then users from domains lower in the hierarchy see the new choice at the end of their current choice lists. If the new choice is not active at the global level, then it is available to the domain users via Configure Choices but does not show as an active choice.
•  Make sure you have the field called "domain" in your list view of the choices while checking if they are properly assigned to the specific domain. I hope this helps.