In other backends, the return value is the list of childIds that had the relation applied to them associating them to the parentId of the relation. In alfresco, that list only contains the parent id. This is causing branching behavior in ACA where those Ids are added to a success or error list to be further processed.
AlfrescoEmbContentImpl#doAddRelation should be updated to match other logic and places that use the addRealtion endpoint should be updated/notified of that change to confirm their behavior remains as expected. Thankfully, to my knowledge, all the many places this method is used, the code that calls this function does not perform any logic on the returned object other than check if any object to throw an error is false. Most places do not pass this object outside of OC but in the instances it is ACA does not perform any logic on this value. I checked all 25 instances. This only affects the implementation of #2320.
Issue
In other backends, the return value is the list of childIds that had the relation applied to them associating them to the parentId of the relation. In alfresco, that list only contains the parent id. This is causing branching behavior in ACA where those Ids are added to a success or error list to be further processed.
AlfrescoEmbContentImpl#doAddRelation
should be updated to match other logic and places that use the addRealtion endpoint should be updated/notified of that change to confirm their behavior remains as expected. Thankfully, to my knowledge, all the many places this method is used, the code that calls this function does not perform any logic on the returned object other than check if any object to throw an error is false. Most places do not pass this object outside of OC but in the instances it is ACA does not perform any logic on this value. I checked all 25 instances. This only affects the implementation of #2320.