Operator guideENbonus-triggerslistconfiguration

Bonus Triggers / List

Single-page trigger configuration workspace with one editable card per trigger, coupon-code chip management, expiration time editing, comments, and a full-form submit action.

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 is the only verified route for Bonus Triggers.

Operators use it to inspect each existing trigger card, update the attached coupon codes, adjust expiration time, and save the full trigger configuration.

How the page is organized

  • the page shows one card per trigger returned by the hook
  • each card uses the trigger name as the card title
  • the left side of the card manages coupon-code chips
  • the right side stores expiration time and free-text comments
  • the footer actions let the operator return to Bonuses or submit all current changes

How to read the page

  • Coupon Codes is a multi-value chip field. Each chip is one code currently attached to the trigger.
  • Expiration Time (minutes) is the numeric validity window stored for the trigger.
  • Comments is operator-facing free text kept on the trigger record.

Main actions

  • add one coupon code to a trigger card
  • remove one coupon-code chip from a trigger card
  • submit the full trigger configuration
  • return to the Bonuses route without saving

Known caveats

  • The page currently edits only the trigger records returned by the route. There is no verified FE action to add a new trigger card or delete a trigger card.
  • Submit sends the whole bonusTriggers payload after converting coupon-code arrays back into comma-separated strings.
  • The success condition and backend ownership are only visible through the FE hook in this pass, so backend semantics stay unverified here.

Verification status

  • status: verified_fe_only
  • verified FE route:
    • /bonus-triggers
Operational notes

Notes

item

The FE route renders editable trigger cards directly from the hook response.

item

The update hook posts one `bonusTriggers` payload after converting coupon-code arrays back into comma-separated strings.

item

Backend controller or service ownership was not traced in this pass, so the route stays FE-verified only.

Related references

Related pages

pageBonus Triggers

Operator documentation for the bonus trigger configuration screen used to maintain trigger names, coupon-code mappings, expiry minutes, and comments.

pageActivity Tag Rules / List

Main inventory for activity-driven tag rules, with search, activity and status filters, grouped rows, clone, edit, and run actions.

pageAffiliate Deals / List

Searchable table of affiliate deal rows with PID filter, create action, dashboard shortcut, and edit/delete row actions.

pageAffiliate Payment Settings / List

Affiliate payment settings inventory page for reviewing configured rows and opening saved records.

pageAffiliate Settings / List

Affiliate inventory list used to review saved affiliates and open detail or report flows.

pageAuto Tags Manager / List

Rule inventory with search, direct navigation to create or reorder, row-level run controls, and job history or recovery actions.