Skip to main content

Release 1.15.3

1. Stronger control and auditabilityconfiguration of client actions

WIFOX-241 – ConfigurableManage Action Types and Subtypes invia Settings
Action types and their subtypes are now fully manageableconfigurable viaon a dedicated Settings page (/settings/actions),page, similar to client/request statuses and verification levels.statuses.
Business impact:

  • BusinessBusiness/ops teams can add, edit, delete and reorderadjust action types/subtypesstructures (types, subtypes, ordering) without developercode involvement.

    changes,
  • keeping
  • Faster reaction to process changes and better alignment betweenthe CRM andaligned realwith workflows.evolving processes.

WIFOX-236 – OrderedOrdering list offor action subtypes
Subtypes of actions can be reordered via drag & drop, and this order is respectedreflected in dropdowns when creating newactions.
Business impact: The most important subtypes appear first, speeding up daily work and reducing misclassification.

WIFOX-216 – New “Verification” action type
A dedicated “Verification” action type has been introduced, using the same fields as comment actions.
Business impact: Verification steps are clearly separated from generic comments, improving traceability for compliance and quality checks.

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: Reduces the risk of exposing sensitive transaction data and ensures consistent, audit‑friendly access behavior across the platform.

  • 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 systembackend now calculates, per bucket, how many leads were created today and how many remain unassigned, using backend aggregation while keeping existing APIs backward compatible.
Business impact:

Managers
gain
  • Real‑real‑time operational visibilityinsight into newdaily lead inflow and backlog.

    backlog,
  • enabling
  • Enables more informedfaster staffing and prioritization decisions.

WIFOX-247 – New Buckets table view with key metrics
The bucketsBuckets page has been redesigned from cards to a table view with new columns for “Leads today” and “Unassigned leads”, and clickable bucket names are now clickable.names.
Business impact: It is easier to scan and compare buckets, quickly identify overloaded areas, and rebalance work.

  • Easier to scan and compare buckets at a glance.

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


3. MoreImproved intuitivefilters, search, and reliablebulk clientwork datawith & UXclients

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

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

    more
  • reliably,
  • Reducesreducing missed matchesresults and manual workarounds when working with imported or external data.workarounds.

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 – ImprovedRevised multi‑client selection via checkboxes
Checkbox selection behavior in client lists has been redesigned (based onusing a proven CRM pattern) to work reliably when clicking and scrolling, with a clear count of selected clients.
Business impact:

  • Bulk operationsactions on clients are more predictable and efficient.

    efficient,
  • Reducesreducing selection errorsmistakes and reworkrework.

    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 agents handling large client sets.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 of columns now respected
Customizations of columns 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. 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 stabilityStability and reliability

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

  • Restores access to session information reliedrequired on infor daily operations.

  • Minimizes downtimeoperations and interruptionsreduces for teams using this data.downtime.

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.