Page Comparison

...

• Required and non-required schema fields possible (CON-128)

• Required and non-required endpoint parameters possible (CON-128)

• API endpoints: Certain URL parameters named just schemaName are now labeled schemaNameId. (see Pull Request: CON-15: Final steps in test configuration)

• API endpoints: Ambiguous URL parameters simply named id are now consistent with TMF guidelines, i.e. schemaNameId (CON-142)

• API endpoint label consistency updates (CON-142)

• Schema change: Renamed some fields from hash to serialized_hash and made descriptions clearer (PR#54)

• Schema change: Added agreement_revision_hash to ConsentRecord (PR#54)

• API endpoints added: /service/individual/record/ (GET) and /service/individual/record/agreement/{agreementId}/all/ (GET) (PR#54)

• API Endpoint removed: /service/individual/record/agreement/ (GET) (PR#54)

• API endpoint query parameters moved to requestBody OpenAPI specification (CON-153, details in PR#58)

• API endpoints that do a LIST operation now have both GET and POST in cases where filtering is possible (PR#58)

• Schema change: PolicyFilter removed (PR#58)

• API endpoints have revisionId as query parameter to fetch specific revisions of Agreement and other revisioned objects (PR#57)

• Schema change: Possibility to store Signature and revision objects for unsaved database objects (CON-152, details in PR#57) - new fields Revision.signed_without_object_id and Signature.signed_without_object_reference.

• Removed schema and endpoints for AuditTracker (we’ll be using generic webhooks for such purposes) (CON-161)

• Removed schema and endpoints for AgreementPurpose (this is now stored directly on the Agreement model, rather than in a separate relation) (CON-163)

Specification changes

• Updates to Terminology section: Consistency across specification and Gherkin scenarios (several smaller changes as part of CON-14)

• "Consent management" is replaced with other more accurate expressions (CON-68)

• “Internal Workflows” largely rewritten with notable changes and details added to universal workflows (CON-109)

• Several smaller quality improvements in terminology and language.

...