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!
As our company was growing 25+ years ago, we were simultaneously pioneering many of today's object-relation concepts in an effort to help companies understand how everything relates to one another from a process and data standpoint. The following patents help outline our focus on delivering a great solution in the workflow automation space for years to come.
As our team works with business analysts around the world, we find out that some of them are new to workflow and concepts within workflow that are achievable. If the latter is the case, we wanted to share some insight into introducing some of the basic concepts of workflow task routing. We hope you find these helpful!
One of our customers once came to us with a specific problem, "we are a data company but it takes a long time to get our data shared to our users". So what's the issue here? Given data security needs today organizations should have several checks and balances to get data into their own employees hands today. You never know who's going to get their hands on to your data, with the stories in the news highlighting hacking crisis' out there with companies such as Facebook, EquiFax, TJX Companies that have all had huge data breaches. These data breaches not only are a cost to the organizations, but also get passed to consumers and ruin their brand trust experience as they possibly have their identity information stolen and misused.
In most organizations with manual processes, everyone does what they are suppose to do (maybe sometimes not) but what's missing is a centralized platform for communication and collaboration. Typically organizations live in their own systems "CRM" for sales, "ERP" for operations, etc. The main reason this causes issues is that there is no accountability. No one knows where a certain item is in the process, because there isn't a centralized macro view.
As many Enterprise organizations implement Micro-services, they either have non-working or satisfactory implementations of Micro services. This is a trend we have seen the last 2 years within our customer base. What companies are truly looking for is a workflow solution to re-architect their Micro-services architecture/solution.
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).
Just like physical engines, software engines today perform most of the heavy lifting within a software application. Software engines are typically running on a server, consuming many resources, spawning many threads, processes and executing code to perform functionality for the end user. We discuss the type of engines below in greater detail, and what you need to know.