[
https://issues.apache.org/jira/browse/FINERACT-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
devi pathak updated FINERACT-2556:
----------------------------------
Description:
## Problem
Currently, updating the approved amount with the same value still triggers:
- unnecessary history entries
- business events
- redundant database writes
These no-op updates do not result in any meaningful state change but still
cause side effects in the system.
## Proposed Solution
Add validation to prevent no-op updates when the new approved amount is equal
to the current approved amount.
The system should reject such requests and ensure that only meaningful changes
are processed.
## Benefits
- avoids unnecessary history entries
- prevents redundant business event triggering
- reduces unnecessary database writes
- improves overall system efficiency and data consistency
## Acceptance Criteria
- Updating approved amount with the same value should be rejected
- No history entry should be created for such requests
- No business events should be triggered
- Proper validation error should be returned to the user
was:
## Description
Currently, updating the approved amount with the same value still triggers:
- unnecessary history entries
- business events
- redundant database writes
This improvement proposes adding validation to prevent no-op updates when the
new approved amount equals the current value.
This helps avoid unnecessary processing and ensures only meaningful updates are
applied.
> Prevent no-op updates for approved amount modification
> ------------------------------------------------------
>
> Key: FINERACT-2556
> URL: https://issues.apache.org/jira/browse/FINERACT-2556
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Loan
> Reporter: devi pathak
> Priority: Minor
> Attachments: image-2026-03-26-21-45-14-591.png
>
>
> ## Problem
> Currently, updating the approved amount with the same value still triggers:
> - unnecessary history entries
> - business events
> - redundant database writes
> These no-op updates do not result in any meaningful state change but still
> cause side effects in the system.
> ## Proposed Solution
> Add validation to prevent no-op updates when the new approved amount is equal
> to the current approved amount.
> The system should reject such requests and ensure that only meaningful
> changes are processed.
> ## Benefits
> - avoids unnecessary history entries
> - prevents redundant business event triggering
> - reduces unnecessary database writes
> - improves overall system efficiency and data consistency
> ## Acceptance Criteria
> - Updating approved amount with the same value should be rejected
> - No history entry should be created for such requests
> - No business events should be triggered
> - Proper validation error should be returned to the user
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
