Sunday, 3 September 2017

Top New Features Coming in Winter 18 Release

#SalesforceRelease #Winter18 #TopFeatures #Salesforceguy
1. Lightning Experience Gets a New Look and Feel
Based on your feedback, we improved information density, legibility, contrast, and even added a splash of color. That means less time scrolling and scanning and more time focused on what matters most. This change applies to Lightning Experience only.
Here’s a closer look at what’s changed.
  • More information density and less white space, so you can see more of what you need without scrolling.
  • Improved legibility (using font size and color) to draw attention to what’s most important.
  • Better contrast between foreground and background, making it easier to scan and scroll while staying focused on what you need. We even added color and a background image inspired by our own Trailhead.
You don’t need to do anything to start enjoying these enhancements. If you like, though, you can change the background image and blue color to a neutral gray. In Setup, enter Themes and Branding in the Quick Find box, then select Themes and Branding, and select Hide.

2. Sales Console: Welcome Forecasting to the Console
#SalesProductivity #Forecasting
You’ve been patiently waiting for Collaborative Forecasts to come to the Lightning Sales Console. The wait is over! Plus, we’ve made other great improvements to Lightning console apps, including the ability to add favorites, navigation rules to make your users’ workflow more efficient, and additional keyboard shortcuts.

3. List Views: Customizations, Mass Inline Editing, and Text Wrapping
#ListViews #Customizations
Reps can get more done with fewer clicks when working from list views. Edit multiple records from a list view, and wrap text in columns to see more at a glance.
No longer experience excessive white space in columns or content that is out of view. Columns in list views, search results, related lists, and elsewhere, such as the App Manager in Setup, are now sized based on the length of the data within them. When you resize your screen, the columns adjust accordingly. This feature is disabled when you set a fixed column width. This change applies to Lightning Experience only.
Sticky column widths have arrived for Recently Viewed list views, related lists, and search results! Change your column widths, navigate away, and when you return, your custom column widths are still there. This change applies to Lightning Experience only.
You can change the column widths for list views, related lists, and search results. But what if you want to revert all those changes? Just use the new Reset Column Widths setting in the list view controls to get back to the default widths. This change applies to Lightning Experience only.
Tired of seeing only part of each field in a list view? We’ve got you covered, because now you can wrap text in list view columns. This change applies to Lightning Experience only.
Found a list view that you like, but don’t have permission to edit it and save your changes? It’s easy to create a list view by using Save As or Clone and then make a few tweaks. If you created list views in this way using Salesforce Classic, you can now do it in Lightning Experience. This change applies to Lightning Experience only.
Your reps can now update up to 200 records without leaving a list view. This feature is new in Lightning Experience.

4. Lightning Sync for Google: Two-Way Event Sync, Attendee Sync, and Support for More Licenses
#LightningSync #GoogleIntegration
Make your team more productive by setting up events to sync both ways between Google Calendar™ and Salesforce. When you do, you get exclusive access to Salesforce Calendar features that are designed to work with Lightning Sync. We’re also introducing support for users on Service Cloud and licenses so you can get even more users syncing between Salesforce and Google applications. These changes apply to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
Lightning Sync is available for Service Cloud and user licenses. Depending on which objects are available through the license, reps can sync contacts, events, or both between their G Suite accounts and Salesforce. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
Save reps time and unnecessary data entry by setting up events to sync between Google Calendar and Salesforce. That way, reps can create and edit meetings from either application. And admins like you can promote Salesforce adoption by making it easy for reps to get important meetings into Salesforce. This change applies to Lightning Experience and all versions of the Salesforce1 mobile app.
When you set up our enhanced scheduling options for Salesforce Calendar, reps can see their Google Calendar™ attendee details and responses from either system. This change applies to Lightning Experience and all versions of the Salesforce1 mobile app.

5. Lightning Knowledge: Multi-language Orgs, Updated Article Actions, and Video Support
#LightningKnowledge #ServiceCloud
Multi-language orgs can now make the move to Lightning Knowledge. When viewing a case in the console, authors can create an article from the Knowledge component. Authors also have a richer text editing experience with video, and they can see who’s viewing articles with event monitoring. This change applies to Lightning Experience only.
Multi-language orgs can now make the move to Lightning Knowledge. When viewing a case in the console, authors can create an article from the Knowledge component. Authors also have a richer text editing experience with video, and they can see who’s viewing articles with event monitoring. This change applies to Lightning Experience only.
Multi-language orgs are now supported in Lightning Knowledge! You can search and read translated articles in Lightning Knowledge. You still create and manage translated articles in Salesforce Classic This change applies to Lightning Experience only.
Users can create articles from the Knowledge component. This change applies to Lightning Experience only.
 Lightning Knowledge authors can create a rich article experience by embedding videos and inserting code blocks. We expanded the list of supported domains for embedding videos in both Salesforce Classic and Lightning Experience.
