Known Issues · Summer 18
Some customers have observed that after post upgrade to Summer '18, it takes longer when an admin attempts to access/edit/view an outbound change set. This behavior was observed with change sets that contain Flow's whose components have several elements.
In Review ·Reported By 11 ·Updated Yesterday
When using lightning:input component with variant=label-hidden as required, asterisk is not visible in UI. This is seen in summer '18 release. This issue is seen because the class="slds-assistive-text" hides the entire label. This issue is also seen for inline edit for required fields.
In Review ·Reported By 2 ·Updated Yesterday
Seeing Blob exceptions when some attachments are in related lists. The attachments get corrupted in the sandboxes. There can be inconsistencies due to the records being copied during different stages of the copy. Note: This is issue os seen only on Sandboxes.
In Review ·Reported By 1 ·Updated 2 days ago
"Send notification email to contact" checkbox displays on case edit page in Lightning regardless if the option is checked or not in Layout Properties in Page Layout.
Scheduled - Spring '19 ·Reported By 20 ·Updated 4 days ago
Some customers may notice that the feature mentioned in the Release notes here https://releasenotes.docs.salesforce.com/en-us/summer18/release-notes/rn_collab_slash_records.htm is not available for them to use
In Review ·Reported By 14 ·Updated 4 days ago
Activity Related To (WhatId) field not pre-populated on NEW from Related List when the detail page is overridden by VF in LEX. Activity Related To (WhatId) field not pre-populated
Scheduled - Spring '19 ·Reported By 2 ·Updated 5 days ago
When a lightning:inputField component sets the attribute disabled=true, the input should become Read Only. However, when the lightning:inputField refers to a Lookup field, it does not become read only and can be edited even if it is disabled.
In Review ·Reported By 44 ·Updated 6 days ago
In Summer'18, lightning:input used with session storage throws Assertion Failed!: Provider type not supported : false
In Review ·Reported By 6 ·Updated 6 days ago
Suppose you have a workflow rule with criteria set to Created and Edited to Subsequently Meet Criteria. In this situation, a record initially meets the workflow rule and fires (as expected). If you do not change the value of the field used in the workflow criteria, you are not editing the record to 'subsequently'...
In Review ·Reported By 7 ·Updated 7 days ago
After Editing an Active Survey’s question responses, the changes get reflected in Survey Runtime. However, the Survey Question Choices related list on Survey Question records does not get updates to reflect the new values.
No Fix ·Reported By 1 ·Updated 7 days ago
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.