<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

API performance improvements using server and user sessions

API's are the primary way to access most applications. And as applications become increasingly feature-and-function-rich, their API can become more complex and impact performance.  Workflow applications evolved in this exact way:  when they were rudimentary then their APIs were small and there were few issues - but as features and functionality were added, API performance degraded noticeably. 

Instantiating  Forms From Within A Process

There are many use cases where a process needs to instantiate and route forms to users for data collection or approvals.   Once the data is collected, that data from forms can be used for computations.

FlowWright HTML5 Designers

FlowWright makes extensive use of the latest UI technologies such as HTML5.  Many FlowWright key features are implemented using HTML5, including our:

Open source workflow vs. FlowWright?

There are many open source workflow products available.  However, for most companies, security is a serious concern.  Open source solution code is available to anyone to view, making it relatively easy to hack the software.  While some organizations still build solutions using open source platforms, the risk is often deemed too high for most organizations that prioritize security.

Time to move off of Microsoft Windows Workflow?

As you may already know, Microsoft no longer supports their Window workflow product - Windows Workflow Foundation.  Many organizations implemented this product from Microsoft for 2 main reasons: it is under the strong Microsoft brand and it was nominally free. 

Executing workflows in real-time using the FlowWright engine

The FlowWright low level API and engine API was built so that workflows can be executed in real-time with high performance.  Although this API has existed in previous versions, FlowWright v9.6 introduced Microservices, making it possible to call a workflow definition via FlowWright's REST API.  Under the hood of the Microservice, the low level API is used to execute workflows in real-time, or in memory. 

Using Microservices as webhooks

Webhooks are very common today.  What are webhooks?  They are a way to get notified when something happens.  For example, if you like to get notified when a virtual machine shuts down in Microsoft Azure, just configure a webhook URL in Azure.  When the virtual machine shuts down at any point in time, it calls the configured webhook URL.  This method is much better than polling to see if the virtual machine has shut down.

Why managing Microservices can be difficult

"Microservices" was once just another buzzword, but now organizations have begun to understand their value and how they can significantly and positively impact business processes. The idea of Microservices arose from the difficulty of managing large systems so as to avoid duplicate functionality in different areas and from the efficiency that their re-useable nature would theoretically deliver.

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.