Make data-driven decisions about your knowledge base content with event monitoring. We added a Knowledge article event type to the EventLogFile standard object for article views. You can see who is viewing articles to better understand how people are using Knowledge within your organization. This change applies to Lightning Experience only.
Track articles that require action by reporting on assignment fields. This change applies to Lightning Experience only.
 The data category chooser component is fully accessible in Lightning Knowledge record home. This component supports the full number of data categories you have enabled in your org.
Experience the improved Knowledge article search to find articles and resolve cases faster.

6. Macros in Lightning: Creating Efficient Support Agents and Happy Customers
#Lightning #ServiceCloud
Lightning Macros can revolutionize the way your support agents work! Macros provide the power to automate common repetitive tasks and resolve issues efficiently, so your agents can spend more time doing what they do best: focusing on customer success. With macros in Lightning Experience, you can add the macro utility to your org’s Lightning Console Apps, such as Service Console, and give agents the tools to quickly resolve customer service issues. Agents can send a customer email and update a case status with a single click.
Quickly and easily edit and add instructions to macros using the new Macro Builder point-and-click interface.
The Record Home page is your one-stop-shop to view and manage macros in Lightning.
Create amazing macros in the context of your work by adding the macro utility to your Service Console utility bar.

7. Dynamic Branding: One Community, with a Different Look for Each Audience
With branding sets, you can change the appearance and style of your community pages based on the audience viewing the page. No need to create individual communities for each customer or business need. Now you build your community once, and simply style it differently for each audience.
Branding sets take advantage of criteria-based audiences in the same way as page variations. Just as you can create several page variations and target them at different audiences, you can create different sets of branding properties to produce a unique look and feel for specific audiences.
In Community Builder, you can:
  • Manage branding sets from the Branding panel (1).
  • Create a set of branding properties (2).
  • Create or assign an audience to your branding set (3).
  • Switch between a tile or list view of branding sets (4).

8. Developers, Build Your Community Your Way
#Communities #CustomTemplate
The Build Your Own template provides the basic pages every community needs: Home, Create Record, Error, Record Detail, Record List, Related Record List, Search, Check Password, Forgot Password, Login, Login Error, and Register. And you can easily add more pages and components for the experience you’re building. Customize your branding and themes to refine the look of your community.
To view all components in the Components panel, select Settings | Advanced and click Show All Components in the Components Panel area.

9. Community Analytics: Community Pulse and Annotations
#Communities #Analytics
See the community stats you care about the most at the top of Workspaces and take action, plus communicate directly on dashboards.
You told us that you wanted to see your most important community stats in Workspaces. We heard you and present Community Pulse! Community Pulse displays up to six metrics of your choosing right at the top of Workspaces. Clicking a metric takes you to the related Moderation or Engagement report or dashboard so that you can take action or get more information.
Foster an environment of open communication sparked by Analytics dashboards embedded in your community. With the annotation feature, partners and customers can converse in Chatter feeds on individual dashboard widgets.

10. Make Your Lightning Pages Dynamic
#LightningAppBuilder #Customization
Now you can control when a component appears on a record page by adding filter conditions and logic to its properties. No need to add anything to your custom components. It’s all handled by the Lightning App Builder. For example, construct a filter that causes a rich text component on an opportunity page to display when the Amount is greater than $1 million.
Component visibility filters are supported for standard components, custom components, and components from AppExchange. If you don’t define a filter, the component displays on the Lightning record page as usual. When you define one or more filters and set the filter logic for a component, the component is hidden until the filter logic criteria are met.

11. Salesforce DX: The New Frontier for Salesforce App Development (Generally Available)
With a focus on source-driven development, Salesforce DX makes it easier for developers to build together and continuously deliver using the tools that make you most productive. Salesforce Developer Experience (Salesforce DX) will be generally available in mid-October 2017.

12. Build Exciting User Interfaces with New Base Lightning Components
Accelerate your development with a fresh medley of 30 new built-in Lightning components. The new components cover a broad range of user interface elements and give you a whole new toolbag for your development.
We are working to reach parity with the Lightning Design System components, and this release brings us closer to that goal. Here’s a visual summary of what we have in store for you.
If this screenshot doesn’t do them justice, head over to New and Changed Lightning Components for a lot more detail, including many more screenshots.
There a lot many other feature as well, Offical release notes is available HTML format as well as PDF file.
#HappyLearning #Salesforceguy 

