The Process Engine manages rules based workflows of any scale, from simple file movement and notification to complex multilayered designs. The services provide a seamless integration with third party vendors providing a solution that meets your exact requirements.

Process designs can be simply created and adapted to meet your current and changing requirements.

Features

• Metadata driven workflows
• Manage media – eg. move, copy & delete
• Marshal and Manage (including load balance and job prioritisation)
• Reporting – eg. Completion/Error Notification

“Process designs can be simply created and adapted to meet your current and changing requirements.”

How It Works

The IPV Process Engine is a networked service that presents control and monitoring interfaces through a standard web services model, typically SOAP or RESTful communication protocols.

The Process Engine provides a framework to run and marshal workflows as described in the definition of a ‘Process’. The engine maintains the state of all processes including recovery, resumption and reporting.

The definition of a ‘Process’ is a set of rules and parameters that are required to drive an activity based on a certain conditions. Activities and the result drives additional activities, linking them together to complete a process or workflow.

The Process Engine utilises available IPV and third party activity libraries to construct a defined process or workflow. Each activity is built on WF4 (Windows Workflow Foundation), a component of the .NET4 development environment, and are constructed to actuate a domain based function, for example; Monitor a user defined watch folder and report changes. Therefore the Process definition must adhere to the available Activities and their requirements for operation.

These Processes are described using XAML as constructed from a suitable User Interface and then injected into the Process Engine via the web services interface.