Using Nautilus (Fiserv branded OnBase) v 20.3.2
We have one user that is showing scan queues that she is not a part of in her Thick Client application only. In Unity, the correct scan queues for the user group she is assigned to display but in Thick she shows a completely difference set of Scan Queues. No filters are set for this user either.
In Config, we confirmed her User Group and assigned scan queues are correct, the other employees in her User Group see the correct scan queues as well and do not have the same issue as her.
In Config > Utils > Configuration Tree, it shows that this user is only assigned the 5 scan queues for her User Group but in Thick she sees 17 more queues than she should not see.
-We uninstalled, and did a fresh install of Thick Client on her machine with same result
-Had user sign onto a different PC with Thick Client installed and same result - she see scan queues she should not see.
-Verified in Active Directory the user is a part of the same OU and Security Groups as her coworkers who do not have this issue.
-After hours with user logged off, we removed the user from her User Group in Config, relaunched Config and added them back into their dept User Group with no change.
-Next day with user logged off, we removed the user from her User Group in Config, and let AD do the mappings per usual that morning when the user logged in to start her day. Confirmed the user was added back the the correct user groups but Thick Client still showed scan queues she should not have access to.
- Went to Config > Utils > Directory Service Authentication - Active Directory Enhanced > Settings > right click user and selected "Evaluate OnBase Group Membership" and verified the OnBase user groups resolved correctly, right clicked the user and selected "Remove Any Mappings for this AD user" and had user log back in and it mapped the correct User Group but Thick Client still shows Scan Queues she should not see.
- each time we cleared cache in Config, multiple IIS resets over many days, but user still see scan queues she should not in Thick (Unity remains correct and only shows the scan queues she is supposed to have).
- reviewed SQL DB for locks or duplicate username entries but did not find anything.
Has anyone seen anything like this where Thick Client show scan queues they should not see while Unity shows the correct ones? This is happening only to 1 user and we are stumped. We have reported this to our first line of support at Fiserv and had a few remote sessions with them and had the user do a screenshare so they could look at all the configs, groups and scan queue permissions with no resolution but it's still being researched by support.
