Question

2 Starting Rules in Workflow

Workflow

Updated January 21, 2014

asked on January 14, 2014

So I'm using Workflow to move submitted Forms from LF Forms. It's pretty straight forward as I have an Incoming Documents folder that is monitored. However, to accomodate the possibility of a Form not being moved properly, I've created 2 starting rules...a "When Entry is Created" and "When Entry is Changed"...and both starting rules use the same criteria. However, whats happening...is when an Entry gets created...the Rules seem to both kickoff the Workflow...thus the documents template, has duplicate info (2 Address Fields, 2 Name Fields, etc.)? Is there something else I'm missing to prevent this from happening? I've attached my Workflow below.

Starting Rule.PNG (54.71 KB)

| Download

Workflow.PNG (27.35 KB)

| Download

0 0

Replies

replied on January 14, 2014

You can check out the Subscriber Trace to see what events are coming in. If I had to guess, Forms creates the document first and the modifies it to set the fields or append pages. The Subscriber Trace should give you exact information on what's going on. Then you could either exclude the Forms user from the rule for Entry Change or tweak it with Entry Changes events (maybe exclude Page creation or something like that).

0 0

replied on January 15, 2014

Miruna,

I'm still stumped...I looked in the Tracer and I'm not seeing why it's duplicating template info? I've attached screenshots of my stack trace results for an entry I tested...also screenshot of Search Results of the last entry and you'll see it's listed twice.

Workflow Search Results.PNG (36.63 KB)

| Download

Sixth Step.PNG (83.29 KB)

| Download

Fifth Step.PNG (82.71 KB)

| Download

Fourth Step.PNG (82.71 KB)

| Download

Third Step.PNG (79.93 KB)

| Download

Second Step.PNG (80.38 KB)

| Download

First Step.PNG (63.56 KB)

| Download

0 0

replied on January 14, 2014

An alternative would be to trigger a Workflow from your Forms Business Process after each Form submission. This way, each time a Form is submitted, your workflow for moving the entry will run on that particular entry once the Forms server has finished saving the Form to Laserfiche.

0 0

View 1 previous reply

replied on January 15, 2014 • Show version history

Mike,

So I added a Service Task to my Processor to start the Workflow, so what I have now are 2 Service Tasks (first is to Save to Repository, second is to Start the Workflow). The issue I'm having now is my Workflow is terminating saying that "No Entry was specified" when it tries to Retrieve Field Values (which is the first step in my Workflow).

0 0

replied on January 18, 2014

Hi Daryl,

I have noticed this on some occasions when implementing the solution myself since Workflow doesn't know when Forms has finished saving the data to Laserfiche. A workaround I have implemented is to add a 1 minute delay in the Workflow before the "Retrieve Laserfiche Forms Content" is called; this will allow sufficient time for the Forms "Save to Repository" action to be completed.

In a future version, there will be functionality to trigger the Workflow process from Forms only AFTER the Save to Repository action is complete and the delay will no longer be necessary.

Hope this helps!

1 0

replied on January 20, 2014

Mike...just curious though...if you're doing a "Save to Repository"...then why would you also use the Retrieve Laserfiche Forms Content, as you can mapp the Forms data to fields in the "Save to Repository" configuration?

0 0

replied on January 21, 2014

Apologies, I'm using the "Save to Laserfiche" feature that was available in Forms 9.0. You're right though Daryl, the "Save to Repository" feature in 9.1 is more robust and can directly copy Forms field data into Laserfiche metadata.

0 0

You are not allowed to follow up in this post.

Question

Question

2 Starting Rules in Workflow

Replies

Sign in to reply to this post.