KnowledgeLake 4.1 is a focused release for commercial teams — universities, state and local government, and enterprises. Five enterprise-requested features your peers asked for by name, three workflow authoring improvements that make build-time cleaner, and roughly 50 defect fixes that compound across thousands of daily interactions.
No new product line. No grand reposition. 4.1 is a focused release for commercial teams — five enterprise-requested features, three workflow authoring improvements, and roughly 50 defect fixes that compound across thousands of daily interactions. Pick a tab on the left for the deep dive.
A wave of quality-of-life features driven directly by enterprise customer feedback. Small changes, compounded across thousands of daily interactions, that make the platform feel like it was tuned for your team — not the other way around.
Three improvements for the people who actually build workflows. Less guessing at design time, less GUID-juggling, and the option to fail loudly instead of silently when routing goes wrong — so workflow authors stop debugging tickets weeks after the fact.
"It is like hiring an AI assistant for everybody in the county. Now our staff can better serve our constituents."
Five enterprise-requested features land in 4.1 — drawn directly from the support tickets, user-voice posts, and quarterly review notes our customer teams have been compiling for the better part of a year. None are flashy on their own. All of them are the small frictions your team hits a hundred times a week, and they compound.
Pick exactly which columns each user sees in Monitor. Hide the ones they never look at; surface the ones they live in. A clerk processing one workflow hides everything that isn't theirs; a supervisor watching every queue keeps the broad view. Less scrolling, less visual noise, fewer "where do I look?" support tickets.
Filter Monitor and index work item grids by what they aren't. Status does not equal "Complete." Vendor does not contain "Acme." Powerful for finding the documents that should match a rule but don't — the exceptions, the strays, the ones eating up your audit time.
A new granular app permission to allow — or deny — a user the ability to edit annotations made by other users. Cleaner audit trail when reviewers shouldn't touch each other's notes; clearer override path for leads who legitimately need it. Less "who left this here?" confusion.
When a user saves edits to document properties in View, the document is automatically checked back in. No more "checked out by you" reminders for the next reviewer who picks it up. The kind of friction nobody bothered to file a ticket about — that everybody noticed disappeared.
A new keyboard shortcut for mass locking — and unlocking — every field in the index panel at once. Built for the moment a reviewer is ready to commit a document and doesn't want to click through ten fields to do it. Adds up to real time saved at the end of a 200-doc day.
This release closes roughly fifty customer-reported enhancements across Monitor, View, workflow, and the index experience. None of them were our idea — every single one came from your support tickets, your user-voice posts, and the conversations your account teams have been escalating for months. You showed us where the platform was getting in your way; we tracked it, prioritized it, and shipped it back to you.
Three improvements for the people who actually build workflows. Less guessing at design time, less GUID-juggling in the field reference, and the option to fail loudly when routing breaks — so workflow authors stop debugging tickets weeks after the fact.
The people building workflows are usually a small, expert subset of your team — and historically, the authoring experience has assumed that. 4.1 doesn't change who builds workflows, but it does change how much they have to remember to do it well. Three changes, none earth-shattering, all asked for repeatedly.
A guided experience for setting up property population steps. Fewer trips back to documentation, fewer mistakes that only surface at runtime, faster onboarding for new authors on the team.
Workflow design surfaces now show human-readable dropdowns where they used to show raw GUIDs. The author sees what they're picking; the reviewer reading the workflow next quarter can actually understand it.
A new option to fail the workflow when a routing step hits an exception, rather than silently continuing. Predictable failure modes for the workflows you really need to trust.
The wizard and dropdowns make it possible for a new admin to build a working workflow without first apprenticing for six months under the person who built the last one. Documentation matters less when the UI tells you what you can pick.
Senior authors stop being human GUID lookups. Workflow reviews can focus on whether the routing logic is right — not whether the right ID was pasted into the right field.
The error-on-route-exception option means workflows fail where they actually broke — not three steps later in a way that takes a week of log-diving to trace.
Workflows authored today get reviewed by people who weren't in the room when they were built. Human-readable dropdowns mean the next audit cycle doesn't start with "what does GUID 7f3a… refer to?"
