Salesforce Spring 18: Quick Preview

Salesforce Spring 18: Quick Preview

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.

spring-18-logo-268x300
Spring 18
  1. 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.

  1. 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.

For example:

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.

  1. Einstein

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.

  1. 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.

  1. 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.

  1. 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.

  1. Find Dynamically Created Components

We can now use cmp.find() to find a component that we have create dynamically with $A.createComponent().

  1. 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.

  1. 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.

  1. Create a custom metadata type. In this example, we named it DiscountLimits.
  2. Create a custom field for your type. We named it maxDiscount.
  3. Create a record. We named it FoodDiscount.

When done, you can reference the custom metadata type in your validation rule. The syntax is:

$CustomMetadata.CustomMetadataTypeAPIName.RecordAPIName.FieldAPIName

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

  1. In Spring 18 Salesforce added two new methods in list class. They are

contains(listElement)

Returns true if the list contains the specified element.

indexOf(listElement)

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.

  1. 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.

  1. 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.

Salesforce Summer 17: Cool Seagulls in Summer

Hi everyone, we all know Salesforce release 3 updates for its system in a year.  Now Salesforce recently launched Summer 17. Summer is hot and in Rajasthan it’s very hot.  So here are few hot and exciting updates for everyone.

Summer_17_Release_Logo

  1. Use Advanced PDF to Render Visualforce Pages as PDF Files (Pilot)

Advanced PDF renders Visualforce pages as PDF files with broader support for modern HTML standards, such as CSS3, JavaScript, and HTML5. This change applies to both Lightning Experience and Salesforce Classic.

To use Advanced PDF, set renderAs=”advanced_pdf” in the tag of a Visualforce page with API version 40.0 or later. This process is similar to the existing process for rendering a Visualforce page as a standard PDF file.

PDF pages rendered with Advanced PDF are subject to the same limitations as legacy PDF pages, including the maximum page size and limited number of fetched resources. Advanced PDF pages also time out after rendering for 2 minutes, which includes asynchronous processing time.

  1. Roll Back Changes in Your Org When Remote JavaScript Methods Throw Exceptions

When a JavaScript method in an Apex class calling a remote action throws an exception, the action isn’t completed. Previously, when a method threw an exception, the action was completed.

For example, when you created an Apex class that used a remote action to add an account to your org and that method threw an exception, the account was added. Now, the account isn’t added. With this enhancement, JavaScript remoting methods that throw exceptions no longer cause changes in your org. This change applies to both Lightning Experience and Salesforce Classic.

  1. Cache Operations Supported in Visualforce Controllers

Cache operations made using the put and remove methods in the Cache Namespace are now supported in constructors and getter methods of Visualforce controllers.

  1. New Option for Parallel Testing on the isTest() Annotation

Use the @isTest(isParallel=true) annotation to indicate test classes that can be run in parallel and aren’t restricted by the default limits on the number of concurrent tests. This makes the execution of test classes more efficient, because more tests can be run in parallel.

  1. Deploy Changes Now Trigger Recompile of All Apex Code

All of an org’s Apex code is now automatically recompiled before completing a metadata deploy, a package install, or a package upgrade.

Previously, a deploy, install, or upgrade left the org with invalidated code, which sometimes caused recompilation errors when many Apex transactions occurred. This change in behavior improves performance following metadata deploys and package updates.

  1. Disable Access to Non-global Apex Controller Methods in Managed Packages (Critical Update)

This critical update corrects access controls on Apex controller methods in managed packages. When this update is enabled, only methods marked with the global access modifier are accessible by Lightning components from outside the package namespace. These access controls prevent you from using unsupported API methods that the package author didn’t intend for global access.

Prior to this update, non-global methods (that is, Apex controller methods that weren’t marked with the global access modifier) could be accessed by Lightning components outside of the package namespace.

  1. Metadata Access in Apex

If you’re an ISV creating apps that use custom metadata components, you can now access     metadata using Apex. This change applies to both Lightning Experience and Salesforce Classic.

