What the document contains
How SignPlus turns a Confluence page into the document people sign, what it reproduces from the page, and where a PDF cannot follow Confluence.
The document people sign is the page, rendered to PDF inside Atlassian’s runtime by one renderer,
with no outside conversion service. The PDF you download and the PDF that goes to Dokobit come
from the same code, so Download the page as PDF shows what will be signed. The one difference
is the {documentName} placeholder: the page title in a download, the signing’s Document name
in the signed document.
Whose view of the page it is
Confluence draws some content per reader: a Jira work items table lists what that reader may see, and an excerpt from a page they cannot open is left out. So the document is one person’s view:
| Started from | Prints the view of |
|---|---|
| The page | The person who started it, even after they close the panel |
| The REST API | The service account that made the request |
| An automation rule | SignPlus itself, because a rule acts for nobody |
What it reproduces
| On the page | In the document |
|---|---|
| Headings, paragraphs, text colour, bold, italic, lists | As on the page, at Confluence’s own proportions, scaled from the body size in export styling |
| Highlighted text | A tinted badge with gently rounded corners. A highlight longer than 40 characters stays an inline tint, so it can wrap |
| Info, note, warning, success and error panels | With their colour and icon. A custom panel keeps its own colour and emoji |
| Status lozenges, dates and user mentions | As the same small rounded badges the page shows |
| Task lists and decisions | With Confluence’s own check box and decision icons |
| Code blocks and inline code | On a tinted ground, in the document’s typeface. The renderer has no monospaced face |
| Emoji | As images, beside the text |
| Images | At the width the author gave them, aligned as on the page |
| Animated GIFs | As one still picture, in place: the frame the animation rests on longest, or its last frame if it never rests. A PDF cannot animate |
| The user profile macro | The photograph, the name and the email address. No REST API gives an app the job title |
Tables
Three kinds, each kept as Confluence draws it:
| Table | Looks like |
|---|---|
| A table an author drew | A grey heading row and a hairline grid. Column widths the author set are kept, and merged cells stay merged across rows and columns |
| A Jira work items table, or a Jira Assets table | A white heading row with subdued headings, as Confluence’s own datasource table |
| Confluence’s listings, such as the meeting notes index, and the user list macro | No box: a rule under each row or group |
Six rows or fewer move to the next page whole. Longer tables split between rows.
Jira content in a table
| Content | In the document |
|---|---|
| Work type, priority and status | The work type and priority as icons, the status as its lozenge. A long status wraps rather than running into the next column |
| An Oktul Work Item Selector field | Each selected work item as a card, as the field draws it in Jira: work type, key, summary, priority, status and assignee. Ten cards, then +N more. In a table of more than five columns each card takes two lines |
| Oktul Work Item Macro for Confluence | As a Jira work items table, with each of its fields drawn as above, Work Item Selector cards included |
| A Jira Assets object | A chip with the object’s label and key |
Without Jira connected, an Assets table prints a notice and Work Item Selector prints keys. See connecting Jira. Cards always show the field’s default columns.
Attachments
With Include attachments on, the attachments the page body refers to follow the document, such as the files an attachments macro lists. Each starts on a new page, captioned Attachment: with its filename. Left out: a file the body does not refer to, a picture already drawn in the page, and SignPlus’s own exports and signed documents.
- Images are drawn one to a page, scaled down to fit the margins and never enlarged. A GIF is drawn as the same still picture the page prints.
- PDFs are merged in, page by page.
- Anything else, a spreadsheet, a Word file or a zip, has no page form and is not appended. Where the page lists it, in an attachments macro for example, that list prints with the page.
Attachments are appended up to 20MB in total. One that would pass the limit is left out without a note in the document, so on a page with large files check Download the page as PDF first.
Where a PDF cannot follow Confluence
Each keeps the page’s words:
- Over thirteen columns: cut into slices, each repeating the first column.
- A cell over 1500 characters: the table prints as a list of headings and values.
- WebP or a broken image: its alternative text.
- Many images: fetched within 8 seconds; the rest print as alternative text.
- Video, live boards, browser-only macros: their link or text, where Confluence gives one.
Download the page as PDF makes the same document. Look at it before anyone signs a page with unusual macros.
Common questions
- Is the signed PDF the same as the downloaded one?
- Yes. Both come from the same renderer. Only the
{documentName}placeholder differs: the page title in a download, the Document name in the signed document. - Do Jira work items tables print?
- Yes, with work types and priorities as icons and statuses as lozenges. Jira Assets tables and Work Item Selector cards need SignPlus connected to Jira.
- Are attachments included in the signed document?
- With Include attachments on, images and PDFs the page body refers to are appended, up to 20MB in total. Other file types are not.
- What happens to a very wide table?
- A table of more than thirteen columns is cut into slices, each repeating the first column.
Related
A problem or a question? Write to support@oktul.com or open a request in the Help Center (opens in a new tab).