+
+
+1. User sends request to create a resource
+2. An empty resource instance is created
+3. Developer sets default values for attribute 1 and 2
+4. Attribute 1 and 3 from incoming request are copied into default instance
+5. Developer overwrites attribute 3
+6. Row is inserted in database
+7. Developer sends notification to service bus
+8. The new resource is fetched
+9. Resource is sent back to the user
+
+### Update Resource
+
+
+
+
+
+1. User sends request to update resource with ID 1
+2. Existing resource is fetched from database
+3. Developer changes attribute 1 and 2
+4. Attribute 1 and 3 from incoming request are copied into fetched instance
+5. Developer overwrites attribute 3
+6. Row is updated in database
+7. Developer sends notification to service bus
+8. The resource is fetched, along with requested includes
+9. Resource with includes is sent back to the user
+
+### Delete Resource
+
+
+
+
+
+1. User sends request to delete resource with ID 1
+2. Developer runs custom validation logic
+3. Row is deleted from database
+4. Developer sends notification to service bus
+5. Success status is sent back to user
+
+### Set Relationship
+
+
+
+
+
+1. User sends request to assign two resources (green) to relationship 'name' (black) on resource 1 (yellow)
+2. Existing resource (blue) with related resources (red) is fetched from database
+3. Developer changes attributes (not shown in diagram for brevity)
+4. Developer removes one resource from the to-be-assigned set (green)
+5. Existing resources in relationship (red) are replaced with resource from previous step (green)
+6. Developer overwrites attributes (not shown in diagram for brevity)
+7. Resource and relationship are updated in database
+8. Developer sends notification to service bus
+9. Success status is sent back to user
diff --git a/docs/usage/extensibility/services.md b/docs/usage/extensibility/services.md
index 7880189eee..7233756062 100644
--- a/docs/usage/extensibility/services.md
+++ b/docs/usage/extensibility/services.md
@@ -102,14 +102,20 @@ IResourceService
+-- ICreateService
| POST /
|
+ +-- IUpdateService
+ | PATCH /{id}
+ |
+-- IDeleteService
| DELETE /{id}
|
- +-- IUpdateService
- | PATCH /{id}
+ +-- IAddToRelationshipService
+ | POST /{id}/relationships/{relationship}
+ |
+ +-- ISetRelationshipService
+ | PATCH /{id}/relationships/{relationship}
|
- +-- IUpdateRelationshipService
- PATCH /{id}/relationships/{relationship}
+ +-- IRemoveFromRelationshipService
+ DELETE /{id}/relationships/{relationship}
```
In order to take advantage of these interfaces you first need to register the service for each implemented interface.
diff --git a/docs/usage/reading/filtering.md b/docs/usage/reading/filtering.md
index 90b03462d8..c6b65f9867 100644
--- a/docs/usage/reading/filtering.md
+++ b/docs/usage/reading/filtering.md
@@ -119,8 +119,8 @@ GET /articles?filter[caption]=tech&filter=expr:equals(caption,'cooking')) HTTP/1
There are multiple ways you can add custom filters:
-1. Implementing `IResourceDefinition.OnApplyFilter` (see [here](~/usage/resources/resource-definitions.md#exclude-soft-deleted-resources)) and inject `IRequestQueryStringAccessor`, which works at all depths, but filter operations are constrained to what `FilterExpression` provides
-2. Implementing `IResourceDefinition.OnRegisterQueryableHandlersForQueryStringParameters` as [described previously](~/usage/resources/resource-definitions.md#custom-query-string-parameters), which enables the full range of `IQueryable