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

Question

Question

Laserfiche 12 - Workflow - Advanced Connection Type in workflows with a DB Task

Workflow
Updated September 30
asked on September 22

Hey All

We upgraded to the Latest Version 12, 6 months ago, We have noticed significant time differences in  Workflows which have a Database connection using Advanced connection type... 

Has anyone else encountered this?

FYI - Changing Connection type to ODBC / Direct the speed is the same as Post Upgrade so LF 11 = LF 12 Times on anything other than Advanced.

Highlighted Row shows the time the WF Version was upgraded, Nothing else in our environment had changed


Startedby - WF Version - Completion Time

Support Case Opened, Just wondered if we were alone on this?
Anyone else experienced this??
 

0 0

Replies

replied on September 30

Identified as a Bug in WF, no indication of a time frame for a fix to be implimented. WF Bug-ID #617030

0 0
replied on September 30

Hi Anthony. Can you clarify on what they said the bug is exactly?

0 0
replied on September 30

Hey Blake,

 

Hope your well, Unfortunately they have only said they are also able to reproduce the issue, So nothing more than that, than logging the bug #.

However what is interesting is you can still use named Variables in your SQL Script, for say stored procedures in the advanced DB task, So after much head scratching and complaints from end users of slow systems, we were able to identify changing the connection type to Direct gained us over 3 - 4 seconds per WF which had a DB Connection type which used to be Advanced using .NET, so that is the current work around until the bug fix is implimented.

Luckily for us we used a global profile, for the connection type, so we only had to change it in Workflow Admin Console, which worked out quite a simple switch over.

 

Hope that helps

0 0
replied on September 30

The code was revised last year to address some security issues found during our internal scans. The query run time was not affected, just cleaning up the connection afterwards rook a hit and was taking about 2 extra seconds. 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...