Operator guideENbonus-mapformbonusesloyalty

Bonus Map / Form

Shared create-and-edit form that captures a Bonus Map name, unique key, title and button translations, and the campaign period.

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 page does

This is the shared form used both to create a new Bonus Map and to edit an existing one. The create screen and the edit screen render the same wizard section, so the first-step fields are identical in both places.

What operators capture here

  • Map name: the campaign name
  • Internal Key: a unique key for the map
  • title, subtitle, and claim-button text translations per language
  • Period start and Period end dates for the campaign

How create and edit differ

  • On create, saving the first step builds a backend draft and then sends the operator straight to the edit screen for that new map.
  • On edit, saving the first step updates the existing draft in place and shows a saved message.
  • The edit screen adds further wizard steps beyond this shared form (visuals, layout, marketing tracking) plus generate-days, translate, confirm-period, and publish actions. Those steps are separate surfaces and are not detailed here.

Why operators open this screen

  • start a new daily-prize campaign
  • rename a map or fix its translations
  • adjust the campaign period before days are generated

Known caveats

  • A new map is created as a draft. Nothing is visible to players until the map is later published from the edit screen.
  • Map name and Internal Key are required, and the key must be unique. Saving with a duplicate key or an invalid period is rejected with an error.
  • The create form does not capture every detail of the map. Visuals, render layout, day generation, and publishing happen on the edit screen after the draft exists.
  • Editing requires BonusMap update permission and creating requires BonusMap create permission; without it the page shows a no-permission notice.

Verification status

  • status: verified_backend
  • FE flow checked from bonus-map/create.tsx, bonus-map/[id].tsx, and the shared wizard hooks
  • backend create and update paths traced to gs-admin-backend bonus-map services
Field dictionary

Fields

field

Map name

Campaign name for the map; required, and used as the title when no separate title is set.

Data Type
string
Editable
true
Required
true
field

Internal Key

Unique key for the map; required and rejected on save if it already exists.

Data Type
string
Editable
true
Required
true
field

Title translations

Per-language title text shown to players for the map.

Data Type
translations-map
Editable
true
field

Subtitle translations

Per-language subtitle text for the map.

Data Type
translations-map
Editable
true
field

Claim button text translations

Per-language label for the claim button players press.

Data Type
translations-map
Editable
true
field

Period start

First date of the campaign period; validated against the end date on save.

Data Type
date
Editable
true
field

Period end

Last date of the campaign period; validated against the start date on save.

Data Type
date
Editable
true
Operational notes

Notes

item

Create validates that mapName and internalKey are present, that internalKey is not already used, and that the period is valid, then inserts a BonusMap row with isPublished false.

item

Create always returns a draft: isPublished, publishedAt, and daysGeneratedAt are forced to unpublished and null on insert.

item

The create page sends only the first-step fields (name, key, title/subtitle/claim-button translations, period) and then redirects to the edit route for the new id.

item

Update applies a partial patch to the existing row; if the map is already published, or the patch sets the publish flag, the service re-validates the publish payload before saving.

item

Routes require authentication only; the BonusMap create and update permissions are enforced in the FE, not by route middleware.

item

No nx-workspace core dependency is involved in the create, read, or update paths.

Related references

Related pages

pageBonus Map

Operator guide for building retention Bonus Map campaigns, a draft-first calendar of daily prizes that players claim across a fixed period.

pageBonus Map / List

Grid of all Bonus Map campaigns with derived lifecycle status, period, generated-day progress, and create, edit, and delete controls.

pageAffiliate Deals / Form

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

pageAffiliate Payment Settings / Form

Create and edit form for one affiliate payment-setting record, with visible PID targeting, minimum deposit threshold, and active-state control.

pageAuto Tags Manager / Create

Full rule-builder for a new automatic tagging rule, including tag actions, coupon actions, KPI field selection, and draft impact estimation.

pageAutomatic Withdrawal / Form

Create and edit form for one automatic-withdrawal rule, including thresholds, KYC, countries, methods, tags, and per-currency limits.