Release Notes: 24/10/2024 Standard API 7.1.0 (_MOD_API_7.1.0)

• #401336 As an external consumer I want to get/set custom data stored in Platina Custom DB
  Implemented the following API endpoints that handle custom data for objects:
  • For custom reference data:
    • GET /api/v7/reference-data/custom
    • GET /api/v7/reference-data/custom/{identifier}
  • For Deeds:
    • GET /api/v7/deeds/{id}/custom-data
    • PUT /api/v7/deeds/{id}/custom-data
  • For Journalized Cases:
    • GET /api/v7/journalized-cases/{id}/custom-data
    • PUT /api/v7/journalized-cases/{id}/custom-data
  • For Documents:
    • GET /api/v7/documents/{id}/custom-data
    • PUT /api/v7/documents/{id}/custom-data
• #439180 As a API Consumer I'd like to be able to get Diary number of created journalized case or deed.
  • The following API endpoints return assigned diary number in X-Platina-DiaryNumber response header:
    • POST /api/v7/journalized-cases/{id}/deeds
    • POST /api/v7/diaries/{id}/journalized-cases
• #439359 As a API Consumer I'd like to be able to get journalized case or journalized deed by diary number
  • The following endpoints were implemented to return journalized case or deed by their diary number:
    • GET /api/v7/deeds/with-diary-number/{diaryNumber}
    • GET /api/v7/journalized-cases/with-diary-number/{diaryNumber}
• #420538 As a API Consumer I'd like to be able to get Case Type per Diary
  • Implemented new endpoint:
    • GET /api/v7/diaries/{id}/case-types
• #420540 As a API Consumer I'd like to get Deed Types per Case Type
  • Implemented new endpoint:
    • GET /api/v7/reference-data/case-types/{id}
    • GET /api/v7/reference-data/case-types/{id}/deed-types
• #420541 As a API Consumer I'd only like to get returned the Secrecy and PUL Levels which I have configured in the Platina Admin
  • Implemented new endpoints:
    • GET /api/v7/reference-data/deed-pul-levels
    • GET /api/v7/reference-data/deed-secrecy-levels
    • GET /api/v7/reference-data/journalized-case-pul-levels
    • GET /api/v7/reference-data/journalized-case-secrecy-levels
• #439954 Added validation for POST /api/v7/deeds
• #442108 Added validation for POST /api/v7/diaries/{id}/journalized-cases
• #442979 Added validation for POST /api/v7/journalized-cases/{id}/deeds
• #442177 As a Stakeholder who installs API 7.x I faced with issues regarding /api/v7/journalized-cases/{id}/deeds and would like them resolved by Core team
• #385125 As an API consumer, I want to receive the same data as was available for WCF-based Standard API, so my implementations still work after migrating to new API. Part 2
  • Implemented new endpoints:
    • GET /api/v7/journalized-cases/{id}/meetings/{meetingId}
    • GET /api/v7/journalized-cases/{id}/meetings/{meetingId}/pre-registration
    • POST /api/v7/journalized-cases/{id}/meetings/{meetingId}/pre-registration
    • PUT /api/v7/journalized-cases/{id}/meetings/{meetingId}/pre-registration
• #393610 As an API developer, I want to prepare initial codebase and infrastructure for automated tests of API
• #393611 As an API Developers, I need to create test data and integration tests for Platina Standard API and achieve 60% coverage
• #423968 As a Project Manager I'd like Platina Core developers to fix for Platina Standard API 7.1.0 High severity Code Smells found by SonarCloud
• #439185 As an API developer, I want to be able to use policies as reusable functionality when sending queries and commands to Platina
• #433162 PostListItem_EnableOutgoingSetting does not affect the number of Origins returned by the endpoint
  • Also addressed similar issue for journalized cases, now API considers MunicipalityInfoHeap_EnableOutgoingSetting setting