Release Notes for PlanetPress Suite Version 7.6.2

The following is a list of last minute issues, features and documentation notes. Last updated March 2026.

Quick links:

Ā System Requirements

Changes

Ā Additional documentation

Known Issues

Ā

Important notices

The PlanetPress Capture ICR feature requires online registration before first use. If you have an internet connection availableĀ when you first configure the Capture Field Processor task, the registration process is performed automatically and silently. If no connection is available or if the automated registration process fails for any reason, you will receive an error message stating the cause of the error and you must then proceed with manual registration before the feature can work. To do so, please contact Objectif Lune Support as soon as possible.
The Planet Press ICR feature relies on .NET 3.5, which is not available on Windows 2000. While this OS is listed as being supported for the rest of the Suite, the ICR feature cannot work on that platform.
When installing the Suite on x64Ā systems, note that there is a specific procedure to follow in order to make the x32 version of the PlanetPress Printer driver available to other computers from the server. The procedure is explained in theĀ Adding the 32-bit printer drivers to Windows Server 2008 64-bitĀ section of this online FAQ:Ā http://help.objectiflune.com/en/knowledgebase/KB/FAQ/PPS/KB1503.html

System RequirementsĀ (back to top)

Minimum Configuration

Pentium 4 Class CPU
1 GB RAM
5 GB Free Hard Drive storage space
1024x768 16bit Color Graphics Adaptor
Windows 2000 SP4

Recommended Configuration

Dual/Quad Core Pentium Class CPU
8 GB RAM
20 GB Free Hard Drive storage space. Note that larger data files will generate larger spool and temporary files which the hard drive must be able to accomodate. When such large files are processed on a regular basis, the hard drive may be required to have several hundreds of MB's of free space.
1600x1200 32bit Color Graphics Adaptor
Dual Monitors
Windows 7 / Server 2008

Supported Operating Systems

Windows 2000 SP4 (Except for PlanetPress Capture ICR feature)
Windows XP / Server 2003
Windows Vista / Server 2008
Windows 7 / Server 2008 R2
Windows 8.1 / Server 2012 R2 (* See notes below)
Windows 10 / Server 2016 / Server 2019 / Server 2025 (** See notes below)
Windows 11 / Server 2022 / Server 2025 (** See notes below)

Note 1:Ā For the above Operating Systems, make sure to read the installation section of the Known Issues for below.Ā
Note 2:Ā When applicable, both the 32-bit and 64-bit versions of the above environments are supported.

Note 3: * While Windows 8.1 and Windows 2012 R2 are supported, Windows 8 and Windows Server 2012 areĀ not.

Note 4: * Capturing print jobs may not work properly if the job was printed through a Metro-style application. This is due to the changes in the printing architecture starting with Windows 8 / Windows Server 2012. These jobs files are stored in the spooler in XPS format. A future improvement will include an XPS to PDF conversion to allow these jobs to be captured and processed as well.

Note 5: ** Anoto Pen Director 2.8 is not supported on any version of from Windows 10 and Windows Server 2012 onwards

Supported Virtual Environments

VMWare, including VMotion, VSphere, VMView.
Hyper-V.

Dxcpl.exe Download Windows - 10 |link|

By following this guide, you should be able to resolve any issues related to DXCPL.exe and enjoy a smooth gaming and computing experience on your Windows 10 system.

: Emulating a powerful GPU with a CPU (via Force WARP) requires an immense amount of processing power. While the game will launch, your frame rates (FPS) will likely be incredibly low, often dropping into single digits.

If you require the standalone executable or are working with legacy software, you can download the full SDK from Microsoft.

Many third-party websites offer standalone dxcpl.exe downloads. Downloading individual .exe files from untrusted sources risks exposing your PC to malware or viruses. dxcpl.exe download windows 10

Ultimately, if you find yourself relying on dxcpl.exe for newer mainstream games, it is a strong indicator that your graphics card is due for a physical hardware upgrade.

Security Note: Always scan any downloaded .exe file with Windows Defender or Malwarebytes before running it. How to Install and Use DXCPL on Windows 10

