Using a lightning email template in a lightning component to send an email in Summer '18 Sandbox we see the Email has
Subject preceded by ENCODED_TEMPLATE:ENCODED:
and the first line of the body set to ENCODED_TEMPLATE:ENCODED:
The Template works fine when the email is sent manually (no such additional text).
The email is sent OK in both cases and the activity and Email object are created OK in Salesforce, but the email sent by the Lightning component has the above additional text - any ideas what might cause this?

This critical update breaks visualforce pages rendered as PDF that are hyperlink formulas visible in portals or web pages that are rendered in a different domain than the SF org - as the URL references are no longer valid -does anyone know of a work around?

We are able to use an Anchor within a Visualforce page OK, but when we use the anchor from a URL associated with a button on a standard object page - such as Case - the Anchor is not used, the page is always displayed from the top. This only seems to happen with new orgs, older ones correctly handle the Anchor either way.

Salesforce supports replacing the standard Social.InboundSocialPostHandler with a custom apex class to provide custom handling of social media posts sent from Social Studio. Unfortunately although Salesforce provides the source code for Social.InboundSocialPostHandler as a starting point for customization, they do not provide links to the associated test class in the documentation, without which any code cannot be deployed to production due to insufficient test coverage. Can anyone provide a test class for the standard Social.InboundSocialPostHandler?

 

Using a lightning email template in a lightning component to send an email in Summer '18 Sandbox we see the Email has
Subject preceded by ENCODED_TEMPLATE:ENCODED:
and the first line of the body set to ENCODED_TEMPLATE:ENCODED:
The Template works fine when the email is sent manually (no such additional text).
The email is sent OK in both cases and the activity and Email object are created OK in Salesforce, but the email sent by the Lightning component has the above additional text - any ideas what might cause this?

We are able to use an Anchor within a Visualforce page OK, but when we use the anchor from a URL associated with a button on a standard object page - such as Case - the Anchor is not used, the page is always displayed from the top. This only seems to happen with new orgs, older ones correctly handle the Anchor either way.