Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/fsl-mobile-workflow-design

fsl-mobile-workflow-design

Verified

Use this skill when designing, troubleshooting, or reviewing FSL Mobile worker workflows — job lifecycle management, offline data capture, customer signature collection, parts consumption, and geolocation-triggered status transitions. Trigger keywords: FSL mobile, field service mobile workflow, offline job lifecycle, technician mobile, service appointment status, briefcase priming, parts consumption mobile, signature capture FSL. NOT for installing, branding, or extending the mobile app itself — use admin/fsl-mobile-app-setup. NOT for offline priming limits and sync conflict resolution — use architect/fsl-offline-architecture.

templates/fsl-mobile-workflow-design-template.md

View on GitHub
# FSL Mobile Workflow Design — Work Template

Use this template when planning, reviewing, or troubleshooting FSL Mobile technician workflows — including job lifecycle, offline data capture, signature collection, parts consumption, and briefcase priming.

---

## Scope

**Skill:** `fsl-mobile-workflow-design`

**Request summary:** (describe what the practitioner or user is asking for)

**Org context:** (Production / Sandbox / Scratch; FSL version; Spring '25 or earlier)

---

## Context Gathered

Answer these before proceeding:

- **Offline mode enabled?** Yes / No
- **Briefcase Builder configured?** Yes / No / Unknown
- **Objects confirmed in briefcase:** ServiceResource / ServiceAppointment / WorkOrder / WorkOrderLineItem / ContentDocument / ContentDocumentLink / Other: ___
- **SA→WO status cascade automation:** Flow / Process Builder / Apex Trigger / None — describe: ___
- **Data Capture flows (Spring 25)?** In use / Not in use / Unknown
- **Service report in use?** Yes / No — template name: ___
- **Parts consumption (ProductConsumed) configured?** Yes / No / Partial

---

## Job Lifecycle Map

Document the required SA status transitions and any WO status that must track SA:

| SA Status | Triggered By | WO Status Change Required? | Automation Owner |
|---|---|---|---|
| Scheduled | Dispatcher | No | — |
| Dispatched | Dispatcher | No | — |
| In Progress | Technician (mobile) | Yes → In Progress | Record-Triggered Flow |
| Completed | Technician (mobile) | Yes → Completed (if last SA) | Record-Triggered Flow |
| Cannot Complete | Technician (mobile) | Optional → review required | Record-Triggered Flow |

---

## Briefcase Field Audit

For each field required in the mobile UI or service report, confirm briefcase inclusion:

| Object | Field API Name | In Briefcase? | In Mobile Layout? | In Report Template? |
|---|---|---|---|---|
| WorkOrder | Status | [ ] | [ ] | [ ] |
| WorkOrder | Description | [ ] | [ ] | [ ] |
| WorkOrder | Subject | [ ] | [ ] | [ ] |
| ServiceAppointment | Status | [ ] | [ ] | N/A |
| (add rows as needed) | | | | |

---

## Server-Side Logic Inventory

For each automation on FSL Mobile objects, classify its sync behavior:

| Automation | Type | Object | Fires At | Risk if Offline? |
|---|---|---|---|---|
| Example: SetWOCompleted | Flow | ServiceAppointment | Sync | Low — acceptable delay |
| Example: RequireFailureCode | Validation Rule | WorkOrder | Sync | High — blocks sync if field not in mobile layout |
| (add rows) | | | | |

---

## Data Capture / Signature Configuration

- **Form type:** Data Capture Flow (Spring 25) / FSL Quick Action / Neither
- **Signature capture:** Yes / No — if yes, ContentDocument in briefcase: Yes / No
- **Signature merge field in report template:** Yes / No — field reference: ___
- **Required fields in Data Capture flow:** (list)
- **Conditional logic needed:** (describe)

---

## Parts Consumption Configuration

- **ProductRequired records in briefcase:** Yes / No
- **NewProductConsumed quick action on WO mobile layout:** Yes / No
- **Stakeholders informed of sync-delay inventory updates:** Yes / No
- **High-value parts requiring real-time accuracy:** (list — these require connectivity at consumption)

---

## Approach

Which pattern from SKILL.md applies? (check all that apply)

- [ ] Customer Signature Capture pattern
- [ ] Parts Consumption (ProductConsumed) pattern
- [ ] Automating WO Status from SA Status pattern
- [ ] Custom pattern — describe: ___

---

## Review Checklist

- [ ] SA status lifecycle documented and all required WO status cascades covered by Record-Triggered Flow
- [ ] Briefcase hierarchy confirmed: ServiceResource → SA → WO → WOLI
- [ ] All fields in mobile UI and service report template are in the briefcase
- [ ] No automation assumes server-side execution while technician is offline
- [ ] Data Capture flows (Spring 25+) or FSL quick actions configured for all structured offline forms
- [ ] Signature capture linked to ContentDocument; ContentDocument in briefcase; merge field in report template
- [ ] ProductConsumed quick action on WO mobile layout
- [ ] Stakeholders informed: inventory updates are sync-time, not real-time offline
- [ ] End-to-end airplane mode test completed
- [ ] Service report PDF validated after sync — no blank fields

---

## Notes

(Record any deviations from standard patterns, org-specific constraints, or decisions made during the engagement.)
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall