Electricity bill: the whole job in one workflowJSON data, print/e-mail split, duplex padding, regional segments with cover sheets, signed PDFs and a DMS archive.

Statements by channel: e-mail, print per branch, DMSEvery customer gets the statement on the channel they chose: signed PDF, print with a cover sheet per branch, and JSON for the archive.

Print spool with cover sheets and inserter marksAn existing PDF spool: the customer number is read from the page, blank pages dropped, a cover sheet inserted per customer and inserter marks stamped.

Telecom invoice spool: print and signed e-mailInvoices from another system are split per customer. Paper customers go to print with marks, digital ones are signed and e-mailed as attachments.

Certificates of attendance from two joined sourcesRegistrations and card-reader entries are grouped, joined and filtered (present at least two days) before the certificates are produced.

School reports with pupil and class averagesTwo CSV exports from the school register are grouped and joined, grade and class averages are calculated, and documents come out per class.

E-invoice: validation, UBL 2.1 and a PDF visualisationERP invoices are checked (VAT ID, IBAN, classification, totals). Valid ones become UBL XML and PDF, invalid ones go back to the ERP.

Data transformation: CSV to JSON per merchantThis workflow produces no pages. It filters, groups with aggregates and writes one JSON per merchant for a DMS or a partner API.

Electricity bill in the layout designerConsumption chart, an energy-class picture picked by the data, item table, HUB3 and OMR marks. Structure tree on the left, the selected chart's properties on the right.

Insurance policy with charts and conditional contentDonut and bar charts, a bonus band that only appears when its condition holds, a coverage table and a product picture per policy type.

Bank statement with a table across pagesThe transaction table repeats its header on every page and shows the closing balance only at the end. The inserter DataMatrix sits on the master page.

Merchant report with charts built from transactionsA daily turnover line chart and a donut by card scheme. The chart sums the transactions itself.

CV as an infographicSkill bars, language dots and a chart, all from the same candidate record. One of ten designs.

CV with a photo taken from the dataSidebar with photo, QR code and language levels.

Product datasheet from ExcelSpecifications per appliance type, energy class and price from a PIM export.

Price list with photosItems grouped by category, each item's picture from the data.

Property exposéPhotos, map, agent and price per m², all from the data.

Boarding pass with an IATA PDF417 barcodeAn IATA BCBP barcode per passenger and flight.

Menu with allergen iconsCategories, prices and allergen icons chosen by the data.

Tri-fold flyer: text flows across three panelsChained areas: the menu flows from panel to panel by itself.

Congress badge with Aztec code and colour by categoryThe colour changes with the attendee category. The Aztec code is used for entry.

Wall calendar computed by a scriptMonth grid with holidays. A script in the workflow computes the days from the year and months.

School report with class averagePupil grades, overall result and a comparison with the class.

Pre-filled PDF formForm fields receive what is already known, and the parent completes the rest.

Barcode control sheetEvery symbology on one sheet, with check digits computed in the workflow.

4×6 shipping label with SSCC and MaxiCodeA GS1-128 SSCC per parcel and a postal code per destination.

Book with contents and running headsChapters start on a new page, and the contents are built from the headings.

Contract with conditional clausesClauses appear depending on the contract type. The amount in words comes from the workflow.

80 mm fiscal receipt with QRVAT recap per rate and a QR code to verify the receipt.

Direct-mail pack in A4, DL and A6Three formats in one document, a conditional flow and master pages per format.

E-mail body designed like a pageA personalised e-mail body using the same data as the attached document.

Group with aggregatesTransaction count, turnover, fees and the largest transaction per merchant.

Filter: approved transactions onlyConditions are built without programming.

Joining two sources (Correlate)Registrations and reader attendance are joined on a key.

Grouping entries per attendeeDistinct attendance days per person.

Validation: VAT ID, IBAN, classification, totalsInvalid records are routed aside before they reach the e-invoice.

Transform: average, result, remedial workCalculated fields with formats and rules.

