Operator guideENchallengesformcreateedit

Challenges / Create And Edit

Create and edit flow for challenge title, game, multiplier goal, currency thresholds, prize setup, creator identity, and lifecycle flags.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this surface does

This docs pack covers both challenge creation and challenge editing, but the FE uses two different interaction models:

  • /challenges/create is a five-step creation wizard
  • /challenges/:id is a single-screen edit form with a duplicate shortcut and right-side preview helpers

Both paths configure the same underlying challenge payload: title, game target, multiplier/min-bet goal, optional prize definition, creator identity, targeting tags, and active state.

Create mode vs edit mode

Create mode

Create mode is a guided wizard with these steps:

  1. Game & Title
  2. Challenge Goal
  3. Prize Setup
  4. Creator Info
  5. Visibility

Each step uses Next Step to advance. The first two steps are the only ones with hard FE validation:

  • Game & Title requires a selected game and non-empty title
  • Challenge Goal requires a valid multiplier greater than 0

Prize Setup, Creator Info, and Visibility can remain empty from the FE point of view, although operators usually still review them before final submit.

Edit mode

Edit mode renders one long page instead of the wizard. It adds:

  • Duplicate in the page header
  • a live Edit Preview sidebar
  • Original Challenge Info with the current record id, stored status, and created date

Edit mode only exposes Active as the visible lifecycle toggle. The stored backend status is still sent back in the update payload, but the operator is not editing it through a dedicated status input on this screen.

What operators should enter carefully

  • Game and Multiplier define the core goal.
  • Currency minimum bet values should be reviewed carefully because they shape challenge eligibility.
  • Active controls whether the challenge remains enabled after save.
  • Prize is configured in its own reward block and can represent different reward models, but the FE does not block save when the prize step is empty.
  • Allow Bonus Participation changes how bonus-using players are treated in the challenge.
  • Created By identity and image are operator-facing presentation fields used in challenge display.
  • Search player is a helper workflow that can prefill creator name and user id before the operator fine-tunes the visible attribution.

Common caveats

  • The create page auto-fills some values from the selected game and from creator loyalty information.
  • Currency setup is a two-step workflow: set EUR first, then optionally Auto-calculate All and expand Show other currencies for manual overrides.
  • Creator image configuration has two source modes: direct URL or selected asset.
  • Create mode submits a fixed status: active payload. Edit mode keeps the existing challenge status in the update payload even though only Active is visibly editable.
  • Duplicate on the edit page is not a dedicated clone endpoint. The FE rebuilds a create payload from the current form values and calls the normal create mutation.
  • The right-side preview card and original challenge metadata are display helpers only. They do not save, publish, or close the challenge.
  • A challenge can be admin-created while still depending on player-side challenge runtime afterward.
Operational notes

Notes

item

Admin create/edit lives in gs-admin-backend, but create and edit do not share the same FE interaction model.

item

Create mode is a five-step wizard with local step validation and a final create submit.

item

Edit mode is a single-screen editor with `Duplicate`, live preview, and original-record metadata.

item

`Duplicate` on the edit page still uses the standard create mutation instead of a dedicated clone route.

item

The create page can auto-fill title from the selected game and creator image defaults from loyalty data.

item

Casino-side runtime should be checked only when challenge progression or winner outcome disagrees with admin expectations.

Related references

Related pages

pageChallenges

Operator documentation for challenge catalog management, challenge editing, winner handling, permission rules, and automatic generation configs.

pageChallenges / Detail

Operator detail surface for one challenge record, including edit sections, duplicate flow, and original challenge metadata.

pageChallenges / List

Main challenge catalog with status tabs, source tabs, active toggle, row actions, and winner lookup.

pageActivity Tag Rules / Create

Create flow for a new activity tag rule, including optional clone-from-existing behavior and condition testing.

pageActivity Tag Rules / Edit

Edit flow for one backend rule or a grouped add and remove pair, including split or merge behavior and condition testing.

pageAffiliate Deals / Form

Create and edit form for affiliate deals, including PID, date window, commercial terms, and responsible person.