Release 1.0.5 (11.09.2024)

Bugfixes:

• WICRM-362 - DoPrevent notRole delete roleDeletion if it usingUsed in identIdentification tokenTokens
  • NowRoles ifthat aare rolein is useduse by any entity in the identification tokens module,module itcan willno longer be impossibledeleted, topreventing deletepotential suchsystem aconflicts role
    or loss of important role-based data.
• WICRM-366 - Fix AssetID Filter transactions by assetId does not work in crmCRM uiUI
  • FixedResolved filteringan issue where the transactions filter by AssetID columnwas not functioning properly in the CRM user interface.
• WICRM-315 - ChangePassword approachRecovery ofUI restoringIssue password - issue with loaderFixed
  • WhenFixed a bug where, during password recovery, the input window would jump after entering an incorrect code,code. Now, the input window used to jump up and return to its place again, updating its status to “Code is incorrect”, now this problem is notupdated presentwithout any disruptive movement in the input window.

• WICRM-369 - Allow Periods ('.') in Translation Labels
  • Now it's possible to use periods ('.') in translation labelslabels, providing more flexibility for labeling translations.
• WR-410 - businessBusiness is still creatingCreation with incorrectIncorrect phonePhone numberNumber Fixed
  • When creatingResolved aan business,issue where businesses were being created with empty or invalid phone numbers, ensuring that the empty phone number field was not being recordedis correctly validated and stored during the business creation process.

Features:

• WICRM-345 - Add Verification Status to Client Filters
  • Added a filter for client verification status toin the clients filterssection, making it easier to filter and view clients based on their verification state.

• WICRM-348 - Remove checkbox 'Create transaction'Transaction' Checkbox and createAlways transactionRecord alwaysTransactions
  • Previously, youtransactions like Deposits or Withdrawals could makebe amade Depositwithout orbeing Withdrawalrecorded transactionif withthe ancheckbox Asset“Create Transaction” was unchecked. This feature has been removed, and notnow createall a transaction, so this action was not recorded anywhere. Now, by removing the checkbox, the possibility to perform the abovesuch operations withoutwill recordingalways thebe transactionrecorded in the systemsystem, hasensuring beenfull removedtransaction traceability.

• WICRM-331 - Reimplement rights chaining to reduce the number of dependencies
  

  • Fully unchain for:
    Projects,
    Roles,
    Clients TFA
    Ident Token

    In another module, I reduced the dependencies to only the essentials.
    Combined ui restrictions with new resolvers approach.

     

    Full list of dependencies :

    • Desks VIEW - (Projects) visibility of desks based on visibility of projects, I can see desks based on visible projects.

    • Employees VIEW - (Projects, Desks) visibility of desks based on the visibility of projects and desks; I can see employees projects and desks assigned to me.
      

    • Clients VIEW - (Projects, Desks) visibility of Clients based on the visibility of projects desks visibility I can see employees based projects and desks assigned to me.
      

    • Requests VIEW - (Clients, Projects, Desks) visibility of requests depends on Clients visibility, I see requests of users that I can see, in turn I can see Clients based on my Projects and Desks, so Projects, desks, Clients should have at least view own rights.

    • Clients tab/Accounts VIEW - chained with core/banking accounts logic, if true → core/banking accounts true.
      

    • Clients tab/Transactions VIEW - fully chained with core/banking transaction logic.
      

    • Clients tab/Requests VIEW - chaining: if checkbox true -> client encrypted email change to false, and vise versa.
       Now, all client submodules checkboxes are disabled if CLIENTS view_own is disabled, so when we decide to click on this checkbox, all necessary dependencies will already be set by that time.

      CORE BANKING
      NOTE! Assets/Accounts/Wallets are fully chained, in our system, these entities cannot exist separately.

    • Core banking/Assets VIEW - (Clients, Projects, Desks Accounts, Wallets, Configurations) - visibility of Assets depends on Clients visibility, I see Assets of Clients that I can see, in turn I can see Clients based on my Projects and Desks.
      We need Accounts for deposit/withdrawal functionality, Wallets for navigating to wallets of this asset by clicking on it.
      Configurations - for currencies list.
      Show transactions history is hidden, in case transactions view: false

    • Core banking/Accounts VIEW - (Clients, Projects, Desks Assets, Wallets) - visibility of Accounts depends on Clients visibility, I see Accounts of Clients that I can see, in turn I can see Clients based on my Projects and Desks.
      We need Assets for expandable row functionality, Wallets for navigating to wallets by clicking on asset which inside of expandable row.
      Configurations - for currencies list, account types in filters.
      Show transactions history is hidden, in case transactions view: false
      Core banking Accounts EDIT - (Banks)

    • Core banking/Wallets VIEW - (Assets, Accounts, Configurations, Clients, Projects, Desks) - Wallets can be seen only after clicking on asset in Accounts of Assets modules so these modules should be visible, visibility of Accounts and Assets depends on Clients visibility, in turn, I can see Clients based on my Projects and Desks.

    • Core banking/Transactions VIEW - (Configurations, Clients, Projects, Desks, clients tab/transactions) - visibility of Transactions depends on Clients visibility, I see Transactions of Clients that I can see, in turn I can see Clients based on my Projects and Desks.
      Configurations - for currencies list and for filters.

      Clients tab/transactions and Core banking/transaction are fully chained; if we set the true view checkbox Clients tab/transactions, then Core banking/transaction will be true too, and the same for the edit checkbox.
      

    • Core banking Cards EDIT - ( Assets, Accounts, Wallets, Bank) - Card CU drawer if fetching Clients and finding accounts and assets of the Client and Bank. Visibility of Assets, Accounts, Clients based on my Projects and Desks so this modules should be true. Configurations are Always used with Assets, Accounts, and Wallets.

    Other modules are fully isolated

    Additional info:
    - Requests tab and Requests are now separated, u can click one of them and another will be disabled, 
    - Now all client submodules checkboxes are disabled if CLIENTS view_own is disabled.

• WICRM-323 - Duplicate clients
  Clients Table Added
  • There isIntroduced a new action in the clients table. Now, ifIf there is an attempt to re-register a client's accountclient to an already registered email or address, suchthe system will now log this attempt in a request will be recorded in the duplicates"Duplicates" table for better tracking and management of duplicate entries.

• WICRM-341 - TransactionsTransaction Info Drawer Added
  • A transaction info drawer inhas transactions module
    • Transaction info drawer is nowbeen added to the transactions module, allowing users to view fulldetailed transactioninformation information.for each transaction.
  • WICRM-227 - Refresh tokenToken implementationImplementation
    • WhileImproved thesession usermanagement isby active,implementing theyrefresh tokens. Now, active users will not be automatically logged outout, improving user experience and session continuity.

  • WICRM-133 - Remove mentionCrassula Mentions from Service

    • Removed all mentions of the Crassula system from servicethe service.

  • WICRM-346 - Run translationsTranslation Deltas on Facade Startup
    • Implemented a feature to automatically run translation deltas on(updates) when the facade startupservice starts, ensuring that the latest translations are applied across the system.