Skip to main content
Sign in

November 2018 - Product Change Log

Rob Dickie
  • Updated

November 30th 2018

  • Added Built At and Certificate of Financial Responsibility number fields to the vessel record
  • Various updates to the CBP 1300 and CBP 3171 documents to pre-populate with more appointment data, saving further data entry time for US customers

 

November 21st 2018

  • Updated the cargo name on the Events table to align with the formatting in the dropdown when creating an event
  • Bug Fixes:
    • Fixed a bug whereby the Cargo for an event would not be correctly selected during editing

 

November 19th 2018

  • Made some updates/tweaks to the new Menu Bar and UI based on user feedback
  • Reverted the IMO duplication check feature as this prohibited workflows in some use cases. A longer term solution which preserves vessel change history will be implemented at a future date to address this
  • Bug Fixes:
    • Sometimes the Type of Cargo checkbox selection would not save on the US Customs 3171 document - this is fixed

 

November 15th 2018

  • We made some optimisations to the Disbursement pages on the DA Ledger view to handle larger Disbursements more efficiently

 

November 09th 2018

  • Provided an option to populate Cargo Manifest documents from AUSGRAIN Bill data for Australian users
  • Bug Fixes:
    • Patched up a small bug that was introduced from the prior release whereby additional vessel details (flag, port of registry) would not populate during appointment creation

 

November 07th 2018

  • Vessel records will now be validated on IMO number instead of name, allowing the creation of vessels which share the same name
  • The IMO Number for a vessel will now be displayed in the Vessel lookup when creating an appointment, making it easier to identify the correct vessels when you have records with the same names
  • System Administrator users can now promote other users to be System Administrators
  • Bug Fixes:
    • The empty state for the Events tables didn't render properly when events grouping was enabled - this is fixed
    • The Events Grouping now displays the correct value when previewing an SOF document

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk