Operator guideEN

Activity Tag Rules / Edit

Edit flow for one stored rule or an existing grouped add/remove pair, including grouped form rebuild, condition testing, and update-only save behavior.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this page does

Use this page to update an existing activity tag rule. The edit route can load a single stored rule, or it can load an existing add-rule and remove-rule pair into one grouped operator form when the route receives both IDs.

How the form is rebuilt

  • The route always loads the primary rule ID from the URL.
  • If add and remove rule IDs are present in the query string, the page loads those records too.
  • The visible rule name removes the (Add) and (Remove) suffixes so the operator edits one clean grouped name.
  • Existing add and remove records fill the Add Tag and Remove Tag sections separately.

Main actions

  • Test Conditions estimates how many users currently match the selected activity and unsaved condition rows. It proves estimator matching only; it does not prove that the live webhook evaluator enforces the same condition keys.
  • Save Rule submits updates for enabled sections that already have a stored rule ID.
  • Back to List leaves the edit page without submitting the form.

Important caveats

  • The shared form can build add and remove payloads, but the verified edit page wrapper only updates payloads that already have an ID.
  • Enabling a missing counterpart section in edit is not verified to create a new stored rule from this page.
  • Disabling an existing counterpart section is not verified to delete that stored rule from this page.
  • When both add and remove sections are enabled, the page lowers the remove rule priority by one in the generated payload.
  • There is no dedicated grouped-rule source API in the verified flow; grouped editing is page composition over individual rule reads and updates.
  • Grouped updates are submitted sequentially by the page wrapper and are not wrapped in one transaction. If a later update fails, an earlier update is not compensated or rolled back.
  • The estimator supports the form's transaction/user condition keys. The live model evaluator supports only minCount, maxCount, minAmount, maxAmount, and timeFrame, so saved form conditions are not proof of live filtering.
  • Estimator Amount labels are inclusive: greaterThan means >= and lessThan means <=. Estimator ID Verification Status checks whether document labels exist; it is not a separate ID-verification status predicate.
  • The edit screen does not provide a durable action-history confirmation. After a partial or failed grouped save, reload the stored rules before retrying.

Route behavior, shared form behavior, grouped rule loading, estimator testing, sequential update flow, and the separate live evaluator have been traced. No workspace-settings or casino-side semantic dependency was found for this edit form.

More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Calculations9 topicsOpen details

Grouped editor merge

Logic
The edit page loads the primary rule ID from the route., Optional add-rule and remove-rule IDs can be loaded from query parameters., The page removes trailing `(Add)` or `(Remove)` from the visible name before showing the grouped editor., Existing add and remove records are mapped into separate Add Tag and Remove Tag sections.

Validation before save

Logic
Rule Name, Activity, and Priority are required., Priority must be at least `0`., At least one tag configuration must be enabled., Enabled Add Tag requires Tag Name to Add., Enabled Remove Tag requires Tag Name to Remove.

Condition availability

Logic
Conditions are only shown for the supported transaction activity codes., Non-transaction activities show an information message and save without condition rows., Add Condition creates a local row with default type `status`.

Condition payload build

Logic
Condition rows are converted into a keyed source conditions object., Empty condition values are omitted except for payment method, where an empty value can be intentionally sent., Amount conditions can carry an operator and value pair., Estimator amount operators map `greaterThan` to `>=`, `lessThan` to `<=`, and `equals` to `=`., Country, document, ID verification, and KYC conditions require user-row data during source estimate., Estimator ID Verification Status uses document-label array presence, the same predicate family as Documents Submitted, rather than a separate ID-verification status field., The same keys are not implemented by the current live model evaluator.

Test estimate

Logic
Test sends the selected activity ID and unsaved conditions object., The source counts distinct users in activity history matching the current activity and conditions., The source returns matching user count plus a sample of recent matching user IDs., Test does not update a rule and does not mutate tags., A successful estimate does not prove equivalent live webhook filtering.

Save payload build

Logic
If Add Tag is enabled, the page builds an add-rule payload., If Remove Tag is enabled, the page builds a remove-rule payload., If both are enabled, the page builds two payloads and appends `(Add)` and `(Remove)` to the generated rule names., The remove payload is generated with priority one lower than the entered priority., The verified edit page wrapper submits updates only for generated payloads that already have stored rule IDs., Multiple existing payloads are updated sequentially.

Update-only caveat

Logic
The shared update hook can support mixed update/create/delete orchestration., The verified edit page wrapper does not pass the full payload array into that mixed orchestration path., Instead, it iterates generated payloads and updates only payloads that already contain an activity tag rule ID., Enabling a missing counterpart section is therefore not verified to create a new stored rule from the edit page., Disabling an existing counterpart section is therefore not verified to delete that stored rule from the edit page.

Grouped update transaction caveat

