Blog Posts

[1] 2 3 4 5 6 7 ... 80 Next 5 items

Top Ideas for Salesforce Lightning

As Salesforce Lightning continues to roll—what is on deck on the IdeaExchange?
Top Ideas for Salesforce Lightning

Top Ideas for Salesforce Lightning

2017 marked the year of Lightning. 2018 and beyond will be no different. With the emphasis clearly on Lightning moving forward, the ideas on the IdeaExchange have flooded in. There are a ton of ideas that range from brand new to features that need to be implemented in Lightning to bring it in line with Classic. Here are some of my top ideas up for vote:

Configurable Default List View in Lightning Experience

This is a no-brainer feature that is requested by most Salesforce users that I have spoken with. For the vast majority of users, being able to view their recently viewed records from the home page is sufficient. In Spring 18 Salesforce gave us Personalized Navigation; it would be great if that was expanded on where every user could tailor their tab’s default list view to what they want it to be.

Lightning Experience: Recycle Bin

At this point, there should be no reason for a user to have to switch back to Classic in order to do something as simple as access the recycle bin. There have been AppExchange Packages and other workarounds developed, but this is something that needs to be readily available out of the box.

Lightning Experience: Lead and Contact List View - Campaign Filter

There are a myriad of reasons why users would want to filter their list view by Campaign, and a user should not have to switch back to Salesforce Classic in order to achieve it. This is a particularly powerful feature when coupled with List Email functionality. This is something that has to make it into future releases.

Ability to Share List View With Group in Lightning

In Salesforce Classic, users have the ability to create list views and share them with themselves, a group of users, or all users. In Salesforce Lightning, users cannot share their list views with groups, which is particularly important for teams who may need to interact with the same set of list views. Having to switch back and forth to Salesforce Classic in order to achieve list view sharing is not ideal and very inefficient.

Process Builder: Error Messages

We all love Process Builder. It provides us with an avenue to perform all types of automation with clicks and not code. It delivers in user efficiency and productivity. But what it doesn’t deliver on is comprehensive error handling when a user triggers an error. Process Builder needs to produce user-friendly error messages.


What are your thoughts on the state of Lightning? What else do you think should be added or improved upon? Share your ideas or thoughts with me on the Arkus Facebook page, in the comments below, in the Success Community, or to me directly via Twitter at @RyanOwensRPO.


Salesforce Spring 18 Ideas Delivered

Salesforce again delivers on ideas from the Community in the Spring ‘18 release.
Salesforce Spring 18 Ideas Delivered

Salesforce Spring 18 Ideas Delivered

Though the list of ideas delivered in this release isn’t huge (literally it’s 12 ideas) there are some good ones this time around. The point count this time is a total of 43,770. It’s also interesting that Salesforce is now not really highlighting delivered ideas in the release notes like they used to. In any case, here are a few ideas delivered worth mentioning.

Streamline Lead Conversion Without Opportunities

In Lead Settings, there are two options now for the Lead Conversion screen: hide the opportunity section completely or have the checkbox for not creating an opportunity on the convert screen checked by default. This idea was delivered with a whopping total of 34,330 points.

Path: Pick Your Own Path

Now we can create a Path based on any picklist field for standard objects. Examples include the ability to track the growth of your relationship with an organization or household, track Campaign progress, or track the support cycle of Cases.  The steps are the same in setting up the path; path steps are based on values in a picklist field, highlight the values using key fields, and include guidance to help users succeed at each step on the path. The Idea addressed by this feature had gathered a total of 5,820 points.

Share Credit for a Deal in Lightning Experience

Yeah for Sales teams! Opportunity Splits that were available in Classic are now in Lightning Experience. Team members working an opportunity can see how much credit they get for each deal. These can then be rolled into quota and pipeline reports for a team. You can add or adjust splits from the Opportunity Splits related list. This idea was delivered with a total of 1,540 points.

Do you have other favorite Ideas delivered in this latest release I didn’t mention? Please feel free to comment below, on our Facebook page, or directly at me on Twitter @LeiferAshley or in the Success Community and Power of Us Hub.

Using Leads in Program Management

The concept behind the Leads object in Salesforce is extremely useful, and not just for marketing and sales teams to hand-off prospects.
Using Leads in Program Management

Using Leads in Program Management

The Salesforce platform is built to be flexible, and making creative use of standard objects can support a wide range of functionality. Increasingly nonprofit organizations are looking to manage multi-step support cases -- instances in which an individual must be deemed eligible for services before a case is created, or perhaps there is an intake process before the type of support is identified.

The most common solution for program management is to identify a process within the confines of a Case - statuses to mark the Case as not-yet-approved or going through intake. This solution works; there’s nothing wrong with it.

