BBT Path

2 Points less for missing edit option

The Idea of this component is good and it's great it's free. We tried it out to display a stage/substage grouped path. Setting it up by defining a grouped path and placing the component on the layout worked fine and selecting the substages for each group is easy. The major drawbacks are that the app not only lacks the ability to EDIT the paths (for whatever reason) but that the custom objects it operates on in the backend (BBT_Path_Step__c and BBT_Path_Group__c as well as "Path Deployment Status") are protected hence only visible to the APEX code of the managed package. So even manual edit is not possible. This leaves the user with deleting and starting over with new path definitions each time something needs to be changed. We realized in a comparison that almost the same user experience can be achieved by using the salesforce path component for the stage picklist in conjuction with a dependent picklist substage. Once the dependency is defined and a new stage is selected on the path component a pop up window opens to set the dependent substage. only drawback here is that the dependent substage value is not visible in the component... Get in touch for details - C

Works great but room for improvement

Easy to install and configure. My only issue with the tool is that the text in the chevron for the final step is illegible. The chevron itself is dark blue and the text inside the chevron is also dark blue so you cannot read the text. Basically, you end up with a dark blue text on a dark blue background for the final step. Can you please change the text color to white to match the standard path component?

Amazing App, It Just Needs Edit Functionality

Let me first say this is an amazing app, It does everything that is needed for end users and solves our biggest use case of needing to have different paths without having different record types. It is pretty easy to set up and requires minimal effort to configure initially. Thats where the problem begins though, The current version of the app is missing one crucial feature, There is no way to edit an existing path, so if you add a picklist value to adjust to a new business process, you have to recreate the path from the start. Another option would be to expose the records where the configuration is stored so customers can manually modify it, even if the UI for editing wouldn't be there. If this key missing feature is added, id me more than happy to adjust my rating, but without it i dont think i could adjust it in good faith.

Option to hide path update button

I wish there was a way to disable the path update button.

Very useful

It is working great, easily create paths, and an amazing alternative to having different Record Types for different paths. One disadvantage is that when you change the Stage on the field, even after saving the record, the Stage on the path is not updated schematically, so we have to reload the record page to make the new stage show as the current one on the Path. It would be excellent if this gets fixed!

Perfect, Clean Addition

Lightweight, easy, and vastly applicable. This managed package is among the best for any application that could otherwise use any more than a single Path for any given Object. If you are familiar with the intense maintenance Record Types can impose on an org, this solution should be a no-brainer. In a lot of cases, especially with the advent of Dynamic Forms for Standard Objects, Record Types are totally antiquated with this addition. With some clever usage coupling conditional visibility and explicitly unique Paths, you can mimic the ease of use that Field Dependency allows for in a context that won't violate Validation Rules or Picklist-choice vs RecordType options.

Amazing tool

We have been wishing for a way to customize the native paths in Salesforce without creating new record types, and this app was the perfect solution. There is only 1 downside we've seen so far. If you change the stage on the path it reflects in the corresponding field, however, if you change the stage in the field, it does not correspond to the path. We've instructed our users to only change the stage using the path, so this is not much of an issue for our org.