See how to use the “soft-lock” option with the Volume- and the Chargeable Weight-Fields on the Booking Mask.
1. “Soft-lock” state (organge coloured)
Is meant to be used mainly for pre-bookings to protect the value inside the Volume-field against COS-internal-synchronisations, when you or another user might want to change the Gross Weight in a pre-booking but keep the volume as it was initially set. This helps you to plan the space on your flights more accurately. It will still let processes like f.e. incoming C-IMP-msgs such as, FWBs, FFRs, FSUs etc, or incoming Bot-data change and update the content of this field.
2. “Super-lock” state (red coloured)
Is meant to be used as usually for cases, when you want to sell a higher Chargeable Weight f.e. due to oversized cargo etc. In this state, the values remain completely protected against any COS-internal synchronization as well as against any external data updates coming from C-IMP-msgs such as FWBSs, FFRs, FSUs etc as well as against incoming Bot-data-updates.
The Pre-Booking tool is meant to be used for bookings lists, that you receive from customers, that have regular weekly shipments.
See how to create a whole bunch of bookings based on one rough-model booking. You also have the option to send out FFR-msgs for each of those bookings.
And all this by just one click of the mouse!
See how to transmit Booking- and Pricing-details from one COS entity to another.
This used for between GSAs using COS, that do intercompany buying/selling.
All bookings details including attached AWB-copy etc (expect internal remarks) as well as the Buying Pricing details such as Airfreight-costs as well as Other Charges due Carrier will be part of that data-transmission.
In the COS-entity that receives that data, the Pricing Selling-side will get populated accordingly and they will also receive an e-mail-notifications about bookings that are getting transmit.
ee how easy you can drag and drop an AWB PDF Copy onto the COS Booking Mask in order to:
1. Call an existent booking
2. Update the major booking details like Pcs, Gr.Wt, Chrg.Wt., Origin, Destination, Commodity and Agent
3. Attached the AWB PDF to the Documents-section of the booking in COS
4. Flag the “AWB Copy” tick to indicate that AWB was received
See how to use the Standard Text Tool so that you do not need to write re-occuring same text again and again.
You can easily store a text in most free-text-fields in COS and “call” it by entering a simple code adding the question-mark-character “?” and then auto-populate the field by using the tab-key.
See how to create a Pop-up in COS, that would hinder users to set back AWBs from status “Assigned” back to status “Created”.
This blocking Pop-up can be useful for certain stations/airlines, that do not want to allow users to set back AWBs the whole way to status “Created” because that action bears a risk. Sometimes forwarding agents might still use an AWB-Nbr, that they have once given for a booking that got cancelled and they might re-use that AWB-Nbr again for another future other shipment.
By keeping such AWBs in status Assigned, such risks can be minimized.
Since the pop-ups are only shown on the Booking Mask, this “safety-measure” obviously only applies when the user is doing this task on the Booking Mask. Withdrawing/setting back AWBs back to Created status, can still be done on the AWB-Stock-Overview screen at any time.
See how to create a pop-up to guide the users, that are cancelling booking in COS to send out an FFR-message with the booking code “XX” to the airline system, BEFORE they set back to AWB to status Assigned.
Using an FFR-message with the booking code “XX” to be sent to the airline system, would also cancel the booking in the airline system. This obviously depends on the “readyness” of the airline-system to allow that.
By this pop-up example, you can “block” users to set back an AWB from Booked to Assigned unless the booking code in all flight-legs in the routing is “XX”.
See how to paste and parse a whole bunch of Dimensions’ details into a booking by just two clicks.
That works for text as well as for screenshots/pictures.
See the new enhanced Detailed Activity Log now showing all detailed changes done in a booking.
Every single change is logged based on individual snapshots each time a user launches a save process on an AWB.
See how to use, create, tailor-make Codes for Commodity (Nature of Goods) for the purpose of being quicker when entering bookings as well as to show commodity of various booking in a uniform way on reports, stats, on flight-manifests and FBL-messages etc.