2021.1

PlanetPress Messenger service from the Workflow console for this one time only. To
avoid getting the error altogether, make sure you launch the PReS Workflow tool once
before sending any document to it.
l
In the LaserFiche connector, when selecting a different template after filling up the fields
and then going back to the first template, the values entered in the fields are lost. They
have to be entered again.
l When loading a Workflow configuration that includes references to Windows printers, the
output task may fail to recognize the printer if the printer driver has changed between the
moment the configuration was set up and the moment it was loaded. This is unlikely to
occur, but it could, for instance, happen when importing a Version 7 configuration file into
Version 8. To circumvent the issue, open the output task's properties, make sure you
reselect the proper printer, close the task and send the configuration again.
l
The HTTP/SOAP service may fail when both it and the Workflow service are logged on
using 2 non-local users or 2 local users with different privileges. To resolve the issue,
make sure both services use the same logon credentials.
l
The WordToPDF task, when run under the LocalSystem account, may seem to hang if
the installation of MS-Word wasn't properly completed for the LocalSystem account. If the
task seems to take longer than it does when run in Debug mode, this may be the case.
You can confirm this behavior by opening up the Windows Task Manager and checking
whether the MSIExec application is running. In order to complete the installation of MS-
Word for the LocalSystem account, follow these steps:
1. Open a command-line window (CMD.exe)
2. Type "AT 10:56 /INTERACTIVE CMD.EXE" (replace 10:56 with the next upcoming
minute on your system)
3. At the specified time, a new command-line window opens. In it, navigate to Word
Installation folder, then type Winword Follow the instructions to complete the
installation
4.
Re-start PReS Workflow and test your process.
l
The WordToPDF task relies on MS-Word to perform its functions. However, MS-Word
sometimes displays confirmation dialogs when it encounters a situation requiring user
input. Such dialog windows cannot be displayed when PReS Workflow runs as a service.
As a result, the process may seem to hang because it is awaiting user input on a window
that isn't displayed. The only way to resolve this situation is to kill the PReS Workflow
service. To avoid these types of issues from occurring, it is imperative that the
Page 29