Leo hit Enter. The results loaded instantly, a cascade of blue links and green URLs. He scanned past the obvious tech forums and the misleading "Download Now" buttons that were actually ads for registry cleaners. He was looking for something specific, something that the modern Windows 10 operating system had tried to bury. By following this guide, you should be able

This is normal behavior. DXCPL is a compatibility tool to help apps run, not a performance enhancer. To improve FPS, lower your game's resolution to 720p and turn all graphical settings to "Low." Conclusion: Is DXCPL a Permanent Fix?

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Canā€™t copy the link right now. Try again later.

If you encounter issues after setting up DXCPL, try these steps: If you require the standalone executable or are

Once installed, Windows will automatically place dxcpl.exe into your system folders ( C:\Windows\System32 and C:\Windows\SysWOW64 ). Method 2: Finding it via Visual Studio or DirectX SDK

Many users use DXCpl to bypass errors like "DirectX 11 feature level 10.0 is required". This is done using (Windows Advanced Rasterization Platform), which uses the CPU to emulate GPU features.

Lower the in-game resolution to 720p or 800x600 and turn all graphics configurations to "Low". "dxcpl is missing" Corrupt installation

DXCPL.exe stands for . It is an official developer tool created by Microsoft.

To avoid third-party risks, here is your approved download path:

ChangesĀ inĀ Ā (back to top)

V7.6.2

24318: AnotoĀ PenDirector 2.8 now distributed with PlanetPressĀ Suite (READ KNOWN ISSUES section below)
SH-37698: Both Anoto Pens DP201 and Live Pen 2 now supported with PenDirector 2.8
24315: Slow processing of Capture operations as database grows has now been fixed.

V7.6.1

23697: Intelligent Mail package barcode (IMPB) now meets the USPS specifications. While the existing barcodes did scan properly, they couldĀ fail to pass the USPS validation procedures because of visual discrepancies that have been addressed in this release. An option, which is turned on by default,Ā is now available to force the human-readable font size to meet USPS specs. Turning it off allows the document designer to use a font of any size.
23659: The timeout issue that could occur when upgrading the PlanetPress Capture database from 7.5.x to 7.6.x has been fixed. The issue would only occur when a large number of orphan PDF files were left stranded in the database.

V7.6

Notable new features and improvements

22198:Ā Support for Windows 8.1/Windows Server 2012 R2. All parts of the Suite have been tested successfully under these OS’es. The only known restriction is that some print jobs cannot be captured correctly from the spooler. This is due to Microsoft’s new print architecture and generally only affects jobs printed from Metro-style applications.
22363:Ā OMR object can use HCF’s. Hardware Configuration Files (HCF) provided by device manufacturers can now be used to create OMR’s. A download feature can search for new HCF’s online as they become available.
22701:Ā Processing files larger than 2GB. Support for files larger than 2GB has now been extended to almost all functionalities of the Suite.
23013:Ā New IMPB barcode. The Intelligent Mail Package Barcode from the USPS is now available in the list of barcodes.
22995:Ā New MailMark barcode. The MailMark barcode from UK’s Royal Mail is now available in the list of barcodes.
22949:Ā New KIX barcode. The KIX barcode from Dutch Royal Mail is now available in the list of barcodes.
22411:Ā PDF/VT creation. PlanetPress Imaging and the Digital Imaging plugin now support the creation of PDF/VT files.
22537:Ā Improved PlanetPress Capture Object.Ā The Capture object now supports custom field values for processing by third party application. In addition, standard and custom lookup tables can be specified for ICR. Enhanced logic allocates patterns based on a least-recently-used value to eliminate issues related to early re-use of patterns.
22671:Ā Opacity/Transparency for PDF files. All objects in PlanetPress Design templates now support custom opacity/transparency values, allowing the background to show through the object. This feature only applies to the creation of PDF output, and only for PDF 1.4 or more recent.
22399:Ā Thumbnails for document templates. PlanetPress Workflow tasks that display a list of available templates now also display a thumbnail image of each template for easier visual selection.
23376:Ā Selectable Spool File Job Name. The Job Name for spool files can be set through the %%Title attribute to allow third-party RIP software to display the proper information on their console.
23319:Ā Improved Font Encoding Dialog. The Custom Font Encoding dialog has been enhanced to filter out duplicate or null entries. It now lists all available glyphs in Unicode order and also implements a search function based on the glyph name.

