Page Comparison

2122. June 2016
With great pleasure Dataloy presents API 3.1
Issues resolved - listed by user story

...

It is possible to extend returned fields of a given endpoint by asking for each subobject to return its "default" view. It can be done by specifying in the JSON message of the "fields" property attached to attach to the HTTP header the property "all":"*". For example, the following JSON attached to the VoyageHeader end-point:

...

...

...

...

All statements of all API calls are now executed in the same single EJB transaction.

...

A generic mechanism to invoke pre-process checks before the deserialization of JSON objects

Created preis introduced. Pre-process components for Cargo and CargoPort objects .

The following control are done have been created so when a Cargo cargo is POST or PUT the following controls are performed:

For not Non-lumpsum cargo: 

• Changing cargoQuantity in a cargoPort does not trigger any calculation on cargoQuantity of other cargoPort.
• The cargoQuantity at cargo level is calculated summing the cargoQuantity of loading ports
• it is not possible assign freightRate freightRate cannot be assigned in both discharge and loading ports.
• The cargoQuantiy used for calculations are those in cargoPort, . cargoQuantity at Cargo level is not used in calculations.
• Freight and freightRate used for calculations are those in cargoPort,.
• API will not use stowageFactor and weightFactor from commodity

...

• Commodity.

Lumpsum cargo: 

• cargoQuantity and freightRate must be assigned at Cargo level.

Port Cost breakdown can now be accessed from portCall.portAgents and furtherfrom portAgents.portCostsOnly . By default, only a link is included by default so use the following functionality to get all you need in one request: provided. Use the functionality Adjust Number of Fields to be Returned from a Request to retrieve all that is needed in a single request.

Related Content

{dynamiccontentbylabel:showLabels=false|showSpace=false}