Support and legacy fixes

How a request is handled

Requests come in through a Slack channel. Each one gets a card, the person who asked hears back with what I think is wrong and how long it will take, and nothing in production changes without my lead’s go-ahead. A record with transactions is never deleted, only made inactive. When the work is done, the card says what was found and what was changed.

What the requests are

Most are orders and billing: an order that will not bill, an invoice that came out empty, a bill-to address that stayed on the old customer. Then duplicate customers to merge, saved searches and reports, roles and permissions. A fair share turn out not to be bugs at all. An invoice came out empty because the order was already billed and only zero value lines were left; an Edit button was missing because the person was signed in with the wrong role. Then the fix is to explain what the system did.

Legacy scripts, fixed at the cause

• Saving a quote showed an unreadable error, so people typed their work in again. An after save script was throwing its own failure after the record had already saved, and the email it was meant to send had stopped as well.
• The service report button emailed raw reports, internal notes included, to a partner programme’s inbox. It now checks where it is sending first.
• Two date fields vanished in edit mode for some users, because a client script’s lookup ran with their permissions and failed without a word.
• The evaluator on an order filled itself in with whoever was last on site. It now stays empty on programme departments and never overwrites a person’s choice.
• A script put a water heater’s serial number where the job address belonged on the scheduling board. Fixed in the script, and the affected orders and cases corrected.
• The AI intake kept setting a type of sale that blocked fulfilment and billing. A guard now corrects it before save, after running in log only mode on real orders first.
• The dispatch board showed the customer and hid the job address, so programme jobs read as the wrong person. The address now sits under the name.
• Expired quotes vanished from the permit queue because of a rule in a shared search. The permit team got a copy without that rule, and the original was left alone.

What it includes

1. Duplicate customers and orders merged, history kept
2. Billing problems traced to the cause, not patched over
3. Inherited scripts fixed where they failed quietly
4. Guards that stop a known bad value before it is saved
5. Saved searches, roles and permissions on request