Aman-Mittal commented on issue #778:
URL: 
https://github.com/apache/fineract-backoffice-ui/issues/778#issuecomment-6211183240

   ## Business process flow
   
   ```mermaid
   stateDiagram-v2
       [*] --> Original: Active loan, original schedule
       Original --> ReAged: reAge<br/>REAGE_LOAN
       ReAged --> Original: undoReAge<br/>UNDO_REAGE_LOAN
       Original --> ReAmortized: reAmortize<br/>REAMORTIZE_LOAN
       ReAmortized --> Original: undoReAmortize<br/>UNDO_REAMORTIZE_LOAN
   ```
   
   Typical use: a restructuring officer re-ages a loan after a hardship 
agreement. A supervisor reviews the new schedule and undoes it if the terms 
were entered wrongly, before any repayment is posted against the new schedule.
   
   ## UI mockup
   
   ```text
   ┌ Loan #000456 · Active · Re-aged on 2026-10-14 ───────────────────────────┐
   │ [Repayment]  [⋮ More actions]                                            │
   │               ├ Re-age …                                                 │
   │               ├ Re-amortize …                                            │
   │               └ Undo re-age         ← UNDO_REAGE_LOAN, shown only after  │
   │                                       a non-reversed re-age               │
   └──────────────────────────────────────────────────────────────────────────┘
   
   ┌ Undo re-age ──────────────────────────────────────── ⚠ destructive ─────┐
   │ The repayment schedule will return to the version before the re-age on   │
   │ 2026-10-14 (12 instalments → 8 instalments).                             │
   │ Note  [ Wrong frequency entered                       ]                  │
   │                                          [Cancel]   [Undo re-age]        │
   └──────────────────────────────────────────────────────────────────────────┘
   ```
   


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