You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "James Dailey (Jira)" <ji...@apache.org> on 2024/08/22 15:59:00 UTC
[jira] [Updated] (FINERACT-1918) Create Loan Product - field transactionProcessingStrategyCode is breaking Mifos-UI
[ https://issues.apache.org/jira/browse/FINERACT-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Dailey updated FINERACT-1918:
-----------------------------------
Fix Version/s: 1.11.0
bouncing to next planned release 1.11.0 from 1.10.0
> Create Loan Product - field transactionProcessingStrategyCode is breaking Mifos-UI
> ----------------------------------------------------------------------------------
>
> Key: FINERACT-1918
> URL: https://issues.apache.org/jira/browse/FINERACT-1918
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
> Affects Versions: 1.9.0
> Reporter: Mohit Sinha
> Priority: Major
> Fix For: 1.10.0, 1.11.0
>
> Attachments: Screenshot 2023-04-06 at 3.04.35 PM.png, Screenshot 2023-04-06 at 3.05.08 PM.png, Screenshot 2023-04-06 at 3.05.27 PM.png
>
>
> Till version {_}1.8.4{_}, the API {_}api/v1/loanproducts{_}, was having the field {_}transactionProcessingStrategyId{_}.
> I have verified that the functionality works fine till {_}1.8.4{_}.
> This field is currently handled in the develop branch of openmf/community-app.
> In the current _develop_ branch of Fineract, _transactionProcessingStrategyCode_ is expected in place of it.
> So, this is causing a breaking change in the community-app.
> Should we fix it over here by allowing both these fields and giving more precedence to _transactionProcessingStrategyId_ if both the fields are passed.
> Or should a commit be made in the community-app to fix this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)