Considerations and Guidelines for Creating Paths

Before creating paths for your users, review the considerations and guidelines for paths.

Available in: Lightning Experience

Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Packages, Key Fields, and Guidance for Success

When you configure key fields and success guidance in a path, kanban views configured for the same object, record type, and picklist also show the information.
Each object can have one path per record type. There is no limit to the number of paths that you can create per org.
If your org has a large combination of objects, record types, and picklists, path creation can take a couple of minutes.
To translate Guidance for Success content, use the Path Step Rich Text component in Translation Workbench.
You can’t include images in path packages.
You can’t package custom values in standard picklist fields on paths.
Path appears for records where the running user has permission to view the record, record type, and all fields used in the path.

When you configure celebrations in a path, the confetti animation is also triggered in kanban views configured for the same object, record type, and picklist.
Celebrations don’t work on the lead status Converted.
Celebrations don’t support field values with a comma in the API name. Delete the comma from the API name or re-create the value. A comma in the label for a field value is OK.

The record type and owner fields aren’t editable in the Key Fields panel. To transfer ownership, users must use the Details tab. To change the record type, they must use the Change Record Type action.
If a path exists for a record type that you delete, the path is also deleted.
You can’t use the page layout to require different fields in different steps. However, you can set up validation rules based on a path step.
Validation messages appear as page-level messages even if you configure the rules to show them near the fields.
If the Opportunity Stage field is in use in field dependencies, all Stage values are shown when selecting the last stage Closed, instead of showing only Closed/Won and Closed/Lost options.
When you add a Path component to a dynamic form, a field’s configuration on the page layout overrides the UI Behavior value selected for it on the dynamic form. For example, Opportunity Information Description is set as required on the Opportunity page layout but has a UI Behavior value of None on the dynamic form. The Path component treats the Opportunity Information Description field as required.