How to publish a HTTP endpoint returning a File efficiently?
I managed to create a http endpoint returning a file by: -instantiating an instance called FD of the custom file document type generalized from type System.FileDocument. -loading contents from an already stored file called SF from disk into FD. -returning the FD from microflow which is called by REST endpoint. ------------- The problem is that a copy of the SF is created in folder deployment\data\files every time the REST endpoint is called and this copy is not deleted. This is causing a huge disk usage. Is there a way to prevent this unintended copy behavior when publishing such a http endpoint that returns a file?