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

Question

Question

Issue with a Conditional Decision

asked on November 6, 2017

Hello!

 

We are using LaserFische for Employee files and we have folders for Active and Inactive employees.  I am trying to create a workflow that will look for either the word TERM in our Status Field or if the term date has data.    This data is pulled from another database we have I have confirmed that the data is being pulled.  When we try to implement he workflow it fails.   I am using a Conditional Decision I have tried  "Starting Entry: Field (Term Date) is empty.  I have also tried several ways of looking for Term in the "Status" Field.   I am not sure if I am being clear.    Anyone have any suggestions?

0 0

Replies

replied on November 6, 2017

Darin,

 

The way you are doing it should work, unless the data is not filled WHEN the workflow starts.  If you are filling it with a database query after it starts, you cannot use the starting entry.  Add a 'Find Entry' after the lookup, and then use the field for the 'Find Entry' activity, not the starting entry.

1 0
replied on November 6, 2017

Searching for the documents and retrieving the field values should let you write the conditional statement that says

If any of these conditions are true 

Token:Retrieve Field Value (Term Date) is not empty

Token:Retrieve Field Values (Status) equals TERM

ConditionalStatement.jpg
1 0
replied on November 6, 2017

Retrieve Field Values is not needed, Conditional Decision can look up fields on the current entry.

0 0
replied on November 7, 2017

Thanks for all help!   It was helpful but after looking at the log (Which I had forgotten about) its actually failing on the next step.  Here is a screen shot of my workflow. 

 

Branch 2 is a copy of the workflow we currently have with no logic for Termed or Active employee it seems its not moving past the PreEmployment on either side.

1 0
replied on November 7, 2017 Show version history

EUREKA I feel like an idiot but I figured it out for some reason the flow was going to the end not to the next step in each branch.  

Thanks for willingness to help.  This only my 2nd week using LaserFiche.

 

1 0
replied on November 7, 2017

Welcome to the party!  I learn something every time I build a workflow, so just know that it will always present you with something NEW!  Answers is great place for help too (even if we end up finding our own answers in the process.)

Hope to see you at Empower in January Darin.

0 0
replied on November 7, 2017

One thing to keep in mind with conditional decisions is that if your conditions don't cover all possible combinations, there's an implied branch all the way to the right with no conditions to keep the workflow from getting stuck. That's probably what you were seeing if it looked like it skipped all branches in your activity.

1 0
replied on November 7, 2017

Michelle I don't Empower is in the budget this Year.   Maybe next year!

 

 

Miruna, that might have been it.   Thanks for info!

0 0
replied on November 6, 2017 Show version history

Darin,  Let me see if I understand your question:  you have a template that is populated with information from two databases.  On this template is a Termination Date field and an Employee Status field.  You want to use one (or both) fields to qualify an employee as terminated.  Your current conditional expression is setup as  "Starting Entry: Field (Term Date) is empty" but is not producing any results.

 

Are you using a find entries activity or a search activity to retrieve entries for your workflow?

Depending upon how you are retrieving entries, you may need to change your conditional from "Staring Entry: Field (Term Date) is empty" to "Output Entries"  OR if you are using a 'For Each' statement, you may need to change to using "Current Entry".  See attached for what I mean.

Hope this helps.

11-6-17 WF entries.PNG
11-6-17 WF entries2.PNG
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.