Field Path

A smarter way to visualize progress.

Track progress, status, and stages with precision - anywhere, anytime. The Field Path component brings full flexibility to how you visualize processes in Salesforce, without the limits of Salesforce’s native Path feature. Choose your field. Choose your path. Choose your flow.

Paths that follow your logic.

Field Path lets you define process flows based on any picklist field - not just the ones Salesforce allows. Whether you're managing opportunity stages, case statuses, or something custom, this component gives you an elegant, visual way to bring that data to life.

Simple to configure, powerful in action. Whether linear or non-linear, your paths stay aligned to your business logic - because that’s where real adoption happens.

Intuitive user experience

Flexibility that puts you in control.

  • Define your own path: Use any field to drive your visual path—perfect for custom objects, alternate processes, or departments with different flows.
  • Linear or non-linear display: Choose the visual experience that fits your use case. Field Path supports both sequential and branched paths for ultimate flexibility.
  • Real-time clarity: Display the current stage of a record at a glance, helping teams stay in sync and move faster with less confusion.
  • No limits, no dependencies: Unlike Salesforce Path, GridMate’s Field Path doesn’t require specific objects, field dependencies, or extra setup. Drop it in and go.
  • Works across record types: Standardize your experience across multiple record types while tailoring the displayed path to each.
Use cases

Flexible paths for real-world processes.

  • Track opportunity or lead stages
  • Display case status for support teams
  • Highlight custom process stages (e.g., contract review, onboarding)
  • Guide users through project phases or lifecycle steps

See the Field Path
in action!

Make the leap from standard to standout.

Unlock path visualization without limits - turn rigid flows into dynamic, user-driven journeys.

Linear path display
Flexible across multiple objects
Flexible across multiple fields
Supports custom picklist fields
Non-linear path option
Reusable across multiple record types
Easy to configure and deploy
Works on custom objects

Frequently Asked Questions

Are GridMate grids supported on the Salesforce Mobile App?

Absolutely! Here's what we recommend:

  • Duplicate the existing grid in your Salesforce Org. This duplicated grid should be specifically configured for access by mobile users.
  • Set a unique name that clearly identifies it as a mobile-friendly grid.

There are two key considerations when it comes to accessing grids on mobile devices:

Set the width for each column – This allows users to scroll horizontally.

Refer to column width specification here.

Set the height of the grid – This enables vertical scrolling.

Refer to the height specification here.

Note: We will be introducing a new component called ‘Mobile Grids’, which will be optimized specifically for mobile phones.

What security and compliance standards does GridMate meet?

GridMate is designed with enterprise-grade security and compliance in mind. We are FedRAMP authorized, which means our solution meets the U.S. federal government’s rigorous standards for data security, access control, and operational transparency.

All GridMate components are built natively on Salesforce, ensuring that your data remains within your Salesforce environment. We do not store, process, or transmit data outside your org, and we align with best practices for secure development and deployment.

Do I need technical experience with GridMate?

Not at all. We’ll equip you with everything you need - from product overviews to sales guides and demo walkthroughs.

Can the record Id be passed to a GridMate component on Experience Cloud?

Yes. GridMate supports this functionality. You can define the recordId property using the syntax "{!recordId}".

Does GridMate store or process data outside of my Salesforce Org?

No. GridMate is a native Salesforce package. We do not store or process any data outside of Salesforce. All our components are metadata-driven and built on Salesforce APIs.

Got any more
questions?

Get Support