New 'Deferred Processing List' functionality

Within finPOWER Connect, certain functionality should not (and in some cases, cannot) occur within a database transaction. This includes:

• Running Application Shortcuts
• Publishing Documents
• Processing Workflows

Of the above, only the running of Application Shortcuts was handled (see KB #10145) and has now been updated to use the new finBL.DeferredProcessingList.

Any Application Shortcuts executed from the business layer (e.g., via finBL.ExecuteApplicationShortcut) within a database transaction (e.g., within a Script , to show the Accounts form) should work as before but just use the new functionality.

The following parts of finPOWER Connect have been updated to cater for deferred Workflow processing:

• Account Type Status Change Rules
• Previously, any Workflow created by the Rule was processed within a database transaction and the Rule failed if the Workflow failed to process. This now uses the Deferred Processing List which means that the Rule will not fail if Workflow processing failed. The Workflow will still be processed but after all database transactions have been committed.
• Workflows created from within a Version 2 type Workflow.
• When the original Workflow has finished processing, any newly created Workflows were processed. This now uses the DeferredProcessingList in there is an uncommitted database transaction.