Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Story

  • [

    VMS

    DATALOYVESSELINTEGRATION-

    5

    394] - As

    an IT Manager I want core Dataloy Products running on Wildfly

    a VRS user I want breakdown for consumption fields so that I can

    simplify my infrastructure
    - Numerous improvements has been developed to make Dataloy VMS run on Wildfly (formerly known as JBoss). Currently, all Dataloy products run on the same application server thereby simplifying the IT infrastructure.
    [VMS-24] - As a User, I want to be able to view and update the list of port areas, so that I can verify that ports are reported in appropriate areas
    - Area Administration module: A new tab called Port Areas has been added, showing all ports and how the ports are categorised in the area reports and corresponding areas.
    - Default sorting: Area Report, Port, Area. Columns: Area Report Code, Area Report Desc, Port Name, Area Code, Area Desc.
    - Refresh Port Areas button: Calculates all areas based on the master data and refreshes the table.
    - There must be a security target. EDIT > gives access to the refresh button.
    - A thread is availabl so the vMS can be used while while waiting.
    [VMS-43] - As a User, I want the Voyage Analysis Dashboard to be available inside the VMS, so that I can open the dashboard directly form the VMS
    - Modules > Voyage Analysis Dashboard: Option will b e active in modules menu if user is logged in and has permisssion to access. If logged in but has no access, the module will be deactivated - illustrated by being "grayed out".
    - Master Data > Dataloy Properties: A property defining the URL for the dashboard is needed (or can this be synch'ed automatically when everything runs on Wildfly).
    - Opening the module:    1. If the module is not configured (i.e. URL is missing), a message appears that the module needs to be configured and please contact an administrator.
       2. If the module is configured the dashboard web page is displayed inside the application (using JX Browser).
    [VMS-201] - As a Charterer, I want to be able to enter 2 decimals for boiler and generator consumption for vessels, so that calculations are more accurate
    - A Dataloy property was changed in view to show two decimals and not automatically round up to one if more than one decimal is entered.[VMS-79] - As a User, I want the list of Various Texts to be limited correctly when editing an existing entry, so that I can avoid wrong input
    - When editing a various text entry added against any table is edited, the list of available texts to pick from should be limited the same way as when adding the entry in the first place.[VMS-194] - As a User, I want the titlebar to show correct information, so that I know which system I am working in
    - The value set in property com.dataloy.customer.env should appear as Environment in the titlebar.[VMS-214] - As a User, I want offhire amounts to recalculate when rates are changed in a TC contract, so that I can get correct results
    - Offhire is not updated when user changes the tc rate in tc contract and the voyage estimate is then incorrect. Stored procedure to update the offhire invoked

 

Bug

  • [VMS-289] - Error when clicking on "Performance Cargo" checkbox when no other cargo is already selected as performance cargo
  • [VMS-340] - Performance tab does not work
  • [VMS-341] - Dates are empty when inserting port call
  • [VMS-342] - Updating Business Unit Name in Freeze Voyage Dialog fails
  • [VMS-324] - Change get_area_id function to return null in case TOO_MANY_ROWS exception is caught

    report consumption in detail

    - For customers wanting to report consumption breakdown this can now be activated. 
     

  • [DATALOYVESSELINTEGRATION-383]  - As a VRS user I want voyage reference and reason for call to be included when reporting to make it easier to connect the VRS report to a port call

    - Its now possible to include voyage reference and reason for call in the reports, this can be enabled and shown for customers wanting this. Including voyage reference and reason for call makes it easier for VRS server to locate the correct port call and many failing messages will be avoided.
     

  • [DATALOYVESSELINTEGRATION-386] - As a VRS user I dont want any dates in the future to be updated when update future dates property is disabled

    - Functionality for not updating future dates has been added. By default future dates will be updated, but this can now be disabled for customers requesting it. If do not update future dates is set then the following dates will not be updated:

    Noon Report: ETA, ETB, ETD
    Arrival Report: ETB, ETD
    In Port Report: ETB, ETD
    Departure Report: ETA Next Port

  • [DATALOYVESSELINTEGRATION-317] - As a VRS user I do not want straits to be skipped

    - Straits are now included, so reports should also be sent for straits.
     

  • [DATALOYVESSELINTEGRATION-363] - As a VRS user I want to hide ETB and ETD in Noon Report so that I don't have to report them

    - A property has been added for hiding ETB and ETD in Noon Report for customers wanting this.
     

  • [DATALOYVESSELINTEGRATION-366] - As a VRS user I want ETD for In Port Report to be optional so that I don't have fill in this when I don't know the ETD

    - A property has been added for making ETD for In Port Report optional.
     

  • [DATALOYVESSELINTEGRATION-367] - As a VRS user I want hours in service removed from In Port Report so that the report makes more sense.

    - Hours in service has been removed from In Port Report 
     

  • [DATALOYVESSELINTEGRATION-382] - As a VRS user I want labels to be clear so that we avoid misunderstandings

    - Labels has been updated and corrected
     
  • [DATALOYVESSELINTEGRATION-384] - As a VRS user I want to be able to report next port as to be announced (TBA) so that I can send departure report when I dont know the next port

    - In Departure report its now possible to report next port as To Be Announced. In case next port is not yet know on departure
     
  • [DATALOYVESSELINTEGRATION-397] - As a VRS user I want ETB and ETD for Arrival report to be optional so that I dont have to report them

     - A property have been added for hiding ETB and ETD in Arrival Report for customers wanting this.
     
  • [DATALOYVESSELINTEGRATION-343] - Support ETD being in the past for Arrival, Port and Noon reports

  • [DATALOYVESSELINTEGRATION-353] - BRT and DEP event log is not refreshed after ARR is updated