User Criteria Not Working (San Diego)

machiavvelli
Tera Contributor

I am developing a scoped application for a client.  I have two record producers on the home page of a Service Portal.

I am trying to configure the record producers to be visible only to certain specified groups or roles.

I have created user criteria and added them to the record producers under the "Available for" related list.

When I impersonate the proper user, I can still see the record producer and I should not be able to do so.

I have run user criteria diagnostics and it says that user should not be able to see the record producer, but that user CAN see it.

Should user criteria be created in the Global scope or my specific scope (I created them in my specific scope)?

What am I doing wrong?

Thank you for any guidance you can give.

 

signed,

- "Dead-end in Dayton"

6 REPLIES 6

Gunjan Kiratkar
Kilo Patron
Kilo Patron

Hi @machiavvelli ,

Clear the cached of instance. Sometimes it happened because of cache memory.

To clear cache, Type 'cache.do' in application navigator

GunjanKiratkar_0-1668088798458.png

 

Try creating in Global Scope as well.

 


Please Mark My Response as Correct/Helpful based on Impact
Regards,
Gunjan Kiratkar
2X ServiceNow MVP
Community Rising Star 2022
Youtube : ServiceNow Guy

I cleared the cache but that didn't change anything.

I deleted both user criteria, re-created them in the global scope and cleared the cache again but that didn't change anything, either.

Thank you for your suggestions, but do you have any others?

Hi @machiavvelli ,

Check what you have mentioned in both Available for and Not available related list of catalog item. Is there any conflict between this 2.


Please Mark My Response as Correct/Helpful based on Impact
Regards,
Gunjan Kiratkar
2X ServiceNow MVP
Community Rising Star 2022
Youtube : ServiceNow Guy

There is nothing in the "Not Available For" related list, so there cannot be a conflict.

machiavvelli_0-1668090687655.png