2022.2

Table Of Contents

The Metadata to PDI task encodes the XML using the default system encoding, not the doc-

ument's. In addition, it does not discriminate between index names written in different cases (e.g.

Name vs. name).

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.

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.

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.

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 doc-

ument to it.

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.

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.

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 ser-

vices use the same logon credentials.

The WordToPDF task, when run under the LocalSystem account, may seem to hang if the install-

ation 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

Page 29