Not Finished Yet — IM2 Open Items

What this page is

The working to-do list: things that are built but not finished, or built and never switched on. Each line comes off this page when it is done. Every line has a permanent number (TD-nn) for referencing — numbers are never reused once a line comes off. Anything that is only worth knowing about lives in the help page for that screen, not here. Each line ends with the owner — who has to act next.

Order of work (Dave, 2026-09-06): this month is automatic PO creation and finishing the rush alerts. TD-12 through TD-15 (stock replenishment, truck stock, RMA tracking and their QuickBooks setup) are ON HOLD until the dust settles — no work on them until Dave says otherwise.

Posting material issues to QuickBooks

This section is only about posting picked material to QuickBooks — the inventory side. New and changed items do post to QuickBooks from Create New Inventory Item and Item Master Display; that part works.

• TD-01. Posting is switched off for everybody. Post selected and post on Pick Review & Posting, and Post now on Pick List, are greyed whenever Settings → Allow Inventory Posting to QB is No (the default). Picks still save and still queue up; nothing has ever reached QuickBooks from the screens, so the whole post path is untested in real use. (Viktor — build; Dave — decides when posting goes live)
• TD-02. Using surplus material. The posting code already handles a line type of SURPLUS (it consumes the RO line and writes no QuickBooks document at all), but nothing on the pick screens can mark a line that way, so it never happens. Decided with Dave 2026-09-06: on the PC pick list only, a surplus line shows with SKU SURPLUS and the item description; entering a quantity updates the RO picked quantity and does nothing else — no QuickBooks document, no inventory movement. Handhelds do not offer it. (Viktor)
• TD-17. "Use surplus" as a resolution on RO Import Issues to Resolve (non-inventory lines). Tested on RO 799007 — the option is not offered. Choosing it should mark the line surplus so it is left off the buy list / Purchasing Workbench entirely, and make it show as the SURPLUS line on the PC pick list (TD-02). (Viktor)

Purchase orders

• TD-03. Create POs does not create anything. On a buy list it is a placeholder. The Allow Auto-Create POs setting only changes the wording on that screen; no purchase order is ever written to QuickBooks. (Viktor)
• TD-04. "Ordered" status on a buy list never appears, because nothing stamps a buy list as released — that is the same on-hold work as Create POs. (Viktor)
• TD-05. You cannot type a line onto a buy list by hand. Every line comes from RO demand, so a non-inventory item, a freight charge or a one-off buy that is not on an RO cannot be added to the buy list and cannot be linked to the PO. Dave 2026-09-06: parked — adding the non-inventory item to the RO by hand puts it on the Purchasing Workbench, and it can be released on a buy list from there. That will suffice for now. (no action)
• TD-06. The "your rush order has been ordered" text message is written and ready but is never sent, because there is no real PO-release event to trigger it. (Viktor)

Getting orders in

• TD-07. Nothing runs on a schedule. The FieldPulse "Pending Material" watcher that fills the RO Inbox is run by hand; there is no hourly job yet. The Allow Auto-FP Watcher setting exists but nothing reads it. (Viktor)
• TD-08. BuilderTrend BOMs. BT has no connection to the app, and imports can only pick from BOM files someone has already copied in. Dave 2026-09-06: for now the BT BOM spreadsheet gets dropped into the manual RO import. Getting BT BOMs in automatically stays open as a technical issue for Jeff and Dave to resolve. (Jeff + Dave)

Setup and switches

• TD-09. Put the menus behind the sign-in. The Handheld Menu is served as a plain file with no sign-in, so anyone with the address sees the tile names (and these manuals). Nothing behind a tile opens without signing in, so no data is exposed, but the menus should still be gated. (Viktor)
• TD-10. Rush alerts to Slack still go nowhere. The switch is on, but the channel address (webhook) has never been set up, so every Slack rush alert is dropped. It is now recorded on the order's history as not delivered, and the tech is told to call purchasing. Needs someone with Slack admin to create it. (Jeff — Slack admin)
• TD-11. Rush alerts by text are ready but switched off. The texting account is wired up; it needs Text rush alerts turned on in System Controls and at least one active rush contact. Dave 2026-09-06: Jeff and Alex Tipton go on the rush contact list; Dave turns texting on once Jeff decides. The rush contact table is still empty and no mobile numbers are on file for either of them — Viktor needs the two numbers to add them. (Dave — numbers, then the switch; Jeff — decision)

Not built yet — new programs

• TD-12. Stock replenishment orders, PC and handheld. A combination of a cycle count and Create RO, on the handheld and on the desktop: count what is on the shelf, and turn what is short into a Requirements Order without retyping it. (Dave — design, then Viktor)
• TD-13. Truck stock program (Dave's overview, 2026-09-06). Per-truck SKU list with Min/Max, a default truck per sign-in name with its own truck job, and copying a list between trucks. Create RO uses an SA Truck customer and the truck job, so replenishing a truck is an ordinary RO. Plus:
• Truck Issue to Job handheld screen — from (defaults to the signed-in person's truck job) and to (a QuickBooks job), prompt SKU and quantity, save for later or post; posting writes a credit memo and an invoice for the items.
• Truck Cycle Count handheld screen — scan SKU, show calculated on hand (issued to truck less issued to job), enter the real count, and issue the difference from the truck job to a default admin job referenced Truck stock write off.
• Reports: transactions by SKU for a truck job (issued to truck, issued to job, balance); a replenish quantity report off calculated on hand against Min/Max; and truck stock write-offs by truck for a date range. (Viktor — October)
• TD-14. RMA tracking. Not sketched out yet. (Dave — sketch it out)
• TD-15. QuickBooks setup the truck program needs first. Create the SA Truck customer and a truck job for each truck. Write-offs post to the job named in the Admin job setting in System Controls (seeded with Admin, validated as an active QuickBooks customer or job when saved — Dave, 2026-09-06). Nothing on the truck screens can be built until the SA Truck customer and truck jobs exist in QuickBooks. (Dave)

Also waiting on Dave

• TD-16. Required date on a FieldPulse-imported Requirements Order. FieldPulse jobs carry no need-by date. Decided by Dave 2026-09-06: required date = import date + a lead time that depends on the RO's class — Service 3, Residential 10, Commercial 15 — in work days. The three settings are live in System Controls, named by class, and every lead-time setting says work days. Company holidays is now a System Controls list of holiday names (eleven federal holidays plus Mardi Gras); the date for each year is computed, so the list never needs re-entering, and those days are skipped by both RO required dates and Purchasing Workbench delivery dates. Still to build: reading the class at import and stamping the required date. No back-fill needed — the existing ROs are test data Dave may delete and re-import. (Viktor)

Values still fixed in code that arguably belong in System Controls

• TD-18. Found while wiring the Admin job into System Controls (Dave, 2026-09-06 — "I try not to hard code anything"). None of these break anything today; each is a decision about where it should live:
• The QuickBooks class ids each RO class posts with (Residential/Commercial/Service) are written into the posting and picking code. The class names are already a settings list, so a class renamed or rebuilt in QuickBooks would need a code change to post correctly.
• The four RO types (Residential, Commercial, Service, Truck) are fixed in three places in code and in a database CHECK constraint, so this one cannot become a setting without a database change.
• The class list on the import screen is the class, not the RO type, and Administration is a valid class — correct as built (Dave confirmed 2026-09-06). It reads the RO classes setting; the four names in code are only the fallback if Settings can't be read. Nothing to change.
• Rush Requirements Orders are forced to type Service regardless of what they are for.
• The income, expense and inventory-asset QuickBooks accounts are settings, but their internal account ids are hidden and can only be changed by a deploy. (Dave — decide which to move; Viktor — move them)