What we shipped, in plain language.

A new screen under Administrator lets an authorised user browse the application’s own tables: choose a table, choose which columns to show, filter and sort them, page through the rows and export the result.

• Paging, sorting, searching and filtering all happen on the server, so a table with millions of rows opens as quickly as a small one
• Only tables belonging to your own company are browsable — platform-wide tables shared between tenants are never listed
• Sensitive columns such as password hashes and secret keys are removed everywhere they appear, and cannot be filtered, sorted or searched on either

Administrators: the permission is granted to no role by default. Grant View Tables to the roles that should have it after re-seeding roles.

The explorer has no way to edit, insert or delete a row, by design and not merely by hiding the buttons. A table maintenance screen bypasses every validation, posting rule and audit trail the application has.

Where data genuinely needs correcting, that is what the Operations Console and its reviewed, permission-gated commands are for.

After the export permission gate shipped, some grids — Sales Orders most visibly — could fail to draw with a scripting error, and row selection or column sorting could stop responding. Which grids misbehaved depended on which screens had been opened first in that session, which is why it looked intermittent and why it behaved differently on a fresh sign-in.

• The gate now applies to each grid individually, instead of altering behaviour shared by every grid in the application
• Where a tenant has withdrawn no export rights, the grid is left completely untouched — a change that takes nothing away should do nothing at all
• Screens no longer load export machinery they never use, so they load lighter

Only the edges carrying a substantial share of the busiest path animate. Animating a dense map wholesale is noise; restricting it makes the motion itself informative — the moving arrows are the mainstream path.

Motion is switched off entirely for anyone whose system requests reduced motion.

Pick a case, or choose “Replay on map” from the case drawer, and a token walks that case’s real trace from start to end. Everything the case never touched dims, the step being traversed highlights, and the node the token sits on glows.

• Play, pause, restart, scrub, and speeds from 0.5x to 4x
• Waiting time is compressed so one five-day gap cannot consume the whole replay — which makes the token’s speed deliberately untruthful, so the real gap is always shown as text alongside

Any signed-in user could export the full contents of any grid they could open, to Excel or PDF, regardless of role. Two new permissions now control it: Export to Excel and Export to PDF.

• Applied uniformly to every grid in the application — not screen by screen, so a new screen cannot ship ungated by accident
• Enforced on the server for the export endpoints as well as hidden in the interface: the toolbar button is presentation, the server check is the control

Administrators: grant these permissions to the roles that need them as part of this upgrade.

The Inventory Dashboard grouped receipt history by material and stamped that one date on every batch of it. Batch-managed stock therefore reported a single age for every batch:

• On the goods-receipt basis, the material’s earliest ever receipt was applied to everything, so stock received this morning was reported as months old and fell into the wrong ageing bucket
• On the last-receipt basis, one new receipt reset the reported age of all existing stock of that material to zero — hiding genuinely old stock from the slow-moving and write-off reports, which is the dangerous direction

Each batch is now aged from its own history, with the material rollup used only for stock that is not batch-managed. A back-dated report also no longer picks up receipts that had not happened yet.

The report date used to change only the age arithmetic — the quantities were always today’s, so an “as at 30 June” report showed current stock against June ages and could never tie to the stock balance on that date.

• Quantities are now reconstructed for the chosen date by rolling back the movements since, so the report ties to the balance as at that date
• A NEW stock class separates recently-arrived stock from the ageing buckets it would otherwise distort
• Ageing policy — bucket boundaries and the ageing basis — is set per company

Earnings, allowances, overtime, terminal benefits, deductions, statutory and technical wage types are seeded into every tenant, so compensation plans, income-tax records and payslips can be configured immediately instead of starting from an empty list.

Seeding is keyed on the wage type code, so a re-run changes nothing and an administrator’s edits to an existing wage type are never reverted.

Uploading a corrected version of a file created a second copy of every row rather than matching and updating the existing ones. Matching is now reliable, and soft-deleted rows no longer claim a key they should have released.

Foreign-key lookups now resolve on keys that are genuinely unique, a lookup field is only ever upgraded to a better one, and a date typed into a date-and-time column is accepted instead of rejected.

A lookup can be constrained to a subset of candidate records, so an ambiguous name resolves within the right scope. A separate utility identifies and merges tasks that earlier uploads duplicated.

Upload a logo against the tenant and it is shown on the sign-in page for that tenant’s address, before anyone has signed in. A tenant with no logo uploaded sees the page exactly as before.

The ship-to address lived only on the order header, so a single customer purchase order covering several destinations had to be entered as several sales orders — splitting the commercial document to describe a logistics fact.

• A sales order line can now name its own delivery address; a line that names none continues to use the header address, exactly as before
• Nothing is backfilled and existing orders are unchanged
• Material planning now distinguishes identical lines bound for different destinations. Previously four identical lines to four warehouses collapsed into one — a 75% short plan, announced only in a log line

Combinations that would record something untrue are refused rather than saved: a line addressed to a different customer, a delivery note line bound somewhere other than the note, and consolidating notes with different destinations onto one invoice.

The worksheet no longer opens empty until a paging control is touched, and a second attempt to save the same set of edits no longer reports “Nothing to save”.

The task list can be narrowed to a due-date window, and a change to a task’s planned end date is noted in its chat, so the reason travels with the date.

A task that has not been finished is now its own status. It renders in the ordinary colour and only turns red once its planned end date has passed, so “not done yet” and “overdue” stop looking the same.

The task worksheet gains a Pivot Analysis tab, and both the worksheet and the pivot remember your layout — column order, widths, grouping and filters — as named variants saved per user.