This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
leon:documents-manager [2020/01/31 10:36] bartek [Attaching extra pages to documents] |
leon:documents-manager [2023/10/18 17:57] rafal [Main page] |
||
---|---|---|---|
Line 3: | Line 3: | ||
**Documents Manager** panel allows managing and customizing documents available in Leon, such as: **Flight Order**, **Trip Sheet**, **General Declaration**, | **Documents Manager** panel allows managing and customizing documents available in Leon, such as: **Flight Order**, **Trip Sheet**, **General Declaration**, | ||
- | The list of pre-defined documents is constantly expanded to cover all documents in Leon. In the future it will be possible to create completely **new custom document** apart from those pre-defined in Leon. | + | The list of pre-defined documents is constantly expanded to cover all documents in Leon. It is also possible to create completely **new custom document** apart from those pre-defined in Leon. |
===== Main page ===== | ===== Main page ===== | ||
- | [{{ : | + | [{{ : |
- | The main page shows **3** filtering options: by **document type**, **language** and **publishing status**, as well as **5** columns: | + | The main page shows **3** filtering options: by **document type**, **language** and **publishing status**, as well as **7** columns: |
- | * **Documents** - saved versions of Flight Order or Flight Brief. | + | * **Name** - name and the saved versions of the document |
- | * **Language** | + | * **Type** - type of the document |
- | * **Published** - the status of the documents, whether they have been published, or not. Click on the white dot if you want to publish saved version - the dot will become green. | + | * **Published** - the status of the documents, whether they have been published, or not. Click on the white dot if you want to publish |
+ | * **Visible in Crew App** - allows indicating which version(s) of the document will be available to Crew on a flight in the Crew App > tab ' | ||
+ | * **Language** - the language of the document indicated within the edit in the SETTINGS tab | ||
* **Last modified** - the date of the latest modification. | * **Last modified** - the date of the latest modification. | ||
* **Action** - once the document has been uploaded you can hover the mouse to see available options: | * **Action** - once the document has been uploaded you can hover the mouse to see available options: | ||
-{{: | -{{: | ||
-{{: | -{{: | ||
- | -{{: | + | -{{: |
-{{: | -{{: | ||
Line 138: | Line 140: | ||
It is possible to attach **extra pdfs** to existing documents in Leon. If, for example, Flight Order needs to have attached an extra page for pilots with towing instructions, | It is possible to attach **extra pdfs** to existing documents in Leon. If, for example, Flight Order needs to have attached an extra page for pilots with towing instructions, | ||
- | {% pdf "towing_instructions.pdf" | + | <code Twig>{% pdf 'towing_instructions.pdf' |
where ' | where ' | ||
---- | ---- | ||
+ | ===== Attaching pdf documents from the checklist items to Crew Tripsheet ===== | ||
+ | It is possible to attach pdf files uploaded to some of the elements of the checklist to the Crew Tripsheet document. | ||
+ | |||
+ | This can be achieved by using the function {{: | ||
+ | |||
+ | This is only possible in the Crew tripsheet for the elements that contain ' | ||
+ | |||
+ | An example of how to embed the code in the tripsheet can be seen below, where the ' | ||
+ | |||
+ | <code Twig [enable_line_numbers=" | ||
+ | {% set files = [] %} | ||
+ | {% for leg in tripsheet.activities %} | ||
+ | {% if leg.checklist.catering and leg.checklist.catering.files %} | ||
+ | {% set files = files|merge(leg.checklist.catering.files) %} | ||
+ | {% endif %} | ||
+ | {% endfor %} | ||
+ | {% for trip in tripsheet.trips %} | ||
+ | {% if trip.checklistTrip.CATBriefsRequired and trip.checklistTrip.CATBriefsRequired.files %} | ||
+ | {% set files = files|merge(trip.checklistTrip.CATBriefsRequired.files) %} | ||
+ | {% endif %} | ||
+ | {% endfor %} | ||
+ | {{ showFiles(files) }}</ | ||
+ | The PDF file(s) will be embedded at the **end of the document**. | ||
+ | ----- | ||
===== Showing a map in documents ===== | ===== Showing a map in documents ===== | ||
Line 153: | Line 179: | ||
You can define **width** and **height** as you wish, as well as the** colour of lines** on the map (see screenshot). | You can define **width** and **height** as you wish, as well as the** colour of lines** on the map (see screenshot). | ||
+ | |||
+ | The parameters set by default: “c_width=2” and “markers_icon_url” which have a format of “red_markers.png” can also be changed. Markers are visible by default, if you want to remove them, set a parameter as “none”. They are red circles that look like: | ||
+ | |||
+ | {{: | ||
---- | ---- | ||
+ | ===== Adding header/ | ||
+ | |||
+ | To add either a **header** or a **footer** as a picture you need to use appropriate tabs in Documents Manager panel. | ||
+ | |||
+ | |||
+ | First of all a file should be uploaded to the right-hand filter, tab **FILES**. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Once it's done, a **code** needs to be inserted in a tab HEADER: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Then, in a **CSS** tab you can set up, that i.e. the footer should appear only on the 1st page, or that the footer should appear only at the bottom of the last page: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | ===== Changes history ===== | ||
+ | [{{ : | ||
+ | It is also possible to see the history of changes of the document as well as to preview the past versions of the code. | ||
+ | |||
+ | To access the history of changes, simply click on the {{: | ||
+ | |||
+ | Len will display the changes history information such as time and date (in UTC) and the name of the user who made changes (as per below): | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Clicking on the {{: | ||
+ | |||
+ | This will allow retrieving any past version of the document by pasting the code from the document to the relevant section of the Document Manager. | ||
+ | |||
+ | ----------------- | ||
+ | |||
+ | ------------- | ||
===== HTML structure ===== | ===== HTML structure ===== | ||