While working on OPENIDM-16833 it became confusing which API operations must be supported for notification signaling and RDVP processing.
Some of the API request that are allowed by IDM on a relationship edge update/patch request do not result in RDVPs being calculated for the object which the "_ref" previously pointed to.
This may have been by design, or a known caveat. Although the Docs show examples of requests that are able to be made, I have not found where the docs specify any limited amount of APIs that we support for use of relationship notification signaling. This should be added to docs if it is known or by design, if it does not already exists.
If this is not by design or a known caveat, then it should be worked as a bug. This would impact the scope of time completion for OPENIDM-15652, or would need to be worked after OPENIDM-15652 and also include any fixes related to OPENIDM-16833.
Below are the update/patch requests made directly to an edge ID that I have found that are allowed by IDM, and also included in the API Explorer. In these examples the "_ref" previously pointed to a different user, and the previous user the "_ref" pointed to does not have their RDVPs updated after the request has completed.: