# Print

A simple button that prints the current page. The block injects print-optimised styles (landscape A4, hidden Puck UI, expanded tables, visible select values) and optionally prompts the user for a title before printing.

Use it for one-click "Print this page" actions on summaries, confirmations, reports, and detail views.

## Available in

* All module types

Print isn't restricted by module — it's a generic page-print action and works wherever you place it.

## When to use

* A *Print Receipt* button on an order completion screen.
* A *Print Report* button at the top of a Reports page.
* A *Print Detail* button on a transaction-record detail view.
* Any page where the user occasionally needs a paper copy of what's on screen.

For receipts and invoices triggered automatically as part of order submission, use **Submit Button**'s receipt/invoice configuration instead — that handles the printer routing and template-driven layout, not a screenshot of the page.

## Settings

| Setting                 | Description                                                                                |
| ----------------------- | ------------------------------------------------------------------------------------------ |
| **Print Configuration** | Opens the configuration modal. Holds the button label, optional title prompt, and styling. |

The configuration modal supports:

* **Button label** — text shown on the button. Default: *Print*.
* **Prompt for title** — when enabled, the user is asked for a title before printing; the title is added to the printed page. The user can cancel.
* **Styling** — variant (default, destructive, outline, secondary, ghost, link), size (default, sm, lg, icon), and full-width toggle.

## How it works

When the user clicks the Print button:

1. **Title prompt** (optional) — if enabled, a dialog asks for a title. Cancel aborts the print.
2. **Style injection** — print-only CSS is injected: A4 landscape, 0.5cm margins, Puck editor UI hidden, table cells set to nowrap, overflow containers expanded, select dropdowns rendered as their selected value, logos hidden.
3. **Title placement** — the title (and current date) is inserted at the top of the printed output.
4. **Viewport adjustment** — the viewport is temporarily widened to at least 1400px so the print render matches what's on screen, not a mobile-collapsed version.
5. **Print dialog** opens. The user picks a printer and confirms.
6. **Cleanup** — viewport, injected styles, and title element are restored after the dialog closes.

{% hint style="info" %}
Print uses the browser's native print dialog. There's no integration with NetSuite's printer routing — for template-driven receipt and invoice printing tied to specific printers, use Submit Button's Receipt & Invoice Configuration.
{% endhint %}

## Examples

**Print a transaction summary.** On a Page module showing a Transaction Record, place a Print button at the top right with the label *Print Order*. Enable Prompt for Title so the user can name the printout (e.g. *Order #1234 — Customer Copy*).

**Print a report.** On a Reports module, drop a Print button next to the page heading. Disable the title prompt — the report's heading is already on the page.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Submit Button</strong></td><td>Triggers receipt and invoice printing as part of order submission, with NetSuite template support.</td><td><a href="/pages/PhZ3dkc4a1LxD8vQ0aja">/pages/PhZ3dkc4a1LxD8vQ0aja</a></td></tr><tr><td><strong>Action Button</strong></td><td>For more complex print flows, an Action Button with custom code can call print logic conditionally.</td><td><a href="/pages/eJnsvUn6cKd9Lt95bP9b">/pages/eJnsvUn6cKd9Lt95bP9b</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/action-components/print.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.