Operator guideENtagsrulesedit

Activity Tag Rules / Edit

Edit flow for one backend rule or a grouped add and remove pair, including split or merge 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 update an existing rule. The edit route can load a single backend rule or merge one add-rule and one remove-rule into one operator form when FE receives both IDs.

What makes edit different from create

  • The route can be opened with addRuleId and removeRuleId query parameters.
  • FE rebuilds the grouped form state from one or two backend rules.
  • Saving can update existing rules, create a missing counterpart rule, or delete the original single rule when it is being split into two rules.

Important caveats

  • The visible name on the edit page removes the (Add) and (Remove) suffixes for grouped editing.
  • When both add and remove sections are enabled, FE lowers the remove rule priority by one.
  • The form still uses the same backend create, update, and delete routes as the rest of the module; there is no dedicated grouped-rule backend API.
Calculation notes

Calculations

calculation

Grouped Editor Merge

Formula Text
FE loads `ruleId` and optional `addRuleId`/`removeRuleId`, removes the ` (Add)` and ` (Remove)` suffixes from the visible name, and rebuilds one form state containing `addTag` and `removeTag` sections.
Operator Note
This merge happens in FE only.
Verification Status
verified_fe_only
calculation

Save Payload Build

Formula Text
Save builds one backend payload per enabled tag section. Existing `autoTagRuleId` values are updated, missing counterparts are created.
Operator Note
One submit can touch multiple backend records.
Verification Status
verified_fe_only
calculation

Remove Rule Priority

Formula Text
When both add and remove sections are enabled, FE saves the remove rule with `priority = addRulePriority - 1`.
Operator Note
This pairing logic is FE-defined.
Verification Status
verified_fe_only
calculation

Split Delete Original

Formula Text
If the original single rule no longer owns either of the saved payload IDs after a grouped save, FE deletes the original backend rule.
Operator Note
This is part of the FE update orchestration, not a dedicated backend feature.
Verification Status
verified_fe_only
Field dictionary

Fields

field

Rule Identity

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

Group
grouped-context
Data Type
composite
field

Rule Name

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

Group
rule-information
Data Type
string
field

Activity

Triggering activity for all rules saved from this editor.

Group
rule-information
Data Type
integer
field

Add Tag Configuration

Existing add-rule payload or the new add-rule section that FE will save.

Group
add-tag
Data Type
object
field

Remove Tag Configuration

Existing remove-rule payload or the new remove-rule section that FE will save.

Group
remove-tag
Data Type
object
field

Rule Priority

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

Group
priority
Data Type
integer
field

Conditions

Matching criteria copied into the saved backend rules.

Group
conditions
Data Type
json-object
field

Active

Active-state toggle saved to the backend rule records.

Group
settings
Data Type
boolean
Operational notes

Notes

item

The grouped editor is FE-owned composition on top of ordinary backend CRUD routes.

item

No dedicated grouped update endpoint was verified in gs-admin-backend.

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