This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
leon:flight-notifications [2016/03/02 12:21] bartek created |
leon:flight-notifications [2022/09/22 19:15] rafal [Grouping] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Notifications ====== | ====== Notifications ====== | ||
+ | <box tutorial> | ||
The main task of the ' | The main task of the ' | ||
Line 9: | Line 10: | ||
For example: you changed STD at 12:00 UTC, then STA at 12:08, ADEP at 12:15, ADES at 12:22 (ADES change was the last one - the notification email about these changes would be sent out at approximately 12:32 (10 minutes after the last change). | For example: you changed STD at 12:00 UTC, then STA at 12:08, ADEP at 12:15, ADES at 12:22 (ADES change was the last one - the notification email about these changes would be sent out at approximately 12:32 (10 minutes after the last change). | ||
+ | |||
+ | You can also enable the **Trigger** which delays sending out email notifications by the number of minutes inserted into fields: | ||
+ | |||
+ | * **Schedule** - applies to schedule changes (ADEP, ADES, STD, STA, PAX, Flight status). For example if you want to set this time for one day (24h), please enter 1440 minutes. All flight details will be sent together with the schedule | ||
+ | * **Details** - notifications about further changes in flight details (all except flight schedule). The typical value here is something short - e.g. 45 minutes. | ||
+ | * **Reminders** - define time intervals (in minutes) when Leon should send email reminders regarding scheduled flights. | ||
+ | |||
===== Notification Properties ===== | ===== Notification Properties ===== | ||
- | [{{ : | ||
As you can see in the screenshot there is a number of sections that influence the type of notification and the time when it was sent but also the content of such notification. Main areas of influence are explained below. | As you can see in the screenshot there is a number of sections that influence the type of notification and the time when it was sent but also the content of such notification. Main areas of influence are explained below. | ||
Line 19: | Line 26: | ||
You can set a notification so that flights added to Leon are grouped. If a flight from the selected group is changed, the notification will include the schedule of all flights from this particular group (including unchanged flights). If more than one flight is changed, one notification will be sent containing information about the changed flights along with other flights from the same group. | You can set a notification so that flights added to Leon are grouped. If a flight from the selected group is changed, the notification will include the schedule of all flights from this particular group (including unchanged flights). If more than one flight is changed, one notification will be sent containing information about the changed flights along with other flights from the same group. | ||
+ | |||
+ | [{{ : | ||
There are **4** options in grouping: | There are **4** options in grouping: | ||
Line 38: | Line 47: | ||
| | ||
Both are separated trips for different clients. If changes are made to the 1st trip, in the notification email there will be also details of the 2nd trip (as it's on the same aircraft, on the same day). | Both are separated trips for different clients. If changes are made to the 1st trip, in the notification email there will be also details of the 2nd trip (as it's on the same aircraft, on the same day). | ||
+ | |||
+ | **Show Country Notes** will include country notes inserted in the ' | ||
+ | |||
+ | **Only for airports** will send notifications only if the flight is scheduled to and from the airports inserted in this field. The airports need to be separated by commas. To receive notifications for all airports, leave this field blank. | ||
+ | |||
+ | **Trip type** will send only for the type selected in the dropdown. | ||
==== Format ==== | ==== Format ==== | ||
- | * 1. **Simplified | + | * 1. **Default simple |
{{: | {{: | ||
- | * 2. **Full HTML** - deleted legs appear as < | + | * 2. **Default full HTML** - deleted legs appear as < |
{{: | {{: | ||
Line 71: | Line 86: | ||
{{: | {{: | ||
- | ==== Flight/Trip ==== | + | ==== Roster/ |
- | You can define what details of either the flight or the trip you want included in the notification | + | [{{ : |
- | tab **Flight**: Ops, Handling, Crew, Pax | + | You can define what details of the roster, the trip or the flight you want to be included in the notification email. You can add various checkboxes in sections such as: |
- | tab **Trip**: Flight, Contract, Notes (notes added in ' | + | tab **Roster**: Notify about schedule changes, Crew squad changes: cockpit, cabin, other (positions FM-Flight Mechanic, LC-Line Checker, PSN, PAD). |
- | ==== Positionings | + | tab **Notes**: mark which notes (Ops, Trip or Sales) inserted in Leon should be included in the notification. |
+ | |||
+ | tab **Trip**: Contract (Invoice), Notes. | ||
+ | |||
+ | tab **Flight**: The checklist items changes: Ops, Handling, Crew, Cargo, Pax, Customs, Notes. | ||
+ | |||
+ | |||
+ | < | ||
+ | ==== Positioning | ||
Leon will send a notification email if a positioning duty is added to Leon and the checkbox **Positioning** is ticked in ' | Leon will send a notification email if a positioning duty is added to Leon and the checkbox **Positioning** is ticked in ' | ||
Line 91: | Line 114: | ||
**Schedule** | **Schedule** | ||
- | Specify how many **minutes before scheduled departure time** you want to receive | + | Specify how many **minutes before scheduled departure time** you want to receive notifications about further schedule changes (**ADEP**, **ADES**, **STD**, **STA**, **PAX**, **Flight status** - see screenshot below). |
For example, if you want to set trigger time for one day (24h), please enter 1440 minutes. | For example, if you want to set trigger time for one day (24h), please enter 1440 minutes. | ||
Line 100: | Line 123: | ||
**Details** | **Details** | ||
- | Specify how many minutes before scheduled departure time you want to receive | + | Specify how many minutes before scheduled departure time you want to receive notifications about further changes in **flight details** (__all except flight schedule__). The typical value here is something short - e.g. 45 minutes (see example below). |
{{: | {{: | ||
Line 110: | Line 133: | ||
==== Include/ | ==== Include/ | ||
- | In the new version you can **include** and/or **exclude** recipients of the partucilar | + | You can **include** and/or **exclude** recipients of the particular |
Click on the < | Click on the < | ||
Line 116: | Line 139: | ||
</ | </ | ||
<span style=" | <span style=" | ||
- | </ | + | </ |
- | Once it's saved, you can see in the field ' | + | Once it's saved, you can see in the field ' |
- | Click {{: | + | Click {{: |
===== Managing notifications ===== | ===== Managing notifications ===== | ||
Every time you create a new notification, | Every time you create a new notification, | ||
+ | |||
+ | You can decide if you want the notification to show times in UTC, in LT or in both UTC & LT by using **Display times in** drop-down box. | ||
You can also select a ' | You can also select a ' | ||
- | Each notification can be deactivated (simply click {{: | + | Each notification can be deactivated (simply click {{: |
Below you can find various **examples** of notifications, | Below you can find various **examples** of notifications, | ||
Line 153: | Line 178: | ||
{{: | {{: | ||
- | * **Office duty** - either the flight status in 'Edit Flight' | + | * **Office duty** - duty added in 'Crew Duties' |
{{: | {{: |