Audit Reports content pack#

Audit Reports is a ready-made folder of three distribution jobs, three data models, and their source workbooks, which report on Reportworq itself: job runs, schedules, users, security, and the instance's own connections. It ships as an importable content pack, the same one Timberline (the built-in demo company) carries, so you can bring it into your own workspace instead of building it from scratch.

What you'll need#

• System Administrator rights, to add the datasource in the one setup step below.

• The Reportworq Content Store datasource. This is Reportworq's built-in, one-click, self-configuring connector to its own operational data, with no connection string, credentials, or driver to configure. If your instance does not already have one:

  1. Go to Settings ▸ Integrations ▸ Add.
  2. Choose Reportworq Content Store from the picker.
  3. In the General section, check Enable Integration and save. The new connection is already named Reportworq Content Store; keep that name. (Older releases name it New Datasource: on those, change the Display name to Reportworq Content Store before you save.) See the note under Point the data models at your datasource for why.

  Its data is instance-wide, spanning every workspace and system-level stores, so its Availability should be set to a workspace whose members are meant to see cross-tenant and administrative data. Adding it is a one-time step; the jobs below reuse it once it exists. For the full access model and what it exposes, see Connect the Reportworq Content Store.

Download#

⬇ Download the Audit Reports content pack (ZIP)

Import it into your workspace#

1. Open Workspace and go to the folder where you want the pack (the workspace root is fine).
2. Click Upload on the toolbar and choose the downloaded ZIP. Reportworq recognizes it as a content pack and imports it rather than storing it as a plain file. You can also drag the ZIP onto the browser, or use ⋯ ▸ Import on a folder.
3. A new Audit Reports folder appears (or Audit Reports (1), if that name is already taken), with everything sorted into three subfolders, each item with a fresh id:
   • Data & Models: the three data models.
   • Report Templates: the three Excel source workbooks.
   • Reports: the three distribution jobs you run.

Point the data models at your datasource#

Connections don't travel in an import. That is how Reportworq keeps secrets out of a portable ZIP. Each of the three imported data models (Activity, Catalog, Inventory & Security) needs to be pointed at your instance's own Reportworq Content Store connection once:

1. Open a data model (double-click it in the Data & Models folder).
2. Select Source in the rail, then the Sources tab. On the source's row, use Change to pick Reportworq Content Store (or Add connection if no source is listed). Every view on that source moves to the connection you pick.
3. Save Changes.

Repeat for all three. This takes a few seconds per model and only has to be done once, right after import.

Keep the connection enabled and named Reportworq Content Store. The data models find the connection you pick above, but the three source workbooks find it by name: their worksheet formulas call RW.Relational.Export with the connection name "Reportworq Content Store". If the connection is renamed, disabled, or not available to the workspace the jobs are in, every formula in the pack fails with "Failed to load SQL Provider for 'Reportworq Content Store'".

Run it#

Each job is ready to run as soon as its data model is bound. In the Reports folder, on the job's row, click the Run icon (or open the job and use Run Jobs). No parameters are required.

The pack's three schedules don't travel either. A schedule is a separate scheduled-content item, not something nested inside the folder, so an import brings the jobs and data models but not their original schedules. If you want the jobs to run on their own, create a schedule under Scheduled Content for each one. The originals run Weekly Activity Audit and System Snapshot weekly on Monday at 08:00, and Monthly Activity Audit on the 1st of the month at 08:00. Otherwise, run them on demand with Run Now whenever you want a fresh look.

What's inside#

About the numbers#

Weekly Activity Audit is windowed to the last 7 days of job history, so right after import, or on any instance still light on run history, it can look thin until your own jobs and schedules have run for a week. Monthly Activity Audit and System Snapshot always show data: the monthly audit reads whatever history exists (even a single day still plots), and the snapshot reads current state, which exists from the moment your instance has any jobs, users, or integrations at all.

Troubleshooting#

• A data model's source is missing, or shows a code such as bc18a420dd430d4e, after import. Expected: that code is the connection the pack was exported from. See Point the data models at your datasource above and pick your own Reportworq Content Store connection.
• A view still fails after you rebind, with "The connection '...' could not be found" or "Object reference not set to an instance of an object". On the Sources tab, use Change on the source's row to pick Reportworq Content Store again and click Save Changes; that moves every view on the source to it.
• A job run fails with "Failed to load SQL Provider for 'Reportworq Content Store'". The worksheet formulas look the connection up by name. Check that the connection's Display name is exactly Reportworq Content Store, that Enable Integration is checked, and that its Availability includes the workspace the jobs are in.
• Reportworq Content Store isn't in the datasource picker. You need System Administrator rights to add integrations; see What you'll need.
• Weekly Activity Audit shows little or nothing. Expected on a freshly imported or recently reset instance; see About the numbers. It fills in as runs accumulate, or you can add the original weekly schedule to speed that up.
• A job's output opens but a sheet looks empty. Confirm the data model it depends on (see the table above) is bound and saved: an unbound model returns no rows, not an error.