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

Question

Question

Why is Workflow re-processing a document?

asked on November 17, 2014 Show version history

I have a customer that had a document missing.  I ran the Audit and found that a User had deleted the document.  However, I can't make sense of what I'm seeing.  The user only has the ability to delete documents from their personal folder.  When I look at the Audit Report..I can see that the document went through the proper process, and ultimately ended up in the "Processed" folder, however, the last activity was that the user deleted to document from their Personal folder.  I'm having a tough time understanding how the document could have been deleted from her personal folder when it was moved from there by Workflow?  I've attached the Audit Report below.

0 0

Answer

SELECTED ANSWER
replied on November 17, 2014

The workflow server that acted on the document on 11/7 is a different workflow server than the one that originally processed the document. Did they deploy a second workflow server? Perhaps this is a test workflow server that somehow was configured to run against their production repository?

2 0

Replies

replied on November 17, 2014 Show version history

You may want to double check the starting rules of the workflows and see if they are being triggered again. Without knowing what the starting rules are, it's hard to say, but you can see that Workflow sets the "Allocated?" field and then moves it to Jane's folder. This is the same first two steps performed by Workflow after the document was initially stored from Quick Fields.

*Edit*

Note that the issue doesn't appear to be that the user is able to delete documents without having the delete right. The issue appears to be that the document is triggering the workflow again and it is being moved back into Jane's personal folder where she then deletes it.

0 0
replied on November 17, 2014

Alex,

I looked through all the Workflows and there are no workflows where the starting conditions would have met the criteria of the document being in the Processed Folder and moving it.  I ran a search on all workflows that ran for the entry and you'll see below, the last workflow activity was on 10/29 (and this was just adding an annotation) however, the Audit shows it moved on 11/7

 

0 0
SELECTED ANSWER
replied on November 17, 2014

The workflow server that acted on the document on 11/7 is a different workflow server than the one that originally processed the document. Did they deploy a second workflow server? Perhaps this is a test workflow server that somehow was configured to run against their production repository?

2 0
replied on November 17, 2014

Yes they did deploy a test Workflow server, however, it was set to run against a copy of the Production Repository (Repository db, files were renamed and Repository ID was changed), but clearly, something must have been missed.  Thanks!!

 

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

Sign in to reply to this post.