FlowWright is designed to be extended and expanded and many of our users push the product into new areas (which we love to see!) To highlight all the ways FlowWright can be extended we summarize them below.
If you never heard of this product before you ma want to familiarize yourself with, NuGet.org as it is becoming very popular. Many developers use this website to include API packages to their software projects. Why should teams use NuGet? Typically when you want to use an API, you have to know what libraries/DLLs to reference; with NuGet all you have to do is to find the package and click install, then the NuGet package manager automatically downloads the selected package and its dependencies and simply adds them to your project.
Developers build most applications using a common design pattern. That pattern can be object-based, object oriented, component-based, modular, etc...: some pattern exists. FlowWright helps developers through use of a layered approach where modules are separated into components, and components break down into objects using a full object oriented design.
FlowWright was built with two mandates: 1) "keep it intuitive" and 2) "do it your way". Most BPM/Workflow products require users to implement everything within their platform ecosystem. Users often learn the hard way that this restrictive approach makes it difficult to accomplish your goals successfully or efficiently. This blog explains why workflow without limitations is the best approach.