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

Question

Question

Broken Workflow Missing Tokens

asked on April 14, 2014

My customer has a complex workflow for invoice approval that uses the Invoice Number and Vendor Name from 'Retrieve Field Values' to move the invoice between approval folders. It also changes the invoice 'Access Rights' as it moves the image.

Recently I made a small change to a Date Token. Upon Publishing the new version, all current workflows lost their token values.

When Publishing, I used the "Yes" option to update currently running workflows.

All current workflows lost their workflow tokens values.  The 'Retrieve Field Values' now returns nothing. The Access Rights are no longer being updated.  The workflows are still running and approvals can still be made, but it has resulted in all current invoices being moved to a single folder as they are approved or paid.  As the Access Rights are not updated the users do not have correct access.

The metadata for the image is still available to the Laserfiche Client.

I have tried this same update on a test installation and it was OK. I have also created additional workflows to manage the broken ones using the metadata.

This is not a trivial issue as there could be 500 to 1000 invoices in workflows at any one time.

 

What is the 'Yes' button for?

I assumed it would update the current workflows with the new date token.

I cannot find mention of it in the manuals.

 

Has anyone else experienced this?

 

1 0

Replies

replied on April 14, 2014

Hi Peter,

 

I have a customer that has experienced this, and is in fact still experiencing it from time to time. I have a case open with Laserfiche Support to try and get to the bottom of the issue, however we have nothing yet.

 

The workaround at this point is to publish the workflow under a different name, then the missing tokens issue goes away.

 

Wish I could be of more help, but as I said, we also don't know what causes this.

 

Sheldon

0 0
replied on April 15, 2014

Thanks Sheldon,

I once had a similar issue when working on my own development server.

I have never had any issues if I select NO when publishing.

 

The answer may be "don't press the YES button".

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

Sign in to reply to this post.