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

Question

Question

How do I specify (or Add Reference to) a specific dll in the Workflow directory path instead of the dll in the Windows GAC?

asked on May 31, 2024

I'm running Workflow Admin Console 11 and Workflow Designer 11 on my Workflow server.

I have a workflow that calls a script that merges multiple PDF files into one PDF file. Recently, the script seemingly hangs (runs for days, instead of seconds/minutes) on some PDF files. In testing, if we take one of the problem PDF files, save it as DOCX, then save it back to PDF, the workflow completes as expected. This led me to think maybe we need a newer of itextsharp.dll (or itext8.dll which supposedly replaces it). I uploaded version 5 of itextsharp.dll and replaced the older version (4) with it in the Workflow folder path. When I look at the references in the Script Editor, it appears that it's still referencing the older version in the Windows GAC:


I tried to add reference to the newer dll that I uploaded to the Workflow path c:\Program Files\Laserfiche\Workflow, but nothing in listed on the server (LFLOW):

I read in other Answers articles that when the workflow runs, it only uses references in the Workflow directory path (is that true?), and you have to register or reference it in the Workflow Admin Console (but where?).

0 0

Replies

replied on May 31, 2024

References will not update automatically because dlls are often version-specific and can coexist to avoid breaking anything using the older numbered versions.

It's the same way older pre-existing workflow scripts will keep references to RepositoryAccess 10.x dlls while new scripts will start with RepositoryAccess 11.x references.

If you're not seeing anything in the folder browser, it sounds more like either a permission issue on the server, or workflow may be limited to specific directories in the admin console.

If folder browsing was blocked outright, you would get an error, and the fact that you can see the GAC means it is able to browse the server to at least some degree.

0 0
replied on May 31, 2024

Thank you @████████. I tried the following settings and still nothing listed in LFLOW. I also tried with just wild card (*) in Allowed Files.

0 0
replied on May 31, 2024 Show version history

Hi Mandi,

You shouldn't have to add allowed directories or extensions unless you only want to include those items; when the fields are blank it defaults to allowing all.

As a next step, I would check permissions on the server itself, and/or try opening the designer on the workflow server to see if you get the same results.

Now that you've confirmed it's not blocked from the workflow settings, it seems like something else is preventing you from seeing the drives.

File Browser Options Node (laserfiche.com)

0 0
replied on June 5, 2024

Maybe I'm going about this the wrong way. How can I get the newer version of iTextSharp to appear in the Loaded Assemblies in Workflow Admin Console?

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

Sign in to reply to this post.