Because FlowWright is an embeddable workflow engine, many customers embed FlowWright to power their application workflows, populate their UIs, integrate system components, accelerate product development, and simplify maintenance. FlowWright is the only embeddable .NET workflow engine available is happily used around the world as a result. We share 3 considerations to keep in mind when going through this process.
API services have become critical over the last few years, with many cloud providers providing APIs for many different services. Even non-UI based applications provide APIs for a variety of services. For example, Microsoft Azure provides APIs to make use of Azure features like storage, key vaults and much more.
One of our customers is a large European natural gas distributor. Providing natural gas to millions of customers requires efficient systems to manage distribution, maintenance, and customer relations. Our customer determined that the best path forward to achieve efficiency is to build systems based on a business process management system that includes processes automated with integrated workflow software.
API's are the primary way to access most applications. And as applications become increasingly feature-and-function-rich, their API can become more complex and impact performance. Workflow applications evolved in this exact way: when they were rudimentary then their APIs were small and there were few issues - but as features and functionality were added, API performance degraded noticeably.
By now you understand that you can pass initial variable/global values to any workflow instance at the start of its execution. These passed in values will be used to initialize the values of the variables and globals defined in your workflow design.
FlowWright supports the standard data types for variables and globals, which are:
Workflow users whose applications make use principally of the Microsoft technology stack often consider open source Java workflow products at the same time they consider .NET-based FlowWright. There are 2 main reasons that most Microsoft users end up choosing FlowWright over free open source Java products.
Another year has come and gone and we couldn't have been more proud of the work our team produced. FlowWright BPM is being used by companies all over the globe. Our CTO, Dileepa Wijayanayake, shares what the new year will have in store for development on our product road map. Click the video below and watch.
There are many open source workflow products available. However, for most companies, security is a serious concern. Open source solution code is available to anyone to view, making it relatively easy to hack the software. While some organizations still build solutions using open source platforms, the risk is often deemed too high for most organizations that prioritize security.