2019.2

documented issue in those two Operating Systems. Microsoft has provided no reason nor
workaround for the problem, therefore PReS Workflow cannot circumvent the issue.
l Under Windows 2000, the SharePoint output task does not work with SharePoint 2010.
Under the same OS, the PlanetPress Capture ICR does not work due to the .NET 3.5
requirement.
l
21465: The SharePoint Output task does not validate the field contents. That's
Sharepoint's responsibility.
l
20143: The Metadata to PDI task encodes the XML using the default system encoding,
not the document's. In addition, it does not discriminate between index names written in
different cases (e.g. Name vs. name).
l Printing PDF files in passthrough mode using a Windows Printer Driver task causes jobs
to be processed sequentially rather than in parallel. This is caused by a 3rd party library
used in the printing process. Possible workarounds are to use a PlanetPress document to
call the PDF files as dynamic images, or to use the PDF file as the Data File for a
PlanetPress Document.
l
JobInfo #4 in the Windows Input Queue task (the original document name set by the
printing application) replaces any non-alphanumeric character with underscores in order
to filter out any invalid characters. Consequently, if the path contains slashes or colons,
those will be replaced with underscores.
l
When the PlanetPress Capture database is set to MS Access, it is considered good
practice to have a single process generate Patterns for documents because the Access
engine may lock the other process out of the database as the first process updates it.
l
After the initial installation, the PReS Workflow Configuration tool may display an error
message the first time you launch it if you had already sent a PReS Workflow Document
to it. You can safely ignore this message, you will simply have to manually start the
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
13554: 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
Page 27