Hello team,
CONTEXT: During the process lifecycle, we want to use blob storage for long-term storage of files that have been stored for a long time in Appian. If users want to access these old files, appian will have to make a GET request to blob storage to retrieve this file and persist it for eventual viewing or download.
I'm trying to send a file to a container in Azure blob storage through an API with a PUT method and I'm facing some problems.
I tested via postman, the same endpoint, with the same settings (headers and query parameters), choosing the binary format for the payload, and uploading the file. I sent the file to the blob storage and called the Get request in Appian to retrieve it. I was able to access the file perfectly in Appian.
When I tried the same thing in Appian, the following situations occurred:
1. When I selected the Content-Type: Document (auto-detect) option, the API returned a status of 403 - Forbidden.
2. When I selected the custom option, specifying the file format (application/pdf), it returned a status of 201 (Created successfully). However, when I requested this same document through the GET endpoint, and after persisting it in Appian, it was somehow corrupted. I can't access it, and when I open the file I get the error: We can't open this file. Something went wrong.
Could someone please help me with this scenario?
Discussion posts and replies are publicly visible
Can you share the config of your integration?
I contacted the API team and found out that it was a restriction on their side. Thank you, Stefan.