Custom Report Screenshots for Slides with Nested Popup States

Custom Report Screenshots for Slides with Nested Popup States

When generating PDF reports in Activator, slides that contain nested popups present a challenge: the default screenshot mechanism only captures the base slide state. Popup states — and states nested inside other popups — do not automatically appear in the generated PDF.

This article explains the manual workaround for capturing all relevant states in the report.

The Problem

Activator’s default report generation captures one screenshot per slide. If a slide has popup states, those states will not appear as separate screenshots in the PDF report unless explicitly configured.

This becomes more complex with nested popups, where a popup contains a secondary popup. In this scenario, both the intermediate state and the final nested state need to be captured. 

Workaround: Manually Define Report States

Report states can be defined explicitly in the slide’s script.js file. This is a developer task. The configuration overrides the default automatic screenshot behaviour and specifies exactly which state combinations should be captured.

Example

Add the following to the script.js file of the affected slide:

JavaScript
if (window.Fusion) {
  console.log('Adding custom report states');
  window.Fusion.reportStates = [
    ['Popup-pop1'],
    ['Popup-pop1', 'ReferencePopup-refs']
  ];
}

What this produces

With the configuration above, the PDF report will contain three screenshots:

  • Screenshot 1: The slide with no active states (base state)

  • Screenshot 2: The slide with Popup-pop1 open

  • Screenshot 3: The slide with Popup-pop1 open, and ReferencePopup-refs (nested inside Popup-pop1) also open

Important: Maintaining Manual States

Once manual report states are configured, they must be actively maintained. If further popup states are added to the slide in the future, the reportStates array must be updated accordingly.

Failing to update the configuration will result in new states being omitted from the PDF report.

Future Improvement

Manual configuration via script.js is a temporary workaround. Support for managing report states directly from the Activator UI is planned for a future release.