Logic
A grouped save can submit more than one source update., The wrapper awaits generated updates sequentially and does not wrap them in an all-or-nothing transaction., If a later update fails, earlier successful updates are not automatically rolled back by the verified page flow.

Estimator and live condition divergence

Logic
Test Conditions uses the estimator implementation for form condition keys., The live model evaluator supports only minCount, maxCount, minAmount, maxAmount, and timeFrame., The current form does not offer those live-evaluator keys., Saving edited condition JSON therefore does not prove equivalent live filtering.
Fields22 topicsOpen details

Rule Identity

Determines whether the editor is modifying one backend rule or a grouped pair.

Group
grouped-context
Data Type
composite

Loading State

Shows that the rule data is still loading before the form is rendered.

Group
surface-state
Data Type
ui-state

Rule Not Found State

Shows that the editor could not load a usable rule record.

Group
surface-state
Data Type
ui-state

Rule Name

Visible grouped rule name used for both add and remove rule records.

Group
rule-information
Data Type
string
Validation
Required: true

Activity

Triggering activity for all rules saved from this editor.

Group
rule-information
Data Type
integer
Validation
Required: true

Description

Optional operator note saved with the activity tag rule.

Group
rule-information
Data Type
string

Add Tag Configuration

Existing add-rule payload or local add-tag section state.

Group
add-tag
Data Type
object
Validation
Tag Name Required When Enabled: true
Caveats
In the verified edit page wrapper, Save updates this section only when it already maps to an existing backend rule ID.

Add Tag Enable Switch

Controls whether the add-tag section contributes an update payload.

Group
add-tag
Data Type
boolean
Caveats
Enabling a missing add-tag counterpart is not verified to create a new backend rule from the edit page.

Tag Name to Add

Tag name saved on the existing add-rule payload.

Group
add-tag
Data Type
string

Remove Tag Configuration

Existing remove-rule payload or local remove-tag section state.

Group
remove-tag
Data Type
object
Validation
Tag Name Required When Enabled: true
Caveats
In the verified edit page wrapper, Save updates this section only when it already maps to an existing backend rule ID.

Remove Tag Enable Switch

Controls whether the remove-tag section contributes an update payload.

Group
remove-tag
Data Type
boolean
Caveats
Disabling an existing remove-tag counterpart is not verified to delete that backend rule from the edit page.

Tag Name to Remove

Tag name saved on the existing remove-rule payload.

Group
remove-tag
Data Type
string

Rule Priority

Base priority used to save the add rule. The page offsets the remove rule by one when both are enabled.

Group
priority
Data Type
integer
Validation
Required: true | Minimum: 0

Conditions

Matching criteria copied into the saved backend rules.

Group
conditions
Data Type
json-object
Caveats
Conditions are only shown for supported transaction activity codes., Estimator support does not prove equivalent live webhook evaluation.

Condition Type

Chooses which transaction or user attribute narrows the match.

Group
conditions
Data Type
enum
Enum Values
status, sequence, amount, country, paymentMethod, paymentProvider, withdrawalWithoutDeposit, documentsSubmitted, kycStatus, idVerificationStatus
Caveats
These keys are supported by the estimator; the live model evaluator currently supports a different key set., In the estimator, `idVerificationStatus=verified` means the user's document-label array is non-empty and `not_verified` means it is empty. This is the same predicate family as Documents Submitted, not a separate ID-verification status field.

Condition Value

Value compared by the selected condition type.

Group
conditions
Data Type
mixed

Amount Operator

Selects the estimator comparison used when Condition Type is Amount.

Group
conditions
Data Type
enum
Enum Values
equals, greaterThan, lessThan
Caveats
Despite the UI labels, `greaterThan` is inclusive (`amount >= value`) and `lessThan` is inclusive (`amount <= value`); `equals` uses exact numeric equality., The operator is stored inside the amount condition JSON and is not a separate database column., This mapping is verified for the estimator and is not implemented by the current live event evaluator.

Active

Active-state toggle saved to the backend rule records.

Group
settings
Data Type
boolean

Test Results

Shows matching-user count and a short sample of user IDs for the current unsaved conditions.

Group
feedback
Data Type
object
Caveats
This represents estimator output, not proof of live webhook filtering.

Test Conditions Button

Runs the backend estimator without saving the rule.

Group
actions
Data Type
ui-action

Save Rule Button

Submits updates for enabled sections that already have backend rule IDs.

Group
actions
Data Type
ui-action

Back to List Button

Leaves the editor without submitting the form.

Group
actions
Data Type
ui-action
More help

Related pages

Activity Tag Rules

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

Activity Tag Rules / Create

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

Activity Tag Rules / Detail

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

Activity Tag Rules / List

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

Activity Tag Rules / Applications

Read-only recent recorded application rows inside rule detail, including user ID, tag outcome, timestamp, and captured activity payload.

Auto Tags Manager

Operator documentation for automatic tag rules, including list monitoring, create or edit, queued job control, and manual rule ordering.