On the receiving end, they should be able to change the ContentTranfers.store property after the transfer is charged, which would trigger a move on the hub side. This would effectively do the same thing the ContentItem.move() function does, but it would utilize the ContentStore API providing more consistency.
On the receiving end, they should be able to change the ContentTranfers .store property after the transfer is charged, which would trigger a move on the hub side. This would effectively do the same thing the ContentItem.move() function does, but it would utilize the ContentStore API providing more consistency.