Ability to see all users in the sys_user reference field irrespective of the domains

balakumar1 · ‎11-13-2014

Hi,

As per the default implementation, users in domain A can't see users in domain B if B is above A in hierarchy, or B is not in the hierarchy of A at all.

We would like users in domain A to see users in domain B in a sys_user reference field.

Is that possible? I feel that this could be a generic requirement across all users of ServiceNow. Wondering if there is already a solution for this.

Maintaining a second sys_user table is an option. But that seems to me like a complex option because the sys_id in the sys_user and sys_user1 table should remain same because in lot of scripts, many parts depend on sys_id. For eg. if(current.assigned_to == gs.getUserID()) {.... }

This will fail if the new sys_user1 table has a different sys_id for the user.

Any help please.

Regards,

Bala

alexander_kubra · ‎12-30-2014

Hi Bala,

I'd suggest adding the global_visibility=true attribute to the sys_user table - it will simply disable domain separation for that table. Basically it will allow you to keep the table sort of domain separated (as the sys_domain column still remains there) but you'll have to write your own ACLs or query Business Rules in order to get the needed "level of separation".

Hope it helps.

Alexander

View solution in original post

williamsun · ‎11-13-2014

Visibility Domains.

Let's users from domain A view things as if they were in domain B, regardless of hierarchy or separation.

Domain Separation - ServiceNow Wiki

balakumar1 · ‎11-13-2014

Hi William,

Thanks for the response. But our requirement is NOT to share ALL DATA of domain B with domain A. We would only like users from domain A to see users from domain B in the user reference field, say for example 'Owner', 'Requested by' fields.

If we make domain B a visibility domain for domain A, in that case, domain A users can see all the data of domain B, not only users.

williamsun · ‎11-13-2014

Hmmm.

Since data segregation is the whole purpose of using domains, you will have a hard time.

There was a previous post on this a week ago where they wanted to make a few "solvers" available so I suggested creating a "duplicate" record for the user in that domain and then a business rule that whenever the duplicate user was selected, it would be replaced by the real user (the one that cannot be viewed)

Another option which might not be for you, is to put the users that need to be seen in the 'global' domain, but that depends on the rest of your setup.

balakumar1 · ‎11-14-2014

Hi William,

Yes, this is one of the solutions. But it seems quite complex to me. I'm currently trying the solution proposed by Michael.