Administrator guide
For the person who installs, configures, and supports the page.
Requirements
| Component | Requirement |
|---|---|
| Fishbowl | 2026.6 or later |
| Plugin | ILC CloudPages plugin |
Installation
Installation is the same for every ILC catalog page. For the full steps, see TBD (public documentation URL).
- Buy the page on ilcreports.com.
- Install the CloudPages plugin in Fishbowl.
- Configure CloudPages with the manifest URL from the purchase.
- Confirm that the purchased pages appear in the installation.
- Grant page access to the users who need it.
Verify. Open the page. Click ? to run the guided tour. The tour changes nothing in Fishbowl.
To configure the page, see Settings.
Updates
Updates are the same for every ILC catalog page.
A customer gets the latest stable version of a page by default. To stay on a previous version, or to return to one, choose the version in the ilcreports.com portal.
Fishbowl keeps its own data through an update. The plugin data in Fishbowl holds the access rights, the module placement, and the page settings. This data also survives a page removal.
For what changed in each version, see the release notes.
Security
The page reads no Fishbowl access right. It changes no behavior based on one. Page access decides who can read change history, and an administrator grants that access during installation.
Who to grant access to. This page suits an administrator-level audience. The page applies no restriction below page access. A user who can open the page can read the history of every audited table. This includes user accounts and group administration. Grant access accordingly.
Considerations
- Fishbowl stores passwords and MFA secrets as hashes. The page never shows the stored value. The page shows that the field changed, and when.
Data handling
Every query and API call the page makes:
| Operation | Against | Right checked |
|---|---|---|
| Query | information_schema, for the audited tables, their columns, and their keys | None |
| Query | The *_aud history tables, joined to revinfo and sysuser | None |
| Query | The audited table, to resolve an id to a name | None |
API saveFile | Writes the CSV export that the user asked for | None |
The page makes no other API call. The page writes nothing to Fishbowl.
Everything runs inside the Fishbowl client. No data leaves it. The user starts the CSV export and chooses where to save it.
Settings
The page has no settings. Nothing inside the page can be configured.
Change where the page appears in the CloudPages plugin page Edit dialog:
| Placement | Default |
|---|---|
| Path | Reports:ILC Products |
| Modules | All |
| Toolbar button | Shown, labelled AuditTrail |
A module toolbar button enables the module-aware launch. Open the page from a record toolbar, and the page loads the history for that record. Remove the page from a module, and the button goes with it.
The row limit is fixed at 5000 revisions for each lookup. No setting changes it.
Troubleshooting
A table is not in the list
- Symptom: the audited-table list does not offer the table.
- Cause: Fishbowl does not audit that table.
- Fix: none. Fishbowl decides which tables it audits.
No deletions appear
- Symptom: a deleted record has no delete row.
- Cause: Fishbowl auditing records what was added and what changed.
- Fix: none.
History starts later than the record does
- Symptom: the history of an old record starts at a recent date.
- Cause: somebody truncated the audit tables.
- Fix: none. The page cannot read what was removed.
Ids show instead of names
- Symptom: a row shows
4where a name is expected. - Cause: the page found no name column and no number column on the table.
- Fix: request the mapping through support.
Only the most recent revisions appear
- Symptom: the history of a record stops short.
- Cause: a lookup returns 5000 revisions at most.
- Fix: narrow the date range or the change type. Load the history again.
A user cannot open the page
- Symptom: one user sees the page and another user does not.
- Cause: that user has no page access.
- Fix: grant access in the CloudPages plugin page Edit dialog.
Before a support request
The page has no debug button. Collect:
- The Fishbowl version and the page version.
- The audited table and the record id.
- The browser console output.
- A screenshot of the page.