What we shipped, in plain language.

The assignee name reached for a field the list query did not fetch, so every row paid a second database round trip — and when that re-fetch found nothing, the whole list raised an error instead of rendering. Serving a 78-task project now costs four queries.

Department is now a visible column on the task worksheet, and every other field the task list can answer is added alongside it — hidden by default and reachable from the column chooser, so the default sheet stays the width it was.

What that adds: assignment (department, role), the dates the plan actually moved on (revised end, actual start and end), ordering and verification, the scheduling pass’s own output (earliest and latest start and finish, total and free float, weight) and provenance (WBS element, task definition, generation date). The new columns are deliberately read-only: a column that looks editable but is dropped on save is worse than one that plainly is not.

A help-documentation seed named a field that lives on a different record, and the chart-of-accounts seed checked for an existing chart by its filing type — which misses a tenant whose chart is filed under an older type code, and then collided with the accounts that tenant already owned.

The chart seed now works out every code it would write and stops if any of them already exists, which is what it always claimed to do. Neither change touches an existing row.

The employment application and job request forms take their second language from the applicant’s mother tongue. Gujarati was selectable as a mother tongue but held no labels, and an unheld language falls back to the default — so a Gujarati applicant was handed the Tamil form and nothing reported it.

The form embeds the typeface it asks for, so the Gujarati face ships with it. Without that the form prints correctly on a developer’s machine and renders every second line blank on the print server. A test now asserts that every language in the catalogue has its face on disk, rather than leaving that to be discovered on paper.

The delivery detail page switches to the colour and size matrix as soon as any item on the note has a variant, and then sends every line to it. A line with no variant matched no cell: it rendered nowhere, could not be edited, and was absent from the grand total — while the header, which sums every item, still counted it. One note read 7,738 in the header and 2,515 in the grid.

Items are now placed through a map that consumes each item exactly once. Whatever cannot be placed — no variant, a missing row or column attribute, or a second line landing on a cell another line already holds — is collected and shown below the grid in a flagged, editable table with its own subtotal, plus a combined product total.

The page also gained a Lines total chip summing every item including unsaved edits, and shows an amber Header says… chip when the two disagree, so a mismatch is visible rather than silent.

A marker is now linked to the production orders it is being cut for, with each order’s own quantities visible while the marker is planned. The marker form and list were rebuilt around that link, and production planning answers the order and quantity lookups the form needs.

The adjustment entry that carries the difference between what the timers logged and the total a supervisor states now stores whether it adds or removes time, rather than leaving that to be inferred from the figures around it.

A new scheduled report sends each person their own timesheet for the day: the tasks they worked, the hours booked against each, and what remains open. It is a real schedule like any other report — it can be re-timed, paused or removed.

Its audience comes from the data, not the schedule: whoever booked time that day is who receives a mail, so nobody has to be added to a recipient list when they join and nobody keeps receiving an empty sheet when they leave.

The Leads grid fetched the whole table and then paged, sorted and searched it in the browser, so the wait to open the screen grew with every lead ever created. Paging, sorting, searching and column filters are now answered by the server, and the screen opens as quickly on the thousandth lead as on the first.

The task list shares the change, and both grids keep their Excel export over the whole result set rather than the page on screen.

The posting service looked for a wage type code that no catalogue has ever contained, so the balancing net-pay leg could never be mapped however carefully the mapping table was filled in. It now reads 9920 Net Pay, which has been in the standard catalogue since the payroll engine shipped.

Creating a second wage type meaning “net pay” would have left two codes for one concept and an even chance of an operator mapping the wrong one.

A GL mapping takes effect from the day it is created, so a mapping added while closing last month’s payroll is dated after the period end and is correctly filtered out — but the refusal then said the wage type was not mapped while the operator was looking straight at the mapping they had just saved.

The message now names the effective window and says to widen it, rather than inviting a second mapping row that will not help either.

