Download the demo system#

Everything described in this guide is available as a content store you can point your own Reportworq at. It carries the reports, jobs, campaigns, schedules, parameters, contacts and data that the rest of this guide walks through.

⬇ Download the Timberline demo system (ZIP)

The download band on the documentation home page always carries the current version, date and size. What is on this page is the same package.

What you need#

Reportworq 6, and nothing else. You do not need to connect a data source. The data the reports read travels inside the package, so the numbers are real and the reports run anywhere.

The fastest way: one click in the setup wizard#

A brand-new Reportworq install ships with this demo built in. On first launch, the setup wizard's "Where should Reportworq store its data?" step offers Set up the Timberline demo system. Choose it and Reportworq extracts the demo into a TimberlineRepo folder next to where a normal repository would go, points itself at it, and restarts to the sign-in page - no download, no unzip, no path to type. The wizard shows you the sign-in (admin@rw.com / Admin_1234) before it restarts and again on the way in.

There is no license in the demo, so Reportworq asks you to activate with your own key on first sign-in, exactly as any fresh install does. Prefer this route on a new install; use the download below to add the demo to an install you have already set up, or to get a newer version than the one bundled with yours.

Install it (download route)#

1. Extract the ZIP. You get a single folder, Timberline-Demo-System.
2. Put it where Reportworq can read and write it. Alongside your existing repository is fine; it is a self-contained content store, not something that merges into one you already have.
3. Point Reportworq at it as the repository, and start the server.
4. Sign in as admin@rw.com with the password Admin_1234, then change it.

There is no license in the package. Reportworq will ask you to activate with your own key exactly as a fresh install does.

Treat it as a sandbox, not a starting point. Explore it, run everything, break things. When you want to build your own content, start a clean repository and bring the patterns across rather than editing Timberline into your production system. Where the files live explains why the jobs are more fragile to renaming than they look.

What is inside#

Parameters still work#

Where a report offers a parameter, a market or a year, it behaves exactly as the guide describes: the parameter drives a lookup into the packaged data, so a burst by market produces one genuinely different output per market rather than the same file under fifteen names.

Release notes#

Changes to the demo system are recorded in the release notes.