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

Question

Question

When does a workflow executes because of event in another workflow

Workflow Version 10
Updated September 1, 2016
asked on September 1, 2016

When does a workflow execute when a workflow rule is met from an event occurring in another workflow? 

 

Here is my use-case...

I have a workflow that is executing when a folder is created within another folder (the Entry Created condition).  One such time this condition is met is from another workflow process.

Will the Entry Created condition wait for the other workflow to finish before it executes or does it execute as soon as the workflow creates the folder?

If it fires immediately, what is the recommended approach to ensure the second workflow waits for the first workflow to finish before it starts executing?

0 0

Replies

replied on September 1, 2016

If I follow correctly, are you saying that another workflow start rule is met by an action in the initial workflow?

It will not wait for the other to finish it is going to trigger immediately.  If you want the other workflow to trigger I would not rely on the starting rules for that.  During the first workflow, after the folder is created, use an Invoke Workflow activity to start the other one.  In the invoke you can choose to wait for it to finish or not

0 0
replied on September 1, 2016 • Show version history

Yes, you are understanding correctly.  

To give more details on my problem let's call the workflow that processes the newly created folder the "Folder Created" workflow and the workflow that is currently being executed the "Document Moved" workflow.  There are several events that can occur which can cause the "Folder Created" workflow to fire. 

 

Here are some use-cases...

- The "Document Moved" workflow is moving a document from one folder to another.  If the folder in which the document is being moved does not exist it creates it.

- It is also possible a user could manually create a folder.

- A Quick Fields scanning process could drop documents into a folder, if the folder does not exist the Quick Fields process will create the folder.

All of these use-cases, and several others, could cause the "Folder Created" workflow to execute.  Given there are many use-cases where the "Folder Created" workflow can be executed it would be preferred to not have to invoke it from the "Document Moved" workflow since this would only handle one of the use-cases.

Any other suggestions on how I might be able to solve this?  Could I solve it someway by locking the newly created folder and have the "Folder Created" workflow wait for the folder to be unlocked before starting its process? 

Would using the "Simple Synchronization Sequence" activity provide me the results I am looking for?

0 0
replied on September 1, 2016

I guess I am still unsure if you want it to trigger or not.  Should the workflows trigger off the actions or are you wanting to avoid the parent workflow starting any of the others?

0 0
replied on September 1, 2016

I want the "Folder Created" workflow to trigger but I don't want it to be invoked directly in the "Document Moved" workflow.  I want it to be invoked simply by the fact that the "Document Moved" workflow created a new folder.  The caveat is that the "Document Moved" workflow is doing other activities with the folder after it creates it and I want to make sure these activities are completed before the "Folder Created" workflow starts doing its own processing of the folder.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...