Workflows: talking about a paradigm shift
We were introduced to the Workflows paradigm on the Riskclick project, and immediately were taken by it. The simplicity and abstraction it provided makes it a perfect framework for many problems, and we have used it for projects ranging from AI thought processes to insurance to eCommerce.
In 2004 we led the creation and the implementation of a proprietary workflow engine, which featured process spawning, BizTalk -based gateway, and web services integration. Using a visual process editor, we used this newly created workflow language to build an underwriting application for the FICOH insurance company of Hawaii.
In 2005 we took the workflow concept and put it to use in games AI for the latest version of NOKs. A computerized entity, for example, might be written to have a specialized profession of guarding an outpost. For that, it would patrol on location, and when an enemy would come too close, the guard would initiate a hot pursue until the enemy is driven far enough. Realizing that this is a classic state-based process, we wrote a C++ workflows engine, with which a whole set of AIs were written.
More than all, workflows change the ways one thinks about problems. We used the concept for the Devix Commerce suite. The system's infrastructure was designed so that every functional task would be exposed as an API to external applications with no translation layer or extra development effort. Other features included a rule engine with a C# interpreter, fully customizable UI and an XSLT-based synchronization framework.
When Microsoft launched their WF, Windows Workflow Foundation, it got even better. While we still maintain our propiatory workflows engine, we could now combine it with the strength of C# and with a built-in visual editor. What makes it a great tool to use, for programmers, users and managers alike.