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

« Previous Version 10 Next »

2. May 2016
With great pleasure Dataloy presents API 3.0

Highlights of this Release:

Highlights of Dataloy API 3.0

Update Sub-Objects and Lists and Update in a Single Transaction

API 3.0 introduces the ability for a user to input/update/replace sub-objects and lists and to update all in a single transaction. It is also possible to update sub-objects (for example, voyage on voyage header resource) by sending in code/id.

Cargo Business Logic Correctly Implemented in the DLP as it is in Kara

Cargo Business Logic has been correctly implemented in the DLP as it is in Kara (for Product Owners). There is an automatic mechanism to invoke business logic during  POST and PUT methods (for architects).

Data Changed Outside the API Refreshed

Each time data is changed outside the API is now refreshed enabling a user to trust data received by the API. Every time there is a change in the database a trigger/s will insert a row in a new table. The table will have three columns:

 - Object Name (the corresponding DLP object name of the table that has been changed)-
 - Primary Key Value (the key of the row that has been changed).
 - Creation Time Stamp (the time stamp of the row creation).

The initial two columns will be the primary key of the table. A job that runs inside DLP will constantly monitor if there are rows in the table - and if yes - will refresh the corresponding cayenne object and delete the row from the table.

Related Content

 Expand to see related content

Unknown macro: {dynamiccontentbylabel}

  • No labels