The FlowWright low level API and engine API was built so that workflows can be executed in real-time with high performance. Although this API has existed in previous versions, FlowWright v9.6 introduced Microservices, making it possible to call a workflow definition via FlowWright's REST API. Under the hood of the Microservice, the low level API is used to execute workflows in real-time, or in memory.
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.
When new clients onboard the FlowWright workflow platform we ensure that they are set-up for success by ensuring all team members have completed our 4 day on-site Training Program.
FlowWright v9.6 has been in the works for a while now - and now it is HERE! This latest version includes upgrades, including a new and very responsive User Interface. We listened to feedback from business users and gave the user interface a much-needed face lift. We had graphics designers and top developers working all year to design and implement FlowWright improvements - a great deal of thought, planning, and effort have resulted in significant benefits for FlowWright customers.
IT migrations are challenging and inefficient if tools are not in place to drive organization and process. FlowWright provides customers several ways to efficiently and effectively migrate processes with ease. FlowWright makes it easy to 1) migrate from other platforms to FlowWright and 2) to migrate between FlowWright servers/environments. The 3 main principal ways FlowWright users perform migrations is outlined below:
Most systems integrate today through APIs or direct database connections. Enterprise services buses are becoming a more popular alternative to API when it comes to creating integrations. Events can easily be processed through ESB when they arrive or when the event happens. Today most UI based applications function based off trigger events; for example- when you click on a button, the code behind the click event of the button performs certain functionality and fires off a "next step" or "task". Take that same concept and apply it to the back end and you are able to perform functions when events fire off. We explain more below.
Service oriented architecture, also known as SOA, has been around for a while, but what about service oriented processes? We currently have customers who are already implementing these types of processes using FlowWright's framework.
Many organizations use paper-based processes and rely on manually passing folder to manage review and approval workflows. This is normal but in efficient. Are you staring at a pile of files and papers piled on your desk that have been there for a month? Many of us sitting here have huge piles of paper that seem overwhelming - and often our productivity suffers because of it. We share your desire to be free of the paper chase!