This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
leon:aircraft-movements-emails [2021/04/07 06:08] bartek removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== MVT Messages ====== | ||
- | <box tutorial> | ||
- | |||
- | This module allows to set up **Movement Emails** for each aircraft. You can define **templates** as well as add new templates. When Flight Watch data arrives to Leon a movement email will be sent out to the recipient. | ||
- | |||
- | ===== Settings ===== | ||
- | |||
- | [{{ : | ||
- | [{{ : | ||
- | |||
- | By clicking the icon {{: | ||
- | |||
- | * **From label** - a label/name which will appear when the MVT email will arrive. | ||
- | * **Reply to email** - an email address to which a MVT email recipient should reply. | ||
- | |||
- | |||
- | |||
- | Once the MVT email has been sent (whether it's automatically or manually), Leon will use the above settings and will show the label. | ||
- | |||
- | {{: | ||
- | |||
- | |||
- | |||
- | ---- | ||
- | |||
- | ===== Templates ===== | ||
- | |||
- | [{{ : | ||
- | |||
- | There are 8 available default templates which can be modified. It is also possible to define your own templates. | ||
- | |||
- | A screenshot below shows an example of the **Take Off** template' | ||
- | |||
- | * **Template' | ||
- | * **Subject** - i.e. " | ||
- | * **Template** - the text should contain tags available in Legend. | ||
- | |||
- | {{: | ||
- | |||
- | Once the **Flight Watch** data is filled in an email for the above template would be as on the example below: | ||
- | |||
- | "Dear Sirs, | ||
- | |||
- | We wish to inform you that the aircraft B-ARTI on flight no BAR21 from WARSAW FREDERIC CHOPIN WAW to GENEVA INTERNATIONAL (GVA) has taken off at 07: | ||
- | Aircraft is scheduled to arrive to GENEVA INTERNATIONAL GVA at 09:45. | ||
- | Aircraft has 23 passengers on board." | ||
- | |||
- | ==== Conditional Tags ==== | ||
- | [{{ : | ||
- | |||
- | It is possible to include or exclude empty fields from the MVT Message. In order to do it you need to use **Conditional tags**. | ||
- | |||
- | To create such condition you need to use '#' | ||
- | |||
- | **{//// | ||
- | |||
- | where **{//// | ||
- | |||
- | In the above case, if the Flight Watch does not include PAX number, or PAX number is 0, this information will not be included in MVT Message. If it is 1 and more, The above sentence will be included in the message. | ||
- | |||
- | It is also important to close one condition before opening another. **Errors in the template will be highlighted orange** in the template and ' | ||
- | ---- | ||
- | |||
- | ===== Rules ===== | ||
- | |||
- | [{{ : | ||
- | |||
- | By clicking on a particular aircraft in a section **Fleet Rules** Leon opens a new screen where you can select **Scenario** (Take off, Landing, Aircraft ready, ETA update) and **Template** (select between those defined on the right-hand side). | ||
- | |||
- | You can also insert a recipient' | ||
- | |||
- | Each Rule has 3 checkboxes: | ||
- | |||
- | * **Non-ferry flight only** - allows to include FERRY flights in MVT Messages (if checkbox is not ticked) | ||
- | * **Client representative** - allows to include Client assigned to the trip in relevant MVT email (if there is a representative assigned to a company, the message will be sent to that representative only, if there is no representative assigned, the email will be sent to the email provided for the Client) | ||
- | * **Handler** - allows to include Handling Agent assigned to the applicable flight in relevant MVT email | ||
- | |||
- | A button **ADD RULE** allows to add custom rules (i.e. a separate rule for a client). | ||
- | |||
- | It is possible to assign a single rule to multiple aircraft by selecting them in the rule settings in section **Aircraft**. | ||
- | In order to turn off the rule, use ON/OFF button nex to the rule. Even if an aircraft have Rules assigned, switching it off will prevent MVT messages being sent for the selected tails. | ||
- | |||
- | {{: | ||
- | |||
- | ---- | ||
- | |||
- | ==== ETA UPDATE MVT to client ==== | ||
- | |||
- | One of the possibilities, | ||
- | |||
- | **EXAMPLE** | ||
- | |||
- | 2 trips are added on the same aircraft: | ||
- | |||
- | {{: | ||
- | |||
- | If a Flight Watch on the **first flight** is filled in with T/O time (indication ' | ||
- | |||
- | |||
- | |||
- | Dear Sirs | ||
- | We wish to inform you that the aircraft B-ARTI on flight to Geneva International (GVA) has taken off at 1248 (1448 Local time). | ||
- | The aircraft is scheduled to arrive at 1501 (1701 Local time). | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ---- | ||
- | |||
- | ===== Legend ===== | ||
- | |||
- | The legend contains **Tags** and right next to them their description plus **Test Data** column showing examples (see below). | ||
- | |||
- | | ||
- | {{ADEP_ICAO}} Airport of departure (ICAO) | ||
- | |||
- | |||
- | < | ||
- | |||
- | |||
- | |||