Story
- [DLP-284] - As a an API user, I want the 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 developer user, I want to build the fields JSON in fields in a way that the JSON message is smaller.
- [DLP-344] - As an API user, I would want better error messages provided by the server.
- The error message format changed.
[DLP-345] - As a User I would like to have distances calculated faster so that I can work efficiently.
- Distances on the saga case is calculated in 15 sec. - [DLP-349] - As an API user, I would like want to delete a schedule.
- Delete a simple VoyageHeader with relations to Voyage, PortCall, Cargo. We need to decide whether or not we should delete voyage, portCall and Cargo also or nullify. - [DLP-366] - As an API user, I want to POST document a Document and be sure ensure that everything is done in one transaction.
- Now the class DocumentResource makes different commits losing the concept of 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.
- The transaction cannot be start in CustomJacksonJsonProvider so the deserialization and the BL must be invoked from the EJB. - [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 an API user I want a new API methods to allocate for allocating and unallocate 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.
- IF the voyage_header_id of the voyage displayed in the Voyage Analysis Dashboard details page is present in the voyage_header_id field of a tbl_budget_voyage_start, show a new "Model" column displaying the details of the voyage represented by the voyage_id in the same table (tbl_budget_voyage_start).
- The new column should show as the first one of the three ("Model", "Preliminary", "Adjusted"). - [DLP-399] - As a an API user, I want to see the voyage status through the API.
- We need this in FSP to be able to prevent users from allocating voyages before any freezed voyages. - [DLP-401] - As an API user, I want business logic implemented both for normal cargo and lumpsum cargo.
- Implement calculation of freightRate for both lumpsum and not lumpsum cargos. - [DLP-411] - As an API user, I want to get port cost breakdown from port call.
...
- [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
Related Content
| Expand | ||
|---|---|---|
| ||
|