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