Happy New Year Everyone. And god bless to them who had hardcoded 2017 in there code. Salesforce has just release Spring 18 and this time also the main focus remains n Einstein and Lightning. In this release there are many good feature are introduced. So let’s take a quick look at them.
- Gather Feedback with Salesforce Surveys (Generally Available)
Salesforce now has introduced Surveys. Create beautiful, easy-to-use forms for collecting feedback and data from your users or customers. Add different types of questions to gather the data you need. All your valuable survey data is stored in your org, so you can harness the power of Salesforce to view data, create reports and dashboards, and share insights with your company.
- Enable the New URL Format for Lightning Experience and the Salesforce
Salesforce is changing the URL format used by Lightning Experience standard apps and the Salesforce mobile app. The new URL format is more readable and addresses the issue of being directed to an unexpected location when accessing Lightning Experience URLs before authenticating. This update doesn’t apply to console apps and communities.
- Current format: https://<lightning.domain.com>/one/one.app/#/sObject/Account/home
- New format: https://<lightning.domain.com>/lightning/o/Account/home
Custom or installed Lightning components that parse a URL may break or behave differently after this change, especially components with logic that relies on window.location or the aura:locationChange event.
Einstein Opportunity Scoring: Artificial Intelligence for Opportunities (Generally Available)
Salesforce has expanded the Sales Cloud Einstein product suite with Einstein Opportunity Scoring. Now we can prioritize our way to more business. This feature is new in Lightning Experience and Salesforce Classic.
Einstein Forecasting: Intelligent Predictions About our Sales Teams (Beta)
Let Einstein take the guesswork out of forecasting. Use artificial intelligence to get more certainty and visibility into how your sales teams are doing. This feature is new in both Lightning Experience and Salesforce Classic.
Einstein Lead Scoring: Clearer Predictive Factors and Detection of Rank and Department
Get a clearer view of the reasons behind each score. And see better scores with rank and department information. These changes apply to both Lightning Experience and Salesforce Classic.
Einstein Insights: Access Account and Opportunity Insights from Your Mobile Device (Pilot)
Einstein Insights are now. See predictions about which deals are likely to be won, reminders to follow up, and notifications when key moments in a deal take place. Reps can take action directly from the insights, including editing the related record or sending emails to relevant contacts. This change applies to Salesforce for iOS and Salesforce for Android.
Einstein Platform Services APIs
Use the Einstein Platform Services APIs to easily AI-enable your apps with image recognition and natural language processing. Using the Einstein Vision APIs, you can leverage pre-trained classifiers or train your own custom classifiers to solve a vast array of specialized image recognition use cases. With the Einstein Language APIs, you can harness the power of natural language processing to analyze text and infer the sentiment or intent behind that text. Make your apps smarter, and look like a genius at the same time.
- Stay on Top of Duplicate Records by Using Duplicate Jobs PERMISSIONS
Good clean data builds the trust of your sales team. It also helps you work toward complying with various data protection and privacy regulations. So you’ve got everything to gain by getting a global view of duplicate records. Use duplicate jobs with standard or custom matching rules to scan your Salesforce business or person accounts, contacts, or leads for duplicates. Share job results with others and merge the duplicates—all within Salesforce. Use information about duplicate jobs we’ve run to track the progress in reducing duplicate records. This feature is new in Lightning Experience.
- Salesforce IoT: IoT REST API, New Context UI, IoT Usage Monitoring, and Email Alerts
Use Salesforce IoT Explorer Edition to process events from connected devices in near real time and create meaningful interactions with your customers. Explorer offers built-in integration with Salesforce data and lets you leverage your Customer Relationship Management (CRM) investments in Salesforce. This release includes a new IoT REST API to retrieve and manipulate orchestrations and their related components, and a new user interface for contexts. Also, Salesforce is introducing an IoT usage monitoring page, email alerts, and the ability to export and delete IoT data for data privacy.
- Use without sharing for @AuraEnabled Apex Controllers with Implicit Sharing (Critical Update)
This critical update changes the behavior of @AuraEnabled Apex controllers that don’t specify with sharing or without sharing to default to without sharing. This change relaxes the security for controllers that don’t explicitly set sharing behavior using these keywords. It’s a best practice to always use with sharing in Apex controllers used with Lightning components.
- Find Dynamically Created Components
We can now use cmp.find() to find a component that we have create dynamically with $A.createComponent().
- Remove Instance Names from URLs for Visualforce, Community Builder, Site.com Studio, and Content Files (Critical Update)
Salesforce is stabilizing the hostname of Visualforce, Community Builder, Site.com Studio, and content file URLs by removing instance names from URLs. This critical update applies to orgs that have a deployed My Domain. It will be activated automatically on March 16, 2019.
Prior to Winter ’18, Visualforce, Community Builder, Site.com Studio, and content file URLs included the instance name of the org, even when a My Domain name was deployed. An instance name identifies where your Salesforce org is hosted. When Salesforce remove the instance name from our URLs, hostnames change.
Here are two examples:
- mydomain–c.visualforce.com replaces mydomain–c.na1.visual.force.com
- mydomain–c.documentforce.com replaces mydomain–c.na1.content.force.com
Note: All *.content.force.com URLs will be replaced with *.documentforce.com.
- Employ Validation Rule Formulas with Custom Metadata Types
If we use validation rules, you know how helpful they can be, but you have to hard code some of the values. Now you can store values you previously had to hard code in custom metadata types and reference them in your validation rules.
Example: Use a validation rule formula to limit discounts on certain brands to 10%. You can use validation rules without custom metadata. However, to change an amount, you must update the hardcoded value. If you have multiple validation rules that check the discount amount, you have to manage all of them. Instead, use a validation rule formula with custom metadata types.
- Create a custom metadata type. In this example, we named it DiscountLimits.
- Create a custom field for your type. We named it maxDiscount.
- Create a record. We named it FoodDiscount.
When done, you can reference the custom metadata type in your validation rule. The syntax is:
Make sure to use the correct suffixes. For the custom metadata type, use __mdt. For fields, use __c. Records require no suffix.
Your validation rule for this example looks something like this:
Discount > $CustomMetadata.DiscountLimits__mdt.FoodDiscount.maxDiscount__c
- In Spring 18 Salesforce added two new methods in list class. They are
Returns true if the list contains the specified element.
Returns the index of the first occurrence of the specified element in this list. If this list does not contain the element, returns -1.
So now we no longer dependent on set to check for duplicate key at the same time we can maintain order as well.
- Collect Debug Logs for Guest Users Without Setting Cookies
In Winter ’17, Salesforce introduced a change that required guest users to set browser cookies to activate debug logging. people didn’t like the Winter ’17 change. Setting cookies is complicated, and the change made collecting debug logs for public users’ asynchronous activity impossible. Now public users no longer need a debug_logs browser cookie to trigger logging. This change applies to both Lightning Experience and Salesforce Classic.
- Avoid Huge Debug Logs for Managed Package Code
Debug logs no longer include ENTERING_MANAGED_PKG events when your log level for the Apex Code category is INFO or DEBUG. To log ENTERING_MANAGED_PKG events, set your Apex Code log level to FINE, FINER, or FINEST.