Hello Team,
Recently we have a customer who reached out stating, in the Email Assist Tasks, attachments with ‘.PDF’ isn’t supported, where as after changing the same file as ‘.pdf’ it supports.
I’ve verified the same behaviour in Local Org as well. https://share.vidyard.com/watch/sBnds3Tm7B7yVCXgXxM4Cv?
Customer ask :: When the file is a valid one and why isn’t out application recocngizing, as .pdf, it seems like most modern applications should be able to handle .PDF as well as .pdf.
Could this be something that will be added in the future, or will this be considred as a limitation?
Thank you!
Customer in question here! The specific ask is for .PDF to be recognized like .pdf is, but that should be true for any file type. If the file can be open and run, it should matter if it is .PdF or .PDF or .pdf or whatever the extension is. Again, this obviously would be for valid files.
If it isn’t possible, I would ask that at minimum the documentation explicitly calls out that something like .CSV or .PDF will fail, even if those file “types” are supported. Actually, it would be great if the documentation is updated to make that clear until this is changed.
Hello@bradley
We have fixed this in our upcoming new component called Email from anywhere. As suggested until we release this new component we will add this in documentation.
Hello@bradley
We have fixed this in our upcoming new component called Email from anywhere. As suggested until we release this new component we will add this in documentation.
Awesome, thank you!