Salesforce Path: The Good & How It Can Be Improved

Salesforce Path is a key Lightning feature.Path guides users along steps in a process, such as working an opportunity from a fresh lead to a successfully closed deal. Path is available for leads, opportunities, quotes, contracts, orders, and custom objects in Lightning Experience. Here is a short list of benefits of this powerful tool as well as features I believe that will take Path to the next level!

The Good

  1. Salesforce Path is an amazing tool for creating a road map for users to follow. Help users from A-Z with a step-by-step process
  2. Path allows for robust reporting by each stage of the Path, and it allows for a quick snapshot of where each record stands in the path.
  3. Path also works very well with Process Builder. With easy to use IFTTT, Process Builder allows the creation of business workflows from the movement of records in Path.
  4. Path allows for custom text at each stage of the path. This allows for a custom message at each stage providing extra communication to help move the user through to the next stage.
  5. You can add up to 5 fields at each stage of the path for the user to add information. This is a great tool if certain information is need prior to moving to the next stage of the Path.

Can Path Be Improved?

I want to start by saying I think Path is an incredible tool that brings a lot of value to Salesforce Lightning. I wanted to write this blog in hopes that users can share their opinions and we can work together to make Path even more powerful. I believe this tool is amazing, but I also feel like their is so much potential and this tool can be developed to be even greater. Here are my thoughts:

  1. Salesforce path has a limit of 5 fields to add at each stage of the path. I think it would be great if they didn’t put a limit on this. Sure, you don’t want to have 15 fields under 1 stage of the path; however, I feel like some situations call for more than 5 fields. Here is the idea on Salesforce if you would like to vote.
  2. Make certain fields required once the user is at that stage of the path. Example, at stage 1- you may not have the information needed to make that field required; however, at stage 3, it would be great to now make that field required  before letting the user move to stage 4.
  3. Hide certain sections that aren’t relevant at that stage of the page. this allows for a more simplistic look of the record page. If information isn’t need until stage 3, it would be great to hide that information until stage 3 is clicked. Here is the idea on Salesforce if you like to vote. 

I’ll keep it short. Let me know your thoughts!

For more information, check us out at