Catalog UI policies and Domain separation

Simon Christens
Kilo Sage

Hi Community

I really hope theres a Domain guru out there who can help me.

Im working in a domain separation environment and im working on "Request nr 0".

Its a Catalog item from where some users are able to to request new Service Request.

Depending on the input my script creates a new Catalog item with the needed Variables, types etc. - works fine.

The challange here is that when my script creates a Catalog UI policy its forced into the Default domain because its Domain separated. (its marked as the default domain in the setup)

Neither Catalog items or Policy actions is domain separated though.

Im am not able to create the Policy in global through a script and as long its not in global (doesnt matter what domain its in) it will not attach to the item meaning that its not shown and doesnt work.

If I change the domain on the Policy manually everything works. (despite that the name of the actions is "empty" and its not possible to choose any variables in it - that i think is because the Policy cannot be "read" due to wrong domain.)

I have looked for Business rules etc for UI policy tables and globals, but theres nothing (this is also confirmed by manually create a Catalog UI policy - thats created in global if you are in Global).

I have tried to force sys_domain to 'global', '' (empty), null but nothing works.

Im afraid that theres some mechanism deep in Service Now that prevents this - i dont know if its intended though.

Anyone who have an idea on what to do ?

Best regards

Simon

UPDATE:

It seems like it takes the domain from req item and passes it to the catalog policy upon creation.

I dont know if in the "session" (non interactive) when the script runs or if there is a rule somewhere that determines this but i think its a rule because if req item is in 'global' it sets the policy domain to the 'default' domain and not global.

5 REPLIES 5

Hi again



I have been blind



the Global -> default is still annoying for me, but if I go through the process while not in Global this works as intended.


The policy is not shown in the Cat item because i operated in Global. If i change domain its shown and works.