Skip to main content

2022-02-04

Bug Fixes

  • Fixed a minor issue recorded in the browser console when logging in to the website. Error was "SyntaxError: JSON Parse error: Unrecognized token '<'"
  • Fixed an issue when loading the Dashboard that resulted in a large file being sent to the browser. Now the server compresses the file before the browser downloads it
  • Fixed an issue preventing the Download options that remove NAD segments from working properly.
  • Fixed an issue caused by AWS outages in various regions that resulted in users not being able to login

New Features

  • The Dashboard function has been re-written to allow the content to dynamically refresh whenever the BAPLIE data is updated (via API Calls or by another user).
  • Added support in Main Content, 2D View and 3D View to show 9'0" and 4'3" height containers
  • Rearchitected the Dashboard to a new framework
    • You can now change the chart type for each chart to either Bar Chart, Pie Chart, TreeMap or Legend Only.
    • Changes to chart types are saved against your profile and reused for all future views of the dashboard
    • Added two new charts for Length and Status, and Primary IMDG code.
    • Added ability to export Dashboard to PDF
  • Upgraded the framework used on the Documentation site to the latest release
  • Rearchitected the 2D and 3D views to remove Container ID as the unique key and to use an internally generated ID instead. This allows for BAPLIE files with the same container number to display all instances of the duplicated container.
  • Added FileName to the 2D and 3D header details shown when you click the info button next to the vessel name.
  • Added support for additional payment methods that are typical in the China region (WeChat Pay and Alipay)
  • Added notification on the bottom left to display if the Facility membership is due to expire within the next 11 days, or if the membership has already expired.
  • Updated the Membership section of Manage Facility to highlight any special offer rates for legacy customers
  • Modified the requirements for usernames to allow period (.) to be used within the username eg firstname.lastname
Back to top