During or after an install (or upgrade), your app can create or update metadata to let users configure your app. Use the new Metadata namespace for accessing metadata in Apex code. The Metadata namespace contains classes that represent metadata types and components as well as classes that let you retrieve or deploy metadata components in the subscriber org.

  1.   Salesforce Integrations: Taking Salesforce to the Next Level

Now you can connect Salesforce with Skype for Business , Gmail, Google Calendar and Microsoft Office 365. They are generally available in both Lightning and Salesforce classic. Nut some of them are only available in Lightning.

  1. Einstein Vision Is Now Generally Available

Sign up for Einstein Vision to receive 1,000 free predictions per calendar month. If you need more predictions, you can purchase them.

Getting an Einstein Platform account is the first step to accessing the API. Use the sign-up page to get an account. You can get an account in two ways.

  • Heroku—When you provision the Einstein Vision add-on, an Einstein Platform account is created for you.
  • Salesforce—Log in with your Salesforce credentials and create an account.

After you create an account, you download your private key file. Use this file to create an access token.

You can also try your hand on a Trailhead project to understand it better.

  1. Removed LockerService Restriction on instanceof in JavaScript

    Previously, Salesforce advised against using theinstanceof operator in JavaScript code when LockerService is activated. This restriction has been removed, except when checking arrays.

There are many more other update related to Lightning and Einstein. As I am also reading them in more details so I might make another post for them in depth. This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release.

Sign up now for a pre release org.

You can read release notes here. Let me know if I missed something here or if you want to add something then let me know in comments section.

Winter 17 is Here! A Quick Preview

Winter 17 is Here! A Quick Preview

Salesforce community is very busy these days. Dreamforce is near and everybody is preparing themselves for this mega event. As winter is here. So today I come up with 10 important feature of Winter 17

  1. Horizontal Navigation Comes to Lightning — One of the main initial features of Lightning, the collapsible side panel navigation, will be a thing of the past when Winter 17 goes live. This will be a big gain in efficiency and will ease the transition from Classic as it is similar to the Classic tabbed header. An awesome feature of the top navigation is when you hover over the tab name, you get a list of recent object records.
  2. Lightning Experience enhancements — Create Custom Apps in Lightning Experience and Navigate More Efficiently, Get Field-Level Help in Lightning Experience, Get Field-Level Help in Lightning Experience using save & New button
  3. Napili Is Now Called Customer Service (Napili) and it now supports more objects.
  4. Now you can use global search instead of Quick Find to find specific setup records, such as the Lead Source picklist or the Sales Rep profile. This feature is available in Lightning Experience only.
  5. Now you can create and manage your global picklist value sets from either user interface. No more switching back and forth to manage all of your picklists in Setup. Also Standard, multi-select picklists can be as detailed as you need them to be with a new limit of 255 characters per entry.
  6. The time window to quick-deploy your validations has expanded from 4 days to 10 days. This larger time window provides you more flexibility for scheduling your quick deployment and helps minimize the impact on your org.
  7. Build Reusable, Invocable Processes — This new feature will allow admins to create one Process and reuse it by invoking it from another Process. It’ll be available in Classic and Lightning editions.
  8. Inline Editing in List View Comes to Lightning —Lightning users will be able to hover over fields in a Listview and click to edit. This feature is in Beta and some restrictions will apply.
  1. Add the force:lightningQuickAction or force:lightningQuickActionWithoutHeader interface to a Lightning component to enable it to be used as a custom action in Lightning Experience or Salesforce1. You can use components that implement one of these interfaces as object-specific actions in both Lightning Experience and Salesforce1. You can use them as global actions only in Salesforce1.
  2. The Lightning Design System is now automatically added to your Lightning Out and Lightning Components for Visualforce apps. The Lightning Design System provides a look and feel that’s consistent with Lightning Experience.

 

Here are the 10 features which I found useful. I will keep updating this list whenever I found any useful feature in Winter 17 release notes. In the meantime you should give a read to Winter 17 notes and if found anything useful share them in comments. Cheers 🙂

Summer 16 is Here

Hi everyone, As we all are aware Salesforce gives us 3 releases in a year.  Now we have Summer 16 is here and this is Salesforce’s 50 release. So I am also excited as any one else. So I give a read of release notes and found some important points need to remember.  I am sharing them here and if you found any other important update please share them in comments.

