Even though EDI is a very old file format, specially in the medical payment transaction processing industry, it's a very commonly used format. The healthcare industry has yet to move to newer technology as XML or JSON, therefore still uses EDI files.
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).
FlowWright Forms are very common within the workflow processes. Forms are meant to be routed to display information or capture information from a user. But, did you know Forms also can have decision logic, validation or business logic built into the form itself? We explain why that is important below.
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.
As you may know, you can build custom steps to do anything that you want them to do, and use them within workflows. Many of our customers build custom steps to perform certain functionality within workflows, but what about the validation of these step inputs? We explain how it works here.
As we travel to meet teams all over the globe using our product, we have the great pleasure of speaking with business analysts,. Business Analysts (BAs for short) know their domain very well, but some are not as familiar with workflow automation, business process automation or digital processes. For some, it's can be a tough process to take domain expertise and transfer it into digital processes. We help explain how to make this less challenging.
Workflow automation is being used by many IT organizations to perform back end IT operations and to automate the processes that these IT operations perform. Most IT processes are procedural, for example, creating user account for a new employee and giving access to systems. In an offboarding process, deactivating a user and removing access to systems. We discuss in detail how workflow automation will lead to cost savings.