What this module is for

The Wheel of Fortune module is the CRM workspace for configuring promotional wheels that can later be shown on the casino side.

Operators use it to:

• keep a catalog of wheel records
• create a new wheel through a five-step wizard
• continue working on an unpublished draft
• publish a completed wheel
• update a published wheel without recreating it

Surfaces in this module

• List: main catalog with Active and All tabs, inline activation toggle, edit, and delete.
• Form: create wizard used to bootstrap a new draft and complete the required wheel setup.
• Detail: manage/edit wizard for an existing wheel, including step saves, publish, and post-publish updates.

What operators usually get confused about

• Status in the list is not a free text field. Unpublished records always appear as not finished, even if some step data is already saved.
• Active is a visibility switch. Publishing and activation are related but not identical. The Active tab also includes unpublished drafts because the backend active filter returns status='active' rows plus isPublished=false rows.
• A create flow does not immediately publish. The first saved step can create an unpublished server-side draft.
• A newly created backend draft is stored as unpublished. Backend create keeps it inactive until the visibility step has been completed and submitted.
• Delete uses the backend paranoid model and removes the row from the active catalog by setting deletedAt.
• Preview links are FE helpers. They build a wheel URL and claim URL from current form values and casino origin settings, but they do not publish the record by themselves.

Verification scope

This module is verified from:

• frontend support hooks used for casino origin, languages, translations, and assets
• casino-side player runtime only as a downstream path for preview/claim interpretation