Issues using HTTP file download Smart service

Hello friend, 

                    I use the HTTP file download smart service to download files to the Appian folder from an endpoint. Now the problem is the files downloaded to Appian folder are not seen to have any extension (.pdf, .doc) sometimes. With no extension, the files aren't recognized by Appian and they're not found in related process models that try to retrieve them. Any one has a clue what is going wrong here? 

 

Thanks, 

Nick  

  Discussion posts and replies are publicly visible

Parents
  • Hi Nick,

    I guess there are some restrictions set in admin console to allow specific type of files into Appian system. Please access the site admin page - /suite/admin/page/file-upload and check.

    Hope this helps.

    Thanks
  • Hi Naveen,
    Thanks for the reply, currently I am able to get the file downloaded to Appian (documents) folder. But the thing is it's not displaying it's file extension type (preferably .doc & .pdf). So my question was generally when you use the HTTP download/Upload smart services what things might corrupt the files transferred.

    Thanks,
    Nick
  • Hi NIck,

    Thanks for the clarification. So, I understand that the file is able to download into the Appian folder but the file extension is missing. And Sorry, I'm not quite sure why the file is getting corrupted and chances of corruption. You may try debugging the issue in the following steps.

    1. Can you try downloading the file from Appian folder and check whether it is keeping the file format as expected?
    2. Can you double check whether file retains the file format at the source location before it is pulling into Appian via this plugin?
    3. If above both are positive then we may need to doubt the plugin functionality.

    Good luck, Thanks
Reply
  • Hi NIck,

    Thanks for the clarification. So, I understand that the file is able to download into the Appian folder but the file extension is missing. And Sorry, I'm not quite sure why the file is getting corrupted and chances of corruption. You may try debugging the issue in the following steps.

    1. Can you try downloading the file from Appian folder and check whether it is keeping the file format as expected?
    2. Can you double check whether file retains the file format at the source location before it is pulling into Appian via this plugin?
    3. If above both are positive then we may need to doubt the plugin functionality.

    Good luck, Thanks
Children