Release 1.15.3
1. Stronger control and configuration of client actions
WIFOX-241 – Manage Action Types and Subtypes via Settings
Action types and their subtypes are now fully configurable on a dedicated Settings page, similar to client/request statuses.
Business impact: Business/ops teams can adjust action structures (types, subtypes, ordering) without code changes, keeping the CRM aligned with evolving processes.
WIFOX-236 – Ordering for action subtypes
Subtypes of actions can be reordered via drag & drop, and this order is reflected in dropdowns when creating actions.
Business impact: The most important subtypes appear first, speeding up daily work and reducing misclassification.
WIFOX-215 – Ability to change action subtype on Actions
If an agent selects the wrong subtype for an action, the creator (or any role with edit permissions) can now correct the subtype.
Business impact: Reduces data pollution from misclassified actions and improves accuracy of reports and KPIs based on action subtypes.
WIFOX-245 – Transaction visibility aligned with role‑based access rules
Transaction visibility has been validated and aligned with existing role‑based permissions across desks, projects, and clients (“view own” vs “view all”), enforced on the backend.
Business impact: Lowers the risk of exposing sensitive transaction data and ensures consistent, audit‑friendly access behavior across the platform.
2. Better visibility and management of leads
WIFOX-248 – Backend aggregation of “Leads today” and “Unassigned leads” per bucket
The backend now calculates, per bucket, how many leads were created today and how many remain unassigned, while keeping existing APIs backward compatible.
Business impact: Managers gain real‑time insight into daily lead inflow and backlog, enabling faster 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 columns for “Leads today” and “Unassigned leads”, and clickable bucket names.
Business impact: It is easier to scan and compare buckets, quickly identify overloaded areas, and rebalance work.
3. Improved filters, search, and bulk work with clients
WIFOX-249 – Client name filtering supports special characters
Filtering clients by first/last name now works correctly when special characters (such as ?) are used, and related text filters have been checked for similar issues.
Business impact: Searches match real‑world data more reliably, reducing missed results and manual workarounds.
WIFOX-242 – Revised multi‑client selection via checkboxes
Checkbox selection in client lists has been redesigned (using a proven CRM pattern) to work reliably when clicking and scrolling, with a clear count of selected clients.
Business impact: Bulk actions on clients are more predictable and efficient, reducing selection mistakes and rework.
WIFOX-230 – Fixed inappropriate error when sorting by name
An incorrect/misleading error that appeared when sorting Clients/Requests by name has been removed.
Business impact: Fewer confusing error states and smoother navigation for users.
WIFOX-255 – Warning in clients’ comments section now renders correctly
A previously missing warning message in the clients’ comments section is now displayed properly.
Business impact: Users receive the intended guidance or restrictions when working with comments, reducing misuse and support questions.
WIFOX-251 – Fast filter customization now respected
Customizations to which fields appear in fast filters are now correctly applied; fields that are turned off remain hidden when reusing saved filters.
Business impact: Filters behave consistently with user expectations, saving time and reducing confusion.
WIFOX-250 – Easier management of fast filters across modules
Users can now remove fast filters directly from the filter popover, and the unified “other filters” view has been added to all modules that use fast filters (with minor UI clean‑ups such as removing unnecessary arrows).
Business impact: Fast filters are easier to manage and clean up, giving users more control over how they slice data across different modules.
4. Stability and reliability
BD-256 – Sessions page fixed (blank screen)
A critical defect that caused the Sessions page to show a blank screen has been resolved.
Business impact: Restores access to session information required for daily operations and reduces downtime.