Notable fixesĀ

22778:Ā PlanetPress Capture Deadlocks. Issues with deadlocks when processing PGC’s concurrently in high volume environments has been resolved
22547, 23190:Ā PlanetPress Capture memory usage and DB size. PlanetPress Capture tasks now efficiently manage and reclaim the memory they use. In addition, the issue with the PlanetPress Database sometimes not reclaiming space for deleted records has been fixed.
20402,21948,22132,22746,23011,23110:Ā SOAP. Numerous improvements and fixes to SOAP services and tasks. Most have to do with WSDL processing and communication timeouts.
21566:Ā Thai glyphs issue fixed. Display and processing of Thai glyphs with superimposed diacritic marks has been greatly improved.
22194:Ā Metadata and PDF Creation performance issues. The loss of performance experienced in some environment after version 7.2.2 has now been fixed. Performance is now back on par – or better – than it was in v7.2.2.
23003:Ā Faxing landscape pages. The issue with faxed landscape pages being cropped and displaying a black bar has been fixed.
22800:Ā Out of Resources issues while creating PDF files. A number of related issues which translated to PDF creation tasks running out of resources at some point have been fixed. In particular, the inclusion of the latest Adobe libraries helped resolved several issues.
22144:Ā PDF merging issues. In some instances, merging PDF’s would result in Access Violation errors although the same PDF’s could be merged with previous versions. This has now been fixed.
22763:Ā CSV output from PlanetPress Database task. The CSV output option would produce inconsistent results when the first field in each record had an empty value. This has now been fixed.
13756:Ā Guidelines in Landscape mode. In PlanetPress Design, guidelines on landscape pages are now displayed properly.

V7.5.3

22217: Business Graphs no longer generate double "+" signs that prevented some of them to be generated properly
22430: PlanetPress Capture ICR support for Dutch language
22456: External scripts shown in the PlanetPress Workflow Scripting task now remain read-only
22469: PlanetPress Fax now correctly handles rotated and landscape pages
22515: Stamping a PDF file twice with the PDF API no longer causes issues with the resulting PDF file
22522: Occasional multi-threading issues with the Output Printer tasks have been resolved
22542: Increased accuracy of barcode Scan task and fixed the temporary files cleanup process
22547: Fixed several memory issues with the Capture library that causedĀ PPWatchService/PPMessenger to consume inordinate amounts of RAM
22562: Fixed occasional installation hang when registering ActionCaptureFieldProcessor.dll

V7.5.2

22328: PlanetPress Capture ICR now includes Portuguese and Spanish recognition (see known Issues)
22309: Workflow Services now automatically restart correctly after a reboot
22156: SOAP client no longer generates duplicate GET/POST requests
21857: SOAP client running in self-replicating processes no longer clears input variables
22170: Barcode Scan task no longer generates invalid metadata when none exists before
22098: Resetting the PressTalk ID of a Style in PlanetPress Document Templates no longer raises an error message
22277: PlanetPress Capture ICR no longer fails when custom AM/PM strings are specified in Windows Regional Options
22124: Number of pages displayed in Windows Spooler is now correct when printing PDF files
21963: PDF Splitter no longer fails when metadata contains empty DataPage nodes
21513: PDF Job Options are now correctly handled when generating PDF/A and PDF/X
22224: SharePoint input/output connectors can now connect to SharePoint 2013
22099: POP3 emails now store the entire message header in JobInfo[6]
22150, 22097, 22259, 22096, 22220: Various translation and documentation fixes

V7.5.1

