Transaction Types; split Permission Key from one Key to Open and Commit

A User could be denied use of a Transaction Type via a Permission Key. This has been enhanced so that there are two Permission Keys, one to allow/ deny a User the ability to Open and Edit Transactions and one to allow/ deny a User the ability to Commit Transactions.

This allows, for example, a User to be able to enter a batch of Transactions but not to be able to commit them. Another User could then review the batch before they commit it.

This change effects the following areas

• Transaction Entry
• Bank Entry
• Account Payment wizard
• Account Transfer wizard
• Account Withdrawal/ Refund wizard
• Income Distribution

Note, for example, if a Transaction Type allowed Open but denied Commit, the User should not be able to use Individual Transaction Entry, but can still open and edit a batch of Transactions.

The following Business Layer Functions and Properties have been obsoleted:

• finTransactionType.PermissionKeyExecute
• Returns PermissionKeyCommit. Use PermissionKeyOpen and PermissionKeyCommit instead
• finTransactionTypeRO.HasPermissionToExecute
• Returns HasPermissionToCommit. Use HasPermissionToOpen and HasPermissionToCommit instead
• finTransactionTypeRO.PermissionKeyExecute
• Returns PermissionKeyCommit. Use PermissionKeyOpen and PermissionKeyCommit instead

The following HTML Widgets have been updated:

• Account Payment Received wizard HTML Widget
• Version: 1.14 (22/12/2022)
• HtmlWidget_AccountPayment
• Account Withdrawal wizard HTML Widget
• Version: 1.13 (22/12/2022)
• HtmlWidget_AccountWithdrawal
• Account Transfer wizard HTML Widget
• Version: 1.05 (22/12/2022)
• HtmlWidget_AccountTransfer
• Account Transaction wizard HTML Widget
• Version: 1.10 (24/01/2023)
• HtmlWidget_AccountTransaction