What we shipped, in plain language.

The task list’s search box only ever looked at the task’s own fields, so searching for a project or an assignee — both plainly on screen — returned nothing, which reads as a broken search. It now covers what the grid shows: task, project, category, priority and assignee, employees and contacts alike.

Three related faults are gone with it:

• The box now means one phrase. Searching “Website Creation” used to return a task called “Creation of banner” on a project called “Website Redesign” — a row containing neither of the words the user typed together.
• Typing anything into the box raised a server error, because the search named two fields a task does not have. An unsearched list loaded fine, which is why it went unnoticed.
• Sorting and filtering on Project, Category, Priority and Assignee were being dropped in silence — the click did nothing and said nothing. Status now filters by picking from the real list rather than by typing a label that never matched, and the export answers to the same column names the grid filters on, so a download matches what is on screen.

Paging is steadier too: rows sharing a creation timestamp could previously swap between page fetches, showing one task twice and another not at all.

A task carried exactly one assignee, so shared work had to be duplicated into a task each. A task — and a recurring task definition, so every occurrence it generates — can now name additional assignees alongside the primary one.

The primary assignee is unchanged and remains the one owner every existing report, notification and filter reads, so nothing that worked before changes meaning. What the co-assignees add is visibility: a task whose primary owner sits outside your part of the organisation is still yours if you are on it, and it appears in your list accordingly.

The Time Spent figure on the task list is now editable, and the cell also opens the full list of time entries behind the total — everyone’s entries, not just your own — so a number can be explained before it is changed.

Correcting the total is a supervisory act: the assignee’s supervisor, anyone above them in the chain, or a system administrator. The person whose hours they are cannot quietly restate them.

Timer entries are facts and are never rewritten. The difference between what the timers recorded and the total asked for is carried by a single adjustment entry, recalculated on each edit rather than stacking up a new row every time somebody changes their mind. Two things are refused by name: a total below what the timers already logged — the honest way to remove logged time is to correct the entry that logged it, and the message says how much is logged — and any edit while a timer is still running.

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.

Loss-of-pay proration counted one full day for every date an unpaid absence touched, whatever the absence said about itself. A half-day leave — a shape the leave screen has always offered and the quota engine has always honoured — therefore cost the employee twice the intended deduction, quietly, with nothing on the payslip to show why.

The day’s weight now comes from the absence record itself: a full day counts as one, a half day as a half, and a partial absence spread over several dates is shared across the span it covers. A weight that could only come from contradictory data is held between nothing and one whole day rather than being trusted.

A full-day absence is deliberately not divided across its span: leave is counted in working days while a span is counted in calendar days, so dividing one by the other would discount every leave that happens to straddle a weekend.

Administrators: this changes net pay for any employee with half-day unpaid absence. On one August run the affected employee moved from 16 to 17 paid days out of 25. Runs already posted are not restated — recalculate the period if the earlier figure needs correcting.

The employment application and the job request are bilingual forms, and the second language now follows the applicant’s mother tongue rather than being fixed. A Hindi mother tongue prints the title, every label and the declaration in Hindi; a Tamil one prints the form exactly as it printed before.

Both forms read from one shared catalogue of labels, because they are the same seventeen sections and must not end up saying different things about the same line. A translation is a lookup and never a transliteration: a mother tongue with no translated set prints in the language the form was drawn in, and a line with no translation prints in English alone rather than mixing two scripts on one page. The mother tongue itself now prints in both scripts — “TAMIL / தமிழ்” — taken from the language master, never invented.

The second lines can still be switched off outright when a plain English sheet is wanted.

Administrators: each language needs its font installed on the print server. Without one the second line simply drops out and the English label carries the meaning.

Form-1 now carries the ESI Corporation seal at its head and Form-2 the EPFO seal, as the sheets filed with the branch office do.

The seal identifies the form, not the employer, so it is shipped with the system rather than being tenant configuration — neither form identifies the employer by letterhead in any case (Form-1 does it by code and address, Form-2 by establishment code). The company logo remains only as a fallback, and if the emblem cannot be read the head prints without a seal rather than the document failing.

Because the mother tongue now decides which language a personnel form prints in, a typo in it is a form in the wrong language. Application Particulars therefore offers the language list instead of a free-text box — the same list the Languages tab uses, so the two screens cannot spell the same language differently — and a value already recorded stays selectable, so opening the dialog can never blank it.

A starting list of languages is seeded, and the dropdown can add to it from its own dialog for a language that is not on the list. Adding is a deliberate act, never a side effect of choosing a value; renaming or removing a language people are already recorded against stays an administrator decision.

Tenant lists built by hand held the same languages twice, under different spellings and casings, once the seeded list arrived beside them. Those duplicates are merged, not deleted: everything pointing at a duplicate is moved onto the single surviving row first, so no employee’s recorded language is lost. A row that cannot be removed because something still points at it is deactivated instead and simply leaves the dropdown.

