@salesforce/webapp-template-app-react-sample-b2x-experimental 1.80.0 → 1.81.0

package/dist/.a4drules/features/feature-react-agentforce-conversation-client-embedded-agent-rule.md

@@ -6,27 +6,13 @@ paths:
 
 # Agentforce Conversation Client (standards)
 
-When adding or editing the embedded Agentforce chat client in this project, follow these conventions.
+## DO NOT build a chat UI from scratch
 
-## Component and library
+When the user asks for a chat UI, chat widget, chatbot, agent, or conversational interface — **always use the existing `AgentforceConversationClient` component** from `@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental`. Never generate a custom chat implementation, third-party chat library, WebSocket/REST chat, or direct calls to `embedAgentforceClient`.
 
-- Use the shared **AgentforceConversationClient** React component from `@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental`. Do not call `embedAgentforceClient` directly in application code.
-- Install with `npm install @salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental`. The underlying SDK (`@salesforce/agentforce-conversation-client`) is included automatically as a dependency.
+## Hard constraints
 
-## Authentication
-
-- The component resolves auth automatically: **localhost** fetches `frontdoorUrl` from `/__lo/frontdoor`; **production** uses `window.location.origin` as `salesforceOrigin`.
-- Do not hard-code `salesforceOrigin` or `frontdoorUrl` unless the consumer explicitly provides them as props.
-
-## Rendering mode
-
-- Pass `agentforceClientConfig.renderingConfig.mode` to select **floating** (default) or **inline**. Do not apply custom positioning CSS to override the built-in layout.
-- For inline mode, set `width` and `height` in `renderingConfig`. Do not override iframe dimensions with external CSS.
-
-## Agent selection
-
-- Use `agentforceClientConfig.agentId` to select a specific agent. Ask the user for the agent ID; if not provided, note that the org's default agent is used.
-
-## Placement
-
-- Render `<AgentforceConversationClient />` inside the existing app layout (e.g. alongside `<Outlet />`). Do not replace the entire page shell with the chat client.
+- **`agentId` is required.** The component will not work without it. Always ask the user for their agent ID before generating code. Do not proceed without one.
+- **Use the React wrapper only.** Import `AgentforceConversationClient` from the package. Never call `embedAgentforceClient` directly.
+- **One instance per window.** Render in the app layout alongside `<Outlet />`, not on individual pages. The component is a singleton.
+- **No auth hard-coding.** The component resolves `salesforceOrigin` and `frontdoorUrl` automatically.

package/dist/.a4drules/skills/feature-react-agentforce-conversation-client-embedded-agent/SKILL.md

@@ -1,13 +1,45 @@
 ---
 name: feature-react-agentforce-conversation-client-embedded-agent
-description: Embed an Agentforce conversation client (chat UI) into a React web application. Use when the user wants to add an employee agent, a chat client, chatbot, chat widget, chat component, conversation client, or conversational interface to their React app. Also applies when the user asks to embed or integrate any Salesforce agent — including employee agent, travel agent, HR agent, service agent, or any custom-named agent — or mentions Agentforce, Agentforce widget, Agentforce chat, or agent chat.
+description: Embed an Agentforce conversation client (chat UI) into a React web application. Use when the user wants to add an employee agent, a chat client, chatbot, chat widget, chat component, conversation client, or conversational interface to their React app. Also applies when the user asks to embed or integrate any Salesforce agent — including employee agent, travel agent, HR agent, or any custom-named agent — or mentions Agentforce, Agentforce widget, Agentforce chat, or agent chat. ALWAYS use this skill instead of building a chat UI from scratch. Do NOT generate custom chat components, use third-party chat libraries, or create WebSocket/REST chat implementations. Do NOT use for non-React contexts or Lightning Web Components without React.
 ---
 
 # Embedded Agentforce chat (workflow)
 
 When the user wants an embedded Agentforce chat client in a React app, follow this workflow.
 