Transforming Excel dataPrices, specifications and energy class from a PIM export.

Purchase orders: quantity up to optimumAmount, quantity and delivery date computed in the workflow.

Data Proof: records at a workflow stepThe grouped records before the output.

A script that builds the calendarFrom year and months the script creates days, weeks and holidays as data.

Payroll calculation in the workflowA script over the joined data calculates contributions, tax by city and net pay.

Derived fields for the designDurations, levels and ordering prepared for the CV graphics.

Check digits (mod 10)An expression computes the check digit before encoding.

CSV inputTens of thousands of rows, detected schema and preview.

Excel inputA PIM export with normalised headers.

JSON inputNested data: items and consumption per bill.

PDF input: an existing spool as a page stream448 pages from another system enter the workflow.

Run parametersValues set per run or by an automation.

PDF outputNaming, grouping, PDF/A, fonts and colour per output.

E-mail outputRecipient, subject and attachment per record.

Metadata for the DMSA JSON per document with fields and the PDF in base64.

Data output as JSONAn output contract defines fields and structure.

UBL 2.1 XML outputAn e-invoice to the Croatian specification.

Fiskalizacija 2.0: XML requestE-reporting to the tax administration from ERP data.

PDF Page Transform: reading values from the pageA rule extracts the customer number from a marked area and starts a new document when it changes.

Stamping DataMatrix marksCustomer, page in group and end-of-set flag on every page.

Page Regroup: a new document per customerPage groups by key, with counters for the marks.

Inserting a cover sheetA PDF in the client's colours in front of every customer.

Sheet Mixer: a layout over existing pagesInserter marks come from a layout and are laid onto every spool page.

Streaming 20,000 pagesBates numbers and DataMatrix page by page, without loading the whole file.

Reading customer, channel and e-mail from the pageSeveral rules on one page, and the results become data.

Extract text with "OCR if no text layer"The document number read from a scanned page, with the OCR options.

Add OCR text layerThe test on a scanned page lists the recognised lines that become the invisible text layer.

Rotate page with Only when page.widthPt > page.heightPt on a sheet scanned sideways.

Redact text matching a patternA regular expression for IBANs, the test counts the matches on the page, the preview shows them blacked out.

Secure redact as a child ruleThe account holder block is removed only on statements (the parent reads the title IZVOD).

A conditionThe child rules (customer number, amount, lookup, barcode check) run only when the document type reads RAČUN.

Look up data by keyThe customer number on the page is found in the master data (CSV), every column comes onto the page.

Classify regionThe rule finds that the invoice corner holds a payment barcode.

OCR of light text on a dark bandSingle block, boosted contrast and inverted colours; a new document starts on the number read.

DataMatrix and OMR marks for the inserter; the test reads them back with a barcode reader (Scanner check).

Stamp pictureA RECEIVED stamp with a signature only on the first page of each document (Only when page.counter == 1).

InspectA click on the page lists the objects under the point, with font, size and whether the font is embedded.

Move objectsThe address block moves into the envelope window; the preview shows the page as it comes out.

Remove objects with object type "images only"The advertising picture goes, the text stays.

HideThe internal note is covered in print, the content stays in the file.

Flatten forms and annotations on an old form, with a receipt stamp that carries the file name.

PDF Data on the folder of received filesFonts (embedded?), images (dpi) and Validate with finding codes.

Data ProofThe old form carries finding PDF-FONT-001, a font is not embedded.

Data ProofA file cut off in transfer becomes a record with finding PDF-OPEN-001, the run does not stop.

Data ProofThe form's font list, Helvetica is not embedded.

Data ProofThe fax image is 150 dpi, found before archiving.

PDF Data, Records of an embedded fileFactur-x.xml or zugferd-invoice.xml, one record per invoice line.

Data Proof27 lines from six Factur-X and ZUGFeRD invoices, with quantity, unit, price and VAT category.

Data Proof after the joinEach line carries the invoice number, date, supplier and its VAT id from the header.

