Skip to main content

Release 1.19.0

1. StrongerSafer clientfinancial auditoperations: accounts, assets, and action visibilitytransactions

WIFOX-282540 – FullSafe clientdelete activityfor logAccounts in& SessionsAssets tab(with rights and checks)
The Sessions tab on the client cardCRM now showssupports adeleting unifiedAccounts activityand logAssets combining:from their modules, but only under strict conditions:

  • clientSeparate actionsrights: across“Accounts CRM,→ TradersroomDelete” and Trading“Assets Terminal→ (logins, navigation, transactions, trading, profile changes, etc.), andDelete”.

  • managerDelete actionsaction onis thatshown clientonly (opening/editingif the client,user creating/updatinghas actions,the tickets,right.

    bulk
    • ops,
  • etc.).

    Backend blocks deletion if:

    • an asset has any balance or transactions, or

    • an account contains any assets with balance or transactions.

Entries include timestamp, actor (client/manager), source app, event type, human‑readable message, and technical metadata, with pagination, sorting and filtering.

Business impact:

  • ProvidesAdmins acan singleclean auditup trailunused foraccounts/assets investigations,without disputesrisking andfinancial compliance checks.history.

  • ReducesHard timebackend tochecks understandprevent “whoaccidental didloss whatof anddata when”or formoney any client across all channels.movements.

WIFOX-386541 – Cancel internal transactions with “ActionsCanceled exist”by indicatormanager” &+ filterreason in+ Clientsbalance tablecheck
TheFor Clientsinternal tabletransactions, managers can now hasset anstatus “Actions exist” column (✅/❌) backedCanceled 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:manager”:

  • TeamsOnly canavailable instantlyfor seeprovider which= clients have any history of actions, and filter to “with actions” or “no actions yet.”internal.

  • MakesA itreason easieris to find untouched clients or ensure that key segments are actually being worked.

2. Buckets & leads: better controlsmandatory and reprocessing

stored

WIFOX-326 – Buckets / Leads: “Only FTD” fast toggle with per‑bucket memory
On /buckets/:id/leads, a new “Only FTD” toggle aboveon 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.transaction.

  • EachWhen bucketcanceling 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 fromdeposits, the Bucketsystem → Leads tab, but only for roles that havechecks the newclient’s permissioncurrent buckets.submodules.leads.reprocessing.

balance;
if
there’s
not
enough
    balance
  • to

    Withreverse permission:the processeddeposit, leadscancellation remainis visuallyblocked distinctwith but become selectable for (re)processing.

  • Without permission: behaviour stays as before; processed leads can’t be reprocessed and users geta clear “no permission” feedback.error.

Business impact:

  • EnablesGives controlledoperations reprocessinga flowsclean, (e.g.auditable whenway strategiesto change)cancel withoutinternal hacks or data workarounds.deposits.

  • KeepsPrevents risknegative balances and analyticsinconsistencies underwhen controlreversing by gating reprocessing behind an explicit role right.funds.

2. Clients module: faster actions and better segmentation

WIFOX-419519 – “FullAdd name”action” columnpromoted +to first/lastquick name filtersaction in bucketClients leadstable
OnIn CRM → Clients, “Add action” is now a visible quick‑action icon directly in each row, right after Edit, instead of being hidden in the Bucket“⋮” → Leads tab, a new “Full name” column (after ID) shows <First name> <Last name>, supports sorting, and is backed by two separate filters: First name and Last name.menu.

Business impact:

  • OperatorsManagers can quicklycreate locateclient and sort leads by name directlyactions in one click from the bucketmain view.list.

  • Name‑basedSpeeds searchesup becomedaily more precisefollow‑up and flexiblereduces (filterextra byclicks first,for last,high‑volume or both).teams.

3. Clients table: smarter duplicate and action indicators

WIFOX-323591 – New “LastSource duplicateID” date”column + filter in Clients table
AThe newClients Last duplicate date field istable now storedhas ona the“Source client and surfaced as an optionalID” column in(after the“Affiliate ClientsID”) table, with sorting, date‑range filtering (Fast Filters) and Customize Columns support.

Business impact:with:

  • LetsDisplay teamsfrom 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 canclient.sourceId (includingor trading)equivalent).

  • VerificationText stillfilter appearsby asSource pending in the personal area.ID.

  • TransitionsInclusion toin RejectedCustomize columns from(can Completedbe orshown/hidden, Pendingorder –controlled Authorizedper fully block top‑ups, new orders, closing/editing orders, and withdrawals.user).

Business impact:

  • AllowsBusiness can quickly slice clients by acquisition source directly in the businessmain toClients grant full trading access earlier while continuing KYC/verification processes.view.

  • SeparatesEasier tradinganalysis authorisationof fromwhich fullsources profilegenerate completionwhich inclients, awithout controlled, explicit way.exports.

5.3. GlobalFast UXfilters and safetysearch: improvementsclearer, global vs personal, and always‑visible search

WIFOX-416321 – LanguageClear selectorvisual dropdownseparation alwaysof visibleGlobal overvs Personal fast filters
Fast Filters
Thefilters languageacross switcherCRM dropdown(Clients, Requests, Actions, Transactions, etc.) now correctlyvisually appearsdistinguish aboveGlobal filters from Personal ones (using the Fastapproved Filtersdesign), panelwithout acrossrelying allon pagesthe andold services“(G)” wheretext both are present.suffix.

