How process automation works: a Linx perspective

A key part of digital transformation is process automation. Greater efficiencies in resources, time and cost can be achieved when business processes are automated.

Do you want to automate your business processes with Linx, but you don’t know how it all works? 

How to build an automated process with Linx

Let’s connect the dots by starting with your desired end-result and working our way back from there. For now, let’s keep it simple and settle for an automated process flow as your desired end-result. 

You may ask:

To have an automated process flow, what do I need?
You need a running Service event that will execute your process flow at specific times or under specific conditions.

What is a service event?
The services available in Linx include Timer, Cron, DirectoryWatch, MSMQService, RabbitMQService, RESTHost, SimpleRESTHost and SOAPWebService. Each service can be configured to trigger an associated service event when specific conditions are met.

Let’s take the Timer service as an example: you can configure it to trigger the TimerEvent at for example 7 am every weekday. When the clock strikes 7 am, the TimerEvent will trigger, and execute your process flow, which could, for example, involve the retrieval of the previous day’s sales records from a database, writing them to a CSV file and emailing it to the regional sales managers. In this context, your process flow is essentially an ‘event handler’.

Host your solution on Linx Server

Ok great, but before we look at the details of the process flow as the event handler, first tell me this:  what must I do to have a running Service event that will execute my process flow when I want it to?
You must start your Service event, but for that to be possible you need a Solution that has been deployed to Linx Server that contains a Service, which in turn contains your Service event. In other words, you need a Service and service event, inside a Solution that is running on Linx Server.

Once the Solution that contains your Service and service event has been deployed to Linx Server, you can start your Service event on Linx Server.

What must I do to have a deployed Solution on Linx Server that contains a Service event that will execute my process flow?
Short answer: you must design a Solution, which is an application that contains all of your programming logic, including the relevant Service with its configured properties, and the process flow that will ‘handle’ the service event when it is triggered.

Ok, but where do I design this Solution?
You design solutions in Linx Designer. From there you can deploy your solution to Linx Server. The Linx application consists of Linx Server and Linx Designer.

Create your solution in Linx Designer

Ok, so I use Linx Designer to design my Solution that I will then deploy to Linx Server… but what goes into designing a Solution?
Well, remember your desired end result? You want an automated process flow. The automated process flow requires a Service event to be triggered and it needs an event handler (all the functions that drive your process flow) to execute when the Service event is triggered. That is essentially what you have to include in your Solution design.

Let’s take it one step at a time … the Service event: how do I add this

Continue reading

This post was originally published on this site