Operator guideENbonusesformcreateedit

Bonuses / Create And Edit

Create and edit workspace for reusable bonus definitions, including targeting, per-currency reward settings, and linked promotional content.

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 surface is the full create and edit workspace for reusable bonus definitions.

Even though the first create step opens as a modal from the list page, operators should treat the whole flow as one form surface because it controls both:

  • the bonus record itself
  • linked promotional content such as bonus banner and bonus page content

When to use create vs edit

  • Use Create when you need a new reusable bonus definition with its own type, validity, and content.
  • Use Edit when the bonus already exists and you need to change validity, activation logic, targeting, currency economics, or content.
  • Use the header Duplicate shortcut only as a quick way to open the create modal from the edit page. In the verified FE flow it does not clone the current bonus automatically.

Form map

The full workspace is split into four operator-facing sections:

  • General Covers the saved bonus type, status toggles, wagering type, schedule, activation timing, and type-specific settings.
  • Settings Covers tags, coupon codes, redirect URL, game or category targeting, and include or exclude country rules.
  • Currency Repeats reward-economics settings per currency code, with the visible keys controlled by the selected bonus type.
  • Content Covers banner text, bonus-page content, linked assets, and links into CMS banner/page editing after save.

What operators should enter carefully

  • Bonus Type is the main branch selector. It controls which currency keys and advanced fields the FE shows later.
  • Valid From, Valid Till, Time From, Time Till, and Valid Days together define the usable schedule.
  • Activation fields such as Times to Activate Per Player, Activation Period to Check, Drop Start DateTime, and Activated Bonus Expiration Period should be reviewed together because they govern eligibility timing.
  • Include Tags, Exclude Tags, Coupon Codes, Next Coupon Codes, and geographic restrictions shape who can reach the bonus.
  • Free Spins Games is mandatory for freespins. The FE blocks save if the game list is empty for that bonus type.
  • Per-currency settings should be reviewed in the EUR base first before operators use FE auto-calculation for other currencies.
  • Auto Payout should be treated as the main cashback-behavior switch for instant_cashback. If it is off, operators should not expect the bonus to behave like an automatically paid cashback configuration.
  • Auto Payout Days and the payout-distribution editor should be reviewed together. If the distribution does not total 100%, the FE highlights the issue and offers auto-balance.
  • Banner and bonus-page content are part of the same workflow. Operators usually save the definition first, then open the linked CMS page or banner for translation polish.

Marketing-facing explanation for instant cashback payout settings

For marketing users, Auto Payout answers one practical question:

  • should this instant_cashback bonus behave as an automatically paid cashback configuration

Use this as the working rule:

  • Auto Payout = ON means the bonus is configured for automatic cashback payout behavior
  • Auto Payout = OFF means the bonus stays an instant_cashback definition, but operators should not expect it to participate in auto-paid cashback flows

This flag matters together with Auto Payout Days:

  • if Auto Payout is on, Auto Payout Days defines the payout timing window
  • if Auto Payout Days is greater than zero, the FE reveals the payout-distribution editor so operators can split the payout percentage across days
  • if Auto Payout is off, Auto Payout Days and payout distribution lose most of their practical marketing meaning because the bonus is no longer being prepared as an auto-paid cashback setup

One downstream effect is already visible in FE:

  • the manual rakeback flow filters bonuses to instant_cashback bonuses where Auto Payout is enabled

So for marketing configuration, the safe interpretation is:

  • enable Auto Payout when the campaign should be treated as an auto-paid cashback offer
  • disable it when the bonus should remain an instant_cashback definition without entering the auto-paid cashback selection flow

Common caveats

  • The create modal bootstraps promotionTitle, termCondition, and description from Bonus Name before the first save.
  • New bonuses start with all weekdays enabled and a long validity window. Operators are expected to narrow that down where needed.
  • Bonus Type is chosen during create. In the edit workspace it is shown as a saved chip, not as a mutable field.
  • NoDeposit appears only for freespins and no_deposit variants.
  • Period To Check NGR, Auto Payout, and Auto Payout Days appear only for instant_cashback.
  • Auto Payout Days > 0 reveals the payout-distribution editor in the FE.
  • Auto Payout is not just cosmetic. In current FE behavior it also affects which instant_cashback bonuses can be selected in the manual rakeback flow.
  • Save order on the edit page is not just one request. The FE updates the core bonus, updates tags, then creates or updates linked CMS banner/page content, and finally publishes those linked content records.
  • Update and Translate is an FE content helper path around the same save flow. It tries to translate linked banner and page content after updating them.
  • Linked CMS page and banner routes become useful only after the bonus has been saved and has a stable bonusId.
