The CreatorCon Call for Content is officially open! Get started here.

Announcements ignore user criteria on Service Portals

BKlus
Tera Contributor

Hello Community,

 

I want to make sure, that some Announcements are only displayed to certain people.

It seems like, that the User criteria that I have assigned to the can view tab doesn't affect the view rules at all.

It doesn't matter if the criteria only applies to one user or if its scripted.

 

What I've done so far:

- The Plugin Service Portal User Criteria Support is installed

- The System Property glide.service_portal.user_criteria_enabled is true

- The Announcement is not public

- The User Criteria is working for other portal widgets 

- The behavior is even the same on other portals

- Also, I've cleared my Browser cache and used incognito mode for testing

 

The only thing I've stumbled over is that the Widget itself does not contain a visibility check for the user criteria, but this should not be necessary.

 

Has anyone experienced the the same Problem?

 

Thank you in advance

 

Regards Bernd

9 REPLIES 9

@BKlus 

Was this working earlier?

Did you recently upgrade?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

@Ankur Bawiskar 

The user criteria itself did work, but we haven't used user criteria with announcements in the past.

We've upgraded to Yokohama a couple of months ago.

@BKlus 

it should work as expected.

Please raise a case with ServiceNow.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Bshirisha
Tera Contributor

Hello @BKlus ,

I’ve used the user criteria for announcements, and it’s working fine—only users who meet the criteria can view them in the mentioned portals. 

BKlus
Tera Contributor

This is not the case with my instance. But good to know that it should work 🙂