Imposition: 16 labels on SRA3Crop and registration marks, colour bar and slug line.

Colour management: spot colour and PDF/X-4Spot-colour separation, CMYK conversion and PDF/X-4 on output.

Nesting mixed formats on SRA3Jobs of different sizes in their ordered quantities.

Die-cut line for the cutterA print group: the cut line only in the cutter file and the proof.

Business cards 20 on SRA3, duplexEvery back exactly behind its front.

Step & repeat from the dataThe ordered quantity per person sets the copies.

Book in 16-page signaturesPerfect binding with creep compensation.

Booklet (saddle stitch)Pages are arranged into sheets for stitching.

The imposed sheet in Page ProofThe sheet with its marks exactly as it goes to press.

Bingo strips for cut & stackAfter cutting and stacking, the strips come out in order.

Padding for duplexEvery document gets an even page count.

PAdES digital signatureCertificate, reason and a visible signature on the PDF.

Signed e-mail attachmentEvery bill signed before it is sent.

Password per recipient: personal IDThe payslip opens only with the employee's personal ID number.

Channels per recipient and consentE-mail when the address is valid and consent is given, otherwise print.

Page Proof: an electricity bill, page by page1,218 pages, 574 records: group, page logic and file size for every page.

Page Proof: policy with chartsThe finished page, exactly as it will print or go out by e-mail.

Page Proof: the table continuing on page twoOverflow with a repeated header.

Page Proof: spool with stamped marksDataMatrix and marks visible on the finished page.

Page Proof: a pack in three formatsA4, DL and A6 in the same document.

Page Proof: the book's contents pageContents with page numbers from the layout.

Page Proof: badges on A4Duplex, 4 per sheet.

Workflow version historyEvery saved version has a note, a time and a stage. You can open an older one, compare it or promote it again.

Committing a version with a noteDescribe what changed and, if you want, promote the version straight to test or production.

Promoting a versionPick a version and a stage. Your working copy stays as it is.

Workflows in a projectStatus, version, default workflow, test dataset and history in one place.

Projects in a workspaceAll 22 starter projects, ready to open.

The project's automationsDraft and deployed automations with their triggers and state.

Automation: folder → workflow → approval → publishEvery step is a node. The “approved” branch leads to delivery.

Approval inboxRequests with attached files, deadlines and decisions.

NoticesPending approvals and failures in one place.

Operations console: jobsJob states, files and run logs.

Deliveries: the Publisher ledgerEvery delivered file, destination and attempt.

Delivery destinationsSFTP print house, e-mail, HTTP DMS and an archive folder.

System healthService, job queue and workers.

Automation versionsThree versions of one automation, promoted to test, staging and production in turn.

Runs of a nightly automationEvery run with its trigger, state and details.

One run in detailEach step with its result and duration: schedule, workflow, condition, DMS delivery and the HTTP call.

Connections to other systemsERP over REST with OAuth2, a DMS, FINA over SOAP with a certificate, SFTP and a webhook. Secrets are never stored in the file.

Tenant administrationEach tenant has its own jobs, storage and limits, and can be suspended.

A job's timelineFrom submission to completion, with every phase in between.

The e-mail reviewers receiveYour own text with variables. The approval link is always added.

Watched folderFolder, file pattern and where processed and failed files go.

Running a workflowWhich workflow version runs and with which parameters.

Approval requestReviewers, how they decide, the deadline and what is being approved.

PublishingDestination, what gets delivered and how long to wait for confirmation.

ScheduleEvery night at 03:00 Zagreb time, with the next runs listed.

REST triggerEndpoint, token and the parameters another system sends.

HTTP request to a DMSA POST with a JSON body over a saved connection, with retries.

ConditionCarry on only when the previous step succeeded.

NotificationA message to the print house once the bills are handed over.

Job Builder: ten steps to a finished jobData, pages, address block, content, formats, print and e-mail, output, extras and review. The workflow is built from these steps.

Straight from the program

Privacy