| Id: | 11660 |
| Product: | finPOWER Connect |
| Type: | NEW |
| Version: | 2.00.02 |
| Opened: | 16/01/2014 |
| Closed: | 23/01/2014 |
| Released: | 05/02/2014 |
| Job: | J012748 |
 High Importance |
|
 Breaking Change |
|
Workflows; New processing mode to limit Database Transactions and let Web Services run
Web Services such as the new Credit Bureau Bank Account Enquiry are prevented from running inside Database Transactions since rolling back the transaction would rollback any records that were created in the ISServiceLog table that is used to audit all external requests.
Previously, processing of a Workflow would take place in a single outer database transaction.
This behavior has been changed so that the following now take place in their own database transactions:
* The 'BeforeProcess' Script event
* Processing of each Workflow Item.
* If more than one item is being processed, e.g., the Workflow has a series of 'Automatic' items, each of these takes place in its own database transaction.
This change may affect Scripts that use Workflows, e.g.:
* If one Workflow Item processed successfully but the next did not, the Workflow will now reflect this. Previously, the database transaction will have been rolled back so that no changes to the Workflow will have been recorded.
* Any Scripts or other processes that attempt to process a Workflow whilst in a database transaction should still work as expected but will fail if attempting to process a Workflow Item that uses a Web Service call, e.g., the new Bank Account Enquiry type item.
IMPORTANT: All existing Workflow types and their corresponding Script code should be tested.