# Release 1.18.0
## 1. Stronger client audit and action visibility
**WIFOX-282 – Full client activity log in Sessions tab**
The **Sessions** tab on the client card now shows a unified activity log combining:
- client actions across CRM, Tradersroom and Trading Terminal (logins, navigation, transactions, trading, profile changes, etc.), and
- manager actions on that client (opening/editing the client, creating/updating actions, tickets, bulk ops, etc.).
Entries include timestamp, actor (client/manager), source app, event type, human‑readable message, and technical metadata, with pagination, sorting and filtering.
**Business impact:**
- Provides a single audit trail for investigations, disputes and compliance checks.
- Reduces time to understand “who did what and when” for any client across all channels.
---
**WIFOX-386 – “Actions exist” indicator & filter in Clients table**
The Clients table now has an **“Actions exist”** column (✅/❌) backed by a persistent `isActionsExist` flag on the client, updated whenever actions are created or deleted. The column is filterable and can be toggled via Customize Columns.
**Business impact:**
- Teams can instantly see which clients have any history of actions, and filter to “with actions” or “no actions yet.”
- Makes it easier to find untouched clients or ensure that key segments are actually being worked.
---
## 2. Buckets & leads: better controls and reprocessing
**WIFOX-326 – Buckets / Leads: “Only FTD” fast toggle with per‑bucket memory**
On `/buckets/:id/leads`, a new **“Only FTD”** toggle above the table filters leads to first‑time depositors when ON, and shows all leads when OFF. Its state is stored **per bucket** (alongside other bucket toggles).
**Business impact:**
- Sales and retention teams can focus on FTD leads in one click, per bucket.
- Each bucket remembers its FTD preference, reducing repetitive setup.
---
**WIFOX-354 – Allow reprocessing of already processed leads (with permission)**
Leads that were previously processed can now be **selected and reprocessed** from the Bucket → Leads tab, but only for roles that have the new permission `buckets.submodules.leads.reprocessing`.
- With permission: processed leads remain visually distinct but become selectable for (re)processing.
- Without permission: behaviour stays as before; processed leads can’t be reprocessed and users get clear “no permission” feedback.
**Business impact:**
- Enables controlled reprocessing flows (e.g. when strategies change) without hacks or data workarounds.
- Keeps risk and analytics under control by gating reprocessing behind an explicit role right.
---
**WIFOX-419 – “Full name” column + first/last name filters in bucket leads**
On the Bucket → Leads tab, a new **“Full name”** column (after ID) shows ``, supports sorting, and is backed by **two separate filters**: First name and Last name.
**Business impact:**
- Operators can quickly locate and sort leads by name directly in the bucket view.
- Name‑based searches become more precise and flexible (filter by first, last, or both).
---
## 3. Clients table: smarter duplicate and action indicators
**WIFOX-323 – “Last duplicate date” in Clients table**
A new **Last duplicate date** field is now stored on the client and surfaced as an optional column in the Clients table, with sorting, date‑range filtering (Fast Filters) and Customize Columns support.
**Business impact:**
- Lets teams prioritise clients recently detected as duplicates and analyse the recency of duplicate events.
- Improves data‑quality monitoring by making duplicate activity visible over time.
---
## 4. Client status & trading access
**WIFOX-444 – New client status “Pending – Authorized”**
A new status **Pending – Authorized** has been introduced and treated as “authorized for trading” across the core system, trading platform and related services:
- Users in **Pending – Authorized** can do everything that **Completed** users can (including trading).
- Verification still appears as pending in the personal area.
- Transitions to **Rejected** from Completed or Pending – Authorized fully block top‑ups, new orders, closing/editing orders, and withdrawals.
**Business impact:**
- Allows the business to grant full trading access earlier while continuing KYC/verification processes.
- Separates trading authorisation from full profile completion in a controlled, explicit way.
---
## 5. Global UX and safety improvements
**WIFOX-416 – Language selector dropdown always visible over Fast Filters**
The language switcher dropdown now correctly appears **above** the Fast Filters panel across all pages and services where both are present.
**Business impact:**
- International users can change language at any time, even with filters open.
- Removes a confusing UI clash and avoids support tickets around “stuck” language.
---
**WIFOX-417 – Transactions: masked “Source card number” column + filter**
The Transactions table now includes a **“Source card number”** column for Bridge Pay card transactions, showing only `first4********last4` and never the full PAN. A fast filter is available that works strictly on first4+last4. The column is configurable via Customize Columns.
**Business impact:**
- Operations and fraud/risk teams can identify transactions by card in a safe, compliant way.
- Improves investigations without exposing sensitive card data or weakening compliance posture.
In the **Requests** module, a new **“Customize columns”** feature has been added to the main table.
Users can now:
- Open a **Customize columns** panel from the Requests table.
- **Show/hide and reorder** all non‑core columns.
- Have their configuration **persist after page reloads** (per user).
**Business impact:**
- Request handlers and managers can tailor the Requests table to their role (hide noise, prioritise key fields) without losing critical information.
- Core, business‑critical columns are always present and in a predictable order, which protects reporting, training, and operational procedures.
- Persistent per‑user layouts reduce repetitive UI adjustments and speed up daily work in the Requests module.