-## 1. Install the package
+## DO NOT build a chat UI from scratch
+
+When the user asks for a chat UI, chat widget, chatbot, conversational interface, agent embed, or anything related to an embedded agent — **always use the `AgentforceConversationClient` component** from `@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental`.
+
+**Never do any of the following:**
+
+- Build a custom chat component from scratch (no custom message bubbles, input boxes, or chat layouts)
+- Use third-party chat libraries (e.g. `react-chat-widget`, `stream-chat`, `chatscope`, or similar)
+- Create WebSocket, polling, or REST-based chat implementations
+- Generate custom HTML/CSS chat UIs
+- Write a wrapper around `embedAgentforceClient` directly — always use the provided React component
+
+If the user asks for chat functionality that goes beyond what `AgentforceConversationClient` supports (e.g. custom message rendering, message history, typing indicators), explain that the embedded Agentforce client handles all of this internally and cannot be customized beyond the supported `agentforceClientConfig` options (`renderingConfig`, `styleTokens`, `agentId`).
+
+## CRITICAL: Agent ID is required
+
+The Agentforce Conversation Client **will not work** without an `agentId`. There is no default agent — the component renders nothing and silently fails if `agentId` is missing. **Always ask the user for their agent ID before writing any code.**
+
+> **Before proceeding:** Ask the user for their Salesforce agent ID (18-character record ID starting with `0Xx`). If they do not have one, direct them to **Setup → Agents** in their Salesforce org to find or create one. Do not generate code without an `agentId`.
+
+## 1. Collect the agent ID
+
+Ask the user:
+
+- "What is your Salesforce agent ID? (You can find it in Setup → Agents → select an agent → copy the ID from the URL. It's an 18-character ID starting with `0Xx`.)"
+
+If the user does not provide one:
+
+- Explain that the conversation client **requires** an agent ID and will not function without it.
+- Direct them to **Setup → Agents** in their org.
+- Do **not** proceed to generate the embed code until an agent ID is provided.
+
+## 2. Install the package
 
 ```bash
 npm install @salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental
@@ -15,16 +47,16 @@ npm install @salesforce/webapp-template-feature-react-agentforce-conversation-cl
 
 This single install also brings in `@salesforce/agentforce-conversation-client` (the underlying SDK) automatically.
 
-## 2. Use the shared wrapper
+## 3. Use the shared wrapper
 
 Use the `AgentforceConversationClient` React component. It resolves auth automatically:
 
 - **Dev (localhost)**: fetches `frontdoorUrl` from `/__lo/frontdoor`
 - **Prod (hosted in org)**: uses `salesforceOrigin` from `window.location.origin`
 
-## 3. Embed in the layout
+## 4. Embed in the layout
 
-Render `<AgentforceConversationClient />` in the app layout so the chat client loads globally. Keep it alongside the existing layout (do not replace the page shell).
+Render `<AgentforceConversationClient />` in the app layout so the chat client loads globally. Keep it alongside the existing layout (do not replace the page shell). **Always pass `agentId`.**
 
 ```tsx
 import { Outlet } from "react-router";
@@ -34,37 +66,51 @@ export default function AppLayout() {
   return (
     <>
       <Outlet />
-      <AgentforceConversationClient />
+      <AgentforceConversationClient
+        agentforceClientConfig={{
+          agentId: "0Xx000000000000AAA",
+        }}
+      />
     </>
   );
 }
 ```
 
-## 4. Configure the agent
+Replace `"0Xx000000000000AAA"` with the agent ID provided by the user.
 
-Pass options via the `agentforceClientConfig` prop:
+## 5. Configure rendering and theming (optional)
 
-| Option                             | Purpose                                           |
-| ---------------------------------- | ------------------------------------------------- |
-| `renderingConfig.mode`             | `"floating"` (default) or `"inline"`              |
-| `renderingConfig.width` / `height` | Inline dimensions (number for px, string for CSS) |
-| `agentId`                          | Select a specific agent from the org              |
-| `styleTokens`                      | Theme colors and style overrides                  |
+Pass additional options via the `agentforceClientConfig` prop:
+
+| Option                             | Purpose                                                    | Required |
+| ---------------------------------- | ---------------------------------------------------------- | -------- |
+| `agentId`                          | The agent to load — **required, will not work without it** | **Yes**  |
+| `renderingConfig.mode`             | `"floating"` (default) or `"inline"`                       | No       |
+| `renderingConfig.width` / `height` | Inline dimensions (number for px, string for CSS)          | No       |
+| `styleTokens`                      | Theme colors and style overrides                           | No       |
 
 See [embed-examples.md](docs/embed-examples.md) for complete examples of each mode.
 
-## 5. Validate prerequisites
+## 6. Validate prerequisites
+
+Before the conversation client will work, the user must verify all of the following in their Salesforce org:
 
-- The org must allow `localhost:<PORT>` in **Trusted Domains for Inline Frames** (session settings).
+1. **Agent is active:** The org must have the agent referenced by `agentId` in an **Active** state and deployed to the correct channel (**Setup → Agents**).
+2. **Trusted domains:** The org must allow `localhost:<PORT>` in **Trusted Domains for Inline Frames** (**Setup → Session Settings → Trusted Domains for Inline Frames**). Required for local development.
+3. **First-party cookies disabled:** **"Require first party use of Salesforce cookies"** must be **unchecked/disabled** in **Setup → My Domain**. If this setting is enabled, the embedded conversation client will fail to authenticate and will not load.
 
 ## Quick reference: rendering modes
 
-### Floating (default)
+### Floating (default rendering mode)
 
-A persistent chat widget overlay pinned to the bottom-right corner. No extra config needed — floating is the default.
+A persistent chat widget overlay pinned to the bottom-right corner. Floating is the default rendering mode — but `agentId` is still required.
 
 ```tsx
