Skelta Workflow.NET architecture is scalable to cater the needs of BPM requirements. Architecture diagram shown below provides the complete gist of its extensibility, interoperability, scalability and the flexibility to integrate with various third party applications or popular Microsoft products.

Click here to view full-size image

Skelta Workflow.NET is built on the robust Microsoft .NET architecture. The product is intended for developers, technical business managers, MIS and system administrators who wish to provide increased value to their software application, products or business processes by the addition of dynamic workflow functionality. It is built around a set of drag-and-drop ASP.NET Web Controls, thereby providing extensive features for workflow designing, tracking and management functionalities.

Skelta Workflow.NET's architecture is extensive, with components of workflow represented by 'Work Items'. The product already includes some vital work items and contains an option that allows developers to add their own work items.

Skelta Workflow.NET is based on the NT Service, and can be deployed even in a load-balanced environment. It contains a 'fail over engine and monitoring service', which transfers the workload to available working servers in the event of a failure.

The product uses database & XML as the repository for storing Workflow definitions, and tracking information. Any OLEDB compliant database can be used for this purpose. Skelta Workflow.NET engine control APIs can be invoked by a SOAP or .NET object. Also a new Workflow can be initiated on SMTP activities. Skelta Workflow.NET is designed as an effective and efficient optional component.

Skelta Workflow.NET’s open architecture exposed by XML and Web Services enable seamless integration with Microsoft .NET Servers and Microsoft Office 2003 products. It extends the functionality of various Microsoft products like BizTalk, SharePoint Portal Server, Windows SharePoint Services, CMS, Office 2003 & InfoPath.