This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Previous revision | ||
leon:email-templates [2019/08/21 07:53] |
leon:email-templates [2023/07/13 13:05] rafal [Rules] |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== EMAIL TEMPLATES ====== | ||
+ | ---- | ||
+ | |||
+ | ===== 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). | ||
+ | |||
+ | It is also possible to set the MVT Messages to be **sent manually only** by selecting the 'Send manually only' option in the ' | ||
+ | |||
+ | You can also insert a recipient' | ||
+ | |||
+ | It is possible to define 'From label' & 'Reply to' per a tail. If it's not set up Leon will use these 2 details defined under {{: | ||
+ | |||
+ | Each Rule has 3 checkboxes: | ||
+ | |||
+ | * **Non-ferry flight only** - allows to include FERRY flights in MVT Messages (if checkbox is not ticked) | ||
+ | * **Send for trip type** - select a trip type for which MVT emails should be sent out | ||
+ | * **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) | ||
+ | * **Send to departure/ | ||
+ | |||
+ | A button **ADD RULE** allows to add of 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 next to the rule. Even if an aircraft have Rules assigned, switching it off will prevent MVT messages from being sent for the selected tails. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== ETA UPDATE for next Client ==== | ||
+ | |||
+ | One of the possibilities, | ||
+ | |||
+ | **EXAMPLE 1** - the same Client on 2nd & 3rd leg of the trip. | ||
+ | |||
+ | 0900 WAW GVA 1100 | ||
+ | |||
+ | 1200 GVA AMS 1330 | ||
+ | |||
+ | 1500 AMS WAW 1700 | ||
+ | |||
+ | In this case, when ETA is changed on the 1st leg, Leon will send MVT ETA Update email to Client A on the 2nd leg. But even if ETA changes on the 2nd leg Leon will not send another MVT email as it's the same Client. | ||
+ | |||
+ | **EXAMPLE 2** - different Clients on 2nd & 3rd leg of the trip. | ||
+ | |||
+ | 1000 WAW STN 1200 | ||
+ | |||
+ | 1300 STN CIA 1530 | ||
+ | |||
+ | 1700 CIA WAW 1900 | ||
+ | |||
+ | In this case, when ETA is changed on the 1st leg, Leon will send MVT ETA Update email to Client A on the 2nd leg. If ETA also changes on the 2nd leg, Leon will send a MVT ETA Update email to the Client B on the 3rd leg. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | Similarly you can define a new rule for your fleet using a scenario **Aircraft ready for next Client** - Leon will automatically send a MVT email to the client assigned to the next leg (as long as it is a different Client). | ||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== 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) | ||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | --------------- | ||
+ | |||
+ | ===== Documents Email Templates ===== | ||
+ | |||
+ | |||
+ | In this panel you can set up email templates for: **Quotes documents**, | ||
+ | |||
+ | You can define **multiple email templates** for the same document or roster changes (for example depending on crew base or language), then select an appropriate template in OPS panel. | ||
+ | |||
+ | Click on any template and fill in **3** windows with appropriate HTML data. On the right-hand side Leon shows preview of the email body. | ||
+ | |||
+ | In a tab **RECIPIENTS** you can add default ' | ||
+ | |||
+ | ---- | ||
+ | |||
+ | Below you can find examples of how this section can be filled in. | ||
+ | |||
+ | === Charter Agreement === | ||
+ | |||
+ | **SUBJECT** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __Preview__: | ||
+ | |||
+ | Charter Agreement LFPG - OMDB 26 Apr 2019 Rev.1 | ||
+ | |||
+ | **BODY** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __Preview__: | ||
+ | |||
+ | Dear James Smith | ||
+ | |||
+ | Please find attached your Charater Agreement from AirHeaven Airlines. | ||
+ | |||
+ | Kind Regards | ||
+ | |||
+ | Ann Davies | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Fuel Order ==== | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | **SUBJECT** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __Preview: | ||
+ | |||
+ | UUWW FUEL REQUEST | ||
+ | |||
+ | **BODY** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **' | ||
+ | |||
+ | ==== Landing Permit ==== | ||
+ | [{{ : | ||
+ | An example of the full **Landing Permit** appears on the screenshot, on the right. |