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

Question

Question

Workflow process not executing when other workflow creates path

asked on June 26, 2020 Show version history

I have a Workflow process that should execute whenever a subfolder is created in a specific folder...here are the conditions.

 

 

I have another workflow process that moves a document into a folder and if that folder does not exist it should create it (see image below)

 

I would expect this to execute the Workflow from the conditions above but it does not do this, what am I doing wrong?

 

Let me give a more details explanation...

 

I have a workflow process that is conditioned to execute when a folder is created in the \rootfolder\parentfolder folder (let's call it CreateFolders).  

I have another workflow process (call it ProcessDocument) that moves a document into folder \rootfolder\parentfolder\childfolder\grandchildfolder.  Assuming childfolder does not exist when ProcessDocument workflow is run, then I would expect the CreateFolders workflow to execute because the childfolder folder is being created as part of the Move Entry workflow action in ProcessDocument workflow.

As a test I also added a Create Entry action in the ProcessDocument workflow to create the childfolder before it moved the document.  Even this did not execute the CreateFolders workflow.  If I go into Laserfiche and manually create the childfolder folder then the CreateFolders workflow process does execute.

FolderCreate.png
0 0

Answer

SELECTED ANSWER
replied on June 29, 2020

It's possible the account associated with your Workflow profile is being excluded from monitored activity in the repository. It's not a default option, but it may have been set up in your case. You would see it in the Workflow Administration Console under Advanced Server Options.

 

4 0
replied on June 29, 2020

That was exactly it...removed the Workflow user from the exclusions and bam!  it works!

0 0
replied on June 30, 2020

Be VERY careful with this, or you may see negative effects. Workflows looping between each over and over..

You could removed the User from the exclusions, but then add an exclusion to your Workflow Processes like (When USER NOT EQUAL "WF") except on the one(s) you wish to still run.

3 0

Replies

replied on June 29, 2020

Two thoughts:

1. Change your start rule to "When Path Starts With"

2. Run the Folder Created WorkFlow from within the Move File workflow, If it does something you don't want to occur if the folder's been there for a while, you could pull the date created from it, and if less than 5 min ago, then end the workflow, else process your tasks.

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

Sign in to reply to this post.