Differences

This shows you the differences between two versions of the page.

--- leon:email-templates [2018/10/29 14:35]
rafal [Legend]
+++ leon:email-templates [2023/07/13 13:05] (current)
rafal [Rules]
@@ Line 5: / Line 5: @@
 ===== MVT MESSAGES =====
-<box tutorial>[[videos:account-configuration:mvt-messages|Video Tutorial]]</box>
+<box tutorial>[[videos:getting-started:mvt-messages|Video Tutorial]]</box>
 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 ====
 [{{ :leon:settings:emails settings.jpg?200|Defining MVT emails: 'Label' & "Reply to email'}}]
@@ Line 29: / Line 31: @@
 ----
-===== Templates =====
+==== Templates ====
-[{{ :leon:settings:new templates.png?150|Aircraft Movement Templates}}]
+[{{ :leon:settings:templates 2.png?150|Aircraft Movement Templates}}]
 There are 8 available default templates which can be modified. It is also possible to define your own templates.
@@ Line 51: / Line 53: @@
 Aircraft has 23 passengers on board."
+-------------
 ==== Conditional Tags ====
 [{{ :leon:settings:Conditional tags.png?200|Example of Content error when creating conditional MVT Message}}]
@@ Line 67: / Line 70: @@
 ----
-===== Rules =====
+==== Rules ====
-[{{ :leon:settings:rules defining.jpg?200|Defining MVT rules for the aircraft}}]
+[{{ :leon:settings:mvt:mvt-handling-split.png?200|Defining a rule in MVT Messages panel}}]
 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 'Scenario' dropdown.
 You can also insert a recipient's email address as well as CC & BCC email addresses - this should be done for both: take off & landing MVT emails.
+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 {{:leon:icons:settings mvt.jpg|}} icon.
 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)
-  * **Handler** - allows to include Handling Agent assigned to the applicable flight in relevant MVT email
+  * **Send to departure/destination handler** - allows to include Handling Agent at either ADEP, ADES, or both, 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).
+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 nex to the rule. Even if an aircraft have Rules assigned, switching it off will prevent MVT messages being sent for the selected tails.
+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.
 {{:leon:settings:Aircraft rules.png?}}
@@ Line 90: / Line 98: @@
 ----
-==== ETA UPDATE MVT to client ====
+==== ETA UPDATE for next Client ====
-One of the possibilities, when creating different MVT rules for aircraft, is **ETA UPDATE MVT** email, which can be sent to a client assigned on the next trip informing him about estimated time of arrival of the aircraft (whether it is a ferry leg or a trip for a different client).
+One of the possibilities, when creating different MVT rules for aircraft, is sending **ETA UPDATE for next Client** MVT email, which can be sent to the next client assigned on the next trip informing him about estimated time of arrival of the aircraft (whether it is a ferry leg or a trip for a different client).
-**EXAMPLE**
+**EXAMPLE 1** - the same Client on 2nd & 3rd leg of the trip.
-trips are added on the same aircraft:
+WAW GVA 1100   **Ferry**
-{{:leon:schedule:Eta update mvt.jpg|}}
+GVA AMS 1330   **Client A**
-If a Flight Watch on the **first flight** is filled in with T/O time (indication 'A' displayed), Leon will send a MVT Take Off email to the recipient of the Take Off rule, as well as the ETA UPDATE MVT email to the 2nd leg client. Example of the ETA UPDATE rule & email below:
+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
+WAW STN 1200   **Ferry**
-   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).
+STN CIA 1530   **Client A**
+CIA WAW 1900   **Client B**
+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 115: / 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).
+<box>**The 'next Client' scenario movement emails are not possible on the Subcharter Flights**</box>
+----
+==== Legend ====
 The legend contains **Tags** and right next to them their description plus **Test Data** column showing examples (see below).
@@ Line 127: / Line 147: @@
 ---------------
+===== Documents Email Templates =====
+In this panel you can set up email templates for: **Quotes documents**, **Fuel Requests**, **Schedule Changes Summary**, **Crew Panel roster change**, **Crew Duties roster change**, **Fuel Requests**, **Permits** or **Schedule sending**.
+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 'From' & 'Reply to' email addresses as well as 'CC' & 'BCC' emails.
+----
+Below you can find examples of how this section can be filled in.
+=== Charter Agreement ===
+**SUBJECT**
+{{:leon:settings:subject example.png|}}
+__Preview__:
+Charter Agreement LFPG - OMDB 26 Apr 2019 Rev.1
+**BODY**
+{{:leon:settings:body example.png|}}
+__Preview__:
+Dear James Smith
+Please find attached your Charater Agreement from AirHeaven Airlines.
+Kind Regards
+Ann Davies
+----
+==== Fuel Order ====
+**SUBJECT**
+{{:leon:settings:fuel order example.png|}}
+__Preview:__
+UUWW FUEL REQUEST
+**BODY**
+{{:leon:settings:fuel order body.png|}}
+**'User sending email'** located in the 'RECIPIENTS' tab next to 'Reply to' box allows setting up an email of the logged in User that is sending the message, as a 'reply to' email.
+==== Landing Permit ====
+[{{ :leon:settings:landing permit.png?200|Landing permit email template example}}]
+An example of the full **Landing Permit** appears on the screenshot, on the right.

Leonsoftware Wiki

User Tools

Site Tools

Differences

Page Tools