This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:email-templates [2020/04/07 07:29] bartek [Documents Email Templates] |
leon:email-templates [2023/07/13 13:05] (current) rafal [Rules] |
||
---|---|---|---|
Line 72: | Line 72: | ||
==== 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' | ||
Line 83: | Line 85: | ||
* **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 128: | Line 131: | ||
+ | < | ||
---- | ---- | ||
Line 147: | Line 150: | ||
- | + | In this panel you can set up email templates for: **Quotes documents**, | |
- | In this panel you can set up email templates for particular **OPS 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. | 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. | ||
Line 187: | Line 189: | ||
==== Fuel Order ==== | ==== Fuel Order ==== | ||
+ | |||
+ | |||
+ | |||
**SUBJECT** | **SUBJECT** | ||
Line 200: | Line 205: | ||
{{: | {{: | ||
+ | **' | ||
+ | ==== Landing Permit ==== | ||
+ | [{{ : | ||
+ | An example of the full **Landing Permit** appears on the screenshot, on the right. |