v3.3.1

Fixed

• Support for multiple run profiles

v3.5.0

Fixed

• Enforced the use of the Content-Length header to prevent server errors.
• Designated the content property in the Attachments table as a NonSortableProperty to prevent database errors when sorting LargeBinary fields.

v3.4.0

Added

• Introduced support for the @Core.AcceptableMediaTypes annotation, allowing specification of permitted MIME types for attachment uploads:

  annotate my.Books.attachments with {
      content @Core.AcceptableMediaTypes: ['image/jpeg'];
  }

• Added support for the @Validation.Maximum annotation to define the maximum allowed file size for attachments:

  annotate my.Books.attachments with {
      content @Validation.Maximum: '2MB';
  }

Fixed

• Removed the previous hard limit of 400 MB for file uploads. Files exceeding this size may still fail during malware scanning and will be marked with a Failed status.
• Resolved issues with generic handler registration, enabling services to intercept the attachments plugin using middleware.

v3.3.0

Added

• Added standard kind and set it as the default so that the configuration needs no adjustment when switching hyper-scalers.
• Added support for uploading and updating attachments via srv.run(INSERT.into(Attachments).entries()) or srv.run(UPDATE.entity(Attachments).set())

Fixed

• Fixed an issue that in multi-tenancy scenarios with separate object stores duplicate object stores per tenant were created when updating the tenant binding via the SaaS dependency service.
• Fixed a race-condition where tenant isolation in separate object store mode could be broken.
• Fixed a case where attachments were not correctly deleted.
• Fixed a server crash when using the AttachmentsSrv.put API to upload an attachment.
• Fixed a server crash when no object store would be bound to the application on BTP.
• Fixed a server crash when the filename would not be given when creating new attachment metadata.
• Fixed an issue where attachment handlers would be missing when all Attachments entity were behind feature toggles.
• Fixed an issue where with storage kind db attachments could not be uploaded as drafts.
• Fixed an issue where the content could be uploaded for a not existing attachments entity.

v3.2.0

Added

• Implemented integration with additional cloud providers for attachment storage:
  • Azure Blob Storage (kind: azure).
  • Google Cloud Platform Object Store (kind: gcp).
• Added support for mTLS authentication for the malware scanning service.
• Added criticality status to the attachment scan status.
• Provided translations for all SAP-supported languages.

Fixed

v3.1.0

Added

• Introduced a sample application in the /tests/ folder to facilitate local development and testing.

Fixed

• Resolved a memory leak that could occur during the malware scanning process.
• Ensured reliable deletion of all related attachments when parent entities are removed, preventing orphaned data.
• Improved handling of attachment deletion for non-draft entities to ensure consistent cleanup.

v3.0.0

BREAKING CHANGE: Replaced usage of the CAP req variable with cds.context throughout the codebase.

Fixed

• Resolved a crash in the malware scanning process when running the CDS server in a multitenancy setup.
• Corrected missing translations for column labels.
• Scan states are now translated.

Added

• Deprecated @attachments.disable_facet
• Introduced support for @UI.Hidden, enabling dynamic hiding of the attachments section in the UI.

v2.2.2

Added

• Enhanced logging capabilities by introducing a logging wrapper, providing more comprehensive and structured output to facilitate easier debugging and troubleshooting.

Fixed

• Resolved an issue in hybrid mode where an incorrect route path variable was used for attachment uploads in local environments.

v2.2.1

Fixed

• Ensured content is correctly stored and retrievable in non-draft mode.

v2.2.0

Added

• Support for the standard plan of the SAP Object Store in multitenant mode. The plugin now attempts to use the standard plan and falls back to the deprecated s3-standard plan if needed.
• Added support for non-draft attachment handling.

Fixed

• Improved error handling and runtime crashes.
• Fixed support for MTLS authentication via Service Manager.