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

Dileepa WIjayanayake

Dileepa WIjayanayake
Find me on:

Recent Posts

From No Communication to Complete Collaboration

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. 

Why component architecture fails in Micro-services

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. 

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

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

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:

Automated processes don't take holidays

Most of us love to enjoy the holidays; in the hurried world of instant connectivity we live in-it is important to not burn out and take time off to regroup and perform better upon your return. But as many folks know, sometimes it's difficult to get everything  completed prior to leaving. There has to be a better way! We explain how workflow automation for certain processes can ensure you actually get to take that vacation time you earned. 

Inside the box vs. outside

Recently we acquired a customer in Europe against a very large BPM/Workflow provider, the reason our platform was a better value was impacted by the fact that we operate alongside your systems but can automate and orchestrate workflow across multiple ones you have in place already. Why does this matter? It's less impactful on your overall architecture.