Automate almost any backend process

Low-code business solutions in minutes

How do Services work?

In Linx users create Solutions that consist of Services and Processes.  

    1. Services are used to automate Processes
    2. Processes contain sequences of functions (like ExecuteSQL, ReadTextFile, CallRestWebService, IfElse, and many more).

Services contain Events (for example, a DirectoryWatch service has a FileCreated and a FileModified event). A Service Event will trigger off processes when they fire (i.e. when a file is created or modified).

Note: Inside of processes, functions are executed sequentially. The output of one function can be used by subsequent functions in the same process.

A Service can contain functions in itself, or link to any other existing Linx process. Depending on the type of service used, you can forward parameters into the processes, for instance a Web Service Service can receive external values, which can then be forwarded to other Linx processes.

Which service do I use?

Timer Service

Allows the execution of a process at a specified time or interval.
PROPERTIES

Web Services

Assemble and publish REST or SOAP web service endpoints. Each webmethod is exposed as an Event on the service.
PROPERTIES

Message Queues

Listen to message queues and trigger processes whenever a message is received.
PROPERTIES

Directory Watch

Watch a directory for file changes, creations, renaming and deletions and call processes when the event occurs.
PROPERTIES

Examples of using Services

Create a Timer Service with an interval of 5 minutes. This service can then run an Email checking process, every 5 minutes, and forward any new emails received.

Use a Directory Watch Service aimed at a specific location, i.e. C:\WIP\Inbox, whenever a file is copied into this location, the service will trigger and a Linx process can take the file and move it to a different location.

Using the RESTWebServices Service, you can set up a set of operations, under any path on your machine (i.e. http://MyMachine/WebService) which then can be called from any application, to trigger specific Linx processes.

How to use Services?

Service events for the most part looks like normal processes in your Linx Project. The difference is that they are triggered by something external to Linx. For instance, the operating system would trigger a Timer event, or a Web call can trigger a WebService event.

EXAMPLE
Below is a very basic example of a Timer Service. The same concepts of navigation, layout and execution will apply for the Directory Watch Service. A Timer Service allows the execution of a process at a specified time or interval. The user can specify a list of days on which the timer should run.  For other Services such as Web Services and Message Queues, please refer to our video library for detailed instructions.

1. To add a Timer service, select the appropriate (Timer) service from the Service button located in the top toolbar. Once selected, Linx will

 

a) Create the new service in the Solution Explorer panel

solution explorer

How we see Services in the Solution Panel

Timer1: This is the service. The appropriate settings for the trigger (event) can be added in the Properties panel (bottom left)

Timer Event: This is where the actual process you wish to put on the timer is stored  I.e. When the Timer Service is triggered, the process inside the Timer Event will fire.

and b) Open a new tab in the middle canvas called “TimerEvent”

Designer Window

Using the TimerEvent Tab

Once the TimerEvent tab is open, you must drag the process you wish to execute on a timer into the TimerEvent canvas.

Next Steps: Automate your solution

Linx provides a powerful automated work-engine to automate most frontend or backend processes. Deploy your solution to the Linx Server to fire events based on a schedule, trigger or exposed as a web service.

Scroll to top