leon:trip
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
leon:trip [2018/03/01 14:57] bartek [Trip] |
leon:trip [2022/11/07 20:42] (current) rafal [Trip] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Trip ====== | ====== Trip ====== | ||
| - | [{{ : | + | [{{ : |
| In this section you can add or amend information relating to the whole trip such as: | In this section you can add or amend information relating to the whole trip such as: | ||
| Line 7: | Line 7: | ||
| * **Trip No** - default trip number assigned by Leon. It can be edited and changed. | * **Trip No** - default trip number assigned by Leon. It can be edited and changed. | ||
| * **Status** - __Option__ - not confirmed, __Confirmed__ - confirmed flight, __Opportunity__ - more information at the bottom of this page. | * **Status** - __Option__ - not confirmed, __Confirmed__ - confirmed flight, __Opportunity__ - more information at the bottom of this page. | ||
| - | * **Type** - trip type: Ambulance, Cargo, Flight for Owner, Other, PAX, Simulator, Technical, Training. | + | * **Type** - trip type: Aircraft repositioning, |
| * **Commercial** - a checkbox to mark if a trip is commercial. When ticked flights show in green in schedule (all flight types); if unticked, the flights will appear in blue. | * **Commercial** - a checkbox to mark if a trip is commercial. When ticked flights show in green in schedule (all flight types); if unticked, the flights will appear in blue. | ||
| + | * **SHOW ON MAP** - an option to view the trip route on the map. | ||
| * **Quotation No.** - here you can add a quotation number and its price, then print sales documents from Table view. | * **Quotation No.** - here you can add a quotation number and its price, then print sales documents from Table view. | ||
| * **Notes** - a field for adding notes for internal usage (these notes don't appear on documents). | * **Notes** - a field for adding notes for internal usage (these notes don't appear on documents). | ||
| * **Extra Information** - these notes appear on Charter Contract and Flight Quotation documents. | * **Extra Information** - these notes appear on Charter Contract and Flight Quotation documents. | ||
| * **Client** - you can choose a client from Phonebook. Once the client is chosen you can also choose **Representative**. This information will show in **Flight brief** and **Charter Contract**. | * **Client** - you can choose a client from Phonebook. Once the client is chosen you can also choose **Representative**. This information will show in **Flight brief** and **Charter Contract**. | ||
| - | * **Take off & Landing emails** - it's possible | + | * **Customer service assignee** - sales person assigned |
| - | * **Move leg to another trip** - if you click inside | + | * **Marketplace** - select a company through which you made a deal with the client. |
| + | * **Take off and landing emails** - specifies recipients for movement email with ' | ||
| + | * **MOVE LEG TO ANOTHER TRIP** | ||
| + | |||
| + | Click this button if you want to either | ||
| + | |||
| + | {{: | ||
| * **Add tag** - you can create a tag for the whole trip and add a colour. If you want to tag a single leg, go to a tab FLIGHT. | * **Add tag** - you can create a tag for the whole trip and add a colour. If you want to tag a single leg, go to a tab FLIGHT. | ||
| * **Notes** - this note can be input manually. It can also be input as a template in [[leon: | * **Notes** - this note can be input manually. It can also be input as a template in [[leon: | ||
| * **Trip Supplementary Info** - additional notes for internal use only. | * **Trip Supplementary Info** - additional notes for internal use only. | ||
| - | <box> If you change | + | Click a clock-icon displayed on top of the notes field to view the **history of changes** of Notes or Trip Supplementary Info. |
| + | Hover the mouse over the Client' | ||
| + | |||
| + | {{: | ||
| + | |||
| + | < | ||
| ------ | ------ | ||
| ===== Flight status ' | ===== Flight status ' | ||
| - | ' | + | ' |
| This is a different status from the ' | This is a different status from the ' | ||
| Line 31: | Line 44: | ||
| * **Different background** - this status is represented by different background (on the right). This also informs OPS Team of this not being an actual flight, so they do not have to work on it. {{ : | * **Different background** - this status is represented by different background (on the right). This also informs OPS Team of this not being an actual flight, so they do not have to work on it. {{ : | ||
| - | * **Shows in Avinode** - can be exported and sold in Avinode as an empty leg. | + | * **Shows in Broker platforms** - can be exported and sold in Broker platforms such as Avinode as an empty leg. |
| * **Aircraft positioning** - in Leon, this status does not position an aircraft from one place to another. Aircraft is visible at the arrival airport of the last confirmed flight (see example below). | * **Aircraft positioning** - in Leon, this status does not position an aircraft from one place to another. Aircraft is visible at the arrival airport of the last confirmed flight (see example below). | ||
| * **Document menu** - disabled for this Trip status. It is impossible to print flight documents for this status. | * **Document menu** - disabled for this Trip status. It is impossible to print flight documents for this status. | ||
| Line 40: | Line 53: | ||
| As you can see in the screenshot the aircraft landed at **EPKK** and the next confirmed flight 3 days later is scheduled from **EPWA**. | As you can see in the screenshot the aircraft landed at **EPKK** and the next confirmed flight 3 days later is scheduled from **EPWA**. | ||
| - | You can add the ' | + | You can add the ' |
| As you also can see in the screenshot, the aircraft has not been positioned and is still placed in EPKK. | As you also can see in the screenshot, the aircraft has not been positioned and is still placed in EPKK. | ||
| ---- | ---- | ||
| - | **See also**: | + | ===== Sending take off and landing emails ===== |
| + | [{{ :leon: | ||
| - | | + | We have changed the way that MVT messages recipients are determined when option ' |
| + | |||
| + | We have added an extra field in the **TRIP** tab: 'Take off and landing emails' | ||
| + | |||
| + | In 'Take off and landing emails' | ||
| + | |||
| + | If the Client is added, 'Take off and landing emails' | ||
| + | |||
| + | This value can be changed to a custom email address, without having to select a Client, or removed completely. It is also possible to insert more than one email address separated by a comma, i.e. email1@client.com, | ||
| + | |||
| + | If the 'Take off and landing emails' | ||
| + | |||
| + | **It is important that ' | ||
| + | |||
| + | ------ | ||
leon/trip.1519916232.txt.gz · Last modified: 2018/03/01 14:57 by bartek