Release 1.0.7 (29.08.2024)
Features:
- WICRM-288 -
AddExport Transactions and Clients to CSV- Added a new feature allowing users to export
transactionstransaction history andclientsclienttodatacsvin CSV format. This enables easier data manipulation and reporting outside the platform, such as for external audits or business analysis.
- Added a new feature allowing users to export
- WR-373 -
ChangeEnforceapproachTwo-Factoractivate TFA methodsAuthentication (phone,2FA)email)Methods- Updated the registration process to require two non-removable 2FA methods: email and phone. After
registrationaccount creation, the user will automatically have2both methodsofenabled, with email set as the default. Users cannot delete these 2FAwhichmethodscannotbutbecandeleted, namely email and phone. Email method after registration will bechange the default2FAmethodmethodin their settings.
- Updated the registration process to require two non-removable 2FA methods: email and phone. After
- WR-372 -
LetRestrictinAccountCAAccessonlyUntilafterPhonephone verifyVerificationNowImplementedonlyaafterrestrictionconfirmingthattheprevents users from accessing their personal account until their phonenumber,numberyouiscanverified.accessThistheaddsuser'sanpersonalextraaccount.layer of security by ensuring that users confirm their identity via phone before proceeding. The“"skip fornow”now"buttonoption, previously allowing users to bypass phone verification, has beenremovedremoved.
- WR-376 -
ConvertNormalize Email Input and Trim Sensitive Data- Improved the way user email addresses are handled by converting them to
lowerlowercasecase.beforeTrimstoringsensative data in wiex clientUser's e-mail addressthem on theserverserver.sideAdditionally, any sensitive data (such as names or email addresses) is nowsavedautomaticallyintrimmedsmalltolettersremove unnecessary spaces, reducing the risk of errors during data processing.
- WR-377 -
semaphoraSemaphoreonIntegrationexchangefor Exchange andwithdrawalWithdrawalSemaphoreIntegratedisaintegratedsemaphore mechanism topreventregulateone-stepsimultaneousoperations,transactions.whichThispassedpreventsandusersmadefromitinitiatingpossiblemultipletostepsmakein transactions that could result in negative balances. For example, if aminususerbalanceperformsonanoneexchangeasset,orbut to add money onwithdrawal, thesecondsystemonewillbynowtheensuresamethatactionboth assets involved are accurately updated without conflicts.
- WR-392 - Add
hashHash Column and Display Transaction Type- Added a new column
andinshowthetypetransaction records to display the hash value for internaltransactionstransactions, ensuring better traceability and transparency. Additionally, the type of each transaction is now clearly displayed to help users differentiate between various transaction types.
- Added a new column
- WR-393 - Clear
inputInputfieldsFieldsifAftercodeIncorrectisCodeincorrectEnteredIf an invalid password is entered,Improved thecodeuserwillexperiencebewhenerasedenteringfromincorrect codes by automatically clearing the inputfieldsfields. This ensures that users don’t have to manually delete incorrect entries and can re-enter the correct information without confusion.
Bugfixes:
- WR-358 -
removeRemovenotificationNotificationonforloginTfaLogin 2FA Error- Removed unnecessary and misleading error
notifications that appeared when there was an issue with logging in using 2FA. This prevents confusion and enhances the overall login experience.
- Removed unnecessary and misleading error
- WR-394 - Fix
issueforwithDeactivatedloginClientofLogindeactivated clientIssueFixedResolved a bug where users with deactivated accounts were still able to access their personal cabinets. Now, if anerroraccountwhenisadeactivated, the userhadwillaccessbetoblockedhisfrompersonalloggingcabinetin,despiteensuringthecompliancefact that hiswith accountstatusmanagementwas “deactivated”.rules.
- WR-111 -
fixCorrected Error Message on Security Page- Fixed a misleading or incorrect error message
inthatimprovewassecuritydisplayedpageon the "Improve Security" page, making it clearer for users to understand the actions they need to take.
- Fixed a misleading or incorrect error message
- Improved the way user email addresses are handled by converting them to
