Aman-Mittal opened a new issue, #795:
URL: https://github.com/apache/fineract-backoffice-ui/issues/795

   #### Summary
   Two complete client-level screens exist, but nothing links to them:
   - **Client Charges** at `/clients/:clientId/charges`;
   - **Client Collateral** at `/clients/:clientId/collaterals`.
   
   Both work when the URL is typed in, but no menu, tab or button on the client 
page leads there.
   
   Separately, the client page's **New Account** menu offers Loan, Savings, 
Fixed Deposit and Recurring Deposit, but not **Share Account**. The 
share-account form already supports being opened for a specific client 
(`?clientId=`).
   
   #### Current behavior
   - **Actions** menu on an active client: Close Client, Propose Transfer, 
Transfer Immediately, Assign Staff, Set Default Savings Account.
   - **New Account** menu: Loan Account, Savings Account, Fixed Deposit, 
Recurring Deposit.
   - The tabs include Savings, Loan, Identifiers, Addresses, Family Members, 
Notes, Documents, Custom Fields, Deposits, Shares and Standing Instructions. 
None of them leads to charges or collateral.
   - In source (`main` @ `8da1086f`), the only links to `['/clients', id, 
'charges']` and `['/clients', id, 'collaterals']` are inside the charge and 
collateral components themselves. `client-view.component.ts` contains neither 
"charges" nor "collateral".
   - `share-account-form.component.ts` reads `queryParams.clientId` to pre-fill 
the client, but nothing navigates there with it.
   
   #### Expected behavior
   - From the client page, staff can open the client's charges (and add one) 
and the client's collateral (and add an item).
   - **New Account** includes **Share Account**, which opens the share-account 
form pre-filled with the client.
   
   #### Steps to reproduce
   1. Open an active client (for example `/clients/view/1`).
   2. Check **Actions**, **New Account** and every tab: there's no route to 
client charges or collateral.
   3. Open `/clients/1/charges` and `/clients/1/collaterals` directly. Both 
pages load and offer **Add Charge** / **Add Collateral**.
   4. Open **New Account**: there's no Share Account option.
   
   #### User impact
   - Client-level fees (membership or registration fees, for example) and 
client-owned collateral (used to secure loans) can't be managed in normal use. 
The screens are effectively dead code for operators.
   - Opening a share account for an existing member means leaving the client, 
going to Products → Share Accounts, and searching for the client again.
   
   #### Evidence
   The New Account menu on client #1, with no Share Account option. This client 
is also a group member, which the page doesn't show (see #794).
   
   ![Client page New Account menu without Share 
Account](https://raw.githubusercontent.com/Aman-Mittal/fineract-backoffice-ui/assets/issue-screenshots/ux-audit-2026-10-16/client-new-account-menu.svg)
   
   `/clients/1/charges` renders "Client Charges · ADD CHARGE · No records 
found", and `/clients/1/collaterals` renders "Client Collateral · ADD 
COLLATERAL · No records found". Both screens are functional, just unlinked.
   
   #### Proposed improvement
   - Add **Charges** and **Collateral** tabs to the client page, reusing the 
existing list components, or at minimum add **Add Charge** and **Add 
Collateral** items to the client's Actions menu.
   - Add **Share Account** to the New Account menu, navigating to 
`/products/shares/create?clientId=:id`.
   - Gate each entry with the same permissions the target routes use. Per the 
existing pattern, the items should be disabled with a "Requires …" tooltip when 
the user lacks the permission.
   - Give the charges and collateral pages' breadcrumbs the client's name: 
"Clients › {client} › Charges".
   
   #### Acceptance criteria
   - [ ] Client charges and client collateral are reachable from the client 
page in one or two clicks.
   - [ ] New Account → Share Account opens the share form with the client 
pre-filled.
   - [ ] The new entry points respect permissions (hidden or disabled with a 
reason when not permitted).
   - [ ] The breadcrumbs on those screens identify the client.
   
   #### Verification status
   Reproduced on the deployed `main` (2026-10-16), superuser, tenant `default`. 
Orphaned routes confirmed in source; direct-URL access confirmed live.
   
   #### Related API capabilities
   - `GET/POST /v1/clients/{clientId}/charges` (client charges).
   - `GET/POST /v1/clients/{clientId}/collaterals` (client collateral).
   - `POST /v1/accounts/share` (share account application for a client).
   
   Related: #754 (client charges can't be paid or waived; it presupposes these 
screens are reachable), #794 (client page content).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to