[
https://issues.apache.org/jira/browse/FINERACT-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054538#comment-18054538
]
Adam Saghy commented on FINERACT-2453:
--------------------------------------
I don’t believe there are any missing transaction types in the list. While not
all transaction types are included, that’s intentional because we don’t need to
reprocess all transactions. Please let me know of any transaction types you
find missing and believe should be covered by the transaction processor.
> Improve logging of transaction processor to account for remaining transaction
> types
> -----------------------------------------------------------------------------------
>
> Key: FINERACT-2453
> URL: https://issues.apache.org/jira/browse/FINERACT-2453
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Edward Kang
> Assignee: Edward Kang
> Priority: Minor
>
> This works on the TODO item listed in processLatestTransaction() in the
> AdvancedPaymentScheduleTransactionProcessor. "TODO: Cover rest of the
> transaction types."
> Existing code creates a log.warn() for many acceptable transaction types,
> which is undesirable.
> The plan is:
> * Remove the log.warn() for transaction types that don't impact the loan
> scheduling process.
> * Group the remaining 19 transaction types based on their function and
> log.debug() their functionality and why they are excluded from being handled.
> * Only use log.warn() when the transaction type is INVALID.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
