attachment-reuse-controls-sample
A CAP Node.js service on @cap-js/attachments@cap-js/attachmentsAn official CAP Node.js plugin for attachment handling, with local database storage and AWS S3, Azure Blob or GCP Object Store integration.sap official, cap with a Fiori Elements object page that embeds the ui5-upload-controlsui5-upload-controlsA reusable UI5 control library for file upload and download under the miyasuta.ui5uploadcontrols namespace, built to sit in front of a CAP service.independent, ui5 library as a custom section.
The working end of the control library: the backend is any CAP service using the attachments plugin, and the control resolves the navigation path from its binding context after being handed the service URL and path as properties. The library itself is a git submodule, so the sample shows the seam rather than a copy.
Facts
Where it sits
Who is behind it
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- A reference application
Connections
Storing uploaded files next to the record they belong to
CAP Node.js attachments with database, S3, Azure or GCP storage
UI5 control library for file upload and download in front of CAP
Download
Architecture
as 2 deployment descriptors state it at 5fdd426, readDownload
Bound, and not drawn
- backend-srvhana
- backend-db-deployerhana
Documented, with no instance in the document
- @cap-js/attachments requires Object Store on SAP BTPbackend-srvconditionalcap-js/attachments — README
For productive use, a valid object store binding is required, see [Object Stores](#object-stores) and [Storage Targets](#storage-targets).
- @cap-js/attachments requires SAP Malware Scanning servicebackend-srvconditionalcap-js/attachments — README
If there is no malware scanner available and the scanner is not disabled, then the upload will fail.
- @cap-js/hana requires SAP HANA Cloudbackend-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicesbackend-srv
Bound in the descriptor, not joined to an entry
hana
Download
Bound, and not drawn
- npmtest-destination-contentSAP Destination service, SAP HTML5 Application Repository service for SAP BTP, SAP Authorization and Trust Management service
- npmtest-app-contentSAP HTML5 Application Repository service for SAP BTP
README
quoted from miyasuta/attachment-reuse-controls-sample, readattachment-reuse-controls
A sample project demonstrating reusable UI5 file upload controls integrated with a CAP backend using the @cap-js/attachments plugin.
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“- Runtime: SAP Cloud Application Programming Model (CAP), Node.js” — miyasuta/attachment-reuse-controls-sample — README
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-attachment-reuse-controls-sample- JSON
- /artifacts/miyasuta-attachment-reuse-controls-sample.json
- MCP
- Connecting an agent