Provide configurable output options for PAW Burst Export instances

Dear team,

Background

Planning Analytics Workspace allows users to burst a Book based on synchronized hierarchies.

The current Burst Export functionality allows users to select an export format such as PDF / Powerpoint or ZIP. However, the way individual burst instances are delivered is largely predefined.

For ZIP export, PAW creates an individual file for each burst instance and packages the files into a ZIP archive.

While this behavior is useful for distributing individual reports, it does not cover all reporting requirements.

Example

Assume the Year hierarchy is selected for bursting and contains:

• 2024

• 2025

• 2026

The current ZIP behavior produces:

Report_2024.pdf
Report_2025.pdf
Report_2026.pdf

inside a ZIP archive.

There is currently no option to choose how these burst instances should be aggregated or delivered.

Requested enhancement

Provide an explicit Burst Output configuration that allows users to control how burst instances are generated.

For example:

• Single file containing all burst instances

• Separate file for each burst instance

• Separate files packaged into a ZIP archive

The available options could depend on the selected export format.

Example output options

Single file

Report.pdf

Containing all selected burst instances.

Separate files

Report_2024.pdf
Report_2025.pdf
Report_2026.pdf

ZIP package

Report.zip
  ├── Report_2024.pdf
  ├── Report_2025.pdf
  └── Report_2026.pdf

Rationale

The current implementation combines two different concepts:

1. Export format

2. Output aggregation of burst instances

These should ideally be configurable independently.

For example, selecting ZIP currently determines that every burst instance becomes an individual file. Users should instead be able to explicitly decide whether burst instances should be combined, separated, or packaged.

Additional consideration

Similar flexibility already exists in other PAW export functionality, where users can choose between exporting content into a single file or multiple files.

Providing equivalent control for Burst Export would make the behavior more consistent and significantly improve flexibility for reporting scenarios.

Expected benefit

Users could configure Burst Export according to their reporting and distribution requirements without having to create workarounds or additional processes.

It would also make the relationship between burst dimensions, burst instances, export format, and output packaging much clearer.

Thanks in advance.

With best regards,
Vitalij