eRS Actions icon

eRS Actions

Interact with the Ers App API

Actions29

Requirement → Delete

AI-generated

Summary

Deletes a single requirement in eRS by its ID, with optional flags to also delete or unlink the bookings associated with it.

Inputs

  • Authentication — Credential type: OAuth2 (recommended, default) or Access Token.
  • Requirement ID (required) — Unique numeric ID of the requirement to delete (minimum 1).
  • Additional Fields > Delete Bookings — Boolean, default false. When enabled, sends delete_bookings as a query parameter to delete all bookings associated with the requirement.
  • Additional Fields > Unlink Bookings — Boolean, default false. When enabled, sends unlink_bookings as a query parameter to unlink (not delete) all associated bookings.
  • Request Options — Node settings for batching (items per batch, batch interval in ms), ignoring SSL certificate issues, an HTTP proxy, and request timeout (default 10000 ms).

Output shape

The API response for the delete request, one result per input item. The exact body is not visible in the provided source, which is a stripped build, so its contents are not confirmed.

The operation is declarative (routing-based), so the request is built from the properties. The source pack does not show the HTTP method or endpoint. Delete Bookings and Unlink Bookings are alternatives; the source does not show how the API handles both being enabled.

Examples

Example 1: Remove a cancelled requirement and its bookings

Requirement ID set to an expression like {{$json.id}}; Additional Fields: Delete Bookings = true.

Example 2: Delete a requirement but keep its bookings

Requirement ID = 123; Additional Fields: Unlink Bookings = true.

Links

Discussion