<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

Training best practices to automate your business processes

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 - Upgrades to the data access layer (DAL) in Workflow

FlowWright's data access layer is the lowest architectural layer in the platform.  This is where all calls to the database are handled.  Whether users are requesting data from the database or updating data within the database, all calls are sent through this data access layer.

FlowWright v9.6 new release overview

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.  

Process Migration Made Easy With FlowWright

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:

Data Acquisition Through Events using Enterprise Service Bus

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 processes

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.

Collecting lots of paper? You are not alone.

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! 

Objects and relations made easy with workflow processes

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. 

3 simple workflow task routing concepts

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! 

If you are still waiting for data, then FlowWright can help you...

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.