What we shipped, in plain language.

The first half of the hiring paperwork is filled in before anybody is an employee, so the Job Request form prints from the recruitment candidate rather than from the employee master.

• The candidate record now holds the particulars the form asks for — previous experience, salary drawn and expected, and the declarations — captured on the candidate screen and previewed before printing
• The office-use block on the form is ruled space: it is there to be written on, and nothing is read back off it
• Anonymising a candidate purges the particulars this form added, along with everything else held about them

An identity card can be printed for an employee from the employee record, or for a selection of employees from the employee list, on a page of its own with a preview first.

• The card is laid out at the standard 91 × 56 mm, two to an A4 sheet, so a batch comes off an ordinary office printer ready to be cut
• Photograph, identifiers and a scannable code come from the employee master, so the card says what the record says
• The layout is a print format like any other and can be tailored per tenant, with the shipped layout always behind it so a card can always be printed

The staged change presented to the approver rendered raw internal identifiers — which is exactly the screen on which knowing which material is being added matters. Each side of the change now carries its label alongside the underlying value, never in place of it, since the drift check and the release both read the value.

The bill-of-materials lint run during change-order impact analysis failed on every change order. The guard around it caught the failure and reported the analysis unavailable, so nothing was ever wrong — but no approver had ever seen a lint finding. The findings are read correctly now.

The change-order form could only modify or remove component lines that already existed. Adding one now has a panel of its own — material, quantity, unit, scrap, sequence, component and supply type, unit cost, currency and notes — with the material, unit and currency searchable rather than a dropdown nobody can scroll at master-data scale.

An addition is now checked when it is staged, not when it is released:

• A component needs a material, a quantity and a unit. A missing one used to surface as a database error inside the release, long after the person who could supply it had left the screen
• Only component lines can be added. Staging an addition against an operation component or a variant rule was accepted, approved, and then quietly did nothing
• A new line carries no currency across from an old row, so it inherits the structure’s currency at release — and where the structure has none either, staging refuses and names the way out

Opening a project’s WBS tab showed a “built using a trial version” banner, while every other grid in the application was fine. One grid component was pinned to a different release line from the rest and ended up loading a second, private copy of the shared library — the copy that never saw the licence being registered at startup. The licence itself was never the problem. All components now share one library and the banner is gone.

Saving a leave application from Employee Self-Service failed with CSRF Failed: CSRF token missing. The screen was calling the server directly instead of through the shared client that attaches the security token, so the page loaded perfectly and only the save broke.

A sweep of the whole application found the same defect on eight more modules with live saves — data access and user management, the organisation chart, expeditor letters, the MBA dashboard, sub-contracting, numbering sequences and web push notifications. All of them now go through the shared client, as do seven further read-only screens, so the fault cannot come back the moment a save is added to one of them.

Add Element switched itself off after the first WBS element on a project that was still a draft, and the status transition buttons never appeared at all. Neither was a screen fault: the project status was simply not being sent with the project, so every project read as though it were already past draft.

The same omission left the Status column blank on the project grid and on the portfolio board.

The status is now served with the project — for reading only. A status change still goes through the transition action, so the rules that govern which move is allowed cannot be sidestepped by writing the field directly. The actual start and end dates, stamped by those same transitions, are served beside it and the “Actual start” field on the detail screen is no longer permanently blank.

The leave type dropdown on Employee Self-Service was empty, so no employee could raise a leave request at all. Leave types are tenant configuration and the screen correctly invents nothing — but that left a tenant that had never configured them with no way through the screen.

A starting catalogue is now seeded — Earned, Casual, Sick, Maternity, Paternity, Bereavement, Compensatory Off and Loss of Pay — modelled on a common Indian private-sector policy. It is a starting point for your HR team to confirm, not a policy: seeding is idempotent by leave-type code, so an edit made by an administrator survives a re-run, and a leave type already in use is never removed.

Seeding a type grants nobody any leave. An entitlement is a quota recorded against an employee, with a number and a validity period, and that stays an HR decision: until quotas exist the balance panel reads zero and a quota-bearing type refuses the request.

Administrators: a tenant with no users yet is skipped by the deploy-time seed rather than having an author invented for it — run seed_leave_types for that tenant afterwards.

A Sales Order line can now carry an output tax code from the tax master, and the code drives the line’s tax percentage instead of the rate being typed in by hand.

The tax code carries across when a quotation is converted into a sales order, so the rate the customer was quoted is the rate the order is raised at.

The daily, weekly and quarterly overtime caps in Overtime Management now read from the roster compliance rules for the plant, so one place governs the limits.

Where no rule has been configured the existing limits continue to apply exactly as before — removing a warning that fires today would itself be the change nobody asked for.

The time and attendance records were all in place, but nothing answered the question underneath them: which employee is on which shift on which date. That plan now exists — shifts, breaks, rotation patterns, crews and a generated roster per period.

