Skip to main content

Release 1.15.3

1. Stronger control and auditability of client actions

WIFOX-241 – Configurable Action Types and Subtypes in Settings
Action types and subtypes are now fully manageable via a dedicated Settings page (/settings/actions), similar to client/request statuses and verification levels.
Business impact:

  • Business teams can add, edit, delete and reorder action types/subtypes without developer involvement.

  • Faster reaction to process changes and better alignment between CRM and real workflows.

WIFOX-236 – Ordered list of action subtypes
Subtypes of actions can be reordered via drag & drop, and this order is respected in dropdowns when creating new actions.
Business impact:

  • Puts the most important subtypes at the top.

  • Reduces selection errors and speeds up agents’ daily work.

WIFOX-215 – Ability to correct action subtype on client actions
Creators or users with edit rights can now change the subtype of an existing action if it was chosen incorrectly.
Business impact:

  • Reduces data pollution from misclassified actions.

  • Improves accuracy of operational and performance analytics.

2. Better visibility and management of leads

WIFOX-248 – Backend aggregation of “Leads today” and “Unassigned leads” per bucket
The system now calculates, per bucket, how many leads were created today and how many remain unassigned, using backend aggregation while keeping existing APIs compatible.
Business impact:

  • Real‑time operational visibility into new lead inflow and backlog.

  • Enables more informed staffing and prioritization decisions.

WIFOX-247 – New Buckets table view with key metrics
The buckets page has been redesigned from cards to a table view with new columns for “Leads today” and “Unassigned leads”, and bucket names are now clickable.
Business impact:

  • Easier to scan and compare buckets at a glance.

  • Managers can quickly spot overloaded or neglected buckets and rebalance workload.

3. More intuitive and reliable client data & UX

WIFOX-249 – Clients: name filtering works with special characters
Filtering clients by first/last name now correctly handles special characters such as ?, and related text filters have been checked for similar issues.
Business impact:

  • Search behaves as users expect in real‑world data scenarios.

  • Reduces missed matches and manual workarounds when working with imported or external data.

WIFOX-230 – Correct error handling when sorting by name
An inappropriate or misleading error when sorting Clients/Requests by name has been fixed.
Business impact:

  • Fewer confusing error states for users.

  • Smoother navigation and less support overhead for simple list operations.

WIFOX-242 – Improved multi‑client selection via checkboxes
Checkbox selection behavior in client lists has been redesigned (based on a proven CRM pattern) to work reliably when clicking and scrolling, with a clear count of selected clients.
Business impact:

  • Bulk operations on clients are more predictable and efficient.

  • Reduces selection errors and rework for agents handling large client sets.

4. Security and access control alignment

WIFOX-245 – Transaction visibility aligned with role‑based permissions
Transaction visibility has been reviewed and aligned with the same role‑based access rules used for desks, projects and clients (view own vs. view all). Enforcement is done on the backend.
Business impact:

  • Reduces risk of exposing sensitive transaction data to unauthorized users.

  • Ensures consistent behavior across modules for compliance and audits.

5. Platform stability and reliability

BD-256 – Sessions page fixed (blank screen issue)
A critical defect that caused the Sessions page to show a blank screen has been resolved.
Business impact:

  • Restores access to session information relied on in daily operations.

  • Minimizes downtime and interruptions for teams using this data.

WIFOX-251 – Fast filter: customization now respected
Customized field visibility in “fast filters” is now correctly applied; hidden fields stay hidden when reusing saved filters.
Business impact:

  • Filters behave consistently with user expectations.

  • Reduces confusion and time lost reconfiguring filters.


Back to top