Account Minimum Payment Change; Cancel now supports scripting

Changes have been made to Account Minimum Payment Change functionality, mainly so that the Cancel function supports scripting.

The finAccountMinimumPaymentChange object now includes a new function ExecuteCancel that takes a parameter accountHistoryPk that defines the Primary Key of the Account History item to cancel. This function will:

• Run script events as described below.
• Validate the data passed to the object.
• Cancel the Minimum Payment change, including updating the Account's Next Process dates.
• Add an Audit Log to the Account.
• AuthorisedName, AuthorisedReason and Reference properties can be set and will be audited.
• Add an Account Log if the LogCreate property is True.

NOTE: The finAccountFunctions.AccountHistoryMinimumPaymentCancel function will continue to work, but now uses the finAccountMinimumPaymentChange object to handle the cancel. This means all the scripting events will be executed. You should consider using the finAccountMinimumPaymentChange object instead of this function.

The following new events are supported in an "Object Event", "AccountCreditLimitChange" type script.

• ExecuteCancelPre
• Runs at the start of ExecuteCancel
• Return False to cancel
• ExecuteCancelPreInTransaction
• Runs during ExecuteCancel, after a Database Transaction has begun but before any work has started
• Return False to cancel
• ExecuteCancelPostInTransaction
• Runs during ExecuteCancel, after work has been completed but before the Database Transaction is committed
• Use to implement additional functionality that must be part of the overall Cancel
• ExecuteCancelPost
• Runs at the end of ExecuteCancel
• Since the Database Transaction is complete use with caution. Any failure here will not affect the overall Cancel