_16__1_.png

  1. Limits increases for the Enterprise, Professional and Unlimited Editions.Find out what’s changed.

 custom apps

If you use a Professional, Enterprise, or Unlimited Edition org, you can now use as many custom apps as you want.

Custom Profiles
Professional Edition orgs can now use up to two custom profiles per license type.
Custom Tabs
If you use a Professional, Enterprise, or Unlimited Edition org, you can now use as many custom tabs as you want.
Field-Level Security
If you use a Professional Edition org with page layouts and add new fields, pay attention to field-level security for your new fields.
Previously existing fields aren’t affected.
Permission Sets
Professional Edition orgs can now use up to two permission sets.
Processes
Professional Edition customers now have access to Process Builder, our premier process-automation tool, and can use up to five
processes to automate repetitive tasks.
Record Types
Professional Edition customers can now use up to three record types per object.
Sandboxes
Professional, Enterprise, and Unlimited Edition orgs include more sandboxes to use for development, testing, and training.

2. Debug logs now include time zone information for activity timestamps. Previously, you couldn’t tell from a debug log which time zone the logged activities occurred in.

3. View Visualforce Controller Exceptions in Debug Logs
Debug logs now include exceptions thrown by Visualforce controllers. Visualforce controller exceptions have been visible in the Salesforce user interface, but the exceptions looked like successes in the debug log. This feature is available in both Lightning Experience and Salesforce Classic.

4. Set the Page Title in Lightning Experience with the <apex:page> title Attribute
In prior releases of Lightning Experience setting the page title of a Visualforce page had no effect. With this release, you can set the page’s title using the title attribute of the <apex:page> tag. This sets the text used in browser windows, tabs, and bookmarks, and makes using Lightning Experience in multiple tabs a better experience.
You can also set a Visualforce page title by adding a static <title> HTML tag to your page. Although using the page’s title attribute is usually preferred, the treatment of the page title is the same.
Finally, while it’s not a primary use case, setting the page’s title, using either technique, also affects the page in the Salesforce1 mobile browser app. The page’s title appears in the history stack, and in browser tabs or windows. The page title doesn’t appear in the Salesforce1 downloadable app.

5. Increased Cross-Namespace Limits

Good news! We’ve increased the number of unique, certified namespaces that can be invoked during a single Apex transaction.
Previously, the limit during a single transaction was 10. We’ve removed this limit and added a cumulative cross-namespace limit.
There’s now no limit on the number of certified namespaces that can be invoked in a single transaction. However, the number of operations that can be performed in each namespace must not exceed the per-transaction limits. In place of the former limit, there’s a new limit on the cumulative number of operations that can be made across namespaces in a transaction. This cumulative limit is 11 times the per-namespace limit. For example, if the per-namespace limit for SOQL queries is 100, a single transaction can perform up to 1,100 SOQL queries. In this case, the cumulative limit is 11 times the per-namespace limit of 100.

6. This critical update disables access to Lightning Experience and the Salesforce1 mobile browser app when using Microsoft Internet Explorer version 11.

7. Contacts to Multiple Accounts lets reps associate a single contact with multiple accounts. Every contact needs to be associated with a primary account (the account that appears in Account Name). And now, your reps can associate more accounts with each contact. The primary account represents a direct relationship; the other accounts associated with a contact represent indirect relationships.

8. Secure Confidential Client Information with Salesforce Shield
Salesforce Shield, a trio of security tools to help monitor data access and usage, prevent malicious activity, and encrypt data at rest. Protect your client information with Shield, which includes Event Monitoring, Field Audit Trail, and Platform Encryption.

9.You can now create a sandbox by cloning an existing sandbox rather than using your production org as your source. Save time by populating any type of sandbox with a previously chosen set of data and metadata. (Sandbox templates, which serve a similar
purpose, are available only for Full or Partial Copy sandboxes.) Sandbox-to-sandbox cloning facilitates iterative development, allowing you to freeze development in one sandbox and pick up where you left off in a new one.

Please let me know what you like most in summer 16 and what you still want to see in Salesforce.