--- name: field-service-work-rule-designer-configure description: "Designs the work rules for a Salesforce Field Service scheduling policy — the hard filters that determine which resources and time slots are eligible for an appointment. Step 2 of the three-part scheduling policy design flow; receives the policy block from sfs-scheduling-policy-designer and delegates to sfs-service-objective-designer when complete. Use this skill when a user wants to design or configure the work rules (hard eligibility filters) for a Field Service scheduling policy." user-invocable: false metadata: version: "1.0" domains: ["Field Service"] --- # Salesforce Field Service – Work Rule Designer **Designs the work rules for a scheduling policy.** This skill collects the work rule configuration through a structured interview — one question at a time — and emits a `workRules[]` block as output. It does not create any Salesforce records. When complete, delegates to `sfs-service-objective-designer`. **Interview phases:** Scheduling Policy → **Work Rules** (this skill) → Service Objectives → Record Creation --- ## Work Rules **Work rules are hard filters.** They refine the candidate list for a service appointment by rejecting any service resource that violates a rule. They are always applied before service objectives, and objectives only ever score the resources that survive the rules. If a requirement is "must," it's a work rule; if it's "prefer," it's an objective. ### The 16 work rule types Each row: **name — engine (DB/Apex) — what it does.** "DB w/ ESO" means the rule runs at the database level *only when Enhanced Scheduling and Optimization is enabled*, and as Apex otherwise. Include at least one DB rule to narrow to ~20 candidates before Apex rules run. | Work Rule | Engine | What it does | |---|---|---| | **Service Resource Availability** | Apex — **MANDATORY** | Ensures a resource is actually available: respects operating hours, travel, breaks, absences, and existing assignments. Also enforces capacity for capacity-based resources. Configurable breaks, gaps, overtime, and travel-to/from-home. | | **Match Time Rule** | Apex | Constrains the scheduling window from an appointment's date/time fields. Ships with standard rules **Earliest Start Permitted** and **Due Date** (both **mandatory**), plus Scheduled Start / Scheduled End (arrival-window based). | | **Match Skills** | Apex | Matches an appointment's skill requirements to a resource's assigned skills; can enforce skill level. Skill Type Logic is **All Skills Match (AND)** (default) or **At Least One Skill Matches (OR)** (OR requires ESO). | | **Match Fields** | DB w/ ESO | Matches one appointment field to one resource field (1:1). Use Extended Match instead when comparing one appointment field against multiple resource values. | | **Match Boolean** | DB w/ ESO | Requires a checkbox field on the resource to be true (or false). **Max 5 per policy.** Ships with standard "Active Resources." | | **Extended Match** | Database | Custom-criteria matching via a junction object linking an appointment field to a related list on the resource (e.g., serviceable postal codes, product lines). | | **Match Territory** | Database | Restricts to resources who are primary or relocation members of the appointment's service territory. | | **Working Territories** | Database | Enforces **primary and secondary** service territory memberships. | | **Maximum Travel from Home** | Database | Caps distance/travel time between a resource's home base and any assigned appointment. | | **Required Resources** | DB w/ ESO | Forces assignment to a resource marked **Required** (Resource Preference on the WO/WOLI). Very restrictive. | | **Excluded Resources** | DB w/ ESO | Prevents assigning a resource marked **Excluded** on the WO/WOLI. | | **Count Rule** | Apex | Caps assignments, hours, or a custom value per resource per day (e.g., ≤8 scheduled hours, ≤N items on a truck). Time Resolution is **Daily**. Up to 10 custom-field count rules per policy. | | **Work Capacity** | Apex — **ESO only** | Enforces per-territory Work Capacity Limit records (e.g., cap install work at 80% of territory capacity). | | **Service Appointment Visiting Hours** | Apex | Enforces customer operating hours / allowed visit windows (e.g., weekdays 8 AM–noon). All-or-nothing rule (no relevance groups). | | **TimeSlot Designated Work** | Apex | Reserves a time slot/shift for a specific work type — only that type schedules in that window. All-or-nothing rule (no relevance groups). | | **Service Crew Resources Availability** | Apex | Ensures a crew-type resource is only assigned when the crew meets the parent record's minimum crew size. | ### Requirements mapping Don't start from the rule list — start from **what the business needs**, then map each requirement to the rule(s) that satisfy it. Walk the user through this mapping: | If the requirement is… | Use this work rule | |---|---| | Resources need specific skills / proficiency levels | **Match Skills**; **Extended Match** | | Non-skill matching factors (e.g., serviceable postal codes) | **Match Boolean**; **Match Skills**; **Extended Match** | | Breaks during the day / specific or multiple breaks | **Service Resource Availability** (+ work rule entries for multiple breaks, ESO) | | Can work go into overtime? Can resources travel outside working hours? | **Service Resource Availability** | | Max number / duration of appointments per resource per day | **Count Rule** | | A specific resource **must** be assigned | **Required Resources** | | A specific resource **must not** be assigned | **Excluded Resources** | | Customer has specific service-call time windows | **Service Appointment Visiting Hours** | | Ensure crew-type resources get scheduled | **Service Crew Resources Availability** | | Appointments have arrival windows / required arrival times | **Match Time Rule** | | Cap travel distance from home / control travel cost across large territories | **Maximum Travel from Home** — ask whether the cap is by **distance** or by **travel time** (see note below) | | Assign specific work types to a resource for part/all of a day | **TimeSlot Designated Work** | | Restrict work to the resource's **primary and secondary** service territory memberships | **Working Territories** | Always include exactly one **Service Resource Availability** rule — the only mandatory rule this skill emits. Never emit Earliest Start Permitted or Due Date — provisioned automatically. **Arrival Window Match Time rules (opt-in default pair).** If the user wants appointments to honor customer **arrival windows**, ask them to confirm, and if they agree, emit **two** Match Time rules with these exact default settings — do not ask the user to fill these in, they are the standard arrival-window configuration: | Setting | Rule A | Rule B | |---|---|---| | Name | `Arrival Window Start` | `Arrival Window End` | | Service Schedule Time Property | `SchedStartTime` | `SchedStartTime` | | Service Time Operator | `Later than or Equal to` | `Before or Equal to` | | Service Time Property | `ArrivalWindowStartTime` | `ArrivalWindowEndTime` | | Pass Empty Values | `true` | `true` | Emit each as a Match Time work rule whose `params` carry those four values (keys `serviceScheduleTimeProperty`, `serviceTimeOperator`, `serviceTimeProperty`, `passEmptyValues`). These are separate from the mandatory Earliest Start Permitted / Due Date rules (never emitted). **Interpreting and emitting break times (clock time vs. shift-start offset):** A Service Resource Availability rule expresses breaks in one of two shapes, and **this skill decides the shape and emits the values the data-layer skill needs** — the data-layer skill never receives a clock time it has to convert. Choose the shape as follows: - **One fixed daily break at an absolute clock time** (e.g. "30 minutes at 12:00 every day") → emit it as an **absolute** break: `{ "mode": "absolute", "startClock": "12:00", "durationMinutes": 30 }`. No offset math, no working-day start needed. - **One or more breaks defined as an offset from the start of the working day** (e.g. "a 30-minute lunch starting 3 hours into the shift") → emit each as an **offset** break, in **minutes from the start of the working day**: `{ "mode": "offset", "earliestStartOffsetMinutes": 180, "latestEndOffsetMinutes": 240, "durationMinutes": 30 }`. All three of `earliestStartOffsetMinutes`, `latestEndOffsetMinutes`, and `durationMinutes` are **mandatory** for an offset break. **When the user states the break in offset terms already** (e.g. "3 hours after the start of day"), that offset *is* `earliestStartOffsetMinutes` (180) — **do not ask for the working-day start; you don't need it.** - **Breaks given as clock times but there is more than one** (e.g. "15 minutes at 10:00 and 30 minutes at 12:00") → you must use the **offset** shape, which means **converting each clock time into an offset from the start of the working day**. You cannot do that without knowing when the day starts, so **ask the user for the shift / working-day start**, then compute `earliestStartOffsetMinutes = (break start clock − day start)` in minutes for each break. Never assume the day starts at midnight (that would turn "10:00" into a wrong 600-minute offset). *(Only ask for the day start in this clock-time case — never when the break is already expressed as an offset.)* **Always emit `latestEndOffsetMinutes` for every offset break — ask for it directly, do not fabricate a window.** The earliest start comes from what the user stated (an offset, or a converted clock time) — **do not invent ± tolerance windows around it** (no "±1 hour" / "±2 hour" options). If the user only gave a break start (or a duration with no stated finish-by), **ask them plainly for the latest the break may end**, phrased in the *same terms they used*: if they gave an offset ("starts 3 hours after start of day"), ask "what is the latest it may end, as time after the start of the day?" and convert (e.g. "4 hours after start" → 240); if they gave a clock time, ask for a clock time and convert with the day start. If the user says the break is fixed/pinned with no flex, set `latestEndOffsetMinutes = earliestStartOffsetMinutes + durationMinutes`. Never emit an offset break missing any of the three fields, and never guess the latest-end. If a break requirement is too involved to convert reliably, ask clarifying questions or recommend the manual approach rather than guessing. **Maximum Travel from Home — establish the cap type, not the unit.** When a requirement caps how far a resource may travel from home, **ask the user whether the cap is by distance or by travel time** — the two are configured differently and the data-layer skill needs to know which. Emit the value and the type in `params`: `{ "maxTravelFromHome": 50, "maxTravelFromHomeType": "Distance" | "Travel Time" }`. Interpret the user's phrasing to set the *type* — "50 miles"/"50 km" ⇒ `Distance`, "45 minutes" ⇒ `Travel Time` — but **do not ask for or emit a distance unit (miles vs km): it is not part of the work-rule config**; the unit is governed by the org's locale/distance settings elsewhere, so the rule stores only the number. For `Travel Time` the value is minutes. Never emit the cap value without its type. ### Per-rule configuration Once the requirements mapping has selected which rules to build, configure the specifics for each. The **`Emit` line gives the exact `params` keys** — use these verbatim so the data-layer skill can map them. Only configure rules the user selected; skip the rest. --- **Service Resource Availability** *(always present)* Gate: Always included — no selection needed. Ask: - "Can work run into **overtime**?" (yes/no) - "Can resources **travel outside working hours** to/from home?" — if yes, ask how many minutes from home (to first job) and to home (from last job); "no limit" = 120; "no" = 0 for both - Breaks interview (see *Interpreting and emitting break times*) Emit: `{ "enableOvertime": true|false, "travelFromHomeMinutes": , "travelToHomeMinutes": , "breaks": [ … ] }` Note: Travel values are minutes — 0 = no travel outside working hours, 120 = effectively unlimited. If user gives no availability detail, emit baseline (`enableOvertime: false`, travel keys and breaks omitted). --- **Match Time Rule** *(arrival windows)* Gate: Only if selected in requirements mapping. Ask: "Should appointments honor customer **arrival windows**?" Emit: Two default rules from the Arrival Window table — no further questions. --- **Match Skills** Gate: Only if selected in requirements mapping. Ask: "Should the resource also **meet a minimum skill level** (proficiency), or is simply *having* the skill enough?" Emit: `{ "matchSkillLevel": true|false }` Note: Do not ask about skill-type AND/OR logic — this skill does not configure `skillTypeLogic`. --- **Match Fields** Gate: Only if selected in requirements mapping. Ask: "Which Service Appointment field must match which Service Resource field, and with what operator?" Emit: `{ "serviceProperty": "", "resourceProperty": "", "booleanOperator": "=" }` Note: Operator is one of `=`, `>=`, `<=`, `>`, `<` (default `=`). Field names are the customer's own — pass through as given. --- **Match Boolean** Gate: Only if selected in requirements mapping. Ask: "Which checkbox field on the resource must be true (or false)?" Emit: `{ "resourceProperty": "", "value": true|false }` Note: Max 5 Match Boolean rules per policy. --- **Maximum Travel from Home** Gate: Only if selected in requirements mapping. Ask: "Is the cap by **distance** or by **travel time**?" (see cap-type note in Requirements mapping) Emit: `{ "maxTravelFromHome": , "maxTravelFromHomeType": "Distance"|"Travel Time" }` Note: Distance unit (miles vs km) is not part of the rule — governed by org locale. For Travel Time, value is minutes. --- **Working Territories** Gate: Only if selected in requirements mapping. Ask: None — selecting the rule is sufficient. Emit: `{ "workingLocationEnablePrimary": true }` Note: No separate Match Territory question — the interview does not emit a standalone Match Territory rule. If primary/relocation-only scoping is needed, advise manual configuration. --- **Service Crew Resources Availability** Gate: Only if selected in requirements mapping. Ask: - "Should the rule evaluate individual crew members' availability and skills, not just the crew record?" → `considerCrewMembership` - "What is the maximum number of extra resources beyond the base crew that can be pulled in?" → `maxAdditionalResources` (optional) Emit: `{ "considerCrewMembership": true|false, "maxAdditionalResources": }` (omit `maxAdditionalResources` if blank) --- **Extended Match** *(advisory only — data-layer skill will not build this)* Gate: Only if selected in requirements mapping. Ask: None — no params to collect. Advise the user to set up before deploying: 1. A junction object with exactly **two** Master-Detail relationships (to Service Resource + matched object) — packaged trigger requires exactly two or the rule fails 2. A Service Appointment Lookup field driving the match; a reference field on the junction matched against it 3. Once those exist, create and configure the rule manually in Setup (Field Service Settings → Scheduling → Work Rules) Capture intended objects/fields in `prerequisites` as advisory text — do not emit in `workRules[]`. --- **Count Rule** Gate: Only if selected in requirements mapping. Ask: Have the user describe the limit in plain terms, then classify into: - `countBy` — `"Appointments"` (count of jobs), `"Hours"` (duration cap), or `"Custom"` (sum of a custom SA field) - `maxValue` — the numeric cap (for Hours, convert to hours) - `fieldHint` — the SA field to sum; `null` for a plain Appointments count Emit: `{ "countBy": "Appointments"|"Hours"|"Custom", "maxValue": , "fieldHint": ""|null }` Note: Time Resolution is always Daily; counted object is always Service Appointment — data-layer skill sets both automatically. Up to 10 custom-field count rules per policy. When countBy is Custom or Hours against a field, add prerequisite: "Confirm field `` exists on Service Appointment." --- **Selection-only rules** *(no config fields — each rule acts as an on/off switch that tells the scheduler to enforce constraints defined elsewhere in the org; selected in requirements mapping, no further questions needed)* **Required Resources / Excluded Resources** Gate: Only if selected in requirements mapping. Emit: `{}` Prerequisite: Resource Preference records must exist on the work order / WOLI — the rule enforces them but does not create them. **Work Capacity** *(ESO only)* Gate: Only if selected in requirements mapping. Emit: `{}` Prerequisite: WorkCapacityLimit records must be configured per territory outside the policy. **Service Appointment Visiting Hours** Gate: Only if selected in requirements mapping. Emit: `{}` Note: Do not ask for the windows — they are per-account data on OperatingHours records, not a policy-wide value. (No relevance-group scoping.) Prerequisite: Each account must have visiting/operating hours populated; the Work Order's Visiting Hours must resolve from the account. **TimeSlot Designated Work** Gate: Only if selected in requirements mapping. Emit: `{}` Note: Do not ask for slot→work mappings — that is data setup. Phrase the selection as "types of work," not "Work Type" (the designation is broader than the Work Type object). (No relevance-group scoping.) Prerequisite: Time slots must be configured to designate the intended work. --- ## Relevance Groups A relevance group scopes a single work rule or service objective so it applies only to certain appointments or resources, instead of the whole policy. This lets one policy hold different logic for different work or resource types — e.g., different break/travel limits for part-time vs. full-time employees, or expedited scheduling for high-value accounts. ### How it works, and the division of labor A relevance group is driven by a Boolean (true/false) field. Every standard or custom Boolean field on the Service Appointment and Service Territory Member objects is selectable in the rule/objective's Relevance Group dropdown. On a work rule or objective, you pick the limiting Boolean field; the rule/objective then applies only to records where that field is true. The two bases are just the two objects the Boolean can live on: - **Service Appointment basis** — scopes by the appointment being evaluated (e.g., a formula checkbox "Platinum Account" that's true when the related account tier is Platinum). Use to target appointment types. - **Service Territory Member basis** — scopes by the service territory member of the resource being evaluated (e.g., "Part-Time" / "Full-Time" checkboxes). Use to target resource populations. Only primary and relocation memberships are supported — not secondary. In the design: decide the basis (Service Appointment vs. Service Territory Member) and the name of the Boolean field that identifies the subset, then record both on the rule/objective in the build spec (`relevanceGroup: { basis, booleanField }`). This skill only decides which field scopes which rule/objective — wiring the group onto the record is the data-layer skill's concern. The Boolean field itself is a prerequisite the user must own, not something either skill in this pair creates: creating the field is a schema change (DDL), and setting its true/false values on records needs a flow, formula, trigger, or data load. So advise the user to, before deploying: (1) create one custom Boolean field on the appropriate object (Service Territory Member for a resource subset, Service Appointment for a work subset) per subset; (2) populate it true for exactly the records in that subset (via flow/formula/import), keepin