User Tools

Site Tools


leon:notifications

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
leon:notifications [2015/07/30 09:31]
rafal [Introduction]
leon:notifications [2016/08/30 13:06] (current)
Line 2: Line 2:
  
  
-The main task of the '​**Notifications**'​ panel is to inform via emails about any __changes__ done in flights added to Leon as well as about __creating__ and __deleting__ flights. It is **Leon users** (OPS, Admins) who decide what sort of notifications are being sent out and to whomby __defining settings__. ​+The main task of the '​**Notifications**'​ panel is to inform via emails about any __changes__ done in flights added to Leon as well as about __creating__ and __deleting__ flights. It is **Leon users** (OPS, Admins) who decide what sort of notifications are being sent out and to whom by __defining settings__. ​
  
 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 ​emails from Leon (which is beneficial for recipients),​ notifications are **not being sent out immediately** after the first change in the flight but after **10 minutes** from the last change. So if there was another change done to the same flight within 10 minutes - time is calculated from the beginning. ​+In order to decrease the number of emails ​outgoing ​from Leon (which is beneficial for recipients),​ notifications are **not being sent out immediately** after the first change in the flight but after **10 minutes** from the last change. So if there was another change done to the same flight within 10 minutes - time is calculated from the beginning. ​
  
 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:
 [{{ :​leon:​admin-notifications:​Notification properties.png?​350|Section '​Notifications'​ - main screen}}] [{{ :​leon:​admin-notifications:​Notification properties.png?​350|Section '​Notifications'​ - main screen}}]
  
-As you can see in the screenshot ​sthere are 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.
  
 ==== Grouping ==== ==== Grouping ====
  
-You can set a notification so that added flights to Leon are grouped. ​The moment ​single ​flight from the selected group is changed, the notification will include the schedule of all flights from the 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:
  
   * 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, ​he will receive information about all his flights in a given day (all recipients who are not planned on the flight will not receive the notification).+  * 2.  **Crew** - if the recipient of the notification is a crew member of the changed flight, ​they will receive information about all his flights in a given day (all recipients who are not planned on the flight will not receive the notification).
  
-__Example__:​ a pilot is scheduled for 2-legs flight STN-AMS-STN and on the same day he is scheduled for 1-leg flight STN-MAN. If there are changes made to the first flight, ​he will get a notification including details of the later flight as well.+__Example__:​ a pilot is scheduled for 2-legs flight STN-AMS-STN and on the same day he is scheduled for 1-leg flight STN-MAN. If there are changes made to the first flight, ​they will get a notification including details of the later flight as well.
  
   * 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 tripsfor 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
leon/notifications.txt · Last modified: 2016/08/30 13:06 (external edit)