We are continuing our dialogue with Salesforce’s Apex product team around the performance differences that are being seen across the various “org shapes”, but as yet there hasn’t been any verified cause.
At the time of writing we are seeing patch level at Summer ‘18 15.1.
As mentioned last month, we already preparing for the Winter ‘19 release, and expect this to arrive into pre-release orgs in the second week of August with the first sandboxes being updated on the 8th Sept.
Occasionally there are critical updates (CRUCs) released by Salesforce that may impact the running of MobileCaddy applications. When these are seen we request that partners do not activate them prior to them being “green lighted” by us.
There is currently 1 critical updates of note, that we request are not activated until they’ve been through our QA processes.
- Remove Instance Names from URLs for Visualforce, Community Builder, Site.com Studio, and Content Files
More information can be found in the Spring ‘18 release notes.
Instance Refreshes and Org Migrations
From time-to-time, Salesforce undertakes a maintenance operation called an Instance Refresh. This is performed for various reason, but primarily to maintain good performance. As part of this your org may be moved to a new data center (note this is not an “Org Migration” – yes, silly naming, we know). More information on this, and steps that might be needed, can be found in this Salesforce Help Document.
* Correct at time of writing.
- Aug 18th – EU11 (Instance refresh)
- Oct 21st – NA3, NA6, NA30, NA31
- Aug 5th – NA29, NA32, NA37
- Sept 15th – EU6
- Sept 16th – EU1