Calculation notes

Calculations

calculation

Create bootstrap from bonus name

The initial create step generates placeholder promo title and text from the chosen bonus name.

Inputs
bonusName, promotionTitle, termCondition, description
Transform
In the create modal, the FE seeds `promotionTitle`, `termCondition`, and `description` from `bonusName` before the first save.
calculation

Create bootstrap validity window

Operators start from a fully open schedule and then narrow the validity window if needed.

Inputs
validFrom, validTo, validOnDays
Transform
New bonus creation starts with today's date as `Valid From`, a far-future `Valid Till`, and all weekdays enabled.
calculation

Bonus type controls currency keys

Changing the bonus type changes which currency settings appear and which amounts the operator is expected to fill in.

Inputs
bonusType, currency
Transform
The FE selects the allowed per-currency keys from `BONUS_TYPE_CURRENCY_SETTING_FIELDS[bonusType]`.
calculation

NoDeposit settings visibility

Operators see this toggle only for reward types that can behave like no-deposit bonuses.

Inputs
bonusType, noDepositFreespins
Transform
The `NoDeposit` selector is shown only when the bonus type is `freespins` or `no_deposit`.
calculation

Type-specific settings visibility

Operators should expect different advanced settings depending on the reward family they selected.

Inputs
bonusType, freeSpinsCount, freeSpinsSetup, freespinsTargetWinAmount, periodToCheckNgr, autoPayout, autoPayoutDays
Transform
`freespins` exposes free-spin count, bet level, and target-win fields; `instant_cashback` exposes NGR-period and payout fields.
calculation

Auto payout is the cashback-behavior gate

Marketing users should decide `Auto Payout` first, then configure payout timing and distribution.

Inputs
bonusType, autoPayout, autoPayoutDays
Transform
For `instant_cashback`, the FE treats `autoPayout` as the main switch for automatic cashback behavior; `autoPayoutDays` only refines the payout schedule after that path is enabled.
calculation

Auto payout distribution visibility

Payout splitting is configured only for cashback bonuses that have a multi-day automatic payout schedule.

Inputs
autoPayoutDays, percentDays
Transform
The FE reveals the payout-distribution editor only when `Auto Payout Days` is greater than zero.
calculation

Payout distribution total must equal 100%

Operators should treat payout distribution as a complete percentage split rather than unrelated day rows.

Inputs
autoPayoutDays, percentDays
Transform
The FE calculates the total of `percentDays`, warns when it is not `100%`, and exposes `Auto-Balance to 100%` as a corrective helper.
calculation

Manual rakeback bonus selection requires auto payout

Turning off `Auto Payout` removes the bonus from the current manual rakeback bonus-selection flow.

Inputs
bonusType, autoPayout
Transform
The FE manual rakeback modal filters the bonus list to `instant_cashback` bonuses where `autoPayout` is enabled.
calculation

Free spins require game selection

Free-spin bonus definitions are incomplete until operators choose eligible games in the settings section.

Inputs
bonusType, gameIds
Transform
Before save, the FE blocks `freespins` bonuses that do not have at least one selected game id.
Operational notes

Notes

item

The create modal bootstraps `promotionTitle`, `termCondition`, and `description` from `bonusName` before the first save.

item

The create modal also seeds `validOnDays` to all weekdays and computes a per-currency payload from the selected `bonusType`.

item

The edit workspace is split into General, Settings, Currency, and Content sections, and each section contributes visible FE-only conditional logic.

item

The FE normalizes `autoPayout` from boolean or `0/1`-style backend payloads before rendering the edit form.

item

`autoPayout` also participates in downstream FE behavior: the manual rakeback modal lists only active `instant_cashback` bonuses where `autoPayout` is enabled.

item

The edit flow persists the core bonus first, then saves tags separately through `update-bonus-tags`, then updates linked CMS banner/page content and publishes those linked records.

item

Banner/page translation and publishing helpers live in the FE flow around the core bonus write path and linked CMS routes.

item

`Update and Translate` is not a distinct backend bonus route; it is an FE orchestration path that wraps bonus save plus banner/page translation helpers.

item

No explicit nx-workspace dependency is required for the current form documentation.

Related references

Related pages

pageBonuses

Operator documentation for bonus catalog management, bonus editing, and player-issued bonus follow-up.

pageBonuses / List

Main working catalog for bonus definitions with search, archive mode, type filters, group filters, and row actions.

pageBonuses / View

Read-only bonus detail screen used to inspect one reusable bonus definition before editing it.

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.