Snapshots, Presets & Schedules

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

Open Reporting -> Reports -> Snapshots & Presets for saved report context and frozen outputs.

Open Reporting -> Reports -> Schedules for recurring report runs.

Workspace Reference

Workspace	Main Action	Main Record
Presets	Save, apply, edit, or remove preset	Reusable parameter set for one report.
Snapshots	Create, open, pin, expire, or clean up snapshot	Point-in-time report output.
Schedules	Create, edit, pause, resume, or review schedule	Recurring report execution rule.

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

Important preset fields:

Field	Required	Meaning
Report	Yes	Report the preset belongs to.
Preset name	Yes	Business-facing name users can recognize.
Parameters	Yes	Saved date range, currency, business unit, template, column set, or other report filters.
Default status	Optional	Whether the preset should load automatically for the report.
Shared or private scope	Optional	Whether other users can use the preset where supported.

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.

Important snapshot fields:

Field	Meaning
Report	Report output captured by the snapshot.
Snapshot label	Business-facing label for the saved output.
Parameters	Scope used when the snapshot was created.
Pinned status	Whether cleanup should preserve it.
Created time	When the output was captured.
Expiry time	When an unpinned snapshot can be cleaned up.

Cleanup

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

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

Schedules

Schedules automate recurring report execution.

Core schedule fields typically include:

Field	Required	Meaning
Report	Yes	Report to run automatically.
Schedule name	Yes	Business-facing schedule name.
Schedule timing	Yes	When the report should run.
Output format	Recommended	PDF, Excel, CSV, or another supported format.
Snapshot label template	Recommended	Naming pattern for saved scheduled outputs.
Max retries	Recommended	How many times the system should retry after failure.
Active	Yes	Whether the schedule should run.

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