Business impact:

  • InternationalUsers usersinstantly cansee change language at any time, even withwhich filters open.are organisation‑wide and which are their own.

  • RemovesLess aconfusion, confusingfewer UImistakes clashwhen andsaving, avoidsediting, supportor ticketsteaching aroundothers “stuck”to language.use filters.

WIFOX-417517 – Transactions:Move maskedsearch out of Fast Filters and place above tables
In all relevant modules, the search field has been moved:

  • Out of the Fast Filters panel.

  • Into the main table header area, always visible above the table.
    Existing saved Fast Filters that contained search parameters were migrated so nothing breaks.

Business impact:

  • Search is now obvious and one‑click for all users.

  • Fast Filters are cleaner and focused on structured conditions, while saved filters continue to work.

4. Actions module: better filters and more complete data

WIFOX-518 – Redesigned “SourceSubtypes” cardselector number”in columnActions +Fast filterFilters
The TransactionsSubtypes selector in Actions Fast Filters was redesigned to clearly show Type → Subtype relationships (per the new UX):

  • Subtypes visually grouped under their parent Action Type.

  • Multi‑select across types and subtypes still works.

  • No change to backend filtering logic.

Business impact:

  • Users understand exactly which subtypes belong to which types when filtering.

  • Reduces mis‑filters and speeds up building correct saved filters.

WIFOX-543 – “Completed” column in Actions table on Client card
The Actions table inside the client card now includes a “Source card number”Completed” column for Bridge Pay card transactions,column, showing onlywhether first4********last4each and never the full PAN. A fast filteraction is availabledone thator works strictly on first4+last4. The column is configurable via Customize Columns.not.

Business impact:

  • OperationsAccount and fraud/risk teamsmanagers can identifyquickly transactionssee bywhich cardactions are still open vs closed for a client.

  • Easier to ensure no important tasks are left unfinished.

WIFOX-573 – Make Comments required for selected Actions
Certain action types can now require a Comment when being created or completed (per configuration). If an action type is marked as “comment required”, users cannot save it without filling the comment field.

Business impact:

  • Ensures key actions always have enough context in athe safe, compliant way.history.

  • Improves investigationsquality of follow‑up and auditability for important processes.

5. Popovers and navigation: smoother UX in CRM

WIFOX-571 – Wider, readable popovers for long text (e.g. action descriptions)
Popovers/tooltip previews (like long action descriptions) now expand horizontally up to a sensible max width, instead of becoming extremely tall and narrow. Text wraps nicely and handles long words/URLs.

Business impact:

  • Long descriptions are easier to read without exposingscrolling sensitivea cardtiny databox.

    or
    • weakening
  • compliance

    Less posture.friction when reviewing details directly from tables.

WIFOX-572 – Redirect each user to their last visited page after login
After login, CRM now redirects each user to their own last visited page, stored per user in local storage (wbcs:{email}:lastVisitedPath), if it’s still valid and accessible. If not, they go to the default start page.

Business impact:

  • Users return straight to where they left off (clients list, specific client, requests, etc.).

  • Saves time and clicks at the start of every session.

6. Configuration cleanup: labels & employee emails

WIFOX-285 – Remove “Label” from UI forms and auto‑generate it in backend
For many configurable entities (action types, buckets, client/request statuses, desks, banks, fee groups, transaction statuses/subtypes, etc.):

  • Label is no longer entered in create forms; only Name is managed by business users.

  • In edit forms, Label is still visible but read‑only.

  • Backend automatically generates a unique label from Name (same logic as clients’ custom fields) and keeps it stable on edits.

Business impact:

WIFOX-442 –
    Requests
  • Module:

    Business “Customizeusers Columns”stop dealing with Pinnedtechnical CoreIDs Columnsand “label” errors.

  • Integrations keep stable identifiers even if visible names change.

InWIFOX-287 & WIFOX-289 – Safe email change for employees (with impact review and audit)
Together these tasks:

  • Analysed all impacts of changing an employee email (auth, analytics, permissions, audit, notifications, integrations).

  • Implemented safe email change in the RequestsEmployee edit module, a new “Customize columns” feature has been added to the main table.
    Users can now:form:

    • OpenEmail acan Customizenow columnsbe panelupdated fromwith thevalidation Requests(format table.+ uniqueness).

    • Show/hideActive sessions, login, password reset, and reorderanalytics allbehavior non‑corewere columns.defined and handled as approved.

    • HaveEvery theirchange configurationis persistlogged afterwith pageold reloadsemail, (pernew user).email, who changed it, and when.

Business impact:

  • Request handlersHR and managersadmins can tailorcorrect theor Requestschange tableemployee to their role (hide noise, prioritise key fields)emails without losingcreating criticalnew information.accounts.

  • Core,System business‑criticalremains columns are always presentsecure and inauditable; aanalytics predictablecontinues order,to whichmake protectssense reporting,over training, and operational procedures.

  • Persistent per‑user layouts reduce repetitive UI adjustments and speed up daily work in the Requests module.time.


Back to top