This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
leon:notifications [2015/07/24 09:30] rafal [Notification Properties] |
leon:notifications [2015/08/13 12:30] ksenia |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | The main task of the ' | + | The main task of the ' |
It is possible to define any number of notifications and from the point of user's view - each one of them will work **independently**. | It is possible to define any number of notifications and from the point of user's view - each one of them will work **independently**. | ||
- | In order to decrease the number of outgoing | + | In order to decrease the number of emails |
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). | ||
Line 14: | Line 14: | ||
[{{ : | [{{ : | ||
- | As you can see in the screenshot | + | As you can see in the screenshot |
==== Grouping ==== | ==== Grouping ==== | ||
- | You can set a notification so that added flights to Leon are grouped. | + | You can set a notification so that flights |
There are **4** options in grouping: | There are **4** options in grouping: | ||
* 1. **None** - flights are not grouped, which means that each flight is being sent individually. | * 1. **None** - flights are not grouped, which means that each flight is being sent individually. | ||
- | * 2. **Crew** - if the recipient of the notification is a crew member of the changed flight, | + | * 2. **Crew** - if the recipient of the notification is a crew member of the changed flight, |
- | __Example__: | + | __Example__: |
* 3. **Trip** - the entire trip of the modified flight is sent (even if particular legs are on different days). | * 3. **Trip** - the entire trip of the modified flight is sent (even if particular legs are on different days). | ||
Line 37: | Line 37: | ||
* 5. **Day** - all flights for the same day for ALL aircraft, including the modified flight, are grouped into one notification message. | * 5. **Day** - all flights for the same day for ALL aircraft, including the modified flight, are grouped into one notification message. | ||
| | ||
- | 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). |
==== Format ==== | ==== Format ==== | ||
Line 73: | Line 73: | ||
==== Flight/Trip ==== | ==== Flight/Trip ==== | ||
- | You can define what details of either the flight or the trip you want to be included in the notification email. You can add various checkboxes (which represent Leon 3.0 checklist) in sections such as: | + | You can define what details of either the flight or the trip you want included in the notification email. You can add various checkboxes (which represent Leon 3.0 checklist) in sections such as: |
tab **Flight**: Ops, Handling, Crew, Pax | tab **Flight**: Ops, Handling, Crew, Pax |