10-03-2013 07:43 PM
I'm currently testing the Web Client in 7.1 build 1150.
Changing access control on records either in web client or rich client immediately propagates between the interfaces. However, if I change a caveat or security level on a Profile, it's taking 20 mins plus for that change to be reflected on the profile when accessing the Web Client.
I.E.. If I upgrade security level, a user logging into rich client will immediately see higher level records. If the same user then opens Web Client, the change will not have taken effect. I even tried changing the users network ID in TRIM to match another user, and they were still logging in to the web client as the old user.
Is this expected and standard behaviour?
10-03-2013 08:19 PM
It sounds like it might be a caching issue.
Are you able to make the security change to a user.
Perform an IIS reset on the server that runs the webclient and retest the security access?
10-03-2013 08:37 PM
10-03-2013 08:49 PM - edited 10-03-2013 09:12 PM
That sounds exactly like the behaviour I'm seeing as it's around 20 mins before I see the change. I did try running the web browser and bypassing the local cache, but expect this is likely happening on the server anyway?
Edit: Yes, would be interested in your page and how you are triggering that log out - I have low-level IT capable users to look after.