The chart of accounts came only from a command run by hand per tenant, and three production tenants had never had it run — which blocks GL account creation outright, because an account has to hang off a chart. The deploy now seeds it.

It seeds only into an empty chart. The shipped template is not the only chart in use, codes collide across standards, and renumbering a chart that already carries posted journals is a supervised act — not something a deploy may do behind the operator’s back.

Two answers to “what is a working day” were live in the product and they disagreed. Leave counted Monday to Friday and ignored holidays and the published roster; payroll already used the proper ladder. An employee whose three-day sick leave deducted three days of quota but two days of pay was a dispute the system could not answer.

There is now one definition, shared by leave and payroll: the published roster first, then the plant’s weekly pattern less that plant’s holidays, and only then the plain calendar fallback — and each answer says which rung it came from.

Until now an absence could only be entered by the employee, through self-service. On a factory floor that is the wrong way round: absence is observed, not applied for, and many of the people it happens to have no login. The only way in was the raw database admin, which writes the row with no duration, no quota deduction, no overlap check and no trail.

Time › Absence Entry closes that. HR picks the employee, the absence type and the dates, and the entry lands on the same record the employee’s own request would have created — so payroll, the leave balance and HR analytics need no special knowledge that it came from HR.

An HR entry is an observation, not an application. It is recorded as approved and the quota is deducted in the same transaction; it does not invent an approval trail through people who never saw it. What it does record is how it came to be there: whether the employee, HR or an import entered it, the reason HR gave, and whether a quota was overridden. Every audit and every payroll dispute reads those from the row rather than guessing.

Where a quota is short the entry is refused. HR may override — real absence must not be blocked by a balance nobody loaded — but only by asking for it, only with the right to do so, and the row is stamped with the fact for ever.

Corrections are honest too. Amending an absence reverses the original and reapplies rather than editing it under the balance, so the quota can never drift. A cancellation hands the quota back. Marking a whole shift or department absent reports row by row — the ones recorded, and each one that was not, with the reason — instead of one number that hides the failures.

The leave quota engine matched a balance by category alone and never looked at the unit it was counted in. The first hours-denominated absence would have taken two days of annual leave for a two-hour errand — silently, and in the direction that costs the employee.

Hours now deduct from hours and days from days, on deduction and on cancellation alike, and a balance that holds both is reported as two figures rather than one meaningless sum. Where no balance of the right unit exists at all, the refusal names the unit — a different problem from “you have none left”, with a different fix.

Administrators: a monthly permission entitlement is itself an hours quota block, generated per employee and per month. Until it is generated the Permission Register has nothing to draw on. Unpaid permission is refused by name until payroll can express it, rather than being recorded as though it were free.

When a permission covers a late arrival, the time evaluation stops raising the exception — but what the terminal measured stays on the record for ever. The minutes late are the measurement; the excused minutes are the judgement, and they are capped at what the permission actually granted. Two hours late on a one-hour permission is still an hour late.

The excused time is credited to the day’s paid hours as well, without which a two-hour permitted late-in would silently have turned the day into a half day.

Coming in late, leaving early or stepping out mid-shift had no record other than the exception it raised. Short Permission gives it one: an absence measured in hours, granted against the shift the employee was rostered onto, in the three shapes the shop floor actually uses — late-in, early-out and a mid-shift gate pass.

Employees request one from the Permission tab of their leave page; HR records and reviews them on the new Permission Register, and can record one on an employee’s behalf exactly as with any other absence.

A permission is meaningless without a shift to measure it against, so an employee with no published roster day is refused by name rather than being measured against a nine-to-five the plant does not work. The monthly entitlement is checked when the permission is asked for, not discovered at month end: past the cap it is refused, or deliberately overridden and stamped.

A mid-shift gate pass is recorded but costs nothing — the middle punches are not part of the day’s pairing, so the excursion is already inside paid time. It is kept because the fact that someone left the premises matters, not because it changes the pay.