But what if there’s a chance that the person requesting support isn’t eligible for that support at all or perhaps ultimately not interested? What happens with the handful of Contacts, and their associated Accounts or Households, that are created at the outset but never go anywhere?

There should be a way to identify an incoming request that still needs an initial review. Are they eligible for services? Have they marked off the boxes needed before they can receive services? Are they even interested in the available services? And is there a way to easily distinguish between eligible and ineligible applicants?

Leads can serve as this early stage of pre-eligibility review, and Process Builder makes it possible to auto-create a Case upon conversion, signalling the initial approval of an incoming request.


Why Leads


At its core, the Lead object is just a holding area for those ill-defined, not-quite-a-Contact-but-not-nothing types of records. They are individuals that we have some knowledge about but may require a go/no-go decision before moving forward. Ephemeral, elusive, and extraordinarily helpful.

They are easy to get into the system, either through an import or even Salesforce’s built-in Web-to-Lead form. Forms can have minimal information to make a client feel at ease, and follow up or more in-depth review and questions can come later.

From a strict database perspective, Leads take up less memory than a Contact and associated Account, being only one record with data pertaining to both. They are easy to auto-assign, transfer, and even delete, if necessary, and they can also still be assigned to Campaigns for nurturing and tracking. They also serve as a clear indication to all users that this is a person or request that has not yet been picked up and reviewed.

The conversion process is already tracked and catalogued by Salesforce, so it can be a trigger or switch that indicates to the system, as well as users, that this individual is ready to receive services.

Prepare for Case Creation

Creating a case on conversion, like creating anything else from Lead conversion, requires some planning. Some key questions to ask are:


  1. What information do we require to confirm initial eligibility or interest?

  2. What information needs to be copied to a Case?

  3. What information needs to stay with the Contact record but be included with the Case?

  4. Are there different types of Cases, and if so, does the type need to be identified even at the early Lead stage?


For each of these questions, prepare the database to work within those requirements. Create any custom fields on the Lead, so they can then pass onto the Case, and make sure to create custom fields on the Case to accept that data, if necessary.

Here is an example of one way to manage thinking through and creating these types of custom fields.


Lead to Case planning


What about that pesky Company field?

Depending on your overall database, you may want to change the label of this field to something like “Family Name.” If you need to keep it as-is for a multi-use database, train users to include something along the lines of “Requester.” Third party form builders will also allow you to set this value automatically.

If you’re using NPSP, the Household Account will be renamed on conversion. If you’re not using NPSP or are not using the auto-name feature, teach your users to use a specific naming convention.

Build the Automation

The goal is to create a Case when the Lead is converted. Process Builder can handle this all on its own. For this demo, only one type of support is provided, but this same concept can be expanded and made as complex as needed.


  1. Name and describe your new Process Builder flow - good documentation is best practice. If possible, make note of any exceptions, as well.

New PB Flow

  1. Select Lead as your Object and “when a record is created or edited”

  2. Identify the first criteria. It’s important to at least include that the IsConverted system field is changed and is now true. Other criteria can be included. Here are my conditions.

Lead to Case process builder flow criteria

  1. As an immediate action, select “Create a Record” and choose Case as the object

  2. Use Lead fields to populate fields on the new Case with the Field Reference option

Lead to Case PB Flow actions

  1. For Contact and Account ID, use the Field References “Converted Contact ID” and “Converted Account ID” respectively

Lead to Case creation converted ID fields for mapping

  1. Save and test


Leads are an option for managing a multi-step program management process, and with Salesforce’s growing solutions for automation via clicks-not-code, it’s easier than ever to utilize this native solution and still make it easy for users.


Have you used leads in a similar way? Do you have a similar use case that you solved in a different way? We’d love to hear about it. Share your stories with us on Twitter, on the Salesforce Community, Facebook, or chat with me @thesafinhold .


Lightning Strikes Spring 18

Winter is here, which means Spring is on its way. What has Salesforce brought us in the Spring 18 release?
Lightning Strikes Spring 18

Lightning Strikes Spring 18

The new year is here and with that, Spring 18 is upon us. Winter 18 marked another big jump in the platform’s progress, and Spring 18 looks to continue that momentum. There are a bunch of features to highlight, but here are some of the new additions and enhancements that stood out to me when reviewing the release notes:

Reply and Forward Case Emails

This is a key feature that has been missing from Service Cloud in Lightning. When working with a Case, users will now have the ability to Reply, Reply All, and Forward emails associated with them. Service Cloud has been limited in Lightning thus far, but this is a great feature that is moving the bar in the right direction.

Themes in Lightning Experience

Salesforce delivers on its promise to start making the platform more customizable from a branding perspective with themes. In Spring 18, administrators will be able to create themes that match their company’s branding without having to use any code. This is an enhancement to LEX that will make a lot of organizations looking for a more branded experience very happy.

