The demo instance gives you a fully functional VeloxFactory environment, pre-loaded with report templates and example data. Everything you can do in a production setup you can do here, with one exception: print tasks do not reach a real printer.

Screenshot placeholder: report-config.index.png
Report Config overview, the landing page after login, with context badges and thumbnails.

---

Access

Demo URL: demo.veloxfactory.dev
Login: demo@veloxfactory.dev · Password: demo

The demo account has full access to all report data, Report Configs, History Records, Print Tasks, Mail Tasks, Connection Configs, Contexts, Common Resources, Printers, Mailers and Mail Templates. It can also generate and use API tokens. User management is not available. ---

Guided Tour

Work through these steps in order for a complete first look at VeloxFactory.

Step 1 - Browse the Report Configs

After logging in you land on the **Report Configs** list. This is the central workspace. Each card shows a thumbnail preview of the report and its context badge. Use the search bar to filter by name, or use the dropdown filters to narrow by context or data adapter. Try typing part of a report name, the list updates instantly, no page reload.

Screenshot placeholder: report-config.index.filtered.png
Report Config overview with the filter bar open and active filter badges.

Step 2 - Explore a Report Config

Click any report to open its detail view. Here you can inspect: - **Parameters** - the inputs the report expects at render time, with their data types and example values - **Fields** - the data columns that populate the report body - **Resources** - image assets embedded in the template (logos, icons) - **Preview** - the rendered thumbnail, generated from the stored example values Scroll through the sections to get a feel for what VeloxFactory extracts from a `.jrxml` file automatically on upload.

Screenshot placeholder: report-config.edit.png
Report Config edit view with parameters, fields and resources.

Step 3 - Render a Report from the Frontend

From within a Report Config, click the **Generate PDF** button. A dialog opens with pre-filled parameter values (taken from the example values stored on the config). You can edit any of them before rendering. Select an output type, **Base64** is fine for a quick look, and click **Generate PDF**. VeloxFactory processes the request and shows the resulting PDF inline within seconds. No API call needed, no setup required.

Screenshot placeholder: generate-pdf.create.png
Generate PDF page with the parameter inputs and the output settings.

Step 4 - Check the History Record

Navigate to **Report History Records**. Your render from Step 3 appears at the top of the list (if you left `createHistoryRecord` enabled in the dialog). Open it to see the full log: the exact request payload, the API response, the rendered PDF, and a thumbnail. From here you can download the PDF directly, trigger a reprint, which creates a new Print Task, or send the document by mail, which creates a new Mail Task.

Screenshot placeholder: report-history-record.show.png
Report History Record detail page with status, payload, PDF preview and the actions.

---

Try It Yourself

Once you have completed the tour, these are good next things to explore on your own.

Upload Your Own Template

If you have a `.jrxml` file designed in Jaspersoft Studio, you can upload it directly to the demo. Go to **Report Configs → Create**, attach the file, and let VeloxFactory analyse it. Within seconds, all parameters, fields, and resources are detected and listed automatically.

ℹ️ Use Jaspersoft Studio 6.21.5. This is the version compatible with VeloxFactory's render engine. Download it from the Jaspersoft Community. Reports created with a significantly newer version may use features the render engine does not support.

After upload, set any missing example values, upload resource files if needed, and click **Generate Preview** to produce a thumbnail. The report is then ready to render.

Call the API Directly

The demo account has API access enabled. To get a token, open the user menu in the top right corner and go to **Account Settings → API Tokens**, copy it immediately, it is only shown once. With the token in hand, render any report with a single HTTP request: ```bash curl -X POST \ https://demo.veloxfactory.dev/api/v1/report-config/{reportName}/render \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "outputType": "base64", "useExampleValues": true, "createHistoryRecord": true }' ``` Replace `{reportName}` with the `report_name` of any config from the list (visible in the detail view). The `useExampleValues` flag tells VeloxFactory to use the stored example values instead of requiring you to pass parameters and data manually, ideal for a first test. The response contains the rendered PDF as a Base64 string and a trace ID you can look up in History Records.

Send a Report by Mail

Mailing is the second way a rendering leaves VeloxFactory. Two mailers are waiting for you under *Configuration*.

Mailer	What it is for
Demo Log Mailer	Writes every mail into the application log instead of sending it. Ready to use, and the safe way to follow the whole path from render to mail task without anything leaving the machine.
Demo SMTP Mailer	The starting point for a real send. It carries placeholder values, `smtp.example.com` on port 587 with scheme `smtp`, user and sender `change-me@example.com`, and it is inactive so nobody picks it before it works.

To send for real, open the SMTP mailer, replace host, port, credentials and sender with the data of a mailbox you own, send a test mail from the form, and set it active. Then write a **Mail Template** with a subject and a body. The editor has a placeholder button that lists every token the template can use. With a mailer and a template in place, open any History Record and click **Mail**, or switch on *Send results via Mail* in the Output Settings of the Generate PDF page. The mail goes out with the PDF attached, and optionally with an xlsx export of the same data. Every mail shows up in the **Mail Queue** with its status, its recipients and the body that was actually sent.

Explore Print Tasks

When rendering via the frontend or API, enable the print task option and provide any printer name (e.g. `demo-printer`). VeloxFactory creates a `ReportPrintTask` record with status **pending**. Since no print service is connected to the demo, the task stays pending, but you can inspect the full record and see how status tracking works. Completed print tasks are purged automatically after a configurable retention period. ---

Demo Limitations

What	Behaviour in the demo
Print tasks	Created and traceable, but no real printer connected, tasks remain pending. Completed tasks are purged automatically.
Mail dispatch	Mailers and Mail Templates can be created freely and a mailing can be configured end to end. The log mailer records the mail instead of sending it; whether a real mail is delivered depends on the SMTP account you enter, the demo has no mailbox of its own.
Live SQL connections	Connection Configs can be created and tested, but no external databases are reachable from the demo environment.
User management	The demo account does not have admin rights, user accounts and permissions cannot be managed.
Data persistence	Uploaded templates, history records, and other data may be reset periodically.

ℹ️ Ready to go further? See Meet the Frontend for a full walkthrough of the UI, or Meet the API for complete API documentation.