Monitor Category Changes; added Script events to handle additional processing requirements

The Account Monitor Category Change wizard/ object has new script events to handle additional processing requirements.

A script of type "Object Events", object "AccountMonitorCategoryChange" should be created to handle Monitor Category change events. After a script has been created, it must be linked to an Account Type on the Scripts page, "MonitorCategoryChange" Event script.

The finAccountMonitorChange object is now used to handle Account Type Rule and Workflow Item Monitor Category changes, previously they used an internal function. This means they can use the event scripts as well. To this end there is a new property on finAccountMonitorCategoryChange "Source". This can be used to determine the source of the change.

The script can handle four events:

ExecuteCommitPre
Runs at the start of ExecuteCommit and can be used to validate and tweak values. Return False, with an error message, to cancel the Commit.

ExecuteCommitPreInTransaction
Runs during ExecuteCommit, after a Database Transaction has begun but before any work has started. It can be used much like the ExecuteCommitPre event, but because it is in a Database Transaction must not be used to interact with the user.

ExecuteCommitPostInTransaction
Runs during ExecuteCommit, after work has been completed but before the Database Transaction is committed. Use to implement additional functionality that must be part of the overall Commit.

ExecuteCommitPost
Runs at the end of ExecuteCommit. Since the Database Transaction is complete use with caution. Any failure here will not affect the overall Commit.