Problems and solutions

See solutions for some of the common problems.

How to exclude URL from URL Protection

Issue
When URL Protection is enabled in WithSecure Cloud Protection for Salesforce, links in emails sent internally and externally have their URL syntax replaced, which may break certain links.
How to allow those URLs pass without entirely disabling URL Protection capability

Resolution
Follow these steps to exclude a URL:

  1. Login to Cloud Protection and go to Administration
  2. Under URL Protection Settings, scroll down until the section Exclusion
  3. Enable Exclude trusted domains,hosts and URLS (if it is disabled) and click on Open the list of trusted domains, hosts, and URLs…
  4. Add the URL you wish to be excluded to the list (make sure it is ticked)
  5. Click Save

Is the assignment of permission set as well as licenses needed for the solution to work properly?

Issue
Is the assignment of permission set as well as licenses needed for WithSecure Cloud Protection for Salesforce to work properly?

Resolution
You need to assign the permission set as well as licenses for WithSecure Cloud Protection for Salesforce to work properly.
If the permission set is not assigned, the user may fail to upload or download files.
If the license is not assigned, then files uploaded or downloaded by the user will not be scanned.

Error output of “System.LimitException: AFSC:Too many queueable jobs added to the queue: 2 (AFSC)”

Issue
I noticed that the following error message is output when a queueable job that adds date field values to related cases on “Case Status Update” is triggered.
This job always starts a new job in the queueable context. Somehow, F-Secure Cloud Protection for Salesforce starts another job in the same context, which leads to the error message.

Error message:
FATAL_ERROR|System.LimitException: AFSC:Too many queueable jobs added to the queue: 2 (AFSC)

Resolution
If you are using an older version of F-Secure Cloud Protection for Salesforce, proceed to upgrade the application to the latest version and check if there is any improvement.

If the issue persists, proceed to report the issue by contacting WithSecure Support. In order for us to collect the debug logs and investigate the issue further at our end, you need to:

  • Allow us the remote login access to your Salesforce organization
  • Provide us with detail instructions on how to reproduce the issue

Calling a Future Method from a Future Method

Issue
WithSecure is using Future Method to run scans and clashes with custom scripts that also uses Future Method. Any suggestions on how to resolve this?

Resolution
By default Cloud Protection for SalesForce uses Queueable Jobs for invoking email attachment scan. However if Future Method was called, this means that the limits of Queueable jobs has been reached so WithSecure App switches to using Future Method instead. It is not possible to call Future Method from a Future Method as they are asynchronous.

We suggest to use the Queueable interface instead of a Future Method for custom scripts. The Queueable interface allows chain jobs, meaning WithSecure job could be started without the system exception from custom jobs.