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

Question

Question

Web Client cannot change template without rights to edit all of the entry's fields

asked on April 18, 2017

I have discovered a difference between the Windows Client and the Web Client in version 10.2, in the way they handle template security when secured fields are added to the entry outside of the template.

In the Windows Client, the user is allowed to change the template as long as they can change the content of every field within the template.  Fields assigned to the document outside of the template can be read-only or invisible to the user without affecting their access to the template.

In the Web Client, the user is only allowed to change the template if they have access to change the value of every field assigned to the entry.   A read-only or hidden field assigned to the entry outside of the template will prevent users from changing the template, even though these fields would not be affected.

This is preventing us from adopting the Web Client because we have values assigned to all of our documents by Workflow, in fields only the Workflow account can change.  We are able to change templates in the Windows Client because the fields are not part of the template itself.

0 0

Replies

replied on April 18, 2017

Hi Bruce, 

 

We can reproduce the issue you described. We found that while we can still change the template if the user is denied read on an independent field, we cannot change the template when the user is granted read but denied edit. In other words, we can reproduce the read-only case, but not the hidden field case. 

 

I apologize for any inconvenience this issue may have caused you. We've filed a bug report (SCR156751 for your reference) and expect to fix the issue for the Laserfiche 10.2.1 release, due out in the next month. 

 

If you could, please confirm that for the 'hidden field' case, that the 'read' field right is explicitly denied on the user in question. That way, it's ensured that user isn't inheriting read access from group membership. If you still see the issue, comment back on the thread and we'll continue troubleshooting. 

0 0
replied on April 19, 2017

Sorry Ryan, you're right, the issue only occurs when the user has read but not write access to an independent field.  I had not properly tested with only the hidden field.  

Thanks!

-Bruce

0 0
replied on May 17, 2017

Hi Bruce,

 

Just as an update, we fixed this issue in the recently released version Web Client 10.2.1. Installing this new version should resolve the problem.

 

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

Sign in to reply to this post.