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

Question

Question

workflow won't match search

asked on March 28, 2016 Show version history

I have a workflow for a client that sometimes won't match either the Delivery Docket or Order Number Field.  95% percent of the time this does work. I have manually put the DD or ON in to the search criteria and it works.  When I manually run the workflow, it shows a syntax error in the search string. Yet it works for most of the time.

I have attached the Workflow. I can supply more details as needed too.

p.s. rename the attached matched.wfi.jpg to remove the .jpg extension :)

0 0

Replies

replied on March 30, 2016 Show version history

From the workflow, it's retrieving field values from the starting entry and using those tokens to search. For the workflow instances that fail, have you checked to see what values it got from the Delivery Docket and Order Number fields? Perhaps someone entered in a value incorrectly and that's causing the search syntax error when Workflow tries to run on it.

*Note - I deleted the workflow you attached because it contains your server information.

0 0
replied on March 30, 2016

Hello Alexander,

The values are correct. I have been able to copy from the fields and use the search string to find the appropriate order.

Are there any particular logs I can send you that may assist?

0 0
replied on March 31, 2016

Search in the Workflow Designer for the instances that failed to run successfully. Open the instance details and view the "Messages" tab to see the exact details of the error. Then look at the "Tokens" tab to see if the search was using the token value that you were expecting it to use.

0 0
replied on April 22, 2016

Hi Jonathan,

 

Just wondering if you were able to solve this workflow issue. If not, please feel free to raise support case in our support site. Thanks!

 

 

0 0
replied on April 26, 2016

A support ticket has been created and we'll update the thread once there is a fix.

0 0
replied on May 8, 2016

The error and warning in the failed instances are like below:

Input string was not in a correct format. [%(SearchRepositoryforFieldXX_Result Count)].

The token "SearchRepositoryforFieldXX_ResultCount" was not found".

It turns out to be a design problem, that tokens %(SearchRepositoryforFieldXX_Result Count) from condition sequence activities are being referenced in condition check. Then under some circumstances, the condition sequence activities are skipped, thus there is no %(SearchRepositoryforFieldXX_Result Count) token. However it still needs evaluating in another activity. That's when Laserfiche Workflow errors out.

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

Sign in to reply to this post.