F-Secure for Salesforce - unable to upload a file after iterative configuration
Good afternoon, I'm experiencing some concerning behavior after installing the F-secure module.
Initially installed the F-Secure packaged application.
Performed simple configuration - blocking specific file types.
This was successful - prohibited file types were successfully blocked and displayed in the "Summary - Analytics" tab.
After making further configuration changes related to notification settings - added email address for "Send From" and "Send to"- the Salesforce-wide file upload functionality stopped working across the org.
I am receiving the following error in the file upload dialog box: "Can't upload Test file.docx."
That message is followed by a Salesforce banner message "Can't upload 1 file."
I have turned off all Fsecure settings and am still unable to upload a file. I receive the same 2 error messages above.
I am able to successfully upload the same Test file.docx file to another Salesforce org where Fsecure is not installed.
There are no additional logs in the Fsecure console of blocking activities (before or after disabling the Fsecure protection settings).
Thanks @HRuusinen - look forward to syncing with you and team today.
Thanks @Dmitriy - we did revert the notification settings, and turned off all f-secure protections to see if we could remediate the issue. WE did not reset the full config b/c we are concerned by the state we are in and need to be 100% sure we know what happened, how it was caused, how to avoid it and how to remediate it if does ever happen again. Reverting the state or uninstalling / reinstalling the package could impact our ability to do that. Definitely appreciate the suggestion, just trying to be methodical in our troubleshooting.
@HRuusinen - Thank you very much for the hands-on keyboard debugging and troubleshooting session this morning. Appreciate your time and obvious expertise in F-secure operation in our environment - as well as Salesforce in general.
Your support for our challenge was fast, professional and WELL BEYOND expectations, Thank you.
For the rest of the community - this was NOT an F-secure problem, but rather a "request limit" associated with our Salesforce org.
Harri helped troubleshoot this end to end through document upload validation across several use cases and Salesforce objects.
Looking forward to getting our Salesforce service limits lifted and moving to production with F-secure protections! Thanks again team.7 2Like
Thanks @DanMellen we are always happy to help. Really great that we found the issue and you can go to the production soon.10 Like
I replied to your email message and I will schedule a meeting with you that we can solve the problem immediately.
Configuring the sender address shouldn’t cause any issues but make sure that you have verified the address that Salesforce can use it. I would like to see what kind of triggers (ContentVersion/ContentDocument/Attachment/email) you have in your Salesforce org.1 1Like