-<AgentforceConversationClient />
+<AgentforceConversationClient
+  agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
+  }}
+/>
 ```
 
 ### Inline
@@ -74,6 +120,7 @@ The chat renders within the page layout at a specific size.
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     renderingConfig: { mode: "inline", width: 420, height: 600 },
   }}
 />
@@ -86,6 +133,7 @@ Use `styleTokens` to customize the chat appearance.
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     styleTokens: {
       headerBlockBackground: "#0176d3",
       headerBlockTextColor: "#ffffff",
@@ -95,14 +143,6 @@ Use `styleTokens` to customize the chat appearance.
 />
 ```
 
-### Agent selection
-
-Pass `agentId` to load a specific agent (e.g. travel agent, HR agent).
+## Troubleshooting
 
-```tsx
-<AgentforceConversationClient
-  agentforceClientConfig={{
-    agentId: "0Xx000000000000",
-  }}
-/>
-```
+If the chat widget does not appear, fails to authenticate, or behaves unexpectedly, see [troubleshooting.md](docs/troubleshooting.md).

package/dist/.a4drules/skills/feature-react-agentforce-conversation-client-embedded-agent/docs/embed-examples.md

@@ -2,16 +2,22 @@
 
 Detailed examples for configuring the Agentforce Conversation Client. All examples use the `AgentforceConversationClient` React component; the underlying `embedAgentforceClient` API accepts the same `agentforceClientConfig` shape.
 
+> **Important:** Every example requires an `agentId`. The component will not render without one. There is no default agent. Replace `"0Xx000000000000AAA"` in every example with the user's actual agent ID.
+
 ---
 
-## Floating mode (default)
+## Floating mode (default rendering mode)
 
-A floating chat widget appears in the bottom-right corner. It starts minimized and expands when the user clicks it. This is the default — no `renderingConfig` is required.
+A floating chat widget appears in the bottom-right corner. It starts minimized and expands when the user clicks it. Floating is the default rendering mode — no `renderingConfig` is needed — but `agentId` is always required.
 
-### Minimal (no config)
+### Minimal
 
 ```tsx
-<AgentforceConversationClient />
+<AgentforceConversationClient
+  agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
+  }}
+/>
 ```
 
 ### Explicit floating
