How does FinDock manage Salesforce release compatibility?
As FinDock integrates more with core Salesforce objects and features, such as the Salesforce Fundraising feature, each Salesforce release introduces new opportunities for customers.
We start working on Salesforce release compatibility as soon as we have the details and development environments. Since FinDock uses a higher release frequency than Salesforce, we always have a new release coming relatively soon after a new Salesforce release becomes generally available.
This means in practice that you can plan on having new Salesforce capabilities available to you with FinDock:
- In FinDock sandbox around 2 weeks after the Salesforce release is available
- In FinDock production around 6 weeks after the Salesforce release is available
Our production updates come later for a couple of reasons. Firstly, we want to ensure all customers get a full four weeks of testing. Secondly, we have Salesforce rollout timelines to accommodate. Salesforce releases reach FinDock and customer orgs at different times, so we need to be sure everyone is on the latest Salesforce release before pushing our updates.
When a release includes Salesforce release compatibility changes, we include the compatibility update in our regular release notes. Changes typically involve Salesforce API versions which we update for a couple of reasons:
- An API version is updated because it is required to use new Salesforce objects, fields or other new features.
- An API version is updated because the version FinDock was using is deprecated, retired or otherwise determined to be a required change by Salesforce, e.g. due to a bug or security issue.
Please note that Salesforce maintains support for many versions of their platform APIs at any given time. Older version that are still supported may, however, be flagged in security reviews. This is expected and does not indicate the API version is a security risk.