Salesforce Release Winter 17 : Top 10 New Features

1. Modify Records from the Kanban View

Everybody hates a detour. Great news: Now you can edit or delete records from the Kanban view. This feature is available in Lightning Experience only.

2. Subscribe to Reports in Lightning Experience

You know that report you check when you arrive in the office every Monday morning? Why not have it emailed to you every Monday at 8:00 AM instead? Subscribe to up to five reports and receive refreshed report results by email on a schedule you set: daily, weekly, or monthly. To start a report subscription, open a report and click Subscribe. Specify when to receive the report, and then go about your business. When you need the report data, it’s waiting for you in your inbox.

3. Assign a Custom Record Page to Lightning Apps, or Make It the Default for All

When you activate a custom record page in the Lightning App Builder, you now have two options. You can make the record page the default for all your users. Or you can assign the record page to one or more Lightning apps to give your users access to a page customized for the app that they’re working in. Use the new Assignments by App column in the Lightning Record Pages related list in the Object Manager to see which Lightning apps each record page is assigned to.

4. Create a New Style of App Page with the New App Page Template in the Lightning App Builder

The new Header and Two Columns template in the Lightning App Builder lets you customize the layout of your app pages a different way. App pages created with this template are available in Lightning Experience and all versions of the Salesforce1 mobile app.

5. Create More Spanning Relationships Per Object in Formulas

Sometimes you want more! We’ve increased the number of unique relationships per object from 10 to 15. This increase is available in both Lightning Experience and Salesforce Classic. Objects can be related to each other via a relationship field.

You can create formulas that reference fields on another object, known as a spanning relationship. When creating a formula in a formula field, field update, or validation rule, you might get an error if you exceed the limit. You’ll hit the limit in several ways, including:

  • You have 15 formula fields and each formula references a unique object.
  • You have 10 formula fields and each formula references a unique object. You then create a workflow field update that references 5 different objects.
  • You have a validation rule that references 4 unique objects, a field update that references 7 other objects, and a formula field that references 4 other objects

For example, you have two custom objects, Object1__c and Object2__c. Object1__c has a lookup relationship with Object2__c. When creating formula fields on Object1__c, you can reference fields found on Object2__c, which then counts as one spanning relationship or object reference.

6. Process Builder : Build Reusable Processes

Now you can create a process that another process can invoke. With invocable processes, you can reuse sections of your processes. Build one invocable process, call it from multiple processes or from multiple action groups in the same process. This ability to reuse can save you precious time, and who doesn’t love that?
You can invoke processes with objects that share at least one unique ID. For example, in the Account and Case objects, the AccountId field is unique to Account and also used by Case. You can create an invocable process that updates a Case record. Then you can invoke it from:

— A process that updates an Account record’s owner
 — A process that adds an Account shipping address or updates it

When you create a process that invokes another process, each one counts toward your process and other applicable limits. DML limits in processes that invoke processes count as one transaction.

When you create a process, have it start when another process invokes it by selecting It’s invoked by another process.

7. Access Owner Fields from Process Builder

Process Builder now lets you access fields on an owner, such as to reference the email or name of a case’s owner. Previously, you could reference OwnerId but not any of the owner’s fields. If you’re working with an object that can be owned by multiple other objects — such as User and Queue — you choose which object’s fields to reference.

8. Add Lightning Components from the AppExchange in Community Builder

The integrated AppExchange experience makes it easy for you to find custom Lightning components on the AppExchange and add them to your org directly from Community Builder.

Browse a selection of components that are ready to add to your community’s Lightning pages by clicking Get more on the AppExchange in the Page Editor. When you add a component, it appears in the Lightning Components pane of all the template-based communities in your org.

9. Use the Lightning Design System in Lightning Apps

Use the Lightning Design System to your Lightning apps by extending force:slds or using a static resource. The Salesforce Lightning Design System provides a look and feel that’s consistent with Lightning Experience. Use Lightning Design System styles to give your custom applications a UI that is consistent with Salesforce, without having to reverse-engineer our styles.

Your application automatically gets Lightning Design System styles and design tokens if it extends force:slds. This method is the easiest way to stay up to date and consistent with Lightning Design System enhancements.

To extend force:slds:

<aura:application extends="force:slds">  
<!-- customize your application here -- >

10. Launch a Lightning Component from an Action

Lightning component actions are custom actions that invoke a Lightning component. Because they support Apex and JavaScript, Lightning component actions provide a secure way to build client-side custom functionality. This feature is available in Lightning Experience and all versions of the Salesforce1 mobile app.

To create a Lightning component action, select Lightning Component from the Action Type drop-down list when you create either a global or object-specific action.

Lightning component actions can’t call just any Lightning component in your org. For a component to work as a Lightning component action, it has to be configured specifically for that purpose and implement either the force:LightningQuickAction or force:LightningQuickActionWithoutHeader interfaces. You can find out more about configuring custom components in the Lightning Components Developer Guide.

You can add Lightning component actions to an object’s page layout using the page layout editor. If you have Lightning component actions in your org, you can find them in the Salesforce1 & Lightning Actions category in the page layout editor’s palette.

There a lot many other feature as well, Offical release notes is available HTML format as well as PDF file.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.