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

   ## Summary
   
   The Working Capital loan detail screen 
(`src/app/features/working-capital/loans/wc-loan-view.component.ts`) presents a 
loan as read-only. Four Working Capital capabilities exist on the Fineract 
backend and are already generated into `src/app/api`, but nothing in this UI 
reaches them:
   
   - delinquency actions — listed, but cannot be created
   - breach actions — no tab at all
   - near-breach actions — no tab at all
   - loan originators — cannot be attached to or detached from a loan
   
   An operator who needs to record a breach action on a working capital loan 
has to leave this UI and call the API directly.
   
   Working through those four surfaced several unrelated defects and coverage 
gaps in the same neighbourhood, tracked here as sub-issues so each can be 
reviewed on its own terms rather than as one undifferentiated diff.
   
   ## Scope
   
   Sub-issues cover:
   
   1. The four missing Working Capital write paths.
   2. A generated-client sync against `apache/fineract:latest`, and the interop 
loan-repayment command that the sync turns into a call with a missing body.
   3. The dashboard guidance tour highlighting the sidebar instead of the card 
its own copy describes.
   4. Global search silently swallowing a result click under load.
   5. RBAC dimensions the existing backend RBAC spec does not reach.
   6. A repeatable demo dataset for manual release-candidate testing.
   
   ## Out of scope
   
   - Editing or deleting existing delinquency/breach/near-breach actions. This 
epic covers create and list; correction paths are a separate concern (compare 
#283 for the equivalent gap on interest pauses).
   - Working Capital screens still using the browser's native `confirm()` — 
tracked in #232.
   
   ## Notes
   
   Items 1 and 2 depend on Fineract 1.15.0+ endpoints that are not reachable on 
the public community sandbox, so their e2e cover is mocked.
   


-- 
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