onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

cds-feature-softdelete

The CAP Java counterpart to cds-softdelete-plugin: the same softdelete aspect, the same annotation, DELETE rewritten as a flag.

Ships the io.github.miyasuta.softdelete aspect and the handlers that go with it — DELETE on an annotated projection sets isDeleted, deletedAt and deletedBy instead of removing the row, composition children follow the parent, and READ filters flagged rows out.

GitHub0 ★

Facts

Last push

Where it sits

Lives in
CAP
Provides
Soft deleteCAPSoft deletecapabilityDeleting a record without removing it — flagging the row, recording who deleted it and when, and keeping it out of reads. The question underneath is what DELETE should mean to a client that cannot tell the difference, and what happens to a composition tree when its root is flagged.
Flavors
Javafrom its runtime

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
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.

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →
PracticalFunctional boundary

The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.

What it declares

Every artifact

Type
CDS plugin
Origin
Independently maintained
Runtime
Java

As a CDS plugin

Distributed through
Maven

Connections2

Download
cds-feature-softdelete connectionscds-feature-softdeleteFUNCTIONAL→ alternative to1alternative to authoredcds-softdelete-plugin→ provides1provides authoredSoft delete

README

quoted from miyasuta/cds-feature-softdelete, read
miyasuta/cds-feature-softdelete/README.mdOn GitHub

cds-feature-softdelete

A plugin for implementing soft delete functionality in SAP Cloud Application Programming Model (CAP) Java applications.

excerpt, no licence read, read the rest, on GitHub

Others providing1

Compare all 2 on the Soft delete page →
Declared alternative
  1. cds-softdelete-pluginCAP plugin turning DELETE into a flag on annotated entities
Soft delete
  1. cds-softdelete-pluginCAP plugin turning DELETE into a flag on annotated entities

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/cds-feature-softdeletetree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
runtimesjava
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, data-and-persistence
History in the atlas2
  1. Entered unmapped because no capability fitted: change-tracking is history of changes, data-privacy is close to the opposite, and inventing an edge would have been worse than the gap. The capability now exists, so the edge is the honest one rather than the nearest one.
  2. First seen.
For your agent
Ref
artifact:miyasuta-cds-feature-softdelete
JSON
/artifacts/miyasuta-cds-feature-softdelete.json
MCP
Connecting an agent