Zum Inhalt springen
Bpanda
Esc
↑↓navigieren↵öffnen⌘Jvorschau

Remove relationships by ID.

Remove relationships by ID. Remove architecture relationships by ids. A Composition follows the state of its part: if the part has a draft, only that draft loses it, and the whole loses it when the part is published; otherwise it is gone at once from the current versions of part and whole. Compositions of a process space are changed one after another; if another one is still being written after a short wait, the request is answered with 409 and can be repeated. Removing a relationship requires the edition of this process space to cover every element the relationship connects. For an element that carries the relationship, covered means the type of every stored version carrying it is included; for an end that only the other side names, that a read bounded by the edition still hands the element out. If one id fails this check, the whole request is refused and nothing is removed.

Security: Manager or Designer of the process space, or an owner of the affected architecture element(s).

DELETE/v1/warehouses/{warehouseId}/architectureRelationships
Autorisierung
AuthorizationBearer-Token (JWT) · headererforderlich
BpmLicenseAPI-Schlüssel · headererforderlich
Pfadparameter
warehouseIdstringerforderlich

Warehouse-Id

Request-Body
erforderlichapplication/json

ArchitectureRelationship-Ids to remove

Array von string
string
Antworten
204

NoContent

403

Forbidden: insufficient permissions, or the edition of this process space does not cover an element one of the named relationships connects

string
404

Warehouse not found

string
409

A Composition is being written, the part was published, or a draft of an element is being published; repeat the request. A 409 naming a relationship that exists on only one of its elements refuses the whole request, so none of the named relationships is removed. Retrying does not help: it clears only once the reference maintenance has dealt with the relationship - it either writes the missing counterpart back, after which the removal works, or removes the relationship itself, after which the id is gone. Daily where that maintenance is enabled, not at all where it is switched off. A relationship whose counterpart element is gone entirely is not refused here: no maintenance reaches that one, so this route removes it, without an event

string
Ausprobieren
Server
Autorisierung
Parameter
Bodyapplication/json
Anfrage
curl -X DELETE 'https://goto.bpanda.com/api/v1/warehouses/string/architectureRelationships' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'BpmLicense: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '[
  "string"
]'
Antwort
NoContent