1. COS 2 Help
  2. System updates
  3. Release v3.3.0

Release v3.3.0

Release date: 27 November 2022

Feature What's new Helpsheet/screenshot
14 Features & Enhancements
  • Make “Blocked” feature UX&UI in Airline-Vendor settings work the same way like in Agent-card
  • Purchase Documents: “Delete” function
  • New setting “show O/C on CB” on general airlines setup screen to steer which O/C shall be shown on integrators UI
  • Instead with FTP, send data to D365 with API calls
  • Login into the Office365 mailbox is possible only with oAuth2
  • Change request re Invoice Coversheet for Serbia: pull the “DPU” from first AWB’s Billing Date Selling, no longer from Issuing Date
  • The “0” or “00” in front of the flight number in received message must NOT mislead the system when the flight in the routing in COS is without this “0” or “00”. The vice versa is also valid
  • Date included in “DIS” FSU message must start being considered as departure date of the flight included in the “DIS” FSU message
  • Irregularity Info: Correct the default text
  • Enable the TagAware on the BE COS cache
  • Bookings Overview filter field optimisation: sorting-logic should not consider lower or upper case letters
  • Implement Template selection in AWB Stock modal from Invoicing Overview
  • Rates fetching: start caching it into app cache
  • API: call from CB to get only airports for Origin- & Dest-selectors having existing Rates in COS
11 Bug-Fixes
  • Rates->Rate Sheets: Delete option is missing/invisible
  • “DEP” FSU message is updating the arrival date
  • Under Pop Up management – Pop up notification unable to deactivate the button
  • After processing of FSU message, an incorrect time is stored in the “Mismatch List”
  • The inactive vendors must not be shown as an option in “Airline Vendor” filter field on “Cargo Sales Reports” preview screen
  • Impossible to generate an irregularity report of any kind
  • WT pricing lines are missing the link to the used Net Rate ID
  • We cannot save new record in “Department Address” without a workaround.
  • Bug when clearing the cache – in several cases we may be clearing too much
  • User editing – wrong validation happens
  • AWB comments management API has the wrong documentation