You are viewing limited content. For full access, please sign in.

Question

Question

Users unavailable for tasks until they login

asked on June 26, 2018

Hello,

I'm having an issue where users are not available to be assigned to a task until they have logged into forms.  It seems that there is a session time out on a users login which keeps alive for about a day.  Unless a user logins into forms daily, they will not have tasks automatically assigned to them by Laserfiche as their userid is not available.

Any insight into how to resolve this would be helpful. Ideally, a person should be able to take a weeks vacation and still have tasks auto assign to them to await them on their return without having to wait for them to login on their return and then manually reassign tasks one at a time to them which is currently the case.

Version 10.1 Forms with windows authentication.

 

0 0

Replies

replied on June 26, 2018 Show version history

Hi John-Paul,

Are you using Directory Server authentication? If so, which version of LFDS? Users do not need to be logged in to be assigned to tasks, but they do need to be identified as valid users by the system and I suspect that is the problem you're seeing.

It sounds like you might be encountering a bug we ran into awhile back. If I'm right, the users aren't getting logged out, they are being marked as "Invalid" when the AD synchronization occurs and therefore do not get validated until they log in again.

You can check this by looking at the user list in Forms Administration. If this is indeed the same issue we encountered, then right after the synchronization most, if not all, of your AD users would have "Invalid" next to their names.

If memory serves, we were running Forms 10.1 Update 2 and support provided a patch we applied to our Directory Server that resolved the issue, but I believe the LFDS portion was rolled into an update shortly after so that might be all you need.

0 0
replied on June 26, 2018

Thank you for the reply, our users are indeed listed as invalid.  I believe you are describing exactly the issue we're having.  Our LFDS version is 10.0.0.270.  

0 0
replied on June 26, 2018

My suggestion would be to apply LFDS 10 Update 2 and make sure you're Forms 10.1 has Update 3 as well.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.