• A rest day is a recorded off day, never a missing row. A gap in a rotation pattern silently understates absence and overstates overtime, so a pattern that does not cover its whole cycle cannot be activated and the builder shows the undefined day in red
• Generating and publishing are separate acts. A draft roster that breaches a limit is useful — it shows the manning problem — but publishing one is refused, naming each breach, because publishing a statutory breach is the breach
• Re-generating a roster replaces only the days the pattern produced, and reports how many human decisions it left alone
• Moving an employee between crews is recorded as history with effective dates, so past rosters that payroll was already computed against are not rewritten
• A locked period is a fact: correct it with a new period, never by editing the old one
• Night-shift eligibility is checked against what is on file — no exemption recorded means not permitted

Administrators: re-seed roles after this upgrade, and seed the roster configuration for each plant.

The General Ledger Journal Entries screen can reverse a posted journal, generating the opposite entry and linking the two.

It reverses manual journals only. A journal raised automatically by a document — an invoice, a receipt, a depreciation run — is one leg of that document and is reversed from the document itself, so the rest of what the document did is unwound with it.

A posted vendor invoice can now be reversed. A reversal cancels a posting — it does not erase the document, which stays visible with its reversal recorded against it.

• Everything the posting did is unwound together, not just the journal: the stock revaluation, the reverse-charge accrual, any vendor advances the invoice consumed, and the vendor sub-ledger entry
• Reversing releases the goods receipt again, so the receipt can be re-invoiced instead of being held shut for ever by a cancelled invoice, and the withholding-tax threshold no longer counts the reversed amount
• An invoice that has been paid is refused by name, rather than being reversed out from under the payment
• A reason is required, and the reversal posts into an open period

Attendance terminals can post punches directly, and each day is evaluated against the published roster to produce worked hours, lateness, early leaving and proposed overtime.

• A missing punch is reported as a missing punch, never as zero hours — zero pays nothing for a day somebody worked, and a full shift pays for a day nobody can evidence
• A device that has gone quiet is flagged as silent. A whole shift with no data looks exactly like a whole shift absent on every report downstream
• Overtime is proposed, never posted. A supervisor accepts it into the existing overtime request process, where the existing caps apply unchanged
• Which shift-day a night punch belongs to is decided once and stored, so payroll, overtime and the shop-floor rollups all count the same night the same way

The daily audit-chain check reported a company whose database was simply behind on upgrades as a verification failure — the same alarm as an audit trail edited directly in the database. The first production run would have sent a tampering alert for a routine upgrade backlog, and the next real one would have been ignored.

The two are now separate: the backlog case names the upgrade to run and states plainly that it is not a tampering signal, and the alert subject says a chain is broken only when one actually is.

The Sales Orders list checked three permission names that do not exist, so the check failed for everyone who was not a company administrator. Users who genuinely held the Sales Order permissions — a CRM Manager, for instance — could not see the View, Add or Edit buttons.

The names are corrected. Nothing about what the server allowed ever changed; only the buttons were missing.

Encrypted fields were implemented three separate times, and all three shared the same set of failures. There is now one implementation, and it closes each of them.

• A value that is not valid ciphertext, or that fails its authentication check, now raises. Previously a detected forgery was returned as though it were the real value — the one outcome worse than an error
• With no key configured the old code stored plaintext; it now refuses
• Each encrypted value is bound to the row it belongs to, so a ciphertext copied from one record into another is rejected instead of decrypting perfectly — verified by running that exact attack against the database
• Keys can now be rotated, which was previously impossible

Nothing stored changes with this release and no field has adopted it yet; this is the foundation the adoption is built on.

Table Explorer suppressed credentials, but every employee bank account number, PAN, Aadhaar, UAN and net salary was browsable, filterable and sortable in a generic grid. Thirty-four columns are now redacted.

• Redaction removes filtering, sorting and searching too — otherwise “net pay greater than” is a way of reading a salary without ever displaying it
• The distinctions are drawn carefully: an account number is hidden while the internal link to a bank account row is not, and one person’s net pay is hidden while a payroll run’s total across everybody is not
• A verification status about an identifier stays visible; the identifier itself does not
• An automated sweep now fails the build if any new sensitive-looking column is neither redacted nor explicitly reviewed, so this cannot quietly regress

The audit trail carried tamper-evidence, but nothing was checking it on a schedule. A daily job now verifies the chain for every company and raises an alert on a break, so a tampered audit record is discovered rather than merely discoverable.

“Ageing by Product Group” grouped on a hierarchy that is not the one the business means by material group, and which most materials do not carry — so the chart collapsed into a single blank bucket, or left the large majority of rows ungrouped.

It now reports the material group from the material hierarchy, which every material carries. On live data one company went from a single blank group to a named one, and another from 3 groups with 398 of 420 rows blank to 36 groups with none blank.

• A material attached above the material-group level is reported as its own group rather than dropped
• The chart and the grid column are retitled to match
• The separate Product Category filter is unchanged — it deliberately targets the product hierarchy