Monday, 24 April 2017

Summer'17 : Top New Features

Top New Feature Coming in Summer 17 Release

1.  Get Expanded Analysis When You Check Your Lightning Experience Readiness  


The Readiness Check is chock full of more actionable advice, including specifics on resolving your JavaScript buttons and links, who’s ready to migrate, and how to use your report to inform your migration plan. And since it only takes one click to get a personalized report sent straight to your email inbox, there’s no reason to wait to kick off the Readiness Check. This change applies to both Lightning Experience and Salesforce Classic.

2. Lightning Sync for Google: Two-Way Sync, General Availability

#Events #Sales

Make your teams more productive by setting up contacts and events to sync between your G Suite account and Salesforce. These changes apply to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.

Now contacts sync in both directions between Google Contacts and Salesforce. Set up reps to sync both ways so that they can create and edit contacts from the application that’s most convenient to them: Gmail or Salesforce. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
No need to hold off any longer! Lightning Sync for Google is generally available and open for business! When you set up your reps to sync contacts and events between their G Suite account and Salesforce, you give them an opportunity to be more productive. Save your reps time and eliminate unnecessary data entry while also doing your part to promote Salesforce adoption across your team. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
Reps have tons of appointments on their calendars, but only a subset of those events contains valuable data that reps want to track in Salesforce. Now setting up reps for both Lightning for Gmail and Lightning Sync lets them choose which Google Calendar™ events sync to Salesforce. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
When Salesforce moves faster, you and your reps can move faster, too. We’ve tinkered under the hood so that contacts and events sync more frequently between your reps’ G Suite account and Salesforce. No setup necessary—you can kick back while your reps enjoy an improved sync experience. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
3.  Kanban: More Objects, More Settings
#Sales #Kanban
Several enhancements make the Kanban View easier to use. These changes apply to Lightning Experience only.
Display Knowledge and Social Persona records in an entirely new way by switching to Kanban view. This change applies to Lightning Experience only.
Money isn’t everything. In the Kanban view, reps can summarize by numeric fields, not just currency fields. This change applies to Lightning Experience only.
Your reps can configure the Kanban view to group cards by the record’s owner. This change applies to Lightning Experience only.
Reps can see in a glance which Kanban cards they don’t have permission to drag.

4. Service Console: Increased Efficiency for All (Generally Available)
The Service Console in Lightning Experience is now generally available and includes a bunch of enhancements. Features like split view, keyboard shortcuts, case hovers, and more are aimed at keeping your support agents productive. With Community 360, agents can see which articles a customer has looked at. But we didn’t forget about our awesome admins. Now you can set up service-related features like Lightning Communities and Lightning Knowledge in a jiffy.
To keep your support agents happy and efficient, we’re giving them some awesome new features. Keyboard shortcuts and split view let agents manage cases faster and with fewer clicks. Combine all that goodness with the new Omni-Channel utility, and your agents have even more power at their fingertips. These changes apply to Lightning Experience only.
Our setup flows take the guesswork out of enabling core service features. Great for newbies or seasoned admins, setup flows walk you through the setup process without having to consult a help topic. Lightning Service now offers setup flows for Lightning Knowledge and Lightning Communities. In the Recommended Setup window, we've also added an easy way to customize your case statuses. This change applies to Lightning Experience only.
Help support agents decrease customer frustration, and improve support. Community 360 shows support agents working in the console whether customers have already looked at pertinent documentation, and if they’ve already filed any cases before calling support. Agents don’t suggest articles customers have already accessed, or open duplicate cases. This feature is new in Lightning Experience.
5. Move Communities Between Orgs with Change Sets
Change sets are now available for Lightning communities and Salesforce Tabs + Visualforce communities, making it easy to move your community between orgs that have a deployment connection. Create, customize, and test your community in your sandbox environment and then migrate the community to production when testing is complete.
Community migration is also supported via the Metadata API.
6. Announcing Partner Central—The New Partner Community Solution
Recruit, onboard, and manage your partner relationships from a central location built on the new, native Lightning solution: Partner Central. Extend your CRM tools and data to channel partners in a responsive, flexible community that is powered by Lightning and the Salesforce platform. Welcome to the new way to drive channel sales!

7. Stay on Top of What Happens in Your Communities with Global Notifications

