Snapshots, Presets & Schedules

This page covers the reusable and automated parts of PinkApple reporting.

Navigation:

• Reporting -> Reports -> Snapshots & Presets
• Reporting -> Reports -> Schedules

Presets

Presets save reusable report parameter combinations.

Use presets when a user or team repeatedly runs:

• the same report
• with the same scope
• with the same date logic
• with the same currency or business-unit selection

Typical preset contents can include:

• date range
• business-unit selection
• currency
• FS template
• column set

Presets are best for speeding up repeatable manual work and reducing user-entry mistakes.

How presets behave in Run Reports

When a user selects a report in Run Reports:

1. the report definition loads
2. any saved presets for that report are fetched
3. the default preset, if one exists, can prefill the parameter area
4. the user can click another preset to replace the current parameter pack before generating

This is why presets should be:

• tied to the correct report code
• named clearly for business use
• validated in runtime before being shared widely

Snapshots

Snapshots preserve the output of a report at a specific point in time.

Use snapshots when:

• month-end or quarter-end outputs must be preserved
• a reviewed management pack should remain frozen
• audit or follow-up work needs a stable historical reference

What users usually see

The snapshots list typically shows:

• snapshot ID
• report code
• snapshot label
• pinned status
• creation time
• expiry time

Opening a snapshot loads the stored output back into the report viewer.

Cleanup

Expired, non-pinned snapshots can be removed through cleanup actions in:

• Administration -> Reporting -> System Settings -> System Admin
• the snapshot area where cleanup is exposed

Schedules

Schedules automate recurring report execution.

Core schedule fields typically include:

• report code
• schedule name
• cron expression
• output format
• snapshot label template
• max retries
• active

Use schedules for:

• morning dashboards
• weekly exception reports
• recurring month-end packs

Only schedule a report after it has passed manual validation in Run Reports.

Good Schedule Practices

• validate the report manually before scheduling it
• keep schedule names business-readable
• use stable report codes
• choose the output format based on the audience
• review next-run, last-run, and failure indicators regularly

When To Use Each One

Feature	Best use
Preset	Reusing parameters for repeated manual execution
Snapshot	Preserving a point-in-time output
Schedule	Automating repeated execution

Related Pages

• Operations & Usage
• Running Reports
• System Settings