This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
leon:email-templates [2018/10/29 09:53] bartek created |
leon:email-templates [2023/07/13 13:05] rafal [Rules] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== EMAIL TEMPLATES ====== | ====== EMAIL TEMPLATES ====== | ||
+ | |||
+ | ---- | ||
===== MVT MESSAGES ===== | ===== MVT MESSAGES ===== | ||
- | ====== MVT Messages ====== | + | <box tutorial> |
- | <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. | 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 | + | ==== Settings ==== |
[{{ : | [{{ : | ||
Line 28: | Line 31: | ||
---- | ---- | ||
- | ===== Templates | + | ==== Templates ==== |
- | [{{ : | + | [{{ : |
There are 8 available default templates which can be modified. It is also possible to define your own templates. | There are 8 available default templates which can be modified. It is also possible to define your own templates. | ||
Line 50: | Line 53: | ||
Aircraft has 23 passengers on board." | Aircraft has 23 passengers on board." | ||
+ | ------------- | ||
==== Conditional Tags ==== | ==== Conditional Tags ==== | ||
[{{ : | [{{ : | ||
Line 66: | Line 70: | ||
---- | ---- | ||
- | ===== Rules ===== | + | ==== 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). | 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' | 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: | Each Rule has 3 checkboxes: | ||
* **Non-ferry flight only** - allows to include FERRY flights in MVT Messages (if checkbox is not ticked) | * **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) | * **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 | + | * **Send to departure/ |
- | A button **ADD RULE** allows to add custom rules (i.e. a separate rule for a client). | + | 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**. | 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 | + | In order to turn off the rule, use ON/OFF button |
{{: | {{: | ||
Line 89: | Line 98: | ||
---- | ---- | ||
- | ==== ETA UPDATE | + | ==== ETA UPDATE |
- | One of the possibilities, | + | One of the possibilities, |
- | **EXAMPLE** | + | **EXAMPLE |
- | 2 trips are added on the same aircraft: | + | 0900 WAW GVA 1100 |
- | {{: | + | 1200 GVA AMS 1330 |
- | If a Flight Watch on the **first flight** is filled in with T/O time (indication ' | + | 1500 AMS WAW 1700 **Client A** |
+ | 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. | ||
- | Dear Sirs | + | 1000 WAW STN 1200 |
- | | + | |
- | The aircraft is scheduled to arrive at 1501 (1701 Local time). | + | |
+ | 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. | ||
Line 114: | Line 128: | ||
---- | ---- | ||
- | ===== Legend | + | 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). | The legend contains **Tags** and right next to them their description plus **Test Data** column showing examples (see below). | ||
Line 124: | Line 145: | ||
< | < | ||
+ | --------------- | ||
+ | |||
+ | ===== 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. |