Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Story
- [DLP-284] - As a user I want the retrieve Events from Cargo Port in the API so that I can use this data in other systems
- [DLP-322] - As API developer I want to build the fields JSON in a way that the JSON message is smaller
- [DLP-344] - As API user I would want better error messages provided by the server
- [DLP-345] - As a User I would like to have distances calculated faster so that I can work efficiently
- [DLP-349] - As an API user, I would like to delete a schedule
- [DLP-366] - As API user I want POST document and be sure that everything is done in one transaction
- [DLP-369] - As API user I want to be sure that all the statements of each call have to be done in the same transaction
- [DLP-372] - As a Product Owner, I want cache performance to be improved, so that this functionality is ready for production
- [DLP-373] - As a user I want a new API methods to allocate and unallocate voyages
- [DLP-384] - As a Trader, I want to be able to compare the underlying COA Model Calculation against the Preliminary Calculation and Adjusted Calculation, so that I can better evaluate the deal
- [DLP-399] - As a user, I want to see the voyage status through the API
- [DLP-401] - As API user I want business logic implemented both for normal cargo and lumpsum cargo
- [DLP-411] - As an API user, I want to get port cost breakdown from port call
Bug
- [DLP-389] - Problem with QueryParser.hasAllPropertySet
- [DLP-390] - Problem with QueryParserSpecial.buildNeededFields
- [DLP-391] - Problem posting remark
- [DLP-392] - Posting VoyageHeader without specifying "isUnallocated" the value is set to null in the DB
- [DLP-393] - Manage "voyage": 0 and "ownedByVoyage":0 in POST PortCall
- [DLP-394] - Problem when a list of PortCalll is PUT changing the portCallSequence (due to the Cayenne sql execution statements )
- [DLP-395] - CargoPortMixIn redefine the name of the property handlingCostCurrencyRef to handlingCostCurrency, this cause problem with BL and deserialization
- [DLP-410] - Nullpointer in VRS API when next port is not included in json
- [DLP-420] - HasSource are not created and attached to the main object