With Global Notifications, your members receive messages wherever they are working, whether in their communities or in their apps. Members receive notifications on any screen—mobile, tablet, and desktop. This functionality is available in communities based on Customer Service (Napili), Partner Central, and any Lightning Bolt solutions.
Notifications in communities
All events that trigger notifications (@mentions and group posts) are supported. Members can even trigger notifications on record feeds. For example, an internal member can trigger a notification from the Salesforce org by @mentioning an external member on a lead or opportunity. When a member clicks a notification, the originating detail page or other appropriate location is displayed for seamless collaboration across communities and apps.
By default, the Notifications icon is hidden in existing communities and displayed in new communities. For the default Customer Service theme layout, show or hide Notifications for your members by selecting Hide Notifications icon in community header in Settings | Theme in Community Builder.

8.  Promote Your Picklist Fields to Global Value Sets
Global Picklists became generally available Winter ’17. Since then, we’ve been busy adding features, and now you can migrate existing picklist fields into global value sets.
Promote a single picklist field into a global value set by editing your picklist field and clicking Promote to Global Value Set.
Field edit dialog showing the Promote to Global Value Set button.
A new global value set is created, and the promoted field now references it. You can also use the new global value set for other fields.
There are a few limitations to be aware of:
  • You can only promote fields that have fewer than 1,000 values (both active and inactive).
  • You can only promote restricted picklists. If you want to promote an unrestricted picklist, first convert it to a restricted picklist.
  • You cannot promote a field to an existing global value set. But check out this Salesforce Lab App for some help.
  • After a field is promoted, you can’t demote it back.

9. Retrieve and Deploy Metadata Using Apex
Salesforce uses metadata types and components to represent org configuration and customization. Metadata is used for org settings that admins control, or configuration information applied by installed apps and packages.
Previously, accessing metadata required using the Metadata API, but you can now use classes in the Metadata namespace to access metadata components from Apex code.
Access metadata from your Apex code to handle tasks such as:
  • Customizing app installs or upgrades—During or after an install (or upgrade), your app can create or update metadata to let users configure your app.
  • Customizing apps after installation—After your app is installed, you can use metadata in Apex to let admins configure your app using the UI that your app provides rather than having admins manually use the standard Salesforce setup UI.
  • Securely accessing protected metadata—Update metadata that your app uses internally without exposing these types and components to your users.
  • Creating custom configuration tools—Use metadata in Apex to provide custom tools for admins to customize apps and packages.
Metadata access in Apex is currently limited to custom metadata records and page layouts. You can retrieve, create, or update custom metadata, but you cannot delete metadata through Apex.

10.  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.
This annotation overrides settings that disable parallel testing by default. A test class that doesn’t have this annotation is restricted by the default limits on the number of concurrent tests.

11. Lightning Data Service (Beta)
Lightning Data Service is now in beta. Use Lightning Data Service to load, create, edit, or delete a record in your component, without using Apex code. Lightning Data Service handles sharing rules and field-level security for you. Lightning Data Service also improves performance and user-interface consistency.
With the move to beta, force:recordPreview has been deprecated and replaced with force:recordData. If you’re using force:recordPreview, you must refactor your components to use force:recordData.
With force:recordData, the targetRecord attribute has been updated to return records in a new shape using the UI API.

12. Override Standard Actions with Lightning Components
At long last, you can override four of the standard actions on objects—View, New, Edit, and Tab—using Lightning components. You can override these actions on standard and custom objects. Overriding standard actions allows you to customize your org using Lightning components, including completely customizing the way you view, create, and edit records.
The ability to override standard actions has long been possible using Visualforce pages. It’s also long been a top request for Lightning components. We’re thrilled to be adding this feature, and we hope you find it just as exciting. (This isn’t just a feature, it’s an adventure.)
All of that said, there’s a lot you need to know to successfully use action overrides with Lightning components. On the surface, adding an action override that uses a Lightning component is almost exactly the same as using a Visualforce page. You simply choose a different item, and away you go.

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

Friday, 26 August 2016

Winter 17 : Top 10 New Features


Top 10 New Feature Coming in Winter 17 Release

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.

Screen Shot 2016-08-24 at 4.58.59 PM.png

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.

Screen Shot 2016-08-24 at 5.01.59 PM.png
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.
Assign a Custom Record Page to Lightning Apps
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.
Screen Shot 2016-08-26 at 2.13.55 PM.png
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.
Screen Shot 2016-08-26 at 2.25.07 PM.png
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.
Screen Shot 2016-08-26 at 2.26.58 PM.png
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.
Screen Shot 2016-08-26 at 2.32.20 PM.png
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.