<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

FlowWright

FlowWright
Our goal is to help you run your business and solutions the way you want them to run - reliably, efficiently, and in control. We aim to improve the quality of your life and your business. We see your success as our success.
Find me on:

Recent Posts

Extending FlowWright - make it work the way you want

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. 

How to use NuGet FlowWright package

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.

Performance monitoring FlowWright engines

Performance monitoring is built into FlowWright workflow.  FlowWright uses performance instrumentation built into the Windows Operating system and leverages the performance monitoring and counters that are also provided by Microsoft Windows.

Things to consider when implementing Microservices

More organizations are adopting Microservices to run their business.  Like any kind of implementation, Microservices should be implemented properly in order to be effective and reliable.

FlowWright object model

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 high level API model

The FlowWright high level API is the main API for all FlowWright components, user interface, business logic, engines and gives all access to functionality and objects within FlowWright.  The API is divided into parent/child objects as described below:

Morphing processes at run-time

Morphing processes at run-time is a complex feature within our workflow product that allows users to create Dynamic Sub-workflows.  FlowWright is currently one of the only products on the market that is able to do this.  The real world example below might sound familiar.

Digital processes that can think

There are many ways to make digital processes make decisions.  Rules are used in almost any workflow process today to determine what path of steps and decisions within a process should be followed. 

Workflow without limitations!

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. 

Workflows that continue processing based on incoming messages; what you need to know

A workflow can publish events an Enterprise Service Bus (ESB.)  And a workflow instance may also wait for certain event or message to arrive: once the message arrives, the workflow process will proceed.