Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Story

  • [DLP-715] - As an API user, I want to invoke POST/PUT endpoints getting the result back, invoking the DLP business logic, without storing anything in databaseto invoke business logic and get a result back without persisting data

  • [DLP-726] - As an API user, I want to limit my results the response so that I don't accidentially accidentally take down the system by requesting too much data

  • [DLP-744] - As a an API user, I want to have Drydock in my FleetPlan

  • [DLP-766] - As a User, I want Dataloy to automatically keep track of all version numbers of the products I use, so that I can get more stable systems

  • [DLP-789] - As DDT API user I would want to have the port lists always up to date

  • [DLP-793] - As software architect I want a generic mechanism to define for which Dataloy classes the Cayenne context commit must be performed when they are removed from a list during the desiarilization

  • [DLP-795] - As a User, I want bunker orders to be created based on estimates to avoid double work

    - System should generate bunker order lines if there are estimates on the port call. 

  • [DLP-809] - As an API user, I want to be able to allocate an unallocated drydock

  • [DLP-816] - As API user I would want to have the AuditLog endpoint available so I can have a better control on what and when have been changed

  • [DLP-820] - As an API user, I want to be able to unallocate an allocated drydock

  • [DLP-825] - As API user I would want have contactInfo attribute in the Vessel object to avoid double API calls

  • [DLP-826] - As a developer, I need the FleetPlanReschedule logic to include DryDock calculations

  • [DLP-856] - As API user I would want to have weblink in the BusinessPartner resource

  • [DLP-860] - As a user I want vessel name to be included the subject of error messages

...