View Revisions: Issue #966
| Summary | 0000966: Integrate Personal Print with PaperCut | ||
|---|---|---|---|
| Revision | 2018-07-02 12:27 by rijkr | ||
| Description | IST: With config item "proxy-print.delegated.papercut.enable=Y", the cost of a delegated print, to a PaperCut managed printer, is split by SavaPage and charged to PaperCut with personal and shared account transactions. Note: a shared-account print is handled as delegated print. Because Job Ticket Printing is handled as delegated print in all cases, for personal prints, the print job creator is seen as both Delegate and Delegator. In a non-job-ticket context, this is not the case: the status of personal prints is not monitored in, and costs are not taken from PaperCut after successful completion. SOLL: Add option to monitor status of personal prints in, and take over cost from PaperCut after successful completion. Activate with config item: "proxy-print.personal.papercut.enable=Y". |
||
| Revision | 2018-07-02 13:20 by rijkr | ||
| Description | IST: With config item "proxy-print.delegated.papercut.enable=Y", the cost of a delegated print, to a PaperCut managed printer, is split by SavaPage and charged to PaperCut with personal and shared account transactions. Note: a shared-account print is handled as delegated print. Because Job Ticket Printing is handled as delegated print in all cases, for personal prints, the print job creator is seen as both Delegate and Delegator. In a non-job-ticket context, this is not the case: the status of personal prints is not monitored in, and costs are not taken from PaperCut after successful completion. SOLL: Add option to monitor status of personal prints in. Just the cost is take over from PaperCut after successful completion (no extra PaperCut transactions are created) . Activate with config item: "proxy-print.personal.papercut.enable=Y". |
||
| Revision | 2018-07-03 12:58 by rijkr | ||
| Description | IST: With config item "proxy-print.delegated.papercut.enable=Y", the cost of a delegated print, to a PaperCut managed printer, is split by SavaPage and charged to PaperCut with personal and shared account transactions. Note: a shared-account print is handled as delegated print. Because Job Ticket Printing is handled as delegated print in all cases, for personal prints, the print job creator is seen as both Delegate and Delegator. In a non-job-ticket context, this is not the case: the status of personal prints is not monitored in, and costs are not taken from PaperCut after successful completion. SOLL-1: When "proxy-print.delegated.papercut.enable=Y", handle all Personal Print as Delegated Print for PaperCut managed printers. SOLL-2: Add option to monitor Personal Prints in PaperCut, in case "proxy-print.delegated.papercut.enable=N": config item "proxy-print.personal.papercut.enable". When "Y", just the cost is take over from PaperCut after successful completion (no extra PaperCut transactions are created). |
||
| Revision | 2018-07-03 13:09 by rijkr | ||
| Description | IST: With config item "proxy-print.delegated.papercut.enable=Y", the cost of a delegated print, to a PaperCut managed printer, is split by SavaPage and charged to PaperCut with personal and shared account transactions. Note: a shared-account print is handled as delegated print. Because Job Ticket Printing is handled as delegated print in all cases, for personal prints, the print job creator is seen as both Delegate and Delegator. In a non-job-ticket context, this is not the case: the status of personal prints is not monitored in, and costs are not taken from PaperCut after successful completion. SOLL-1: When "proxy-print.delegated.papercut.enable=Y", handle all Personal Print as Delegated Print for PaperCut managed printers. SOLL-2: Add config item "proxy-print.personal.papercut.enable" (default N) to monitor Personal Prints in PaperCut, to be used when "proxy-print.delegated.papercut.enable=N". When "proxy-print.personal.papercut.enable=Y", just the cost is take over from PaperCut after successful completion, and no extra PaperCut transactions are created. |
||
| Revision | 2019-01-02 21:16 by rijkr | ||
| Description | IST: With config item "proxy-print.delegated.papercut.enable=Y", the cost of a delegated print, to a PaperCut managed printer, is split by SavaPage and charged to PaperCut with personal and shared account transactions. Note: a shared-account print is handled as delegated print. Because Job Ticket Printing is handled as delegated print in all cases, for personal prints, the print job creator is seen as both Delegate and Delegator. In a non-job-ticket context, this is not the case: the status of personal prints is not monitored in, and costs are not taken from PaperCut after successful completion. SOLL-1: When "proxy-print.delegated.papercut.enable=Y", handle all Personal Print as Delegated Print for PaperCut managed printers. SOLL-2: Add config item "proxy-print.personal.papercut.enable" (default N) to monitor Personal Prints in PaperCut, to be used when "proxy-print.delegated.papercut.enable=N". When "proxy-print.personal.papercut.enable=Y", just the cost is taken over from PaperCut after successful completion, and no extra PaperCut transactions are created. |
||
| Revision | 2019-01-05 11:53 by rijkr | ||
| Description | IST: If config item "proxy-print.delegated.enable=Y" and "proxy-print.delegated.papercut.enable=Y", the cost of a delegated print to a PaperCut managed printer, is split by SavaPage and charged to PaperCut with personal and shared account transactions. In this configuration also non-delegated prints, like shared-account and personal print, are handled as delegated print (for personal prints, the print job creator is regarded as both Delegate and Delegator). If "proxy-print.delegated.enable=N", the status of a personal print to a PaperCut managed printer is not monitored in PaperCut, and costs are not taken from PaperCut after successful completion. SOLL-1: When "proxy-print.delegated.enable=N" and "proxy-print.personal.papercut.enable=Y" (default N), the status of a personal print to a PaperCut managed printer is monitored in PaperCut. SOLL-1A: If printed via job ticket, job ticket cost is leading, and thereby extra PaperCut transactions are created (just like the Delegated Print scenario). SOLL-1B: If printed directly (not via job ticket), costs are taken from PaperCut after successful completion, and no extra PaperCut transactions are created. |
||
