Issues Resolved in Dataloy API 3.1
Story
- [DLP-284] - As an API user, I want to retrieve Events from Cargo Port in the API so that I can use this data in other systems.
- Possible to extract event data from cargo port via the API. - [DLP-322] - As an API user, I want to build the JSON fields in a way that the JSON message is smaller.
- [DLP-344] - As an API user, I want better error messages provided by the server.
- [DLP-349] - As an API user, I want to delete a schedule.
- [DLP-366] - As an API user, I want to POST a Document and ensure that everything is done in one transaction.
- [DLP-369] - As an API user, I want to be sure that all the statements of each call have to be done in the same transaction.
-Â Ensure that every API call is executed in the same EJB transaction. - [DLP-372] - As a Product Owner, I want cache performance to be improved
- [DLP-373] - As an API user I want new API methods for allocating and unallocating 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 an API user, I want to see the voyage status through the API.
- [DLP-401] - As an 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