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.
Webhooks are very common today. What are webhooks? They are a way to get notified when something happens. For example, if you like to get notified when a virtual machine shuts down in Microsoft Azure, just configure a webhook URL in Azure. When the virtual machine shuts down at any point in time, it calls the configured webhook URL. This method is much better than polling to see if the virtual machine has shut down.
"Microservices" was once just another buzzword, but now organizations have begun to understand their value and how they can significantly and positively impact business processes. The idea of Microservices arose from the difficulty of managing large systems so as to avoid duplicate functionality in different areas and from the efficiency that their re-useable nature would theoretically deliver.
Every day we hear about how data has been compromised. This is the world we live in and it creates an increasing need for securing business and personal data. FlowWright's workflow product minimizes security concerns by requiring access only to data that it needs to make decisions - and this is done easily by pointing to data via a key. FlowWright is fundamentally focused on data security. FlowWright is based on client-server web technologies but uses many ways to ensure user information is secure.
FlowWright supports many infrastructure configurations with out of the box and a little bit of configuration. The simplest form being an application server and a database server; including running all in one machine. FlowWright users benefit from the platform supporting Virtual machines within VMWare, Microsoft Azure, Amazon or any other VM or cloud platform.
FlowWright engines are architected as worker processes or robotic workers that perform work for workflow processes. Whether the engine is processing workflows, forms, ESB events, they are all processed by robotic workers. Robotic workers are designed for performance, but they are also able to return all resources used by the worker such as CPU, RAM any other resources back to the Operating System (OS).
Most processes today are static, no matter how many workflow instances that you kick off, they all have a similar structure. We also know the data fed into these workflows might be different, and therefore decisions made within the workflow instances might be different.