Platina Standard API



missing
Platina Standard API Endpoints

Purpose

  • Exposes Platina core functionality.
  • Is developed and maintained as a core part of Platina.
  • The consumer should feel confident in taking a dependency from a maintainability standpoint.
  • Is updated and tested as part of each release.
  • Stable contracts versioning strategy.
  • Support Platina standard customizations.
  • A roadmap which focuses on improved scalability and security.

Responsibilities

  • Create/Update/Delete Platina journalized cases, deeds and work documents.
  • Authorize access.

Conceptual Information Model

missing

Limitations

  • Scalability, messages sent to API affects all Platina users, including internal Platina users.
  • Authorization is managed by Platina, this is not very scalable.
  • Concurrency, assumes no concurrent access to information.
  • Service host relies on TCP/IP binding. Support for HTTP/S binding will have to be added as requested.
  • The service assumes a one to one relation between diary and instance to be configured in Platina

Benefits compared to Platina legacy APIs

  • Contract driven development.
  • Stable contract versioning.
  • Continuous feature development.
  • No data dependencies using for example datasets (legacy .net)