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

Question

Question

Laserfiche Client showing a different last modified by user than Workflow Subscriber Trace

asked on April 1, 2015

Ran into an odd behavior with the action by recorded trustee being different than the Laserfiche Client.

 

I have some guesses as to why this happens but thought I'd post it encase someone else runs into this in the future.

 

1.) Renamed the existing Workflow User account and gave different permissions for a business reason.

2.) Changed a starting rule reference from "User - does not equal - Former Workflow Account" to the new account

3.) Changed the workflow profile to the new Workfow User account and republished.

4.) A day later, I fired the workflow to test and it ran into an infinite loop (runaway workflow).

 

I disabled the rule and manually ran the workflow and in the Client it shows the "Last modified by - New Workflow Account Name". However, in subscriber trace, it shows the action was taken by the "Former Workflow Account Name".

 

Restarting the Laserfiche Workflow Services on the server resolved the issue and subscriber trace now matches the updated Workflow Account name viewable from the Client.

 

Cheers,

Carl

0 0

Replies

replied on April 3, 2015

We cache the names for about an hour, but it looks like there is a bug in the part of code that clears out the cache. Thanks for pointing it out, we'll address it for Workflow 9.2.1.

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

Sign in to reply to this post.