Here in this post, we will tell you about the forthcoming new URL format of the Salesforce Lightning experience and the Salesforce mobile. In the previous time, there had been chances that you had to face in the earlier time about the URLs. As the pre-eminent Salesforce consulting companies in USA, we will give you an insight of entirely new formatting of Lightning URL.
At the time of Spring 2018, we are also giving the Critical Update Console (CRUC) setting that eventually guides you to test entirely new URL format. Before the coming of summer’2018, the URL format will also be authorized for each of the customers. For returning to the old format, you will then have to log the case with the best Support team of Salesforce to put it off.
Even the new Salesforce customer orgs made at the time of spring’18 will be resorting to this entirely new URL format just by default, and there will also be the requirement of logging the case with Salesforce just for the CRUC setting for making it accessible with ease. Well, the Salesforce does not officially support our UI URLs. It is simple to alter or replace the Salesforce UI URLs as and when required. Unlike SOAP endpoints, UI URLs are also not formally supported.
Let’s check out the dissimilarity in both:
Specimen of the new URLs:
Actual format: Account Home URL
Recently developed format: Account Home URL
Actual format: Account Record View
Currently developed format: Account Record View
Factors to consider for this alteration:
The top-rated Salesforce CPQ service provider, we have listed the essential elements about this lightning change-
Parse of the URL:
It is also possible that logic which parses complete URLs will generally break except if it is only the pattern that complements on, for instance, 15 or 18 characters object IDs. Every personalizes or installed Lightning elements that parse a URL will have the ability to break or act very differently after entire alteration, especially the parts with a logic that also depends on window.location or the aura:locationChange event. We also provide the Salesforce field services that you can select as per your preferences.
Adding frameworks in URL:
When you have some query string frameworks added to the actual URL then they will also be revised separately when moved into the browser. For example: /one/one.app?myparam1=xyz&myparam2=abc will then be revised as /lightning?0.myparam1=xyz&0.myparam2=abc.
Regrettably aura:locationChange event is only discharged when the hash part of the complete URL alters. As there is no such URL hash in a recently developed URL format, then you will not find any events firing. Safe Harbor: We will also move through a distinct perspective for discovering the URL changes.
Factors that will not be influenced by this alteration:
The filter reports by the URL frameworks in Lightning experience will perform in the same way as the Reports functionality supports it. You can also find the details in Spring’17 Release Notes
Communities URLs will not affect it through the alteration for the Spring release.
The console URLs will not exert influence on this alteration for the Spring release. The Console team includes more upgrades come Summer’18.
#4 Saved URLs:
The current URLs will function for the predictable future. All the links that you save or include in the emails will be interpreted in the advanced URL format at the moment you execute the same. When there is upgraded URL format authorized for your org, that entire format is something that you can view in browser address bar.
The advanced URL format for Lightning will be eventually advantageous for the customers. It is advised to validate this critical update in a Sandbox first for testing it and then, later on, make obligatory adjustments before the currently developed URLs goes live for all.