2022.1

l Using the PT-PT setting to perform ICR on AlphaNumeric fields may not work properly. If
you encounter the issue, use the PT-BR setting instead, or use another PlanetPess Field
in your document design.
l Barcode scanner task may have issues reading 2-D barcodes printed/scanned with low
resolution. Make sure the scans and the original printed output are at least 300DPI (600
or better recommended).
l When printing through a Windows printer driver on Windows Server 2008 or Windows
Server 2008 R2, the Job Owner setting is ignored. This is caused by a documented issue
in those two Operating Systems. Microsoft has provided no reason nor workaround for the
problem, therefore PlanetPress 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
The SharePoint Output task does not validate the field contents. That's Sharepoint's
responsibility.
l
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 PlanetPress Workflow Configuration tool may display an
error message the first time you launch it if you had already sent a PlanetPress 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 PlanetPress Workflow
tool once before sending any document to it.
Page 28