FINERACT-1152: Use projected schedule to validate EMI end date in loan reschedule#5689
Open
San-43 wants to merge 1 commit intoapache:developfrom
Open
Conversation
2c5e10c to
02409ef
Compare
c0e8525 to
b867efd
Compare
Author
|
Hello @adamsaghy, sorry to bother you. After carefully reviewing everything, running tests in my local environment, and double-checking the failure causes, I’m convinced this was baseline/pipeline drift, as I suggested in a comment on FINERACT-1152. Could you please approve the workflows again? And if you have time, could you also review my changes? Please let me know if there is anything wrong. |
Author
|
Another baseline/pipeline drift? |
Author
|
I believe this is ready for review/merge. |
b867efd to
ca80a71
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Description
This PR fixes FINERACT-1152; loan reschedule validation and term-variation generation for EMI changes with
endDatewhen other reschedule changes (for exampleextraTerms) are submitted together.Previously, EMI/end-date validation effectively depended on the current installment schedule, which could reject valid requests where the end date only exists in the projected post-reschedule schedule.
Changes
emimust be positiveendDatemust not be beforerescheduleFromDateendDateendDateis before the next projected installment dateendDateandemifields for create-reschedule request payload examplesI would like to mention #5619 since it helped me to have a better overall view of the problem and the potential fix. Hope this goes well. Pls let me know if anything should be changed.
Checklist