fbpx

Adding a Path to Case Records in Lightning Experience

With the advent of the Path functionality in Lightning Experience, which was formerly known exclusively as a Sales Path, this opened up a new and useful way of highlighting key fields and guidance for success for Salesforce users. What happened very quickly is that administrators and developers started clamoring for this Path functionality to be extended to standard and custom objects.

With the Spring ’18 release, we have a lot more standard objects as well as all custom objects now supporting the Path functionality. You can pair a path by Record Type and associate the path with any picklist on the object you choose to work with.

In this screen demo which I have just added to my Service Cloud Consultant Certification course, I show you how to add a Path to the Case object. This is once again enabling more functionality out of the box with Salesforce, where you used to have to create a Visualforce page. Paths are a powerful feature that can save both yourself and your users a lot of time.

1 thought on “Adding a Path to Case Records in Lightning Experience

  • Hi Mike,
    Is it necessary to create a separate path component for every case record type if I want to use the status field. I thought Case Status field is .tied to a record type and a support process, with that said if I have associated 4 out of 5 case record types with a one support process shouldn’t I be creating one path component per support process? I feel like the path setup doesn’t take that into account, do you know if my understanding is correct? In my org most of the case rec types are tied to one support process which governs which case statuses should be displayed on the page, so why am I required to create separate path component for each record type that are tied to the same support process.

Leave a Reply

Your email address will not be published. Required fields are marked *

error

Enjoying this? Please spread the word :)