E-services

FlowWeaver PRO

The open FlowWeaver helps the visitor reach an answer. PRO lets the visitor send it in — to your receiver, with a receipt and a reference number. The same editor, the same viewer, the same file format.

What PRO adds

The Submission and Email result nodes
The receiver contract: catalog, receipt, retry — never addresses in the guide
The schema of what is sent, stamped at export
Health rules about recipients, review and schema
The row in the receiver's list, case type from a code list, an e-mail copy to the visitor

What the versions contain

Both versions
Area	Content
Questions	Single choice, multiple choice, number, date, lookup, multi-lookup, place on a map
Content	Image, annotated image, code, note
Logic	Multi-condition rules, formula calculations, route analysis
Pages	Multi-field pages, headings, spacing, repeated pages
Integration	Service calls to the host's backend, lookups, map provider, file contract
Endings	Result
The editor	Palette, properties panel, preview, health check, history, import and export, templates, versions and publishing, translation mode, modules and levels
The visitor	The viewer with progress, navigation, locale packs, colour scales, theme
Contracts	The file format, storage, lookup, map, events, file, the submission schema type
Server	The server-side experiment with a step model

FlowWeaver PRO only
Area	Content
Nodes	Submission, Email result
Fields for submitting	Free text, rating, consent, attach a file, review before submitting, the e-mail, phone and personal ID templates
The receiver contract	The host registers a receiver with a catalog, a receipt and a retry window. Addresses are never in the guide, only ids and names
The submission	Structured answers, the row in the receiver's list, robot protection, the same id on retry, an e-mail copy to the visitor
The schema	Derived from the guide and stamped at export. Export schema in the File menu
Email result	A recipient from the catalog or the visitor's own address, subject and body with answers, an output dialog in the editor
Health rules	Missing or removed recipient, a copy without an owner, a broken e-mail copy, submission without review, a stale schema
Canvas and panel	Sent to on the card, the recipient picker, the row editor, case type from a code list, the recipient inspector
Capabilities	submission and emailResults, the submission module
Server	The email result's step body in the server experiment
Beyond the library	The reference receiver, the Sitevision module, the identity contract as a sketch

A guide built with PRO still opens in the open FlowWeaver: the viewer draws the submission as a result and sends nothing, and the fields for submitting show as usual. The editor keeps the nodes but does not offer them for new ones. The file format is the same.

Try the e-services

Every guide here sends something in. Rebuild it in the editor or try it as a visitor — the receiver is a demo that answers with a reference number.

Companies

The examples here are built for companies rather than a municipality — the same questions, rules and results, in a private e-service. Each one is also a template: open it, rename it, save it as your own.

Insurance claimPRO A claim at a made-up insurer: the policy from the register, follow-up questions per type of damage, the place on a map, pictures — and the compensation after the deductible worked out as you type. Rebuild Try
Quote requestPRO A painting firm asks what it has to know before quoting — the trade, the rooms and the area — and works out a rough estimate as the customer types. Rebuild Try
Booking requestPRO A salon without a calendar: the service out of the firm's own list, two days that would work, and an email draft to answer — nothing is booked until somebody answers. Rebuild Try
Membership applicationPRO An association where the kind of membership decides both who is covered and what it costs: the family is added a line at a time, and the fee stands beside the consent. Rebuild Try
ComplaintPRO An online shop where the order and the item come from the register and every fault has its own follow-up — two rules in a row, so both the torn seam and the wrong size get asked about. Rebuild Try
Conference registrationPRO Questions that are only asked sometimes, a menu without what you are allergic to, one session at a time for as many as you like — and a registration that becomes a place in the queue when the organiser has run out of places. The number of places lives with the organiser, not in the guide. Rebuild Try
Notice to move outPRO A housing company where the notice period comes from the contract rather than the form — and the days of rent are counted while the tenant picks the day. Rebuild Try

Surveys

Questions answered on a scale, several on one page — the same tool and the same submission as the guides.

How do you like living here?PRO A housing company's tenant survey: a way to decline right at the start, three ratings on one row under a heading, a 1–10 rating on its own page, a follow-up question when the rating is low, and an average in the thanks. Rebuild Try

Business logic

When the guide has to calculate something or collect details: variables, formula calculations and field validation.

BorrowPRO The loan calculator, but the visitor reviews and sends in an application. Rebuild Try
Housing allowance – detailsPRO Identity number, housing cost, floor area and income — with format validation and limits that catch mistakes at once. Rebuild Try

Advanced flows

E-services with several fields per page, the Page Builder, email results and secure execution on the server.

An e-service with pages and fieldsPRO Several fields are answered on one page instead of one question at a time. Rebuild Try
Page BuilderPRO Responsive pages with fields, texts and blank rows — and the same page rendered as a service of its own. Rebuild Try
Secure execution (a simulated BFF)PRO The same e-service run through a backend-for-frontend. The client gets formula-free view models — the calculation and the rules stay on the server. Rebuild Try
Fault reportPRO A fault report end to end: contact details on one page, the place on a map, a category from a lookup, a photo with marks, and the problem in the resident's own words. Rebuild Try
Email result with an attachmentPRO Produce an email draft and get the attached file back with it — nothing is uploaded and nothing is sent. Try
Submission and receiptPRO Review the answers, submit and get the receiver's reference number — and see the honest failure when the receiver rejects. Nothing is sent. Rebuild Try
Order formsPRO A repeating page instead of a folder tree: the visitor picks a form from a lookup, says how many and adds more. A review per page and an email that counts them. Rebuild Try
The recipientsPRO The publisher's half: the catalog with addresses, the default recipient, and why the address never reaches the browser. Try