20726, 21395: Random failures when creating PDF files in Asian markets have been fixed. Specifically, Fonts and "xshow" errors do not occur anymore.
21994: The Capture Field Processor task now adds field coordinates in inches to the metadata, rather than in points
21855: Spool file size drastically reduced when printing using a Windows driver
21945, 21975: Much improved clean up of temporary files and folders created by PlanetPress Capture and PlanetPress Fax
21970: Drastic reduction in PlanetPress Workflow RAM usage
22013, 22016: PlanetPress Capture Document Manager and Get Capture Document task no longer raise errors when retrieving annotated PDF files.
22008: When performing ICR on multi-area PlanetPress Capture fields, spaces "inside" the string are no longer stripped from the results.
21979: Capture Condition can now check the number of patterns available for any specific pattern sequence
22071: Hyper-V virtual environment is now officially supported.
22029, 22073: Launching the PressTalk Editor for the PressTalkBefore/After section of the document properties no longer causes an error. In addition, accessing online Help for the Global Function editor no longer displays an error message.
22010: Create PDF once again properly updates the metadata for the newly created PDF

V7.5

18247: Metadata fields can now be prevented from being overwritten by other fields with the same name
20025: The File Size condition can now evaluate file sizes larger than 2GB
20054: The SharePoint Output task now supports Content Types.
20419: PB-First projects are no longer run multiple times when user rights were mismatched
20467: PlanetPress Search can be instructed to open PDF files using the system's default PDF viewer
20468: New PlanetPress Workflow option: Open Current Configuration.
20539: PlanetPress Workflow now publishes a new %v system variable containing the current time's milliseconds
20556: Digital Action now allows multi-page Tiffs and VDX files to become the current data file on task completion
20800: The ErrorBin process now receives new %{error.xxxx} variables for better error handling
20883: XML Splitter now correctly refreshes the XSLT code
21061: Crop/Cut marks added to large paper formats now behave as expected
21340: PlanetPress Workflow logs now include Elapsed Time values for processes and tasks
21341: HTTP Response Code and contents can now be set dynamically
21357: Clipped regions on images with dynamic dimensions now behave as expected
21383: HTTP Client task now supports SSL 3 and TLS 1
21426: Metadata generated by the Capture Fied Generator now contains the Document's ID
21449: Task PGC To PDF can now also be used as a condition
21474: Rulers in PlanetPress Design are now refreshed correctly after minimizing/maximizing the window
21475: Find Capture Document task can now retrieve closed documents
21476: Find Capture Document task can now search for documents older than a dynamic number of days/weeks
21496: POP3 Emails with very large custom headers are now captured properly
21503: PlanetPress Search can now open and merge password-protected PDF files
21533: A corrupt PlanetPress Capture custom Field list no longer causes List Index out of bounds error
21534: PlanetPress Design now accepts print page ranges over 100 000.
21541: LPR Service now cleans up sent files or moves them to the Error folder correctly
21546: Loop task now resets the metadata properly on each iteration and creates a single backup data file.
21555: Performance of Capture Field Generation task has been greatly improved
21568: The refresh WSDL option in the SOAP Client task now behaves as expected
21581: PlanetPress Search criteria are now displayed in a collapsible window pane
21647: Comments can be added to any task PlanetPress Workflow for better documentation of processes
21690: Printing from Vista and up to a Windows printer shared on another computer now works as expected
21724: The PDF Splitter can now split the PDF according to the Metadata
21750: PlanetPress Capture ICR feature now available
21834: Capture Field Processor task can now add Advanced Field Information to the metadata, including time stamps
21930: Files created in Windows Temp are now cleaned up properly

V7.4

Numerous enhancements to PlanetPress Capture. See documentation.
17677: Open XSLT task accepts variables
17731: PlanetPress Workflow includes a Document Preview option
20400: Major performance improvement in Metadata Creation task (over 250%)
20463: ODBC connexions on x64 systems no longer returns C1500 Error
20549: LPD Input task processes jobs in the order they were submitted
20592: PlanetPress Talk array definition now accepts variables as "length" parameter
20675: Issue with Metadata Sequencer sometimes skipping pages has been resolved
20701: Barcode Scan task inside a loop generates correct Metadata
21207: Plugged memory leak in some self-replicating processes
20179: Fixed rare issue where Create PDF would generate a 4GB invalid PDF
17721: "Run from here" option available in PlanetPress Workflow
20096: SharePoint tasks now accept Secondary Site Collection Administrators
20406: HTTP Server Input's Job Infos are now set properly
20493: Secondary inputs in self-replicating processes no longer run only once
20917/20915: HTTP Server now sets MIME-Type and Response File Name properly
20916: Processes with time intervals of 0 seconds no longer use up 100% CPU
19914: Page numbers in PDFs generated from Optimized PS are now set properly
20405: Folder Capture task is again able to process files with no extension

