Fixed on 22 October 2026

Fiscal calendars and number ranges fixed once in use; field help on every field; direct deposit and pay files; US Forms W-4 and I-9 and FMLA; identity verification by country; the careers site, Internal Jobs and calendar invitations; AI allowed by default for a new company; Tool Grants; the change board; quality inspections; configurable bills; 360° cards; ASK and gate entries.

Release 20261022 added or changed the following.

Nuevo

• Fiscal Year Variants, Fiscal Years and editable Fiscal Periods; number ranges fixed once in use, with fiscal-year and fiscal-period resets. See Fiscal year variants, fiscal years and fiscal periods, and number ranges fixed once in use.
• A “?” on every field, list heading and record field. See Field help: the “?” beside every field.
• My Bank Accounts, Direct-Deposit Changes, Direct Deposits, Pay File Settings and Pay Files. See Direct deposit: My Bank Accounts, HR approval and the bank pay file.
• United States only: My W-4, W-4 Submissions, My I-9, Form I-9, FMLA Settings, My FMLA Leave and FMLA Cases. See United States only: Form W-4, Form I-9 and FMLA leave.
• Identity Verifications by country, in a sandbox until a live connection is configured. See Identity verification by country.
• Careers Site, Internal Jobs and Calendar Invitations. See The careers site, Internal Jobs and calendar invitations.

AI allowed by default for a new company

• A company created from this release on starts with every AI area Allowed. An administrator turns any area off (or to suggest) in Platform › Access & Security › AI Governance › AI Settings, which states the commitment: “AI features are allowed by default for this company; an administrator can turn any area off.” Company data is not used to train AI models.
• Existing companies keep the settings they had.

Agentic AI (KSA TKT-000174 to TKT-000189)

• Fixed arguments win; Only when is checked against the tool’s inputs; Calls per run is enforced; Agent and Tool are fixed once a grant exists; a change of grants offers Publish now; versions keep their grants and default model; approvals show who decided, when and the note. See Agentic AI: Tool Grants that hold, the publish prompt, versions and approvals that say who decided.

Change control (IN TKT-000499, TKT-000589, TKT-000590)

• One person, one discipline: nobody is put on two disciplines of one review board. A role’s other holder is chosen instead; when there is none the step reads “Only holder already approves another discipline (<discipline>) …”. The same rule now holds on change orders.
• Where the company allows one person more than one discipline (Platform › Configuration › Core Settings › Runtime Settings, Manufacturing: Let one person sign more than one discipline of a change request, with a reason), the reason is kept on the step and in the audit trail. Steps signed by one person across disciplines are flagged in Same signer on several disciplines; nothing is rewritten.
• Submit, and raising a change order, are refused while a step can be given to nobody: “<ECR-000012> cannot be submitted: nobody can sign its <quality> step (<why>). Set who signs it on Manufacturing › Change Board, or give the role to somebody who did not raise it on Platform › Access › Roles, then try again.”
• Needed by before the day the request was raised is refused; an older request dated so reads “date before request” instead of thousands of days overdue.
• An approved change request can be converted to a change order from its own record.

Quality inspections (IN TKT-000587)

• Manufacturing › Control › Quality › Quality Inspections shows what was inspected (a production order, an operation or a goods receipt), the plan, the characteristics, the result and the usage decision.
• New inspection raises one from a production order (final, first-article, pre-shipment or after an operation) or a goods receipt, with the plan that applies or a released plan you choose.
• Record result: type what was measured on each characteristic; each is judged against its limits, and the inspection passes only when every one is within them.
• Usage decision: accept, rework, scrap, return or replace, and why. A failed lot stays blocked until it is made; what it raises (a replacement requisition, a rework order, a re-inspection) is linked to it. Completing a production order raises its final inspection from the one QI- series.

Bills, configurations, 360° cards and ASK (IN TKT-000586, TKT-000594, PFC TKT-000005 to TKT-000011)

• A bill of materials whose lines carry a selection condition or a quantity formula is never exploded without a configuration: it is refused, naming the lines. Make the order from a configuration.
• A configuration’s tree is read from its root on every per-configuration screen.
• A 360° card with no + Add says where such a record is made, with the record’s own action button where it may be run. On a purchase order, Dock Appointments has + Add, filled from the order.
• A locked requisition grid says what to do.
• ASK books a truck or a gate entry as a dock appointment (Supply Chain › Warehouse › Dock Scheduling › Dock Appointments), not as a yard movement.