Skip to main content

Release 1.0.5 (11.09.2024)

Bugfixes:

  • WICRM-362 - Prevent Role Deletion if Used in Identification Tokens
    • Roles that are in use by any entity in the identification tokens module can no longer be deleted, preventing potential system conflicts or loss of important role-based data.
  • WICRM-366 - Fix AssetID Filter in CRM UI
    • Resolved an issue where the transactions filter by AssetID was not functioning properly in the CRM user interface.
  • WICRM-315 - Password Recovery UI Issue Fixed
    • Fixed a bug where, during password recovery, the input window would jump after entering an incorrect code. Now, the status “Code is incorrect” is updated without any disruptive movement in the input window.

  • WICRM-369 - Allow Periods ('.') in Translation Labels
    • Now it's possible to use periods ('.') in translation labels, providing more flexibility for labeling translations.
  • WR-410 - Business Creation with Incorrect Phone Number Fixed
    •  Resolved an issue where businesses were being created with empty or invalid phone numbers, ensuring that the field is 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 in the clients section, making it easier to filter and view clients based on their verification state.

  • WICRM-348 - Remove 'Create Transaction' Checkbox and Always Record Transactions
    • Previously, transactions like Deposits or Withdrawals could be made without being recorded if the checkbox “Create Transaction” was unchecked. This feature has been removed, and now all such operations will always be recorded in the system, ensuring full transaction 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 Table Added
    • Introduced a new action in the clients table. If there is an attempt to register a client to an already registered email or address, the system will now log this attempt in a "Duplicates" table for better tracking and management of duplicate entries.

  • WICRM-341 - Transaction Info Drawer Added
    • A transaction info drawer has been added to the transactions module, allowing users to view detailed information for each transaction.

  • WICRM-227 - Refresh Token Implementation
    • Improved session management by implementing refresh tokens. Now, active users will not be automatically logged out, improving user experience and session continuity.

  • WICRM-133 - Remove Crassula Mentions from Service

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

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