Guides
Client Login

Rule Editing

Confidently and Safely alter a rule configuration

1) Before you edit: what to know

  • A rule belongs to a specific scope.
  • Some rules are direct (editable in that scope).
  • Some rules are inherited from parent scope (typically not editable in child scope).
  • A rule can have different states (for example enabled/disabled/dry-run depending on your setup).

Safety recommendation

Before changing production logic:

  • note the current rule name/ID/state,
  • capture current values/screenshots,

2) Navigate to the correct scope

  1. Open Decision Engine.
  2. In the left Scopes panel, pick a view:
    • Product
    • Account
    • Group
    • Card Group
  3. In the tree, select the exact node where you want to work.
  4. Confirm scope path in breadcrumb before opening rules.

3) Find and open the rule

  1. Use filters on the rules screen if needed (name/description/tags/state).
  2. Look in:
    • Direct Rules table (rules defined in selected scope)
    • Inherited Rules table (rules inherited from parent scope)
  3. Click the rule row to open its summary.

4) Check whether the rule is editable

In the rule summary view:

  1. Click Edit.
  2. If the rule is inherited and locked, the UI shows a disabled edit state with the message that inherited rules cannot be modified.

If you cannot edit:

  • go to the parent scope that owns the rule,
  • or create a new direct rule at your scope (depending on your operating model).

5) Understand the editing sections

When a rule opens, you edit it section-by-section in accordion panels:

  1. Details
  2. User Adjustable Values
  3. Current Transaction
  4. Historic Transactions
  5. Rule Outcomes

(There is also Raw DSL mode for advanced usage.)

6) Edit Details (name, description, tags, state)

In Details you can typically update:

  • Name
  • Description
  • Tags
  • Rule state

For first-time editors:

  • Keep naming clear and business-readable.
  • If changing state, do it intentionally and confirm impact.

7) Edit User Adjustable Values (if used)

In User Adjustable Values you can tune parameter values used by predicates and historical logic.

Typical operations:

  • Edit an existing UAV value/range/type.
  • Add a new UAV if missing.
  • Remove unused UAVs carefully.

Important:

  • UAV changes can affect multiple conditions in the same rule.
  • Validate type and scalar/list compatibility before saving.

8) Edit Current Transaction conditions

In Current Transaction:

  1. Review existing conditions first.
  2. Add/remove/update conditions.
  3. Verify logical combinators (AND/OR behavior).
  4. Double-check value source (literal vs user adjustable value).

Good practice for rule editors:

  • Change one thing at a time.
  • Avoid large multi-condition rewrites in a single edit unless planned.

9) Edit Historic Transactions logic

In Historic Transactions:

  1. Review each transaction-history block.
  2. Confirm history type (card/merchant), period settings, predicates, and aggregator/operator/threshold.
  3. Verify “include current transaction” behavior where used.
  4. Re-check combinators between history groups.

Common risk area:

  • wrong time window or wrong aggregator parameter can radically increase/ decrease hit rate.

10) Edit Rule Outcomes

In Rule Outcomes:

  1. Confirm outcome behavior for TRUE/FALSE/SKIPPED branches.
  2. Verify linked action mappings are still correct after predicate changes.
  3. Ensure no required action was accidentally removed.

11) Optional advanced mode: Raw DSL

The summary includes a Raw DSL mode.

Use this only if:

  • your team is comfortable with DSL-level editing,
  • and you have validation/review steps in place.

For most support edits, prefer section-based editing (Details/UAV/Current/Historic/Outcomes).

12) Save safely

  1. Click Save when in edit mode.
  2. If you changed rule state, the UI may request confirmation before final save.
  3. Wait for success toast/message.

If Save is disabled:

  • a required field may be invalid,
  • or one section has unresolved validation error.

13) Handle unsaved-change prompts

If you switch modes while editing, the UI can warn that unsaved changes will be discarded.

When prompted:

  • choose Cancel if you want to keep editing,
  • choose confirm only if you intentionally want to discard edits.

Updated 12 days ago