2026.14Minor release2026.14: Help in the product, and a desk that asks first
2026.14 brings help and announcements into the product, lets a task action ask the reviewer a question before it runs, and keeps knowledge applying as your organisation grows. It reads more kinds of document, stays readable while it is being upgraded, and ties what people can see to the roles they hold. Here are the highlights.
A review desk that asks first
- An action can ask before it runs. A task action can open a dialog first: choose a reason from a list, fill in a field, add a comment, or complete a short form. The dialog writes to the document as you go, so dependent choices update, and Cancel puts everything back.
- Tabs that do not apply step aside. A form tab can carry a condition that hides it when it has nothing to say, and a hidden tab never holds up Approve.
- Checks can warn without blocking. A validation rule can raise a warning instead of an error. Warnings show in amber with their own icon and never stop a task from completing.
- Overrides stick. An exception you have overridden stays overridden when the task is reopened, and a check the platform itself closed is never shown as an override.
- Nothing slips past the form. An Exceptions button in the task toolbar lists any open exception the form has nowhere to show, and long lists fold into a summary with a count per field.
- A cleared field is empty everywhere. Scripts and background steps read a cleared field as empty rather than as the text first read from the document, and a pick-list answer that is not on the list is kept and flagged instead of erased.
- Fewer surprises while you work. Assign on open explains why a task cannot be assigned to you and offers to open it anyway. Rows removed together stay removed after Approve, a refused row delete puts the row back, and the toolbar says when work is still queued. A lookup that answers late no longer lands on the wrong field or freezes the page.
- Kiosk keeps moving. A document reached while it was still being fetched in the background no longer hangs on “Downloading…”, and loading indicators clear when you leave the task.
Knowledge that keeps applying
- Sets match on what a feature is, not which copy it is. A knowledge set applies when a document carries a feature of the same type and contents as the one the set names, whenever either record was created, and a new document reuses the existing record instead of minting a duplicate.
- Reruns see what you attached. A document run again picks up the features attached to it since its last run, and adding or removing a feature from the document card now saves.
- Search every feature. The Knowledge Features page searches on the server, so a match is found however many features your organisation has, with the type filter and sort working alongside it.
- See the knowledge a run used. Every task has standing Task, Documents, Knowledge and Exceptions tabs, and analysts can see, and change, the knowledge a run applied.
More documents, read sooner
- More formats in. Images, JSON and XML arrive as documents with their own viewers, and HTML and iXBRL filings can be viewed and labelled as filed.
- Large workbooks open in seconds. Spreadsheets with dozens of sheets and tens of thousands of formulas parse in a fraction of the time, and the workbook viewer works from the parsed cells.
- Email attachments behave like files. Each attachment opens in the main view or beside the email, and PDF attachments are parsed and published as documents of their own.
- Steadier page preparation. Pages can be classified from their images, documents embedded in a page can be cut out into pages of their own, and a scan with only blank pages keeps them rather than failing.
Running the platform
- Help and announcements in the product. Documentation lives in the product, with guidance on the field an article governs, and announcements that appear when people open the app or enter an organisation.
- A maintenance page during upgrades. While the platform is being upgraded, people see a page that says what is happening and when Kodexa is expected back, with chat where it is available, and the app returns by itself.
- Permissions, not switches. The organisation show/hide switches are replaced by role permissions that the platform enforces. Every new project gives the organisation’s members an editing role on it, so the person who creates a project can work in it. Access granted through an identity-provider group is removed at the next sign-in once the person leaves the group.
- Schedules and polling in view. A Schedules view shows what is scheduled to run and how it went. Polling jobs check each project on its own cadence, can be asked to check now, and say what they decided.
- A refreshed look, in your colours. Navigation, forms, dialogs and notifications are refreshed, your brand colours and welcome images carry through, and the interface is available in US English, Japanese and Spanish. A project can be retired in favour of the project that replaced it while staying readable.
For teams building on Kodexa
- Ask for only the fields you need. Every list endpoint accepts a fields parameter, so a job that reads a few values per record no longer downloads the whole record.
- Mistakes caught at save time. Saving a data definition warns about a field name a formula refers to that does not exist.
- Plans that wait without being blocked. A step can wait for another step to settle without failing when that step fails, and the step graph shows how many documents are queued, running and done.
- AI calls accounted for. Costs are attributed to the assistant, step or script that made the call, repeated prompt prefixes are cached, and a failed call records what the provider said and where it went.
— The Kodexa Team
