Known Issues · Summer 16
In Review ·Reported By 59 ·Updated 6 days ago
When a Lightning Page contains both a Custom Lightning Component AND a Custom Visualforce Component, users without the "View Setup and Configuration" system permission may be unable to access the page.
In Review ·Reported By 45 ·Updated 10 days ago
In Review ·Reported By 6 ·Updated 26 days ago
When using a custom "Log a Call" Quick Action on Cases, the "[Person] logged a call" Feed Item is not generated if a Process Builder flow updates the generated task. When saving, you will notice that you receive a message that lets you know it was successful, the Chatter Feed refreshes and the Feed...
In Review ·Reported By 22 ·Updated 2018-07-17
Trial org created through a template will have incorrect FLS settings if FLS and page layout settings are different
In Review ·Reported By 4 ·Updated 2018-07-10
For some organizations the Sharing Criteria rules list when adding components to a change set will display duplicates. This can cause the error "Package member already exists" if both items attempt to be added to the change set.
In Review ·Reported By 57 ·Updated 2018-06-25
When the URL decoded value of startURL contains a relative path with white spaces before the first existing question mark, "Bad_Start_Url, startURL was not a relative path or contained invalid characters" is thrown when redirected to the auth provider servlet.
In Review ·Reported By 3 ·Updated 2018-06-11
When using a SOSL query that uses an OFFSET clause in Apex, the results are ordered by ID. The same query run via the API (for instance from the Query Editor view in the Developer Console) will return the results sorted by relevance.
Fixed - Summer '18 Patch 5.0 ·Reported By 23 ·Updated 2018-06-09
Since Summer'16, the following code in Lightning Component doesn't work expectedly. The "v.date1" is defined as Date type and is expected to be cleared as well as Spring'16. ----- component.set("v.date1", ""); -----
In Review ·Reported By 4 ·Updated 2018-05-30
Edits to User records that trigger a rounding or padding operation on Geolocation custom fields could fail to trigger flows.
No Fix ·Reported By 12 ·Updated 2018-05-23
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.