Release 1.0.5 (11.09.2024)

Bugfixes:

WICRM-362 - Do not delete role if it using in ident token
- Now if a role is used by any entity in the identification tokens module, it will be impossible to delete such a role
WICRM-366 - Filter transactions by assetId does not work in crm ui
- Fixed filtering by AssetID column
WICRM-315 - Change approach of restoring password - issue with loader
- When entering an incorrect code, the input window used to jump up and return to its place again, updating its status to “Code is incorrect”, now this problem is not present

WICRM-369 - Allow '.' in translation labels
WR-410 - business is still creating with incorrect phone number
- When creating a business, the empty phone number field was not being recorded correctly

Features:

WICRM-345 - Add verification status to clients filters

WICRM-348 - Remove checkbox 'Create transaction' and create transaction always
- Previously, you could make a Deposit or Withdrawal transaction with an Asset and not create a transaction, so this action was not recorded anywhere. Now, by removing the checkbox, the possibility to perform the above operations without recording the transaction in the system has been removed

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
- There is a new action in the clients table. Now, if there is an attempt to re-register a client's account to an already registered address, such a request will be recorded in the duplicates table

WICRM-341 - Transactions info drawer in transactions module
- Transaction info drawer is now added to view full transaction information.

WICRM-227 - Refresh token implementation
- While the user is active, they will not be automatically logged out
WICRM-133 - Remove mention of Crassula from service
WICRM-346 - Run translations deltas on facade startup