V7.3.1

20437: Overlapping PlanetPress Capture Fields no longer cause some Ink Contents to be missing
20428: Accented characters in Address Objects are rendered correctly
20425: Metadta Level Creation task now takes into account the Selected status Metadata Nodes
20422: Multiple processes running simultaneously and using monochrome bitmap images now behave as intended
20418: LaserFiche output task processes PDF/A and PDI indexes as intended

V7.3

Improvements
18230: Metadata overhaul: similar performance, twice the power, three times less memory requirements
17736: Sample Data, Metadata and Document Thumbnails now available in PlanetPress Workflow
17710: Contents of PlanetPress Capture pages and fields can exported to PS / EPS
20239: Ability to add PlanetPress Imaging Indexes to Metadata; New Metadata to PDI task
17749: Refresh metadata option now automatically checked when Group/Document markers are used
17751: PlanetPress Capture information now implements secure communication protocol
17735: CEPNet barcode support (Brazil)
17733: HTTP input task can process attachments directly (no need for Load External File task)
18228: PlanetPress Capture Fields can be assigned mask for future ICR support
17628: Brazilian Portuguese support in all applications
17714: PlanetPress Capture API includes new information: timestamps, pen information, distinction of inks, etc.
17694: Inks for each PlanetPress Capture field can be turned on/off, rendered in different color or strokewidth
20100: New PlanetPress Workflow task to import/export metadata
20234: Dramactic quality improvement when rendering PlanetPress Capture Inks
17623: Extended character support for QR code object
17726: Digital action plugin can now update PPSearch's database
18227: PlanetPress Search is now a stand-alone application; Adobe Acrobat/Reader no longer required
17676: PlanetPress Search command line options to silently refresh/rebuild database
20270: HTTP Input task can set MIME type dynamically
18250: PlanetPress Messenger can now communicate across subnets
20127: PlanetPress Capture API includes new methods to allow simple scripting of complex Capture conditions
20083: New "Enhance PDF with PlanetPress" option available from Windows Explorer context menu
Fixes:
12999: HTTP Server in self-replicating processes now sends response back after second execution
13008: Printer-centric DataMatrix barcode no longer generates dictstack overflow
13037: PlanetPress indexes containing "=" character no longer cause issues in PDF/A format
13040: Finishing options are preserved after running the Capture Field generator task
13043: "Add cut marks" option on pages with conditions no longer displays an error
13654: ODBC in Windows 7 64 bits: the issue with "Edit SQL" option is fixed
13671: After losing connection to LaserFiche Server, no Exception Error message occurs
12949: "Error evaluating resource type" no longer occurs when producing Optimized PostScript job
13668: Memory is now correctly released after running multiple processes extracting information from PDF files
12947: Dramatic time improvement when using Create Metadata for documents with Datamatrix barcodes
12986: Items can now be deleted from Virtual Drive in Win 7 x64
12997: Static repeat option with Address object now works as intended
13010: Combining PDF Splitter + Capture Fields Generator now works as intended
13009: Plug-in "Send Email" works as intended with Outlook 2010 in service mode
13004: SharePoint Site/Document Library names now support accented characters
13019: Dashes in text box no longer remove the following blank space
13022: Documents with arabic font printed in Optimized PostScript now work as intended beyond the first page
13034: Simultaneous access to SharePoint from Ouput plugins now works as intended
13035: Running subprocesses in step by step mode now works as intended
13047: PPSearch now sorts PDF file names as intended
13048: Barcode size in Design Mode is now consistent with its printed results
13056: PDF Security settings in PlanetPress Image now work as intended
13070: Text object: issues with local variables and repeat options have been corrected
13079: Folder Input task no longer "skips" over some files under heavy loads
13664: Zapf Dingbats font in Input PDFs is now carried over properly to output file
13017: PlanetPress Capture no longer fails with 'Document was inked outside of known fields.' for valid inks that contain a single point
20085: Embedding OL Metadata into a PDF already containing embedded OL Metadata generates error 3001
12936: Batch files can now be run as External Programs in 64 bits OS:

V7.2.4

12816: Installing Service Pack 1 for Windows 7 or Windows Server 2008 R2 no longer deactivates the application

V7.2.3

12368: SOAP Client now handles some complex data types
12580: Input Tray attribute from captured spooled file is reflected consistently in the Metadata
12577: Metadata Sequencer processes one-record sequences properly
12545: PDF Text Extraction tolerance parameters can be changed in Registry (contact Support for more info)
12457: Original name of Chinese email attachments is saved properly on Chinese systems
11755: User-defined functions can be used as expressions whtin the Condition Definition window
12255, 12268, 12331, 12449: various GUI enhancements to PlanetPress Capture modules

V7.2.2

12298: New language added to GUI: Simplified Chinese
12443: Datamatrix barcodes encode all values properly
12470, 12478: The merging of non-linearized PDFs and the merging of blank PDF pages works as expected
12438: The Create PDF task can now process PS files in passthrough mode
12432: The Page Archiving option is again available
12338: Siginificant performance improvements in PlanetPress Capture Field Generator task

V7.2.1

12387: Updating from 7.2.0 to 7.2.1 on Win7 x64 now completes correctly
12379: Custom-made plugins are preserved upon upgrading

V7.2

11961: Characters using EUDC fonts are properly displayed when job is produced by service in Windows Vista or higher
11095: ODBC drivers are used properly with Windows 7
11680: Fixed issue when moving the PlanetPress Image application from one ESX server to the other
11844: Fixed issue with using PrintShop Mail connector in PlanetPress Workflow with Windows 7
11273: Fixed issue where PlanetPress Workflow concurrent processes could hang while working with documents using region/regionline command
11579: Fixed "Error while executing plugin: I/O error 103" in Digital Imaging task
11797: PDF API can now be called properly from JScript
11758: Fixed font issue where some glyphs would not print properly if the font did not explicitly support 1252 Latin 1 encoding
12004: PlanetPress Image now correctly adds Document Index information to XMP portion of the PDF/A archives it generates
11122,11799: The Output to Printer Queue task and the PB-First Connector now take into account the current metadata selections (unselected items are not processed)
12095: The Word To PDF task properly handles SQL statements longer than 255 characters
12264: The Create MRDX task no longer inserts redundant User Data fields in the metadata
1564: PlanetPress Fax, PlanetPress Image, along with the LPR, LPD and FTP services all produce standardized logs
10752: The PlanetPress Database task now sets the outgoing emulation properly

V7.1.3

10979: All files are now properly installed when updating from a previous version to this one.

V7.1.2

10811: Support for VMWare VMotion. PlanetPress Suite applications running under any supported Virtual Environment now display additional information in their title bar. Other than that, the behavior of all the Suite applications remains the same as when they run on a physical PC.
10803: Fixed issue with Optimized PostScript documents being ripped on newer Creo Servers. (VPS caching is still not supported for printer-centric documents, however).
10780,10781: Fixed issue with Suretrac connector when using the JobID parameter. In addition, unselected nodes in the metadata are now correctly ignored while creating the MRDX file.
10746,10794: Fixed issue where PDF pages with a CropBox setting would sometimes appear shifted on the output document. In addition, the Autorotate setting is now OFF in the Create PDF action task, so its behavior is now the same as that of the Design Tool's preview mode.
10605: Chinese characters outside of the standard Big5 encoding but belonging to the extended HKSCS table are now correctly displayed. In addition, CJK printer fonts referenced in documents that are being RIPped to PDF are now substituted with the MingLiu font rather than Courier.
10814: Fixed issue with the SOAP client task that prevented it from successfully connecting to a WSDL containing unreachable imports.

V7.1.1

10566: The Concatenate PDF Folder task now generates metadata automatically
10603: Address objects extending from bottom to top now behave properly
10575: The issue with dynamic Windows Printer Queue Names has been corrected
10581: The Metadata Sequencer now accepts dynamic values and new settings allow for creating a specific number of sequences
10543: Non letter-sized PDF files displayed on more than one page are now positioned properly
10612: VDX files can now be processed by NexStation Versions 9, 10, and 11
10576: Both the Create PDF task and the Windows Printer Capture task now have the option of generating optimized/unoptimized PDF files. As a rule of thumb, PDFs should be created unoptimized because processing them is much faster. The PDFs should be optimized only once the processing is complete and the final PDF is ready to be output.
10572: Floating-point errors while extracting text from some PDF files has been fixed.

