Operator guideENtagsrulescreate

Activity Tag Rules / Create

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

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

Use this page to create a new activity-driven tag automation rule. Operators choose the triggering activity, configure one or two tag actions, optionally add transaction-only conditions, test the conditions, and then save the rule or rule pair.

Main workflow

  • Start with Rule Information: name, activity, and optional description.
  • Enable Add Tag, Remove Tag, or both.
  • Set priority and active state.
  • If the selected activity supports conditions, add the required condition rows and test them before saving.

Important caveats

  • When both Add Tag and Remove Tag are enabled, the save action creates two backend rules.
  • If this page is opened from Clone Rule, FE first loads the source rule and pre-fills the form with a new name ending in (Copy).
  • Conditions are not available for every activity. The FE only enables them for the hard-coded transaction activity codes.
Field dictionary

Fields

field

Rule Name

Human-readable rule name shown on the list and detail pages.

Group
rule-information
Data Type
string
field

Activity

Activity event that triggers the rule.

Group
rule-information
Data Type
integer
field

Description

Optional explanation for operators maintaining the rule.

Group
rule-information
Data Type
string
field

Enable Add Tag

Turns on the add-tag payload section.

Group
add-tag
Data Type
boolean
field

Tag Name to Add

Tag that will be added when the rule matches.

Group
add-tag
Data Type
string
field

Enable Remove Tag

Turns on the remove-tag payload section.

Group
remove-tag
Data Type
boolean
field

Tag Name to Remove

Tag that will be removed when the rule matches.

Group
remove-tag
Data Type
string
field

Rule Priority

Execution order for the backend rule.

Group
priority
Data Type
integer
field

Conditions

Optional matching criteria used only for supported transaction activities.

Group
conditions
Data Type
json-object
field

Active

Sets whether the new rule is active immediately after save.

Group
settings
Data Type
boolean
Operational notes

Notes

item

FE uses the same form component for create and edit, but create can start from a `cloneFrom` rule query parameter.

item

Conditions are FE-gated by activity code and do not appear for every activity.

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 / 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 / List

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

pageActivity Tag Rules / Applications

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

pageAuto Tags Manager

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