27 Jun Salesforce Summer ‘18 Release from the viewpoint of the Admin/Developer
Summer is in full swing now and this can only mean one thing – we are presenting yet more novelties from the Salesforce Summer ‘18 Release! This time we will have a closer look at some improvements that will surely be interesting to all Salesforce developers.
Option to create External Services is generally available now
External services might become a perfect extension of the basic Salesforce functionality, thanks to which processes will be optimised for ordinary users of this platform. The option of calling the methods of an external service through Salesforce Flow makes it possible to import the required data quickly. An example here is the connection with the credit service in order to determine the payment terms that can be proposed to a given customer.
Logging in without a password
From now on, Salesforce Community provides the option of convenient logging in using a verification code. This way Community members, customers or other external users can get access to the platform with the code sent by e-mail or text message.
Shorter validity of verification links
No more endless greetings! E-mail verification links with a shorter validity make the platform securer. So, Salesforce offers the possibility to configure links to expire after 1, 7 (default) or 180 days. Remember that the default link validity was as many as six months before!
Visual Flow improvements
You can have up to five active Flows in the Essentials and Professional versions. The latest Salesforce Release presents such improvements as:
Capturing Date/Time values in Flow Screens
There is a new type of field: Date/Time in Cloud Flow Designer, used for example for planning events or meetings.
Flow debugging in Cloud Flow Designer
Cloud Flow Designer offers also a debugging option to increase testing and error spotting effectiveness. Now, it will be possible to set the values of input variables, restart Flow quickly, and track the details of what is going on in real time during Flow execution.
E-mails with process error notification
When the process or Flow execution fails, Salesforce sends a message with an appropriate error notification and details of specific elements, containing the ID and name of the organisation where a given error has occurred. This facilitates identification of the right organisation in order to repair the error if you manage many of them.
Monitoring the transaction limits generated by Flow and processes
Processes and Flow can perform powerful operations, which are most often included in transaction limits. Now it will be possible to track these actions in logs to determine which operations contribute to exceeding the limits. Such details help eliminate or prevent errors resulting from, for example, too many SOQL queries being generated or a given operation taking too much time.
● FLOW_START_INTERVIEW_LIMIT_USAGE – Covers the scope to which the limit is used by the transaction during the process or Flow is started but before it is executed. It also covers the limit for each transaction.
● FLOW_ELEMENT_LIMIT_USAGE – Shows how much limit is used by the process or Flow, the total number used by a transaction after Flow and the transaction limit.
● FLOW_BULK_ELEMENT_LIMIT_USAGE – Covers the limit used by Flow executed collectively, the total number used by the transaction after its completion and the transaction limit.
More efficient grouping of Scheduled Actions and Flow Interviews
In this release, Salesforce introduced a solution to the reported Known Issue. Earlier, when performing scheduled actions, Salesforce used to group them irregularly. Processes initiated by different users and containing different versions of processes or Flow could be performed together. This made it difficult to design Flow such that its execution would not exceed the applicable transaction limits. The solution consists in standardising the grouping method of the scheduled actions. Actions with the same execution time, the same process or Flow version ID, and initiated by the same user are executed together.
Controlling the debugging mode of Lightning Components
Apex Switch Statement
One of the most awaited instructions has finally appeared in the Apex code! The switch will make it possible to check if a given expression is equal to one of many options and to split further logic based on that. The switch computes the expression and then executes a code block corresponding to the result. If none of the defined values is compliant with the result, a default code block is made or, if there is none, no action will be taken.
Custom Metadata Type Records accessible from the Validation Rule level
From now on, it will be possible to directly refer to Custom Metadata Type Records in a Validation Rule with the use of $CustomMetadata global variable. Thanks to that, adding the same values to every rule separately will be avoided. The possibility to refer to Custom Metadata Type is also an improvement for subscribers. Earlier, after adding a Validation Rule to the managed package, it was impossible for the subscriber to edit it. Now, if the logic is defined well, also personalisation will be possible. Access to fields can be obtained through $CustomMetadata.type.record.field syntax.
Increased Debug Log size limit
Salesforce increased the debug log size limit from 2MB to 5MB and it will be possible to store up to 250MB at the same time. However, it also needs to be noted that Salesforce Summer ‘18 Release will change the storage duration of system logs and so they will be automatically deleted after 24 hours instead of 7 days. The storage duration of monitoring logs will remain the same for now.
We have already got used to Salesforce introducing a range of improvements for users with its every release. These are largely features proposed by Salesforce Community. This way, we – users – have an actual influence on the development of the platform, which is a rare phenomenon and it should be appreciated. Salesforce Summer ‘18 Release is yet another huge step forward, which lets the company leave its competitors further and further behind.