@@ -19,18 +25,19 @@ A floating chat widget appears in the bottom-right corner. It starts minimized a
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     renderingConfig: { mode: "floating" },
   }}
 />
 ```
 
-### Floating with a specific agent and theme
+### Floating with theming
 
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     renderingConfig: { mode: "floating" },
-    agentId: "0Xx000000000000",
     styleTokens: {
       headerBlockBackground: "#032D60",
       headerBlockTextColor: "#ffffff",
@@ -50,6 +57,7 @@ The chat renders inside the parent container at a specific size. Use this when t
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     renderingConfig: { mode: "inline", width: 420, height: 600 },
   }}
 />
@@ -60,6 +68,7 @@ The chat renders inside the parent container at a specific size. Use this when t
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     renderingConfig: { mode: "inline", width: "100%", height: "80vh" },
   }}
 />
@@ -73,6 +82,7 @@ The chat renders inside the parent container at a specific size. Use this when t
   <aside style={{ width: 400 }}>
     <AgentforceConversationClient
       agentforceClientConfig={{
+        agentId: "0Xx000000000000AAA",
         renderingConfig: { mode: "inline", width: "100%", height: "100%" },
       }}
     />
@@ -91,6 +101,7 @@ Use `styleTokens` to customize colors. Tokens are passed directly to the Agentfo
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     styleTokens: {
       headerBlockBackground: "#0176d3",
       headerBlockTextColor: "#ffffff",
@@ -104,6 +115,7 @@ Use `styleTokens` to customize colors. Tokens are passed directly to the Agentfo
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     styleTokens: {
       headerBlockBackground: "#0176d3",
       headerBlockTextColor: "#ffffff",
@@ -118,6 +130,7 @@ Use `styleTokens` to customize colors. Tokens are passed directly to the Agentfo
 ```tsx
 <AgentforceConversationClient
   agentforceClientConfig={{
+    agentId: "0Xx000000000000AAA",
     styleTokens: {
       headerBlockBackground: "#1a1a2e",
       headerBlockTextColor: "#e0e0e0",
@@ -129,40 +142,37 @@ Use `styleTokens` to customize colors. Tokens are passed directly to the Agentfo
 
 ---
 
-## Agent selection
-
-Use `agentId` to load a specific agent from the org. If omitted, the org's default employee agent is used.
-
-### Specific agent by ID
-
-```tsx
-<AgentforceConversationClient
-  agentforceClientConfig={{
-    agentId: "0Xx000000000000",
-  }}
-/>
-```
+## Full layout example
 
-### Agent with inline mode and theming
+Shows the recommended pattern: agent ID passed directly, single render in the app layout.
 
 ```tsx
-<AgentforceConversationClient
-  agentforceClientConfig={{
-    agentId: "0Xx000000000000",
-    renderingConfig: { mode: "inline", width: 400, height: 700 },
-    styleTokens: {
-      headerBlockBackground: "#0176d3",
-      headerBlockTextColor: "#ffffff",
-    },
-  }}
-/>
+import { Outlet } from "react-router";
+import { AgentforceConversationClient } from "@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental";
+
+export default function AppLayout() {
+  return (
+    <>
+      <Outlet />
+      <AgentforceConversationClient
+        agentforceClientConfig={{
+          agentId: "0Xx000000000000AAA",
+          styleTokens: {
+            headerBlockBackground: "#0176d3",
+            headerBlockTextColor: "#ffffff",
+          },
+        }}
+      />
+    </>
+  );
+}
 ```
 
 ---
 
 ## Using the low-level `embedAgentforceClient` API
 
-The React component wraps `embedAgentforceClient`. If you need the raw API (e.g. in a non-React context), the config shape is the same:
+The React component wraps `embedAgentforceClient`. If you need the raw API (e.g. in a non-React context), the config shape is the same — `agentId` is still required:
 
 ```ts
 import { embedAgentforceClient } from "@salesforce/agentforce-conversation-client";
@@ -171,7 +181,7 @@ const { loApp, chatClientComponent } = embedAgentforceClient({
   container: "#agentforce-container",
   salesforceOrigin: "https://myorg.my.salesforce.com",
   agentforceClientConfig: {
-    agentId: "0Xx000000000000",
+    agentId: "0Xx000000000000AAA",
     renderingConfig: { mode: "floating" },
     styleTokens: {
       headerBlockBackground: "#0176d3",

package/dist/.a4drules/skills/feature-react-agentforce-conversation-client-embedded-agent/docs/troubleshooting.md

@@ -0,0 +1,51 @@
+# Troubleshooting
+
+Common issues when using the Agentforce Conversation Client.
+
+---
+
+### Chat widget does not appear
+
+**Cause:** Missing or invalid `agentId`. The component will not render anything without a valid agent ID.
+
+**Solution:**
+
+1. Verify `agentId` is passed in `agentforceClientConfig` — it is required
+2. Confirm the ID is correct (18-character Salesforce record ID, starts with `0Xx`)
+3. Check that the agent exists and is **Active** in **Setup → Agents**
+
+### Chat loads but shows "agent not available"
+
+**Cause:** The agent exists but is not deployed or is inactive.
+
+**Solution:**
+
+1. In **Setup → Agents**, ensure the agent status is **Active**
+2. Verify the agent is deployed to the correct channel
+
+### Authentication error on localhost
+
+**Cause:** `localhost:<PORT>` is not in the org's trusted domains for inline frames.
+
+**Solution:**
+
+1. Go to **Setup → Session Settings → Trusted Domains for Inline Frames**
+2. Add `localhost:<PORT>` (e.g. `localhost:3000`)
+3. Restart the dev server
+
+### Chat fails to authenticate / blank iframe
+
+**Cause:** "Require first party use of Salesforce cookies" is enabled in the org's session settings. This blocks the embedded client from establishing a session.
+
+**Solution:**
+
+1. Go to **Setup → Session Settings**
+2. Find **"Require first party use of Salesforce cookies"**
+3. **Uncheck / disable** this setting
+4. Save and reload the app
+
+### Multiple chat widgets appear
+
+**Cause:** `AgentforceConversationClient` is rendered in multiple places.
+
+**Solution:** Render it once in the app layout, not on individual pages. The component uses a singleton pattern — only one instance should exist per window.

package/dist/CHANGELOG.md

@@ -3,6 +3,22 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [1.81.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.80.1...v1.81.0) (2026-03-09)
+
+**Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental
+
+
+
+
+
+## [1.80.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.80.0...v1.80.1) (2026-03-09)
+
+**Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental
+
+
+
+
+
 # [1.80.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.79.2...v1.80.0) (2026-03-07)
 
 **Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental

package/dist/force-app/main/default/classes/MaintenanceRequestTriggerHandler.cls

@@ -0,0 +1,66 @@
+public with sharing class MaintenanceRequestTriggerHandler {
+
+    /**
+     * Handles before insert logic for Maintenance Request records
+     * Automatically assigns workers based on request type and updates status to Assigned
+     */
+    public static void handleBeforeInsert(List<Maintenance_Request__c> newRequests) {
+        // Map to store request type to worker type mappings
+        Map<String, String> requestTypeToWorkerType = new Map<String, String>{
+            'Plumbing' => 'Plumbing',
+            'Electrical' => 'Electrical',
+            'HVAC' => 'HVAC (Heating & Cooling)',
+            'Appliance' => 'Appliance Repair',
+            'Pest' => 'Pest Control'
+        };
+
+        // Collect unique worker types needed
+        Set<String> workerTypesNeeded = new Set<String>();
+        for (Maintenance_Request__c request : newRequests) {
+            if (request.Type__c != null && requestTypeToWorkerType.containsKey(request.Type__c)) {
+                workerTypesNeeded.add(requestTypeToWorkerType.get(request.Type__c));
+            }
+        }
+
+        // Query for available workers by type
+        Map<String, List<Maintenance_Worker__c>> workersByType = new Map<String, List<Maintenance_Worker__c>>();
+        if (!workerTypesNeeded.isEmpty()) {
+            for (Maintenance_Worker__c worker : [
+                SELECT Id, Name, Type__c, Rating__c
+                FROM Maintenance_Worker__c
+                WHERE Type__c IN :workerTypesNeeded
+                AND IsActive__c = true
+                ORDER BY Rating__c DESC NULLS LAST, Name ASC
+            ]) {
+                if (!workersByType.containsKey(worker.Type__c)) {
+                    workersByType.put(worker.Type__c, new List<Maintenance_Worker__c>());
+                }
+                workersByType.get(worker.Type__c).add(worker);
+            }
+        }
+
+        // Assign workers to requests
+        for (Maintenance_Request__c request : newRequests) {
+            // Only process requests with 'New' status (or null, since 'New' is the default)
+            if ((request.Status__c == 'New' || request.Status__c == null) &&
+                request.Type__c != null && requestTypeToWorkerType.containsKey(request.Type__c)) {
+                String workerType = requestTypeToWorkerType.get(request.Type__c);
+
+                // Check if we have available workers for this type
+                if (workersByType.containsKey(workerType) && !workersByType.get(workerType).isEmpty()) {
+                    // Assign the first available worker (highest rated)
+                    Maintenance_Worker__c assignedWorker = workersByType.get(workerType).get(0);
+                    request.Assigned_Worker__c = assignedWorker.Id;
+                    request.Status__c = 'Assigned';
+
+                    // Set scheduled date to 3 days from now
+                    request.Scheduled__c = DateTime.now().addDays(3);
+
+                    // Rotate worker to end of list for round-robin assignment
+                    workersByType.get(workerType).remove(0);
+                    workersByType.get(workerType).add(assignedWorker);
+                }
+            }
+        }
+    }
+}

package/dist/force-app/main/default/classes/MaintenanceRequestTriggerHandler.cls-meta.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
+    <apiVersion>65.0</apiVersion>
+    <status>Active</status>
+</ApexClass>

package/dist/force-app/main/default/classes/MaintenanceRequestTriggerHandler_Test.cls

@@ -0,0 +1,308 @@
+/**
+ * Test class for MaintenanceRequestTriggerHandler
+ * Validates automatic worker assignment, status updates to Assigned, and scheduled date setting
+ */
+@isTest
+private class MaintenanceRequestTriggerHandler_Test {
+
+    /**
+     * Setup test data for all test methods
+     */
+    @testSetup
+    static void setupTestData() {
+        // Create test maintenance workers with different specialties
+        List<Maintenance_Worker__c> workers = new List<Maintenance_Worker__c>{
+            new Maintenance_Worker__c(
+                Name = 'John Plumber',
+                Type__c = 'Plumbing',
+                IsActive__c = true,
+                Rating__c = 4.5,
+                Phone__c = '555-0001'
+            ),
+            new Maintenance_Worker__c(
+                Name = 'Jane Electrician',
+                Type__c = 'Electrical',
+                IsActive__c = true,
+                Rating__c = 4.8,
+                Phone__c = '555-0002'
+            ),
+            new Maintenance_Worker__c(
+                Name = 'Bob HVAC',
+                Type__c = 'HVAC (Heating & Cooling)',
+                IsActive__c = true,
+                Rating__c = 4.2,
+                Phone__c = '555-0003'
+            ),
+            new Maintenance_Worker__c(
+                Name = 'Alice Appliance',
+                Type__c = 'Appliance Repair',
+                IsActive__c = true,
+                Rating__c = 4.7,
+                Phone__c = '555-0004'
+            ),
+            new Maintenance_Worker__c(
+                Name = 'Charlie Pest',
+                Type__c = 'Pest Control',
+                IsActive__c = true,
+                Rating__c = 4.3,
+                Phone__c = '555-0005'
+            ),
+            new Maintenance_Worker__c(
+                Name = 'Inactive Worker',
+                Type__c = 'Plumbing',
+                IsActive__c = false,
+                Rating__c = 5.0,
+                Phone__c = '555-0006'
+            )
+        };
+        insert workers;
+    }
+
+    /**
+     * Test that plumbing requests are assigned to plumbing workers
+     */
+    @isTest
+    static void testPlumbingRequestAssignment() {
+        // Query for plumbing worker
+        Maintenance_Worker__c plumber = [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'Plumbing' AND IsActive__c = true LIMIT 1];
+
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'Plumbing',
+            Description__c = 'Leaky faucet in bathroom',
+            Priority__c = 'Standard'
+        );
+        insert request;
+        Test.stopTest();
+
+        // Verify assignment
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c, Scheduled__c, Type__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(plumber.Id, insertedRequest.Assigned_Worker__c, 'Worker should be assigned');
+        System.assertEquals('Assigned', insertedRequest.Status__c, 'Status should be Assigned');
+        System.assertNotEquals(null, insertedRequest.Scheduled__c, 'Scheduled date should be set');
+
+        // Verify scheduled date is approximately 3 days from now (within 1 minute tolerance)
+        DateTime expectedDate = DateTime.now().addDays(3);
+        Long timeDiff = Math.abs(insertedRequest.Scheduled__c.getTime() - expectedDate.getTime());
+        System.assert(timeDiff < 60000, 'Scheduled date should be 3 days from now');
+    }
+
+    /**
+     * Test that electrical requests are assigned to electrical workers
+     */
+    @isTest
+    static void testElectricalRequestAssignment() {
+        Maintenance_Worker__c electrician = [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'Electrical' AND IsActive__c = true LIMIT 1];
+
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'Electrical',
+            Description__c = 'Outlet not working',
+            Priority__c = 'High (Same Day)'
+        );
+        insert request;
+        Test.stopTest();
+
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(electrician.Id, insertedRequest.Assigned_Worker__c, 'Electrician should be assigned');
+        System.assertEquals('Assigned', insertedRequest.Status__c, 'Status should be Assigned');
+    }
+
+    /**
+     * Test that HVAC requests are assigned to HVAC workers
+     */
+    @isTest
+    static void testHVACRequestAssignment() {
+        Maintenance_Worker__c hvacWorker = [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'HVAC (Heating & Cooling)' AND IsActive__c = true LIMIT 1];
+
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'HVAC',
+            Description__c = 'AC not cooling',
+            Priority__c = 'High (Same Day)'
+        );
+        insert request;
+        Test.stopTest();
+
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(hvacWorker.Id, insertedRequest.Assigned_Worker__c, 'HVAC worker should be assigned');
+        System.assertEquals('Assigned', insertedRequest.Status__c, 'Status should be Assigned');
+    }
+
+    /**
+     * Test that appliance requests are assigned to appliance repair workers
+     */
+    @isTest
+    static void testApplianceRequestAssignment() {
+        Maintenance_Worker__c applianceWorker = [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'Appliance Repair' AND IsActive__c = true LIMIT 1];
+
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'Appliance',
+            Description__c = 'Dishwasher not draining',
+            Priority__c = 'Standard'
+        );
+        insert request;
+        Test.stopTest();
+
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(applianceWorker.Id, insertedRequest.Assigned_Worker__c, 'Appliance worker should be assigned');
+        System.assertEquals('Assigned', insertedRequest.Status__c, 'Status should be Assigned');
+    }
+
+    /**
+     * Test that pest requests are assigned to pest control workers
+     */
+    @isTest
+    static void testPestRequestAssignment() {
+        Maintenance_Worker__c pestWorker = [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'Pest Control' AND IsActive__c = true LIMIT 1];
+
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'Pest',
+            Description__c = 'Ants in kitchen',
+            Priority__c = 'Standard'
+        );
+        insert request;
+        Test.stopTest();
+
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(pestWorker.Id, insertedRequest.Assigned_Worker__c, 'Pest control worker should be assigned');
+        System.assertEquals('Assigned', insertedRequest.Status__c, 'Status should be Assigned');
+    }
+
+    /**
+     * Test bulk insert with multiple request types
+     */
+    @isTest
+    static void testBulkRequestAssignment() {
+        Test.startTest();
+        List<Maintenance_Request__c> requests = new List<Maintenance_Request__c>{
+            new Maintenance_Request__c(Type__c = 'Plumbing', Description__c = 'Leak 1', Priority__c = 'High (Same Day)'),
+            new Maintenance_Request__c(Type__c = 'Electrical', Description__c = 'Issue 1', Priority__c = 'Standard'),
+            new Maintenance_Request__c(Type__c = 'Plumbing', Description__c = 'Leak 2', Priority__c = 'Standard'),
+            new Maintenance_Request__c(Type__c = 'HVAC', Description__c = 'AC Issue', Priority__c = 'High (Same Day)'),
+            new Maintenance_Request__c(Type__c = 'Appliance', Description__c = 'Fridge Issue', Priority__c = 'Standard')
+        };
+        insert requests;
+        Test.stopTest();
+
+        List<Maintenance_Request__c> insertedRequests = [
+            SELECT Id, Assigned_Worker__c, Status__c, Type__c
+            FROM Maintenance_Request__c
+            WHERE Id IN :requests
+        ];
+
+        // Verify all requests were assigned
+        for (Maintenance_Request__c req : insertedRequests) {
+            System.assertNotEquals(null, req.Assigned_Worker__c, 'All requests should have assigned workers');
+            System.assertEquals('Assigned', req.Status__c, 'All requests should be Assigned');
+        }
+
+        System.assertEquals(5, insertedRequests.size(), 'All 5 requests should be inserted');
+    }
+
+    /**
+     * Test that requests without type are not assigned
+     */
+    @isTest
+    static void testRequestWithoutType() {
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Description__c = 'General maintenance',
+            Priority__c = 'Standard'
+        );
+        insert request;
+        Test.stopTest();
+
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(null, insertedRequest.Assigned_Worker__c, 'Worker should not be assigned without type');
+    }
+
+    /**
+     * Test that inactive workers are not assigned
+     */
+    @isTest
+    static void testInactiveWorkerNotAssigned() {
+        // Delete all active plumbing workers
+        delete [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'Plumbing' AND IsActive__c = true];
+
+        Test.startTest();
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'Plumbing',
+            Description__c = 'Emergency leak',
+            Priority__c = 'High (Same Day)'
+        );
+        insert request;
+        Test.stopTest();
+
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(null, insertedRequest.Assigned_Worker__c, 'Inactive worker should not be assigned');
+    }
+
+    /**
+     * Test that requests with non-New status are not automatically processed
+     */
+    @isTest
+    static void testNonNewStatusNotProcessed() {
+        // Query for plumbing worker
+        Maintenance_Worker__c plumber = [SELECT Id FROM Maintenance_Worker__c WHERE Type__c = 'Plumbing' AND IsActive__c = true LIMIT 1];
+
+        Test.startTest();
+        // Create a request with status explicitly set to 'In Progress'
+        Maintenance_Request__c request = new Maintenance_Request__c(
+            Type__c = 'Plumbing',
+            Description__c = 'Manually assigned request',
+            Priority__c = 'Standard',
+            Status__c = 'In Progress'
+        );
+        insert request;
+        Test.stopTest();
+
+        // Verify the request was not processed by trigger (no worker assigned)
+        Maintenance_Request__c insertedRequest = [
+            SELECT Id, Assigned_Worker__c, Status__c, Scheduled__c
+            FROM Maintenance_Request__c
+            WHERE Id = :request.Id
+        ];
+
+        System.assertEquals(null, insertedRequest.Assigned_Worker__c, 'Worker should not be auto-assigned for non-New status');
+        System.assertEquals('In Progress', insertedRequest.Status__c, 'Status should remain as originally set');
+        System.assertEquals(null, insertedRequest.Scheduled__c, 'Scheduled date should not be set by trigger');
+    }
+}

package/dist/force-app/main/default/classes/MaintenanceRequestTriggerHandler_Test.cls-meta.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
+    <apiVersion>65.0</apiVersion>
+    <status>Active</status>
+</ApexClass>

package/dist/force-app/main/default/objects/Application__c/fields/Status__c.field-meta.xml

@@ -27,6 +27,11 @@
                 <default>false</default>
                 <label>Background Check</label>
             </value>
+            <value>
+                <fullName>Under Review</fullName>
+                <default>false</default>
+                <label>Under Review</label>
+            </value>
             <value>
                 <fullName>Approved</fullName>
                 <default>false</default>

package/dist/force-app/main/default/objects/Maintenance_Request__c/fields/Assigned_Worker__c.field-meta.xml

@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<CustomField xmlns="http://soap.sforce.com/2006/04/metadata">
+    <fullName>Assigned_Worker__c</fullName>
+    <deleteConstraint>SetNull</deleteConstraint>
+    <description>The maintenance worker assigned to handle this request</description>
+    <externalId>false</externalId>
+    <label>Assigned Worker</label>
+    <referenceTo>Maintenance_Worker__c</referenceTo>
+    <relationshipLabel>Maintenance Requests</relationshipLabel>
+    <relationshipName>Maintenance_Requests</relationshipName>
+    <required>false</required>
+    <trackHistory>true</trackHistory>
+    <trackTrending>false</trackTrending>
+    <type>Lookup</type>
+</CustomField>

package/dist/force-app/main/default/permissionsets/Property_Management_Access.permissionset-meta.xml

@@ -272,6 +272,11 @@
         <field>Maintenance_Request__c.Tenant_Home__c</field>
         <readable>true</readable>
     </fieldPermissions>
+    <fieldPermissions>
+        <editable>true</editable>
+        <field>Maintenance_Request__c.Assigned_Worker__c</field>
+        <readable>true</readable>
+    </fieldPermissions>
 
     <!-- Field Permissions: Maintenance_Worker__c -->
     <fieldPermissions>
@@ -363,12 +368,6 @@
         <readable>true</readable>
     </fieldPermissions>
 
-    <!-- Tab Visibility -->
-    <tabSettings>
-        <tab>Property__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-
     <fieldPermissions>
         <editable>true</editable>
         <field>Agent__c.License_Expiry__c</field>
@@ -633,50 +632,4 @@
         <field>Tenant__c.Status__c</field>
         <readable>true</readable>
     </fieldPermissions>
-
-    <!-- Tab Settings -->
-    <tabSettings>
-        <tab>Application__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>KPI_Snapshot__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Lease__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Maintenance_Request__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Maintenance_Worker__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Notification__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Payment__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Property__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Property_Owner__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Property_Sale__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
-    <tabSettings>
-        <tab>Tenant__c</tab>
-        <visibility>Visible</visibility>
-    </tabSettings>
 </PermissionSet>

package/dist/force-app/main/default/triggers/MaintenanceRequestTrigger.trigger

@@ -0,0 +1,5 @@
+trigger MaintenanceRequestTrigger on Maintenance_Request__c (before insert) {
+    if (Trigger.isBefore && Trigger.isInsert) {
+        MaintenanceRequestTriggerHandler.handleBeforeInsert(Trigger.new);
+    }
+}

package/dist/force-app/main/default/triggers/MaintenanceRequestTrigger.trigger-meta.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ApexTrigger xmlns="http://soap.sforce.com/2006/04/metadata">
+  <apiVersion>65.0</apiVersion>
+  <status>Active</status>
+</ApexTrigger>

package/dist/force-app/main/default/webapplications/appreactsampleb2x/package.json

@@ -15,8 +15,8 @@
     "graphql:schema": "node scripts/get-graphql-schema.mjs"
   },
   "dependencies": {
-    "@salesforce/sdk-data": "^1.80.0",
-    "@salesforce/webapp-experimental": "^1.80.0",
+    "@salesforce/sdk-data": "^1.81.0",
+    "@salesforce/webapp-experimental": "^1.81.0",
     "@tailwindcss/vite": "^4.1.17",
     "@tanstack/react-form": "^1.28.4",
     "@types/leaflet": "^1.9.21",
@@ -43,7 +43,7 @@
     "@graphql-eslint/eslint-plugin": "^4.1.0",
     "@graphql-tools/utils": "^11.0.0",
     "@playwright/test": "^1.49.0",
-    "@salesforce/vite-plugin-webapp-experimental": "^1.80.0",
+    "@salesforce/vite-plugin-webapp-experimental": "^1.81.0",
     "@testing-library/jest-dom": "^6.6.3",
     "@testing-library/react": "^16.1.0",
     "@testing-library/user-event": "^14.5.2",

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-base-sfdx-project-experimental",
-  "version": "1.80.0",
+  "version": "1.81.0",
   "description": "Base SFDX project template",
   "private": true,
   "files": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-app-react-sample-b2x-experimental",
-  "version": "1.80.0",
+  "version": "1.81.0",
   "description": "B2C sample app template with app shell",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",