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

Question

Question

Access Denied [9013] Workflow

asked on September 21, 2016

Hello,

I am having some issues with workflow in the below simple process I am not really sure what the issue is this time.

 

Any help I can get would be great thanks..

1 0

Replies

replied on September 21, 2016

This seems to be triggered by using workflow named user instead of admin even though I gave full privileges.

0 0
replied on September 21, 2016

The Access Denied [9013] error is being returned by Laserfiche Server and typically refers to insufficient access rights, not privileges. You should double-check those, e.g. in the desktop Client or in Web Access.

I would expect you would receive the same error if you logged into a client application as the same user and tried moving the same (or similar) entry with the same origin and destination folders.

0 0
replied on February 1, 2017

I'm having the same issue - who would need to have the sufficient rights to move the entry? In this case both myself (the user) and the WF (workflow user) account have full rights and privileges.

0 0
replied on February 1, 2017

You want to look at the entry access rights on the destination folder, not feature rights or privileges.

1 0
replied on January 22, 2021 Show version history

In our situation, we found that a change had been made to the folder months before (we don't process many of the document type that are in the folder - so the impact of the change did not hit until quite a while after the change).  Basically we restricted access to Weblink, but did it in such a way that it caused the folder to be unavailable when new documents needed to be stored there.  Once I changed the access rights back  to inheriting the parent folders rights, the Workflow processed without error.

Wanted to share in case it helps someone else.  So glad to have this forum to brainstorm in!

Thank you!

Christine

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

Sign in to reply to this post.