Update 5:30 pm ET 5/19. Fix Package Available !!!
Skuid has released a set of packages to addresses the issue introduced with the Salesforce Summer 15 patch 5 update. These are:
- Banzai - Update 9 Patch 1
- Rockaway - Point Release 3
This release is available at https://www.skuid.com/skuidreleases
Below are some more details about the issue, our resolution, and answers to some common questions we've gotten over the last 2 days.
On Tuesday May 17 Salesforce implemented patch 5.0 to all Summer 16 Sandbox instances.
Here is their release note documentation: https://success.salesforce.com/issues_releases_view?release=202005000
The release notes indicate that a fix was implemented to this issue: “ Static resources not loading when the critical update for "Serve Static Resources from the Visualforce Domain" is enabled" (https://success.salesforce.com/issues_view?id=a1p300000001ACTAA2) We have been following this issue for a long time because it had affected our customers. However the implementation did not address the defect and introduced additional issues.
The release removed the ability to use relative URLs to access StaticResource files residing in the local namespace from managed-package namespace subdomains of the .visual.force.com domain.
This means that any static resources that you as a customer have uploaded to support your Skuid implementation cannot be accessed from within our managed-package namespace.
- You might directly load a resource called “TestJSResource" in your org (which means it’s in the local namespace),
- A relative link to that resource (defined in skuid as /resource/TestJSResource) will get appended to the skuid subdomain. It will look like:
This link will return a 404 error. An absolute link that does not include the skuid subdomain will continue to work:
Impact: The following items will not work in your Summer 16 sandbox until this is fixed.
- Custom components
- Custom themes and font files
- Images being sourced from static resources
Extent: This patch update has only been added to Summer 16 sandboxes. It affects no production instances yet. You can see the instances where this patch has been applied on the release notes page (first link above)
This issue is not related to our recent Rockaway release. It impacts all versions of Skuid.
Are other vendors impacted by this? We assume the answer is yes, but we have no specific information about other vendors. Skuid is unique in the level of customization that is allowed on top of a managed package. Most packages do not allow users to add their own static resources that are used by the package.
What have we done about the issue.
1. Since this was an issue introduced by the Salesforce release, we are continuing to follow protocol to get it addressed leveraging our partner relationship. There is a case opened which is being escalated by our customers who are impacted by the issue. Thank you for your assistance in this escalation. The case number is 13869100. We will continue to work with Salesforce on this case.
2. Skuid also has taken action directly. We have released a set of packages as of 5:30 pm on 5/19/2016. These are available for Banzai and for Rockaway. You can get these packages at https://www.skuid.com/skuidreleases
Why did Skuid not know about this: Early in a release cycle, Salesforce provides preview sandboxes that we use to ensure Skuid compatibility. Now that the Summer 16 release is well along and has been more widely distributed we no longer had that luxury. Salesforce pushed the patch into all Summer 16 sandbox orgs. Release timelines do not allow for preview staging for every patch. Sandboxes are what this is designed for. We do however recognize that the activities occurring in sandboxes are business critical (like training and development), which is why we are acting with great urgency to address this.
We certainly have a strong relationship with Salesforce. At every level of the company we have gotten assurances that they will respect Skuid and not break our integrations. This is the first time in our history where a change made by Salesforce has had this sort of widespread customer impact. We will certainly be debriefing this issue with connections in Management at Salesforce, and exploring ways to better prevent it in the future.