After releasing a Customer Order, a confirmation report is automatically generated as a PDF in the background (routed to a No-Printout logical printer and archived as 'Printed'), which makes the Report Archive show every released order as already printed even though the client actually wants to print each one manually later — assigning the report to a new, unmapped logical printer just produces a stream of error-status rows in the print job table instead.

All FAQ questions / Reporting and analytics

Answer

Route the report to the built-in 'IFS PDF Archiver' logical printer instead of creating a new, unmapped one — from the Printer Definitions window, assign the report to that printer. Anything sent to the IFS PDF Archiver lands cleanly in the Report Archive without generating a PDF automatically or leaving behind error-status print job rows, and from there it can be printed manually whenever needed, giving you the 'available in archive, not auto-printed' behavior without the side effect of accumulating failed print job records.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions