Raise, assign and track technical requests

Both Requests and My Requests open pre-filtered to My Tasks and Active — so the Requests menu also shows only requests you manage until you remove the My Tasks filter from the search bar. To see the whole queue, clear that filter; to load-balance a team, group by Manager or use the left search panel, which filters by Stage, Technical Request Type, Team and Manager with live counters.

Six views are available: kanban (default, grouped by stage, quick-create on), list, calendar (by deadline, colored by stage), pivot, graph and form. The list shows each request's name, customer, manager, technical team, request type, deadline and priority, and totals the Planned and Spent hours at the bottom — the same two measures the pivot and graph slice.

Search filters worth knowing: Unassigned (no manager), High Priority, Urgent, Blocked, Overdue, Deadline Today, Deadline This Week, and Archived. A request counts as Overdue when its deadline has passed and its stage is not a folded (closed) one.

The header carries the stage bar (click a stage to move the request) and the kanban-state selector. An OVERDUE ribbon appears once the deadline is missed. The main groups:

The name, customer, sale order, stage, kanban state, priority and planned hours are tracked — every change to them is logged in the chatter. The deadline itself is not tracked; note deadline changes in a chatter message when the history matters.

Survey & Measurements tab

The first tab is the survey journey hub. It shows the journey phase bar (Opportunity › Pre-Quote Survey › Quotation › Won › Production Survey › Production), status cards for the pre-quote and production surveys, a progress bar, and one Run Step button that always performs the suggested next step. Around it sit the explicit buttons: Schedule Pre-Quote / Open Pre-Quote, New Pre-Quote (offered only once the current pre-quote is Completed or Approved), Schedule Production Survey / Open Production Survey, Create Quotation and Release to Production (each appears only when it is the suggested step), and View All Previous Surveys. Below, once at least one survey exists, a read-only Previous Surveys list shows every linked survey with its type, surveyor, progress and state. All of these buttons require the Survey User access right.

Time Sheet tab

Four cards summarise the effort: Planned (editable — the budget), Spent (sum of the entries below), Remaining (planned minus spent, never negative) and Entries. Under them, a progress bar shows spent as a percentage of planned, capped at 100%, and an inline list records the entries themselves — Date, Employee, Description, Hours. Logging the first entry on a request still in New silently moves it to In Progress.

Team Members tab

A simple crew list — Employee, Role, Assigned Hours, Start and End — plus an Add Team Member button that opens a small dialog for the same fields. Team members listed here are informational; hours assigned to a member are not checked against the timesheet entries.

Contact Information and Additional Information tabs

Contact Information holds the on-site contact: Contact plus its read-only email and phone, and a secondary Co contact. Additional Information keeps the request-type description snapshot, the kanban Color, the Sequence, and the created/updated audit fields.

Customer Location tab

Geolocation for the visit. Enter Latitude and Longitude directly, click or drag the marker on the interactive map, or use the buttons:

Once both coordinates are set the tab also shows the Google Maps URL and a QR code a driver can scan. The address block itself is the customer's address, editable here and written through to the customer record.

When a request is created, WindoorERP can schedule a to-do activity — "Assign technician for …" — on one designated technical manager. This fires only when an administrator has set the system parameter sale_order_line_input.technical_manager_user_id to that user's id; without it, creating a request notifies nobody. The companion parameter sale_order_line_input.notify_technical_manager (default on) switches the behaviour off without losing the configured user.

"Start date must be before end date." — the Planning dates are crossed; fix either date.

"Please select a Customer on the opportunity before creating a technical request." (or the sale-order variant) — the source document has no customer; set one first.

A request has no TR reference — it was created with the New button instead of the request dialog. The reference cannot be added later; if the number matters, raise the request from its opportunity or order.

New requests notify nobody — the technical-manager system parameter is not set; see Assignment notifications above.

The Requests menu looks empty although requests exist — the My Tasks default filter is hiding other managers' requests; remove it in the search bar.