.. /*
    * This file is part of the SavaPage project <https://www.savapage.org>.
    * Copyright (c) 2026 Datraverse B.V.
    * Author: Rijk Ravestein.
    *
    * SPDX-FileCopyrightText: (c) 2020 Datraverse B.V. <info@datraverse.com>
    * SPDX-License-Identifier: CC-BY-SA-4.0
    *
    * For more information, please contact Datraverse B.V. at this
    * address: info@datraverse.com
    */


.. _app-papercut-delegated-print-front-end:

|DELEGATEDPRINT| to PaperCut Front-end
--------------------------------------

If the requirements for :ref:`Delegated Print to PaperCut <app-papercut-delegated-print>`
are *not* met, SavaPage can still generate PaperCut Account Transactions for print jobs
from a printer *not* managed by PaperCut, provided the following conditions are met:

-  Configuration Property
   ``proxy-print.delegate.papercut.front-end.enable`` = ``Y`` (default
   ``N``).

-  The |RST_CHECKBOX_ENABLED| checkbox for |RST_GUILABEL_PAPERCUT_FRONT_END| is
   checked in the :ref:`Proxy Printer Edit dialog <ch-webapp-admin-proxyprinter-edit-identity>`
   for the printer to which the job was sent.

When these conditions are met, SavaPage printing costs are applied
within PaperCut, in the same way as described in 
:ref:`Delegated Print to PaperCut <app-papercut-delegated-print>`,
after CUPS notifies that the print job has been successfully completed.