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

Question

Question

Run a Workflow at the end of a Quick Fields session

asked on January 29, 2015

I understand that there is an option in Quick Fields to run a workflow after a document is stored.  Is it possible to set this up so that a workflow will only run after the last document is stored instead of each document?  Thanks!

 

0 0

Replies

replied on January 29, 2015

Not at this time.

1 0
replied on January 29, 2015

Hi Shelby,

Can you expand upon your request? In what way would this functionality be beneficial to your users? What process(es) do you envision using this feature within?

1 0
replied on January 29, 2015 Show version history

Thanks for the quick replies!  One of my customers runs a Quick Fields session once a week.  The schedule is inconsistent and is never really run on the same day.  He wants to have his Workflow run on these documents right after the Quick Fields session is finished.  

I know that we will be able to set up a scheduled Workflow for a certain interval of time (i.e every hour) to look in this specific folder.  However, due to the inconsistent schedule, the Workflow will find nothing in that folder most of the time.  It just seems a bit inefficient to have Workflow run unnecessarily most of the time.  

If anything, I can also set up a condition at the beginning of the workflow to check if the folder is empty and if so, end the workflow.  Just thought I'd check here to double check.  Thanks!

EDIT: The workflow described runs on all the documents from Quick Fields and will not be done on an individual level.  We won't be able to use a "Entry Created" starting rule.

0 0
replied on January 30, 2015

Hello Shelby,

 

I've read through this problem and tried to come up with ideas. The easiest option may be to add in Business Process functionality to the Workflow, which means that the scanner would be able to log into the Laserfiche repository, and then Invoke the Workflow manually using a Business Process function along the toolbar.

Selecting the Designer space opens the properties for the Workflow itself in the properties pane, and within that you should see the below option.

Once this is ticked to yes, you can then allow users to start the Business Process from the Laserfiche Client. You can add in security and requirements/conditions for when/where the function is available.

You can add the button to the toolbar:

  1. Load the Laserfiche Client
  2. Under Tools, select Options
  3. Within the Toolbars tab, select Customize Toolbar
  4. Within the Commands tab, select Business Processes
  5. Drag the desired function into the toolbar

 

A very similar alternative could be to use a Form as opposed to a Business Process button. Simply design the Form to be submitted and Invoke the Workflow once submitted.

 

There is a more complex alternative that would allow you to fully automate this process. That would involve adding a Placeholder field to the folder, and having this placeholder field be set to "Unprocessed" at the end of each day by a schedule.

When the scan is completed, the first document comes in and a Workflow would run on Entry Created. It would check to see if the folder has the value "Unprocessed", and if it does then it Invokes the Workflow that you have been referring to. You would also place an Assign Field Values just before the Invoke Workflow, that would edit the "Unprocessed" value to "Processed". You would also want to add in a Delay activity, and leave a period of time for all the remaining documents to be scanned in. What this means is that when that second document gets stored, the Workflow will then see that the folder has a value of "Processed" and won't run that Workflow you want. (It will only run once!)

What this means is that when you run that scan, that first document will Invoke your Workflow, and none of the others will. However this isn't a perfect solution because you would need to be aware that its possible the "Processed" field value wouldn't be applied as quickly as the storage of the second document, and so its possible that the second document might also trigger the Workflow too. 

 

Certainly the first option is far simpler. If you have more questions about the complex alternative, feel free to reply and I will try and get back to you with more details.

1 0
replied on February 2, 2015

Thanks so much, Nathan! I'll bring that option up and see if he goes for it.  If not, I can build the workflow you described as well.  Thanks!

0 0
replied on January 30, 2015

I have accomplished this by a very round about method that I wish to avoid in the future, I would be very interested in seeing this functionality built into QF

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

Sign in to reply to this post.