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

Question

Question

Workflow Starting Rule Behavior - Client vs Web - Document Import

Workflow Web Client
Updated November 30, 2015
asked on November 23, 2015

We have two workflows. One with starting rules to fire  on entry created, and the other on entry updated.

 

When dragging a word document from a user's desktop into the Laserfiche desktop client the desired behavior is exhibited where only the entry created workflow runs.

 

When importing from the document from the Laserfiche Client's File-> Import menu, desired behavior is exhibited where only the entry created workflow runs.

 

When dragging a file from the user's desktop into Web Access for import, both the update and create starting rules are triggered and both workflows run. This is undesired.

 

When importing a file from the Web Access menu both the update and create starting rules are triggered and both workflows run. This is undesired as well.

 

What would be the difference in how workflow starting rules are evaluating an entry update vs creation when being imported from Web Access? I've tried adding more conditions to the "entry updated" workflow but it seems to always fire when an entry is created from the web client no matter how strict I make them.

 

Thank you for your time,

Carl

0 0

Answer

SELECTED ANSWER
replied on November 30, 2015

Yes, that's what Robbie and I tracked it down to. Web Access unlocks the document before extracting text, which causes the Laserfiche Server to fire the document creation notification, followed by the entry change one once the text is added. It only happens when documents are not under version control.

It's fixed in Web Access 10. There are 2 possible workarounds in version 9. You could turn on version control on the parent folder, so Web Access will create all new documents as version controlled (and hold on to the lock when extracting text). Or, you could modify the Entry Change starting rule in WF and specifically exclude Page Created/Written events.

0 0

Replies

replied on November 23, 2015

Web Access is version 9.2.1.568 and Client is 9.2.1.635 and Workflow is using the following assemblies.

 

0 0
replied on November 23, 2015

I'm not seeing it in a basic test. If you look in the Subscriber Trace, what user is displayed in the Entry Change event that triggers Workflow when you import through Web Access?

0 0
View 7 previous replies
replied on November 24, 2015

I have it sending an email which includes the initiator's name and it's been showing up as the user performing the task for both.

 

Subscriber trace:

 

I imported document 11 through the web client and then renamed it to 12 and put it through the desktop client.

 

A few difference:

- Entry name includes extension when going through the web client

- Registering a change event occurs when going through the web

 

 

 

0 0
replied on November 24, 2015

Are you using classification levels? If so, I think I found the bug. It is updating the document after unlocking it.

0 0
replied on November 24, 2015

According to LF Admin Console VERS Classification Levels are not used on any repository.

 

This was an issue I was able to recreate from our production environment into our development environment and appears specific to web client imports only.

 

Thanks for looking into this btw!

0 0
replied on November 24, 2015

Carl, could you add a condition on Entry Changes to your starting rule for Entry Change? It doesn't matter what you choose to include for Entry Changes, I just want to see what the condition evaluation will say in the Subscriber Trace. Based on what changes, it might help us narrow down what's going on.

0 0
replied on November 25, 2015

Sure,

 

 

This was adding in the new document 13 from the Web Client

0 0
replied on November 25, 2015

Can you run an audit report against the document and see what may be happening to it after it's created? If it doesn't turn up anything useful, can you open a support case with your reseller so we can look into this further?

0 0
replied on November 30, 2015

Carl, did you have "generate searchable text" checked in the import dialog?

0 0
replied on November 30, 2015

Yes Miruna. This was checked on both the web import and the client import.

 

Is the thick client creating the searchable text before creating the entry while the web client creates the entry and then adds in the searchable text?

0 0
SELECTED ANSWER
replied on November 30, 2015

Yes, that's what Robbie and I tracked it down to. Web Access unlocks the document before extracting text, which causes the Laserfiche Server to fire the document creation notification, followed by the entry change one once the text is added. It only happens when documents are not under version control.

It's fixed in Web Access 10. There are 2 possible workarounds in version 9. You could turn on version control on the parent folder, so Web Access will create all new documents as version controlled (and hold on to the lock when extracting text). Or, you could modify the Entry Change starting rule in WF and specifically exclude Page Created/Written events.

0 0
replied on November 30, 2015

Thank you for the info and explanation!

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

Sign in to reply to this post.

Details
Related Posts
Loading ...