assets-relations Collection
Description
The asset relations of the specified Test or Resource.
URL
/qcbin/rest/domains/{domain}/projects/{project}/{entity collection}/{entity ID}/assets-relations
/qcbin/rest/domains/{domain}/projects/{project}/{entity collection}/{entity ID}/versions/{version number}/assets-relations
Where /{entity collection}/
is one of: /tests/
or /resources/
.
Remarks
Using the application/xml;type=collection
CONTENT_TYPE header, this resource can perform batch processes.
If a batch process fails, the response contains the exception. However, the client cannot know in which state the batch failed.
Example: The client requests to post 10 entities, and after posting three entities, posting the fourth entity fails. The client gets the failure exception, but not information about which operations succeeded and which failed.
With a batch delete, the deletion is performed on entities belonging to the parent. For example:
../tests/3/asset-relations
deletes all asset-relations where the from-endpoint-id is 3.
A batch delete can also use a Filter to restrict the items deleted. For example:
../tests/3/asset-relations?query={id[>=1 And NOT = 5]}
deletes all asset-relations where the from-endpoint-id
is 3 and whose ID is greater than 0, but not 5.
HTTP Methods
GET: Returns the collection of Asset Relations.
PUT: Updates an Asset Relation. If type=collection, updates a list of entries.
DELETE: Deletes the items identified with the URL. Deletion can be restricted with Filter.
POST: Creates a new Asset Relation. If type=collection, creates multiple new Asset Relations.
Media Type |
GET
|
PUT
|
DELETE
|
POST
|
---|---|---|---|---|
application/xml |
![]() |
![]() |
![]() |
![]() |
application/xml;type=collection |
-
|
![]() |
-
|
![]() |
application/json | - | - | - | - |
Returns
One of the HTTP Return Codes.
A JSON string of the same format as the data returned with a GET operation.