ESI Declaration Form-1 and PF Nomination Form-2 now print from the employee record, in the statutory layout, ready to be signed and filed with the branch office.

They are printed from the employee profile, with a preview before the paper. Both are locked layouts: their wording is prescribed, so unlike the tenant’s own forms they cannot be redesigned in the print designer.

Behind them is a proper nominee register. A nomination is not a family member: it is recorded per scheme — the ESI nominee and the PF nominee may be different people — with a share, and it is ended by being revoked rather than deleted, so the record of who was nominated when survives. Form-2 keeps the two apart as the statute does: the family table is the family, the nomination box is the nomination.

What the record does not say, the form does not invent. Shares are reported as recorded and never quietly adjusted to add up — a set that does not total 100% is flagged for HR to correct in the record, not corrected on the paper. An unanswered question prints blank rather than ticking a box, and the establishment code is taken from the statutory filing details in force today, with none on file printing blank.

An export receipt settles invoices that were booked at their own exchange rates, while the bank pays at today’s. The gap between the two is the realised exchange difference and it belongs on the gain or loss account.

The journal has posted it that way since the foreign-currency work shipped, which is why Simulate always showed the right figures. The customer ledger row did not: it converted the receipt at the receipt’s own rate, so the difference landed on the customer’s account as well as on the exchange account, and the customer ledger disagreed with the receivables control account by exactly the gain. In foreign currency the customer was always square; in rupees the account was overstated.

The ledger row now takes the settlement figure from the same calculation the journal uses — read, not recomputed — so there is one definition of what the receipt relieved and not two. Reversing a receipt no longer quietly puts the difference back onto the customer either.

Administrators: rows written before this can be repaired with the backfill_receipt_local_relief command. It refuses a row it cannot settle honestly — a foreign-currency invoice carrying no usable rate, or a home-currency row, where a gap is a discrepancy rather than an exchange difference — and names it for someone to look at.

Tasks Upload takes the TA template Excel sheet a merchandiser already maintains and creates the project’s tasks from it. The upload is in two steps: a preview that writes nothing, showing the project it resolved, the counts and every question it has, and then a commit.

Only the rows marked Task reqmnt = Y are loaded. An N row is a task the plan says this order does not need — it is counted and reported as not required, never as a failure.

Where the sheet and the system disagree, the upload reports rather than guesses:

• A department name matching more than one department in the hierarchy is refused, naming both candidates, rather than picked.
• A near-miss spelling is matched, but the substitution is stated in full — both spellings, on the row — never applied silently.
• An employee is resolved by id; if the Name column disagrees with the record found, that is reported, and the name never overrides the id.
• The Dependent Task column is free text that does not name a task exactly, so it is recorded in the task’s notes and never turned into a real dependency. A dependency guessed from prose would drive the schedule off unvalidated text.

Re-uploading over a project whose work has already begun is safe: the opening status is set on creation only, so a task already in progress or completed is never walked back and no recorded progress is erased. The commit re-reads and re-checks the file itself rather than trusting the preview sent back to it, so an edited preview cannot slip a row past validation.

Reading the preview needs task view access; committing needs the right to create tasks.

The Customer box on the AR direct invoice and on an adjustment note was blank for accounts-receivable users. The list was being read from the CRM customer master, which those users are correctly not members of, and the refusal was swallowed into an empty dropdown — so a permission gate doing its job looked exactly like a broken screen.

Both forms now read the customer list from the reference tier, under a permission the affected roles already hold. Nobody gains access to the CRM module in order to fill in a dropdown. The list carries the credit currency and payment term with it, because the invoice defaults both from the customer.

Two further consequences of the same fault are gone. A refusal now names the missing permission on the field instead of showing an empty list. And the adjustment note loaded its five lookups as one batch, so a single refusal emptied companies, currencies, suppliers and the chart of accounts too and reported “Failed to load reference data”; each list now stands on its own. An invoice raised against a customer since deactivated shows that customer’s name rather than an empty box.

The gate operators recording a front-desk entry had no warehouse or storage location to choose from: both lists came from the inventory master, and no front-desk role grants inventory module access.

Both lists are now served from the reference tier under a permission those roles already hold, and the storage location list carries its parent warehouse so the second dropdown still narrows to the first.

An employee’s application form can now be printed as a PDF from the employee record, with a preview before it goes to the printer.

It is a reprint of the master, not a second form to fill in: the print takes no field from the screen, so a blank on the form is a blank on the record — and the record grew the fields the form actually asks for, family particulars among them, rather than the form inventing them.

• A default is not an answer. An unrecorded blood group, an age of zero and an absent wage all print blank rather than printing a value nobody supplied
• The photograph is embedded in the document itself, so it is there on paper and in the PDF you email
• The layout is a print format like any other, so it can be tailored per tenant — and printing never depends on that: the shipped layout is always there behind it

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