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

Question

Question

Bugs/Issues with Schedule Page Generation in WF 11

Workflow Version 11
Updated February 28
asked on March 4, 2022

I just started updating some of my workflow processes to take advantage of the new PDF Page Generation and DCC callback options and ran into a couple of issues.

1. The WF 11 Designer seems to install without some of the files used by the new process, so I get a validation error if I try to publish from anywhere other than directly on a WF Server

Could not load file or assembly 'Laserfiche.DistributedProcessing.Common, Version=11.0.0.0, Culture=neutral, PublicKeyToken=607dd73ee2bd1c00' or one of its dependencies. The system cannot find the file specified.

 

2. The callback functionality works, but it looks like the server and repository names have been swapped in the callback so it was generating a warning every time.

For example, if my server was server.local and my repository was MyRepo, the workflow instance started by the DCC call back would show server.local as the repository and MyRepo as the server.

This affected the starting entry because it thought the server was the name of the source repo and it would generate warnings about the conflict between that and the connection profile in the activities.

As a workaround, I added a find entry and change starting entry at the start of the workflow, then added a fake connection profile with the values swapped so it wouldn't generate any warnings.

1 0

Answer

SELECTED ANSWER
replied on March 4, 2022

These are both known issues. The first one is addressed in the upcoming update for Workflow 11. The second one is in DCC and unfortunately, we don't have a patch planned.

1 0
replied on May 4, 2023

Looks like the 1st issue was addressed in the Workflow 11 Update 1 release. Are there any plans to address the second issue or has it already been addressed?

0 0
replied on May 23, 2023

An update to DCC is planned for later this year. No release date has been set yet.

0 0

Replies

replied on February 27 • Show version history

Update as of 2/27/2025: This is still a problem - DCC mixes up the repo name and the server on the callback to workflow. Versions in use are Workflow 12 and DCC 11:

 

 

Throwing the same error Blake reported:

 

It still does the job we ask, but is very annoying.  Is this set for an update?

0 0
View 1 previous reply
replied on February 27 • Show version history

Hi Bill,

I haven't heard anything about an update yet, but I have a workaround to get rid of the warning messages.

I just added a fake connection profile to the workflow with the information reversed like it is in the response (username/password don't matter).

Then, I use Find Entry with the correct connection profile, and if I'm referencing the Starting Entry, I also refresh that from the Find Entry.

1 0
replied on February 27

The warning is correct though. You are trying to use an entry from one repository in a workflow that has a connection profile for another repository. So it can't assign field values or copy metadata.

0 0
replied on February 27 • Show version history

Hi Miruna,

The warning is only correct in the sense that the profiles don't match, but that is happening because the DCC sends invalid information for the starting entry.

The profile mentioned in the warning references a nonexistent repository because the server and repository names are reversed in the DCC callback.

0 0
replied on February 28

Very clever, Blake, thank you - 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...