The out of the box way to apply User Criteria is tedious. First, the user needs to log out, which is something that everyone hates. The user has to go through multiple SSO white flashing screens or he has to re-enter his password. Overall, it might take up to 15 seconds untill user can use ServiceNow again.
Secondly, users want the effect to happen immediately. If you have changed your location from Norway to Sweden and you are still seeing only location specific requests for Norway employees, you might think it’s not working as expected. Everyone hates situations when they call Service Desk complaining something is not working and they are presented the same old question – ‘Have you tried logging out and in?’. There are no winners here.
Log out requirement is done for performance reasons: User Criteria is cached and is only build once, when the user has logged in.
There are some drawbacks in OOTB UC set up:
1) User needs to log out and back in which can take some time.
2) Complete user cache has to be rebuilt from 0. I would think this has quite some performance impact compared what I will suggest next.
Let’s say the criteria is based on user’s language and the user is using service portal. Let’s make sure he has no need to log out to see his language-based catalog items.
Now let’s create some Scripted user criteria records which would confirm the user criteria was applied immediately. Do this for Sweden and Norway. As in example:
Add the user criteria to some catalog items. Let’s say iPad’s can only be ordered if your language is Swedish, and iPhone’s if it’s Norwegian. Now let’s open the Service Portal:
You can see both criteria’s were evaluated and Sweden one was applied, however, when we change our language to Norway, this is not re-displayed and the criteria is not re-applied until we log out or clear server cache.
So how can we do it without logging out or clearing all server cache?
By clearing user’s private user criteria cache object whenever he changes his language.
If we use cache inspector tool (more on my previous article), we can locate the UC cache object name: criteria_cache.
To add it to the portal let’s modify the ‘User Profile’ Service Portal widget by cloning it and adding the copy to our page. Modify the server code whenever user language is changed to clear his UC cache with this code:
That’s it! No more need to log out and back in. Effects are immediate once you go back to the catalog.
Does this kind of scripted user criteria have performance implications?
No, because there is another user object cached which holds all user profile specific information, including his language setting. Therefore, user criteria scripts are only looking for the value in the cache and not performing any database queries.