The user would like improvements to transfers and advances. First, they would like repayments to be linked to the correct advance. Additionally, the user would like custom fields to show as read-only in the details and highlight viewer. Next, the user would like erroneous transfers/advances from classic to be imported regardless of incorrect account codes. The user would also like the repaid flag to be read-only. Finally, the user would like a way to report on transfers/advances imported into the system that need to be fixed at post-import time.
We have decided to leave part of this problem up to the user to fix. We don't have a way to link repayments to their respective advances automatically so the user must do this. However, we're going to adjust InterfundTransactionType to have two new values:
LegacyRepay - for repayments that have valid accounts
ClassicTransferAdvance - for transactions with invalid accounts (see account rules for transfers/advances/repayments)
Reporting on these values will allow the user to have a report of transactions for the current fiscal year that need to be re-posted
We need to make a few adjustments to the UI as well:
Update the StandardCustomFields for InterfundCashTransaction to be marked as calculated so they show up as read-only in the UI
Add customfields for InterfundCashTransaction to the UI
Update the InterfundCashTransaction grid to disable repay/edit/delete buttons for any transfer/advance in an archived posting period. Make the appropriate changes to the detail viewer to remove edit buttons as well
We need to update InterfundCashTransaction:
getTransactionType should no longer throw an exception. Instead, it should create the appropriate InterfundCashTransaction with one of the following types: [Transfer, Advance, RepayAdvance, or ClassicTransferAdvance]
If it's a repayAdvance, modify it to be a LegacyRepay IF importing
Add a rule to replace the exception being removed in getTransactionType() that will fire when NOT importing
The user would like improvements to transfers and advances. First, they would like repayments to be linked to the correct advance. Additionally, the user would like custom fields to show as read-only in the details and highlight viewer. Next, the user would like erroneous transfers/advances from classic to be imported regardless of incorrect account codes. The user would also like the repaid flag to be read-only. Finally, the user would like a way to report on transfers/advances imported into the system that need to be fixed at post-import time.
We have decided to leave part of this problem up to the user to fix. We don't have a way to link repayments to their respective advances automatically so the user must do this. However, we're going to adjust InterfundTransactionType to have two new values:
LegacyRepay - for repayments that have valid accounts
ClassicTransferAdvance - for transactions with invalid accounts (see account rules for transfers/advances/repayments)
Reporting on these values will allow the user to have a report of transactions for the current fiscal year that need to be re-posted
We need to make a few adjustments to the UI as well:
Update the StandardCustomFields for InterfundCashTransaction to be marked as calculated so they show up as read-only in the UI
Add customfields for InterfundCashTransaction to the UI
Update the InterfundCashTransaction grid to disable repay/edit/delete buttons for any transfer/advance in an archived posting period. Make the appropriate changes to the detail viewer to remove edit buttons as well
We need to update InterfundCashTransaction:
getTransactionType should no longer throw an exception. Instead, it should create the appropriate InterfundCashTransaction with one of the following types: [Transfer, Advance, RepayAdvance, or ClassicTransferAdvance]
If it's a repayAdvance, modify it to be a LegacyRepay IF importing
Add a rule to replace the exception being removed in getTransactionType() that will fire when NOT importing