Id: | 12660 |
Product: | finPOWER Connect |
Type: | NEW |
Version: | 2.02.05 |
Opened: | 10/12/2014 |
Closed: | 23/02/2015 |
Released: | 26/03/2015 |
Job: | J014620 |
![]() |
Workflows; New "Workflow Executor" object to process Version 2 type Workflows
With the introduction of Web Services into Workflows and the general increase in complexity of Workflows, executing a Workflow via the methods in finWorkflowFunctions is too restrictive.
A new finWorkflowExecutor object has been added into which a Workflow can be loaded and processed or an item actioned.
This object gives far more information about the state of the Workflow.
The Workflow Type Script can now access the Workflow Executor object for certain events as per the following code sample:
Dim WorkflowExecutor As finWorkflowExecutor
WorkflowExecutor = DirectCast(eventArgs.GetObject("WorkflowExecutor"), finWorkflowExecutor)
The template Workflow Type Script adds a WorkflowExecutor reference if the Workflow Type is "Version 2".
Since the way that Workflows are executed differs when using a Workflow Executor, Workflow Types can now define a Version on the General page of the Workflow Types form. Version 2 Workflow Types will be executed via a Workflow Executor (the preferred method) whereas Version 1 Workflow Types will still be executed via methods in finWorkflowFunctions.
New Workflow Types should be created as "Version 2" Workflow Types and this may be enforced when adding future Workflow functionality such as Account Application Workflows. Future Workflow functionality may also be limited for non-"Version 2" Workflow Types.
WARNING: If you set a Workflow Type to "Version 2", ensure it is fully tested since, as mentioned above, differences in the way that Workflows are processed may affect the Workflow, particularly if Workflow Type Scripts are involved.
Workflow Type Scripts for "Version 2" Workflows should not use any functionality from finWorkflowFunctions; Only Workflow functionality available through the Workflow Executor should be used.