Business Layer objects will fail to commit if Account could not be sent an SMS or Email Document

The following wizards (and their supporting business layer functionality) will fail to commit if attempting to send an SMS or Email Document to an Account where none of the Account's Clients can receive the Document:

• Bank Transaction Reverse
• finAccountPaymentReverse/ finBankTransactionReverse
• Account Restructure
• finAccountRestructure
• Account Payment Arrangement
• finAccountPayArrangementAdd
• Floating Interest Rate Change
• finAccountFloatingInterestRateChange
• NOTE: This is a bulk wizard so the check is only performed in the business layer when calling the ExecuteCommit method. If one Account fails, the entire Commit will fail.

The finBankTransactionReverse, finAccountRestructure and finAccountPayArrangementAdd objects now have a CanSendDocument method that can be used to ensure the Account can be sent the Document. This is now used from the User Interface (i.e., the corresponding wizard) and also allows Scripts to ensure that a Document can be sent when using these objects.

Where applicable, the above wizards now check that the Document (e.g., the Advice Document) can be sent when leaving the relevant wizard tab (or, in the case of the Bank Transaction Reverse wizard, clicking the 'Finish' button).

A new business layer function finAccountFunctions.CanSendDocument has been added. This can be used by Scripts to easily check whether an Account can be sent a Document (mainly for Email and SMS Documents).