Summer19 – Nerd @ Work

Our week’s trailblazer is Claudio Marzorati, who will be listing some of his favorite Summer’19 Salesforce platform release.

Claudio is a Senior Salesforce Developer @ Sintegra s.r.l. (Milan). He worked with different retails that allowed him to increase his technical background on several aspects.
From analysis, to development, to the direct relationship with the customer, nothing is left to chance.
Other passions are running and travels!

Summer 19′ hass finally arrived and in our org all changes are going to be applied.

Here I summarize some of the most important features that can impact your org.

Lightning URL parameters have been namespaced

Finally they have been release the funtiality that forces URL parameters to be namespaced.
So if you add ?foo=bar to the URL, it will get auto-stripped.
But if you add ?c__foo=bar to the URL, it will persist.

Keep Record Context When Switching from Salesforce Classic to Lightning Experience

When you switch from Salesforce Classic to Lightning Experience, you land on the same page in Lightning Experience, if it exists. If the same page doesn’t exist in Lightning Experience, you are redirected to your default landing page, which is determined by the org default or your customizations.

Choose from Two Record View Options

Now you have two record page view default options. Choose between the current view—now called Grouped view—and the new Full view. In Setup, enter Record Page Settings in the Quick Find box, and select Record Page Settings.

Full view (1) displays all details and related lists on the same page. Grouped view (2), the original Lightning Experience record view, focuses on specifics by grouping information across tabs and columns.

Search Picklist Fields in List Views

You don’t have to manually pick through your list views to find the picklist values you’re looking for. List view search now includes picklists in your query results. Dependent picklists and picklists with translated values aren’t searchable.

Continuation

Finally we can use the Continuation pattern from an Aura component or a Lightning web component. Continuation class
in Apex are used to make a long-running request to an external web service Process the response in a callback method. An asynchronous callout made with a continuation doesn’t count toward the Apex limit of 10 synchronous requests that last longer than five seconds. Therefore, you can make more long-running callouts and integrate your component with a complex back-end API. In Lightning-Web-Component now we can use
@salesforce/apexContinuation in order to provides access to an Apex method that use the Continuation.

Aura Components

There a lot of improvements expecially in LWC and below I report the most used in my develop.

lightning:recordEditForm

– density option

Sets the arrangement style of fields and labels in the form. Accepted values are compact, comfy, and auto. The default is auto, which lets the component dynamically set the density according to the user’s Display Density setting and the width of the form.

– onerror handler event changed

You can now return the error details when a required field is missing using event.getParam("output").fieldErrors. To display the error message automatically on the form, include lightning:messages immediately before or after the lightning:inputField components.

lightning:inputField

– reset function added

Resets the form fields to their initial values.

There are few deprecated component in force and ui: force:recordEdit, force:recordView, ui:input (all types), ui:button, ui:menu (all types), ui:output (all types), ui:spinner.

Web Component

Salesforce is spending a lot of time and resources in improving this new components. There are a lot of new functionalities added and below I report the most significant.

lightning-input

– autocomplete function added

Controls autofilling of the field. This attribute is supported for email, search, tel, text, and url input types.

– date-style (or time-style) function added

The display style of the date when type='date/time' or type='datetime'. Valid values are short, medium, and long. The default value is medium. The format of each style is specific to the locale. This attribute has no effect on mobile devices.

lightning-input-field

– reset function added

Resets the form fields to their initial values.

lightning-record-edit-form