Additional documentationĀ (back to top)

PlanetPress Design Tool

When calling a condition before it has been created (for instance, on the Document itself), the Design tool may not show the proper value for that condition. Make sure you press F5 to refresh the layout prior to previewing the results.
To improve your Document Design experience, use the smallest possible sample data file, regardless of the type of data you're using. The Version 7 feature that allows several Sample Data Files to be used with a single document was designed specifically to help the document designer test out the business logic with representative pages of data, rather than having to navigate through hundreds of data pages in order to replicate a specific condition found on one of the pages. For instance, if one of the conditions you implemented becomes TRUE on page 500 of your sample data file, you'd be better off creating a subset of that sample data file and including that subset as an additional sample data file, so you can test specifically with it when proofing the document design.Ā Ā

Metadata

TheĀ IndexĀ property for each level that supports it is 1-based in PlanetPress Talk while it is 0-based in all other languages. This is by design: Document designers who want to display the value of the Index property simply need to drag & drop theĀ IndexĀ value from the MetaData to the page area. This allows easy implementation of functionalities likeĀ PageĀ IndexĀ ofĀ Count. Other languages remain 0-based because it is expected practice in most of them.

Known IssuesĀ (back to top)

Installation

Under Windows 2000, when updating VCREdist 2005 to VCRedist 2005 SP1, the system requires an extra reboot to be performed manually after the installation of PPSuite 7.
The Installer may unexpectedly shut down while attempting to install prerequisite libraries. This only occurs if the Windows Update tool is awaiting confirmation from the end-user to install a batch of updates. To prevent the issue from occurring, make sure you complete the Windows Updates prior to installing PlanetPress Suite.
Upgrading versions of PlanetPress Suite older than V7.1 on Windows 7 or later will require a new activation code since those Operating Systems were not supported in these older versions.
19550: After installing a new font, rebooting the system may be necessary before PlanetPress Workflow can use it. This is due to how the Windows operating system works: it notifies visible applications of such changes but since services are not visible, they never receive the notification. Rebooting the system allows them to rebuild their list of available fonts.

Internal RIP

Documents containing arrays with more than 65000 elements (roughly) may fail to rip in printer-centric mode. Attempting to print such a document on different printing devices may result in the job sometimes failing, sometimes not. This is rip-dependent. To circumvent the issue, use Optimized PostScript mode.

PlanetPress Design Tool

24956: When sending a form from Design to the local Workflow on a computer with 14 processor cores, the operation fails without an error message. The operation completes succesfully if there are fewer or more cores.
23551: When using Acrobat Distiller as the system's default PostScript interpretor to preview a document, images stored on the virtual drive are not displayed on pages yet no error is reported. This is due to restrictions imposed by Distiller on accessing local resources. To circumvent the issue, use the Internal interpretor instead (which uses the same libraries anyway).
Channel Skip emulation may not behave properly if the document uses Metadata and the first character in the data file is a channel skip code. One possible workaround is to modify the emulation settings so that it adds a single line at the beginning of the data file.
The Binding options of the Document Properties are ignored when printing the document to a Windows Printer Driver. You must specify the appropriate Binding Options in the Driver's configuration instead.
No part of a PlanetPress Capture field can be positioned beyond the left or top edges of the physical page, as negative values are not supported for Anoto patterns. However, the fields are allowed to extend beyond the right and bottom edges.
When using the preview feature on documents that include PlanetPress Capture Fields, setting the option to refresh the metadata may prevent any captured Ink from being displayed in the resulting preview. Therefore, if you have printed and signed your document and want to preview the result with its ink, do not set the option to refresh the metadata.
When using a PlanetPress object to call other pages in a loop, the called pages must not contain any Capture Fields. However, Capture Fields can be present on the calling page.
OnChangeĀ conditions do not behave properly on virtual pages used with the nUp object. Use advanced conditions instead.
While designing a document template, the Metadata may sometimes display unexpected results when additional fields have been added to the Metadata. In particular, when importing a pre-existing Metadata file that reorders the data records, or that removes/adds data records. Perform a Preview of the document to double-check your document design.
When attempting to display some PDF files, PlanetPress Design may report an error similar toĀ Error Code 109: The pipe has been ended. If you encounter this error, go to PlanetPress Design Preferences, select theĀ Behaviour > Image resourcesĀ section and make sure the option toĀ Display PDF and EPS in colorĀ is enabled.
When a clipping region is defined in a Picture object, resizing that object on the page may move it slightly on the page. Make sure you adjust its location back to where it is supposed to be. In addition, when the clipping region is inverted, the object's bounding box may be altered. Use the object inspector to adjust it back to adequate values.
Page-based conditions set through the Conditions dialog box may behave erratically when the document uses Metadata that reorders or unselects some data records. To work around this issue, use advanced conditions instead.
In right-to-left mode, text selection beyond paragraph limits may cause unexpected behavior. Just make sure you do not select text beyond the end of a paragraph.
In right-to-left mode, variables may be displayed beyond the width delimitor in the text editor. This is a display issue that only occurs at design time.
Arabic variable data is reversed inside the text object when data encoding is IBM864 (pre-reversed encoding). Use a Data Selection object or a PlanetPress Talk object instead. Alternatively, convert the data stream to a different encoding.

