Skip to content

Resource - Scenario

Wogeez Engine Wogeez Engine

Overview of Scenarios

In Wogeez, a scenario defines an interactive flow designed to be displayed on a physical device, such as a kiosk. A scenario is composed of:

  • Resources, such as images, tickets, forms, or videos
  • Steps, which define the sequence of screens and actions the user will follow
  • Triggers, which define when the scenario should start or stop
  • Jumps, Navigation rules and user interactions

Scenarios are delivered as a package (an archive file) that contains all the necessary assets and configurations for playback.

For details on how to structure or edit a scenario package, please refer to the developer documentation.

Versioning in Scenarios

Every time you make a change to a scenario, you can create a new version. This versioning system allows you to:

  • Track and organize changes over time
  • Test updates without losing the previous version
  • Quickly roll back if needed
Danger

If you upload a scenario using an existing version number, the current version will be overwritten. Always make sure to update the version number before publishing changes to avoid accidental data loss.

Managing Visual or Content Variants

If you want to create alternate versions of a scenario (e.g., for different logos, languages, or branding), it's recommended to create separate scenarios, not just new versions. Versions should reflect the evolution of a single scenario—not different variations for different audiences.

Deploying Scenarios with Flexibility

Wogeez supports flexible deployment strategies, allowing you to gradually roll out or test changes:

Continuous Deployment

Push updated scenarios automatically to devices as soon as a new version is ready. This ensures users always get the most recent experience.

Canary Releases

Deploy a new version to a small number of devices first, to test and monitor how it performs in real-world conditions before deploying to all devices. This reduces the risk of bugs impacting all users at once.

A/B Testing

Deploy two or more versions of the same scenario across different groups of devices or locations. This allows you to compare performance, measure engagement, and choose the best version based on real data.

Deploying Scenarios to Devices

Scenarios can be deployed to one or more devices that are equipped with the Wogeez engine (such as interactive kiosks). Wogeez allows you to:

  • Assign one or several scenarios per device
  • Deploy specific versions of a scenario, independently of others
  • Push updates to individual devices or in batches across multiple kiosks

This gives you full flexibility to control how and where each scenario is used, whether you need to update just one device in a location or roll out a new version across an entire network.

Scenario Engine and Playback

Wogeez Engine

The scenario engine is the component that reads and displays the scenario on the device, this engine is called Wogeez Engine.

  • Each device can be configured to use a specific engine version.
  • Currently, there is only one version of the Wogeez Engine available.

The scenario version (your content updates) is not the same as the engine version (how the device renders it).

Storage and Quota Usage

Each version of a scenario is stored separately and uses disk space. This storage counts against your company’s allocated quota.

To manage this efficiently:

  • Delete outdated or unused versions regularly
  • Avoid uploading redundant or oversized media files

Best Practices

  • Use versioning to manage evolutions of the same scenario
  • Use separate scenarios for alternate versions (branding, region-specific content, etc.)
  • Change the version number before uploading to prevent overwriting
  • Name your versions clearly for easy tracking
  • Monitor your storage usage and clean up regularly
  • Refer to the user documentation for guidance on how to prepare and manage your scenario package

Summary

Element Description
Scenario Interactive user journey for kiosks
Scenario format Provided as a packaged archive (bundle of content + configuration)
Scenario version Tracks changes and evolution of a scenario over time
Overwrite risk Yes – if using the same version number during upload
Variations strategy Use separate scenarios for each branding or visual variant
Scenario engine "Wogeez Engine" – handles how the scenario is displayed on devices
Engine version Only one available today (not to be confused with scenario version)
Storage usage Each version uses disk space, counts against your company’s quota