Warranty Workflow

This page ties together the Service Requests and Service Orders concepts into the workflow your CSRs and trades actually live in.

At a glance

• Three actors: Homeowner (Home Owner Portal), CSR (Blazor Warranty), Trade (Trade Portal).
• Homeowner submits → CSR triages and creates lines → CSR dispatches a Service Order → Trade schedules and completes → BC pays.
• Lien waivers and BC payment use the same pipeline as construction POs — no second integration to maintain.
• Aging is tracked by LateAfter thresholds per request type — CSR aging dashboard at Blazor Warranty Pages/AgingItems/.

The full warranty cycle

   Homeowner                 CSR (Blazor Warranty)             Trade (Trade Portal)
   ──────────                ───────────────────────           ─────────────────────

   1. Submit SR  ────►  2. Triage; create lines ─────►   3. Get Service Order
      (HOP)             (statuses: o, q, d, r)               (work-orders.aspx)
                                  │
                                  ▼
                         4. Confirm date / amount  ◄────  5. Schedule visit
                                  │                         + ConfirmVendor=1
                                  ▼
                         6. Mark line Completed (c)  ◄──   7. Do the work
                                  │                         + upload lien waiver
                                  ▼
                                                            8. BC pays vendor
                                                            (TransmissionPaymentStatus)

Where homeowner-facing behavior lives

• Submit a request: Warranty.aspx and Warranty-imageUpload.aspx in the Home Owner Portal.
• See status: Warranty.aspx lists the homeowner’s requests with line statuses.
• Photos: uploaded via Warranty-imageUpload.aspx, stored under Service/ and surfaced via ServiceRequestFile.

Where CSRs work

• Triage queue: Blazor Warranty ServiceRequests/Index page.
• One-request workspace: Blazor ServiceRequests/Detail to add lines, notes, status changes.
• Order dispatch: Blazor ServiceOrders/Create selects vendor and amount.
• Aging: Pages/AgingItems/ shows lines exceeding their LateAfter threshold by request type.

Where trades work

• Open SOs: work-orders.aspx and work-order-search.aspx in the Trade Portal.
• Scheduling: schedule.aspx reflects the SO ScheduledDate.
• Payment: identical to construction — lien waiver via lien-wavers.aspx, BC pays via TransmissionBill* queues.

Reporting

The five reporting views you’ll actually use:

All warranty reporting views and their consumers

View	Used by
vwServiceRequest	CSR list
vwLotServiceRequests	Field — what’s open on this lot
vwContactsServiceRequests	Sales — what’s open for this homeowner
vwServiceOrderManagement	Manager dashboard
vwServiceOrdersNotCompleted	Aging / past-due