<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Processing EDI files using FlowWright automation

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.

Are self optimizing workflows possible?

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).

Form Computations Using Workflow Processes Automation

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.

.Net Workflow Software Engines

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. 

Document your processes, so you won't get lost later....

Documenting your business processes is just as important as actually applying automation to your processes.  There are several reasons why you should always document what your team is doing when creating and editing processes; we summarize some things to consider below.

Types of sub-workflows

Sub-workflows or sub-processes are key part of any workflow process.  Instead of ending with very large processes, you should always break them down to smaller chunks and make sub-processes to ensure things remain clean. We explain why this is an important step. 

Custom step validation in FlowWright

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.

Does your business analyst understand process automation?

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.

Why all workflow products are not created equal ==

If you are looking for workflow automation solutions, you know there are many workflow/business process management software platforms out in the market. The workflow/bpm market is divided into two (2) main areas we discuss below:

Cost savings in your cloud environment when using workflow automation

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.