flow of the data

Let's imagine you would like to be informed whenever the aircraft has landed. You'd like to tag the message and create the parameter that contains value of the airport (if that exists).

From RAW aircraft data to wilco layout

Aircraft sends the raw data (OOOI) that could be parsed as explained in the chapter create layout. In this example we are interested in the ON report:

We are interested in the value of the airport. To get that, we first need to parse information from the raw data - FROM/TO (here: LTFM, LFBO). In wilco, that specific information is coded by using FW.setTo and FW.setFrom:

Now, all the future layouts will automatically decode the information FROM/TO of that aircraft. Having that information, we can proceed with creation of the IFT.

From data reception to wilco action

From here, we can now create the IFT that would do what you want, as explained at IFT at Layout chapter.

Send email on reception of the report

Since you would like to be informed whenever the aircraft has landed, the IFT shall be created at reception of the report. We will use here the code FW.email, and it could look as below:

If you test the alert, you'll have a quick look up at the result:

After try with email you could see what it would look like at your email inbox:

Tag message

In order to tag the message, we will use the code FW.tag:

All the future messages will be taged on timeline. If you'd like to see the message that you're working on to be tagged, you'll need to reparse it (see the edit layout section).

Create parameter

To create the parameter that contains value of the airport (if that exists), we would use the FW.set code.

Results of IFTs

Parsed message would now look different on the timeline. We should see the tag (LANDED) and the icon that the email was sent:

While the message itself will contain the parameter (airport) created: