Appearance
Reporting System Settings
The System Settings workspace contains the cross-cutting controls that support the whole reporting module.
Navigation: Reporting -> Setup -> System Settings where available
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| System Settings | Reporting -> Setup -> System Settings where available | Maintain approved data sources, system admin actions, schedules, elimination rules, and maintenance controls. |
| Report Catalog | Reporting -> Setup -> Report Catalog | Use approved data sources in report definitions. |
| Run Reports | Reporting -> Reports -> Run Reports | Validate reports before scheduling or snapshotting them. |
| Snapshots, Presets, And Schedules | Reporting -> Reports or Reporting setup areas where available | Maintain trusted recurring outputs and clean up expired snapshots. |
Tabs In This Screen
- System Admin
- Schedules
- Elimination Rules
- Approved Data Sources
These are administration tools. They should be maintained deliberately because they affect multiple reports, not just one.
Approved Data Sources
Approved data sources are the most important system setting for report setup.
They are the bridge between:
- governed report logic
- report-definition setup in the catalog
Use it to:
- expose approved sources to definition lookups
- keep unsupported sources out of the catalog
- support seeded or system-generated report setup
- keep runtime definitions aligned to what the system actually supports
Whenever a report source is:
- added
- materially changed
- retired
review the approved data-source list first.
System Admin
The System Admin tab exposes maintenance actions for the reporting domain.
Seed System Catalog
Use this when you want Pinkapple to populate default system report definitions.
Good use cases:
- a fresh tenant needing a baseline catalog
- a controlled rebuild after a reporting cleanup
Do not use catalog seeding as a substitute for governance. Seeded content still needs review and activation discipline.
Cleanup Expired Snapshots
Use this to remove expired, non-pinned snapshots and keep reporting storage under control.
This is periodic maintenance, not a day-to-day end-user action.
Schedules
Schedules create recurring report runs using cron-based timing.
Core fields usually include:
- report code
- schedule name
- cron expression
- output format
- snapshot label template
- max retries
- active
Only schedule a report after it has already been validated in Run Reports.
Good schedule practice:
- start with a clear business schedule
- use stable report codes
- choose the output format deliberately
- keep snapshot labels readable
- monitor failed or stale schedules regularly
Elimination Rules
Elimination rules support consolidated reporting where inter-company or inter-unit balances must be removed from consolidated views.
Use them only when consolidated reporting has been designed formally with finance ownership. They should not be created casually.
Recommended Operating Order
Use the system settings area in this order:
- review Approved Data Sources
- build or seed the Report Catalog
- validate reports in operations
- activate Schedules
- run snapshot cleanup periodically