The one thing to keep in mind is that only one theme can be active at a time and that the active theme applies to the entire instance of Salesforce.

Gather Feedback with Salesforce Surveys

In Spring 18, Salesforce will be delivering a native Survey tool. The tool will provide organizations the ability to easily create forms and collect feedback. The data captured via the form will integrate directly into Salesforce, which will in turn open up the opportunity to leverage Salesforce’s reporting capabilities to view analytics and provide insights on survey results.

The major thing to note with this new tool is that it is a paid feature. There are many third party tools currently available, but a survey feature native to Salesforce is going to interest a lot of people.

Personalized Navigation in Lightning Experience

Often times at an organization using Salesforce, users work with specific items over others. Some users may interact daily with a certain tab while others may bypass it and go directly to what is relevant to them. Salesforce addresses this by providing users the ability to personalize their navigation bar to suit their individual needs. Users can reorder tabs, and rename or remove items that they’ve added.

Users will have the ability to create temporary tabs. These tabs can contain things like a specific dashboard that they need to view often, a list view, or a record and can be named whatever the user wants. Temporary tabs are removed from the navigation when a user switches applications or logs out, but users will also be able to choose to permanently add those items to the navigation bar. This level of flexibility will make users who have been looking for this for a long time smile.

Stay on Top of Duplicate Records with Duplicate Jobs

Most of us are familiar with the current way of managing duplicate record entries. Salesforce takes things a step further in Spring 18 by providing the ability to run scheduled duplicate jobs. These jobs can be set up to run and leverage standard or custom matching rules to scan Salesforce Person Accounts, Contacts, or Leads.

The results of the duplicate job can be compared against other entries and merging can be accomplished from there. Pretty nifty, right? For organizations using Performance and Unlimited editions of Salesforce, this is going to take duplicate management to a new level.


What do you think of the improvements and additions in Spring 18? Want to share your thoughts? Let me know what you think on the Arkus Facebook page, in the comments below, in the Success Community, or to me directly via Twitter at @RyanOwensRPO.


Salesforce Spring 18 Release Notes Rapid Reaction

It sure doesn’t feel like Spring in the Northeast, but Salesforce is moving forward regardless. Here’s a quick reaction blog post, with the hopes that it brings some warmer weather along with it.
Salesforce Spring 18 Release Notes Rapid Reaction

Salesforce Spring 18 Release Notes Rapid Reaction

To start, I feel it is necessary to mention some branding changes, as opposed to an actual feature being delivered. Salesforce is officially all in on the Lightning brand. For example Force.com is now Lightning Platform, so say goodbye to the good old days of Force.com development. My formative years building out Salesforce apps were all done on Force.com, so this is a little sad for me. Now onto the features:

Streamline Lead Conversion without Opportunities

This change applies to Lightning Experience only folks, so if you like the feature and have been waiting for something like this, you’ll have to be in Lightning to utilize it. Have you ever wanted to convert a Lead without creating an Opportunity? I know I have. Lots of times. I’ve worked in many organizations that would really benefit from utilizing Leads, but the conversion process is confusing when it comes to Opportunities, especially if the reason for using Leads is not to track a potential sale, rather to track a potential person for any reason -- recruiting perhaps. With this handy new feature you, as the administrator, can set the default behavior, to either change the checkbox behavior for creation of Opportunity on conversion or choose to hide it altogether. This minor user experience modification opens up a world of new use cases, thanks to being able to control a single checkbox. Thank you for this one, Salesforce!

Keep Track of Events with Community Calendars

Internal users of Salesforce get to create calendars and share them with each other. This feature has existed for a while in Lightning Experience. There was no component for it though, so if you wanted to display data in a calendar format for a community user you, as the administrator or developer, would need to build one. With this feature a calendar can be used and shared within communities (desktop version is the preferred method of accessing it) to share data. Users can also add events to calendars. Pretty nifty stuff.


Connect Your Pardot Campaigns to Salesforce Campaigns (Beta)

This beta feature becomes Pardot’s B2B solution. Pardot literally becomes a native app inside of Salesforce -- in Lightning Edition only -- called B2B Marketing Automation. Once Campaign Alignment is turned on, users can only create campaigns in Salesforce; campaigns in Pardot become inactive and read only. Only connected campaigns work within Pardot. That oddball checkbox user field “Marketing User” is required to use the app; look at that little checkbox continuing to be relevant, even though a permission set license is also required. You can try this out in a Pardot training environment, and you should; contact Salesforce to get a training environment. Users who are familiar with Salesforce as an interface are really going to love this, and in all likelihood adoption of Pardot will see an increase amongst savvy Salesforce users.

Please feel free to comment below, on the Salesforce Trailblazer Community, on our Facebook page, or directly at me on Twitter @JustEdelstein.

 

[1] 2 3 4 5 6 7 ... 80 Next 5 items