The official Κατάλογος χαρακτηριστικών Doconut lists browser printing and PDF export as viewer capabilities. Controlling access to them still requires two separate decisions: whether Doconut presents the relevant action and whether the host application authorizes that operation for the current user and document.
For the exact controls supported by your installed build, start with the τεκμηρίωση Doconut and the packaged samples available from the official σελίδα λήψης Doconut. Do not copy configuration keys or source code from an unrelated version or an unverified article.
1. Ορίστε πρώτα την Πολιτική Εκτύπωσης
Write down who may print and under which conditions before changing the toolbar. A useful policy answers questions such as:
- Is printing allowed for every viewer, only certain roles, or specific documents?
- Does the decision depend on tenant, case status, document classification, or expiry?
- Is a watermark required on printable output?
- Should print events be audited?
- Can a user print an older document revision?
- What should happen when permission changes while the preview is open?
Avoid a single global Boolean when the real rule is contextual. Model printing as its own operation so it can be authorized independently from viewing and downloading.
2. Διαχωρίστε την Κατάσταση UI από την Εξουσιοδότηση
The host page can decide whether to present a print control after it receives an application-owned permission result. That improves clarity for users who cannot print.
However, hiding a control is not an authorization boundary. A user can still call a known endpoint directly, replay an earlier request, or invoke browser printing on visible content. Every server route that produces printable output must enforce the same policy.
Use distinct states in the UI:
| State | Viewer behavior | Server behavior |
|---|---|---|
| Printing allowed | Show the supported print action | Authorize and create the requested output |
| Printing denied | Hide or disable the action with a clear explanation | Return a forbidden response |
| Policy unknown | Keep the action unavailable while permission loads | Do not create output |
| Session expired | Ask the user to reauthenticate | Reject the stale request |
3. Προστατέψτε το Τερματικό Εκτύπωσης
Protect the application operation that invokes printing or returns printable output. The authorization decision should account for tenant membership, ownership, classification, workflow state, and document revision. Resolve the document on the server instead of accepting a client-supplied path or storage URL.
If your application prints through a viewer-specific route instead of creating a PDF, apply the same authorization before invoking that route.
4. Διαμορφώστε την Έκδοση του Προβολέα που Έχετε Εγκαταστήσει
Once the server rule exists, configure the Doconut UI using the exact option documented for the package and sample files shipped with your version. The ζωντανές επιδείξεις Doconut let you observe supported viewer behavior before you commit to a particular integration. Verify:
- Where the option is set: server configuration, view model, or client initialization.
- Whether it hides a toolbar item, disables an action, or affects generated output.
- Whether the value applies per viewer instance or globally.
- Whether print and export are separate operations.
- Whether an update changed the option name or default.
Treat the official sample as the source of truth. A plausible-looking property name is not enough evidence that the installed viewer recognizes it.
5. Διαχειριστείτε την Εκτύπωση του Περιηγητή Ειλικρινά
A viewer setting cannot guarantee that visible information will never be printed or captured. The browser may print the host page, and users can take screenshots or photographs. Keyboard interception and print-specific CSS can improve the expected experience, but they are bypassable client-side measures.
If the host page should not produce a useful paper copy, your application can use its own print-specific presentation to replace the preview with an explanatory message. Keep that host-page behavior separate from Doconut's documented viewer controls.
Do not describe this as document protection. Use server-side rendering, authorization, controlled exports, and visible watermarks when your risk assessment calls for stronger deterrence.
6. Διατηρήστε το Κατέβασμα, την Εξαγωγή και την Εκτύπωση Ξεχωριστά
Users and developers often treat these as one “read-only” switch, but they represent different data flows:
- View displays rendered content.
- Download returns the source or another stored file.
- Export creates a derivative format.
- Print produces a printable representation or invokes browser printing.
Authorize each operation explicitly. A user who cannot print may still be allowed to download, or the reverse. Your toolbar should reflect the server's decisions rather than define them.
7. Προσθέστε Χρήσιμα Γεγονότα Ελέγχου
If printing is sensitive, record the decision without logging the document itself. An event can include the user, tenant, document identifier, revision, policy outcome, timestamp, and correlation ID.
Record both successful and denied attempts. If the print service creates a temporary file, also record whether its cleanup completed. Keep file paths, tokens, document titles containing personal data, and printable content out of routine logs.
8. Δοκιμάστε Πέρα από το Απουσία Κουμπιού
The toolbar is only the first assertion. Add tests for the whole operation:
Authorized user
- The intended print action is visible.
- The print request succeeds for an allowed document.
- The correct revision is used.
- Required markings appear on generated output.
- The audit event records success.
Unauthorized user
- The action is absent or disabled.
- A direct request to the print route returns a forbidden response.
- Changing the document ID does not bypass the rule.
- A URL copied from an authorized session cannot be reused improperly.
- The denial does not reveal whether another tenant owns the document.
State changes
- Permission revoked during a session is enforced on the next print request.
- An expired session cannot print.
- A deleted or superseded document produces a controlled error.
- Temporary print output follows the configured retention rule.
Browser automation can verify the visible state and response code. Integration tests should verify policy evaluation and document-level authorization independently.
Συχνές Ερωτήσεις
Απενεργοποιεί η απόκρυψη του κουμπιού εκτύπωσης τη συντόμευση εκτύπωσης του περιηγητή;
No. It removes an intended viewer action only if the installed viewer implements that behavior. Browser printing and screen capture require separate consideration and cannot be fully prevented by client-side code.
Πρέπει η άδεια εκτύπωσης να περιλαμβάνεται στο URL προβολής;
Prefer a server-side authorization decision tied to the authenticated user, document, and operation. If a temporary reference carries permissions, scope it narrowly, protect it from logs and referrers, and revalidate sensitive actions.
Είναι η απενεργοποίηση της εκτύπωσης αρκετή για εμπιστευτικά έγγραφα;
No. It is one usability or deterrence control. Confidential workflows also need storage protection, object-level authorization, controlled exports, retention rules, monitoring, and an accepted residual-risk model.
Συμπέρασμα
A trustworthy Doconut print-control implementation starts at the server and ends in the interface. Define the policy, protect the operation, configure only the documented option for your installed viewer, explain the result to users, and test direct requests as well as toolbar visibility. Use the official feature page, documentation, downloads, and demos as the implementation sources rather than recreating product code in the article.