PlanetPress Workflow Tool

24956: When sending a form from Design to the local Workflow on a computer with 14 processor cores, the operation fails without an error message. The operation completes succesfully if there are fewer or more cores.
Anoto Pen Director 2.8 is not supported on Windows Server 2012 and Windows 10.
22356: 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.
21962: 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)
21405: 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.
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.
21465: The SharePoint Output task does not validate the field contents. That's Sharepoint's responsibility.
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).
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 (when using PP-Production or PP-Office).
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 of the Suite, the PlanetPress Workflow Configuration tool may display an error message the first time you launch it if you had already sent a PlanetPress 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.
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.
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 config was set up and the moment it was loaded. This is unlikely to occur, but it could, for instance, happen when importing a Version 6 configuration file into Version 7. 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 services use the same logon credentials.
13559: 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
4. Follow the instructions to complete the installation
5. Re-start PlanetPress Production and test your process.
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 PlanetPress Production 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 PlanetPress Production service. To avoid these types of issues from occurring, it is imperative that the configuration for the WordToPDF task be tested thoroughly in Debug mode prior to sending it into production. In particular, the connection to the database must be validated.
The WordToPDF task requires the default system printer to be set to a queue that uses the PlanetPress printer driver. If you change the default system printer or if you import a PlanetPress Workflow configuration file from another PC that includes an instance of the WordToPDF task, you must review the properties of each instance of the task and click OK to validate its contents. A new printer queue will be created if required and the default printer will be reset properly. If you do not perform these steps, running the configuration will result in several error messages being logged and the task failing.
The preferences for the PrintShop Mail Web connector may not be saved properly if you set them and close the PlanetPress Workflow Configuration tool without first sending the configuration to the service. Make sure you send the configuration before exiting from the Configuration tool.
13009: With Outlook 2010, the Send Email functionality requires that the service be run with administrative credentials in the domain. In addition, both Outlook and the PlanetPress Workflow Configuration tool must *not* be running while the service is.

PlanetPress Imaging

MS Outlook 2007, when configured to use POP3 may block PlanetPress Imaging and PlanetPress Workflow from sending emails. The reverse may also occur. If you encounter such an issue, you must shut down one of the applications to run the other.
When running PlanetPress Imaging on Windows 7 x64, you may get watermarks on your output even though the software is activated. To correct the problem, run PlanetPress Imaging with an Administrator user account when activating it.

Other

The Microsoft Office 2010/2013 line of products has not been certified for use with PlanetPress Suite. Some of its products may not be compatible with the connectors included in the Suite.
Barcodes produced in printer-centric mode may have a slightly different aspect from those produced in Optimized PostScript mode. This is due to the different types of 3rd party libraries being used to generate the barcodes. However, all barcodes scan correctly.