Operator guideENtagsruleslist

Activity Tag Rules / List

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

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 shows

This page is the operational inventory for all saved activity tag rules. Operators use it to find an existing rule, confirm which activity it listens to, see which tags it adds or removes, and open the appropriate detail or edit flow.

How to read the list

  • ID is the primary backend rule identifier used for navigation and audit lookups.
  • Rule Name is the visible grouped rule name after FE removes the (Add) and (Remove) suffixes when possible.
  • Activity shows which activity event must happen before the rule can apply.
  • Tags shows the visible + tag and - tag chips for grouped rows.
  • Priority controls execution order. Higher values are processed first.
  • Status is the backend isActive state rendered as a badge.

Main actions

  • Create Rule opens the create flow.
  • Edit opens the grouped editor. When the row represents both add and remove actions, FE passes both backend IDs to the edit page.
  • Clone Rule opens the create page with one existing rule preloaded.
  • Run calls the backend execution endpoint for the visible rule or for both grouped rule IDs.

Important caveats

  • The row grouping is a frontend convenience. Operators should not assume one visible row means one stored backend row.
  • Run is available from the list, but the currently verified backend execution service returns a placeholder result shape and does not prove a complete batch-processing implementation.
  • Search is applied after the backend list response is returned, so it behaves like FE-side filtering over the fetched page.
Calculation notes

Calculations

calculation

Grouped Rule Row

Formula Text
FE groups backend rows by the same base name after removing ` (Add)` and ` (Remove)` suffixes, the same `activityId`, and priorities within a difference of 1.
Operator Note
One visible row can represent two backend rules.
Verification Status
verified_fe_only
calculation

Grouped Priority Pairing

Formula Text
When FE builds a grouped add/remove pair, the remove rule is expected to sit one step below the add rule priority.
Operator Note
This pairing assumption is FE-owned and drives grouped-row display.
Verification Status
verified_fe_only
calculation

Visible Timestamps

Formula Text
`createdAt` and `updatedAt` are formatted in FE as `yyyy-MM-dd HH:mm` before rendering the grid.
Operator Note
This is presentation logic only.
Verification Status
verified_fe_only
Grid columns

Columns

field

ID

Primary backend rule identifier used as the row navigation key.

Visual Type
grid-column
field

Rule Name

Visible grouped name for the rule row after FE removes `(Add)` or `(Remove)` suffixes where possible.

Visual Type
link
field

Activity

Activity event that triggers the rule logic.

Visual Type
badge
field

Tags

Shows which tag will be added and which tag will be removed when the grouped rule is viewed as one operator row.

Visual Type
chip-group
field

Priority

Execution order for backend rule processing. Higher values are intended to run first.

Visual Type
grid-column
field

Created

Rule creation timestamp after FE formatting.

Visual Type
datetime
field

Updated

Last update timestamp after FE formatting.

Visual Type
datetime
field

Status

Backend active-state flag for the rule.

Visual Type
badge
field

Actions

Shortcut actions for edit, clone, and backend run.

Visual Type
action-group
Filter dictionary

Filters

field

Search

Searches by rule name or tag name inside the current fetched result set.

Type
text
Affects
list_results
field

Activity

Limits the list to rules attached to one tracked activity.

Type
select
Affects
list_results
field

Status

Limits the list to active or inactive backend rules.

Type
select
Affects
list_results
Operational notes

Notes

item

The FE list groups related add/remove rules before rendering the grid.

item

Search filtering is applied in FE after the backend page response is received.

item

No gs-casino-backend dependency was required for the current list surface.

Related references

Related pages

pageActivity Tag Rules

Operator documentation for activity-driven tag automation rules, including list, create, edit, detail inspection, and recent application history.

pageActivity Tag Rules / Create

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

pageActivity Tag Rules / Detail

Rule inspection page with backend identity, conditions, timestamps, impact estimate, run action, delete action, and recent application history.

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.

pageActivity Tag Rules / Applications

Recent application history shown inside the detail page for one rule, including action performed, timestamp, and captured activity data.

pageAffiliate Deals / List

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