1. Operating Model
TrackForcePro works best when users know which surface to use first. The product is no longer just a popup. It is a three-surface toolkit.
Launcher Popup
Use it to check the current org, jump into a tool quickly, and resume your last workspace. It should be the fastest starting point, not the place for long tasks.
Workspace Tab
Use this for serious work: SOQL, GraphQL, Records, Org Tools, Debug Logs, Label translation, and settings. Anything with tables, builders, or multi-step flows belongs here.
In-Page Overlays
Use these on Salesforce pages when the current page context matters. This includes TF Sidebar, Show All Data, LWC Explorer, right-click actions, and Setup Search.
2. Role-Based Learning Paths
Different Salesforce roles need different first wins. Start training with the path that matches the person’s daily work.
| Role | Start Here | Primary Skills |
|---|---|---|
| Admin | Records, Org Tools, Setup Search | Find metadata by API name, manage debug logs, custom labels, validate field values, move quickly through Setup. |
| Developer | SOQL, GraphQL, Metadata Explorer | Query data, inspect flows and Apex, compare objects, use page overlays to jump from context into workspace. |
| Support / Ops | Show All Data, Sharing, Field History | Triage record issues, verify user access, inspect values directly from a Salesforce page. |
| Consultant / Trainer | Launcher, Training Guide, Quiz | Teach the surface model, guide first-use flows, reinforce learning with labs and quiz-based recall. |
3. Daily Workflows to Teach First
- Find a record problem fast: open a record page, launch Show All Data, inspect fields, jump to Sharing or Field History, then open Records for deeper comparison.
- Search metadata by API name: use Setup Search on any Salesforce page for quick discovery, then use Metadata Explorer in the workspace when you need broader results and follow-up actions.
- Inspect a broken page component: open LWC Explorer from the page, select the component, separate Apex vs UI API vs GraphQL traffic, then use the large editor window to jump straight into the LWC bundle or Apex class.
- Triage a failing automation: search the Flow by API name, open Debug Logs, run the record context through SOQL or Records, and capture the result path for the incident owner.
- Translate or update labels safely: use Org Tools for export/import/translation workflows instead of doing repeated manual label edits.
4. Hands-On Labs
These labs are designed for training sessions, onboarding, or self-study. Each one teaches both product navigation and Salesforce problem solving.
Search a Flow API name, Permission Set API name, and Record Type API name from Setup Search. Then repeat the same search in Metadata Explorer and compare which surface feels faster for discovery versus detail.
From a record page, use the context menu to open Show All Data, then open Field History or Sharing, and finally route into the workspace. The goal is to understand handoff between overlays and deep tools.
Open Settings, verify inline edit protections for production orgs, then practice changing a harmless visual setting and using Save & Apply. This teaches the difference between editing a setting and applying it across surfaces.
Open a Salesforce page with custom components, launch LWC Explorer, compare one imperative Apex call with one UI API or GraphQL request, and practice opening both Edit Code and Edit Apex in the large editor window.
5. Trainer Notes
When users struggle, the issue is usually not feature depth. It is feature selection. The best coaching sequence is:
- Identify the user’s job to be done.
- Pick the correct surface first.
- Teach only the next two actions, not the whole product.
- Reinforce with one lab and one quiz round.