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

Question

Question

Running Business Process on Folder

asked on June 2, 2014 Show version history

So I'm having a tough time here.  I have a scenario where a customer has a folder that gets created with a batch name (ABC 6/2/14).  In that folder are numerous documents...the user is responsible for going through each document and determining if that document is Codable or not...so we have a field called Codable (Yes or  No).  The end user wants to be able to go through the folder, index the document with Yes or No, and then run a business process on that folder so that if the documents are indexed as Yes, they go to a certain folder, if they're NO, they go to a different folder (which I'm using a Routing Decision for).  Once all the documents have been moved, they want the folder deleted.  I'm having trouble getting this process to work.  I'm close, and can get the documents to move to the proper folder and the empty folder deleted, the issue is, once their in the Codable Yes or No folders, the Workflow seems to terminate...and I can't figure out what my sequence needs to be in order to get it to not terminate.  Below is a folder structure and workflow.  Any insight would be appreciated.

0 0

Answer

SELECTED ANSWER
replied on June 9, 2014 Show version history

From your workflow and how you explained it, I mapped out a workflow that does essentially what you're trying to do minus some other conditional decisions.  Is this what you are wanting?  It is almost identical to your original workflow, the only difference being that the start of the workflow first find the folder instead of the documents.  Doing this establishes the folder first so that you can delete it after the files have been moved for processing.

 

 

After the folder is deleted, I would make another business process workflow that does the routing. Set up the business process conditions to only be available if the document is in the workers folder and the field has been changed to Yes, No or Needs Changes.  Then you can use the routing decision you have at the end.

0 0

Replies

replied on June 2, 2014

Are you saying that you want the actions in "Needs Changes" to happen after the WF goes through either "Codable" or "Non-Codable"? If that's the case, then you should move them after the "Codable"/"Non-Codable" Conditional Decision.

0 0
replied on June 2, 2014

No, there's 3 possible decisions that can be made once it's in Afyia Millers folder.  Codable, Non-Codable, or Needs Changes.  The issue I'm having is that once I kick off the Business Process to start the above Workflow, the documents do nothing when I change the Field to Yes, No, or Needs Changes.  You can see below where it's getting terminated along with the messages.

 

 

 

0 0
replied on June 2, 2014

Can you post a screenshot of the conditions in one of the branches in the Conditional Decision? Are they set on the entry you just deleted?

0 0
replied on June 2, 2014

So I'm deleting the folder that is empty under Incoming Batches...my conditions are set for Starting Entry field are Yes, No, or Needs Changes (I have no other options other than Starting Entry).

 

0 0
replied on June 3, 2014

So I'm deleting the folder that is empty under Incoming Batches...my conditions are set for Starting Entry field are Yes, No, or Needs Changes (I have no other options other than Starting Entry).

replied on June 9, 2014 Show version history

Looks like the error is because of the starting entry condition.  You said that you have no other options but do you not have any options under the token conditions?

 

Question: What initially starts the workflow?  Is it manually started through the business process or does it start every time a batch is brought into the repository?

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

Sign in to reply to this post.