Here's a list of Critical Updates released by Salesforce that have
potentially impacted your Frisbii configuration. Please check whether this applies to you and follow the instructions if it does.
We'll be updating this article regularly.
Preparing for changes to Apple's privacy statement
In the latest version of iOS, Apple has added further tracking restrictions to third-party apps. These limitations affect the Spring '21 version of the Salesforce mobile app, which is released on February 15, 2021.
These new restrictions may prevent your personalized web content from being displayed in the Salesforce mobile application for iPhone and iPad.
Test the Spring '21 beta version of the Salesforce application before releasing it to your users.
Where: This change applies to the Salesforce for iOS mobile application in all editions, with the exception of Database.com.
Who : the following configurations can be assigned :
Visualforce pages
Third-party content rendered via the drawing area or Lightning components using <iframe>
Third-party applications using cookies, sessionStorage or localStorage
Why: Apple has announced that iOS 14 includes additional restrictions on third-party content. To protect user privacy, cookies and other storage are not available by default for external applications in WKWebView, used to render web content in the Salesforce mobile app (and all other iOS apps).
For more information, see Intelligent Tracking Prevention in WKWebView in the WebKit documentation.
The Salesforce mobile application is updated to the latest Apple standards in the Spring '21 release and these WKWebView restrictions take effect.
How: sign up for the Salesforce mobile beta program at mobilebeta.salesforce.com.
We recommend that you update your third-party integrations to use methods that do not rely on cookies.
For more information on best practices, see this blog post.
We understand that these configuration changes can take time.
In the meantime, your users can authorize the display of third-party content in the Salesforce app by updating their device settings.
To unblock third-party content only for the Salesforce app, on an iOS device, go to Settings | Salesforce, then deactivate Prevent cross-site tracking.
This step does not compromise your privacy in other applications.
Withdrawal of legacy versions of the Lightning Platform API
Where: With the release of Summer '21, the following legacy versions of the Lightning Platform API will be removed and will no longer be supported by Salesforce:
SOAP: 7.0, 8.0, 9.0, 10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0, 19.0, 20.0
REST: v20.0
Bulk data transfer: 16.0, 17.0, 18.0, 19.0, 20.0
* Release date currently scheduled for June 2021, but subject to change.
Customers will be able to continue using these legacy API versions until the Summer '21 release, at which point these legacy versions will no longer be available. When these legacy versions are removed, applications using the impacted API versions will suffer an interruption as requests will fail and result in an error indicating that the requested endpoint has been disabled.
Who: Before the Summer '21 release, customers will need to modify or upgrade their applications to work with the most recent versions of the APIs available, to avoid any disruption caused by software referencing of removed versions. By migrating to the latest versions of our APIs, customers will benefit from advanced capabilities and improved performance and security.
Why: Click here for the full article this link.
How: To identify which applications use APIs that will be removed, contact the developers of the applications you use in your organization to determine these API versions.
If you are unable to contact the developers of your applications, check the event logs that report REST and SOAP API activity in your Salesforce organization as follows:
Use a tool such as the Salesforce CLI to run a SOQL query on the EventLogFile object, which returns a log of all actions performed in your organization over the last 24 hours.
sfdx force:data:soql:query -q "SELECT LogFile, EventType, CreatedDate FROM EventLogFile WHERE EventType IN ('API', 'RestApi')" -u <your-username>
For each result, execute a REST request using the endpoint to obtain the data and copy it to a .CSV file.
For example /services/data/v46.0/sobjects/EventLogFile/0AT3i000005vXpWGAU/LogFile
Copy the body of the response into an application such as Excel to display event log data more easily as a .CSV file.
Examine each .CSV file and determine whether requests are made to endpoints with API versions prior to 20.
EventType SOAP/API -- Examine the values in the API_VERSION column for API_TYPE "E" or "P" records
EventType REST/RestApi -- Examine the values in the URI column and note endpoints with "/v20.0" or lower in the path
All integrations that consume versions 20 and below will be impacted by this API removal.
For more information, follow the Trailhead module Downloading and viewing event log files.
For the Mass Transfer API, go to the "Mass data loading tasks" page in Configuration and view the details of each "Mass Transfer V1" task. All tasks with a value of 20.0 or less in the "API version" field will be affected by this API removal.
Salesforce Platform API versions 21.0 to 30.0
Salesforce has also announced that versions 21 to 30 of the Salesforce Platform API will be removed and unsupported by summer 2022, so it's possible that, among other things, your PDF templates will be affected.
Here is the link to the full article.
Salesforce Release Note: