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

Question

Question

Wait for Folder to Contain An Entry from a List

asked on July 22, 2022

I have a list of entry titles, and I want to wait for a certain folder to contain one of them before proceeding.

For example, if my list of entry titles is A, B, and C, I want to wait for the folder "Autofile" to contain an entry called A, an entry called B, or an entry called C. It doesn't matter which one is there.

I do not know ahead of time how many titles will be on the list or what the titles will be, since they come from a Forms process, so I cannot hardcode the titles or how many conditions to use like the screenshot below.

What I need is a condition like "Entry : Name is contained within [List]" or something similar. Unfortunately, the other way around is not an option, as the selector for Folder Contents only has choices of Entry or Document, so I can't target the list itself.

Is this possible in Workflow (On-Prem)?

0 0

Replies

replied on July 22, 2022

I don't think that's possible in the content conditions.

What exactly are you trying to accomplish? For example, what is triggering the workflow that contains the wait condition and how does it relate to the Forms process?

There might be another solution (I usually avoid Wait for Entry Change).

0 0
replied on July 22, 2022

In short, a Forms submission is performed with a table of accounts. For each account (we have no idea how many ahead of time) a document will end up coming into Laserfiche from an external source once an external step is completed. We have no idea when it will complete since it's outside of Laserfiche and is a manual step. All the workflow (which the Forms process invokes) has access to is what the document will be called when it comes in, which is unique.

I need this workflow to wait for the document/documents for that Forms to exist, then perform some steps on each doc once it is found.

I don't want to iterate through the document titles waiting for each to exist one at a time, because we have no idea when each one will come in or in what order, and if we're stuck waiting for the doc for the current iteration, any documents that already came in will just sit there unfiled, but I suppose that is an option even if not ideal.

Thanks

0 0
replied on July 22, 2022

Unfortunately, the wait for entry change isn't going to support that because it doesn't seem to have any "is in" type option for the entry names.

However, I wouldn't personally go that route anyway. I had a similar process and the more volume you have and the longer the waits, the greater the chances that something will get stuck, and it happened to us often enough that I ended up going a different route.

It doesn't sound like Wait for Entry Change would do what you want anyway, because if the process is meant to act on each document as they come in, the first document would end the wait and even if you do it in a loop, two documents could come in close enough together to have one get missed.

Does the Forms process also need to wait for the documents, or are you just using data from the Forms process to act on the documents?

 

0 0
replied on July 23, 2022

The Forms process waits for all documents to be processed before it can continue.

Not sure what you mean by one getting missed, since as far as I can tell (and it at least worked that way when I tested with metadata fields being assigned) Wait for Entry Change will work retroactively. In other words, if two docs came in at the same time that one workflow needed to handle, I believe it would still be able to handle both even if one was already there when the "Wait for Entry Change" action started.

0 0
replied on July 25, 2022

I would look at creating another workflow that monitors for the creation/import of the document and then set a field on the rest of the documents to trigger the wait for entry change to proceed to the next step.

0 0
replied on July 25, 2022

Hi Bert,

How would this other workflow monitoring for creation/import help? I know what starting conditions I could use to kick it off, but what metadata could I set on each document that would indicate to the Wait for Entry Change action that this document belongs with this one specific workflow instance?

0 0
replied on July 25, 2022

You can either pick an existing field or create a new one that the 2nd workflow applies to the documents.  Then in the first workflow's "Wait for Entry Change" event, set it to wait for the field to have the specific value that will be set by workflow 2.

0 0
replied on July 25, 2022

The problem is how the first workflow would know which documents belong to it and not another instance of the same workflow. The reason it matters which instance processes the document is because the last step is passing the URLs of the documents back into the specific Forms instance that invoked it.

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

Sign in to reply to this post.