> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/release-notes/2026/june-2026.md). # June 2026 ## 24 June 2026 This is a large release, and most of it is about speed. The case list, the contact list and the search box are the screens that handle the most data, so they are the ones with the most to gain as an account grows. Each has been reworked so that the database does the filtering, sorting and paging, and AgileCase deals only with the rows you have actually asked for. Every account benefits, and the larger the account, the more noticeable the difference. Alongside that there is a set of refinements — most notably to date entry — and a better way of previewing documents. ### Performance #### Faster case and contact lists The Cases and Contacts lists now page in the database and return only the page you are looking at. Totals in the pager are unchanged and the screens look exactly as they did. They simply arrive faster, and on the largest accounts the difference is considerable. #### A rebuilt quick search Quick search has been rebuilt around the full-text index: * Contact and company searches use the full-text index directly, so looking someone up by the start of a name or client code returns results almost immediately. * Each part of the search returns its most recent 500 matches, keeping results focused on current work and bringing them back promptly. * Search terms now have a minimum length, which keeps results relevant to what you are looking for. Two refinements came with it: * The **Open date** and **Close date** filters on case search now apply to your results. * The search form handles any combination of field checkboxes, so you can narrow a search to exactly the fields you want. The **Known As** field is no longer included in quick search. It is rarely populated and costly to search, and leaving it out is part of what makes the rest so quick. If you do use it, let us know. There is more on searching in [General Search](/user-documentation/finding-your-information/general-search.md). #### Contact and case pickers The contact and case lookups that appear throughout AgileCase now wait until you have typed three characters, and pause briefly while you are still typing. A name typed at speed results in one search rather than a dozen, so the suggestions you actually want arrive sooner. #### Contact Details tabs load when you open them The Cases, Related Cases, Related Contacts and Notes tabs each load the first time you click them. Opening a contact is noticeably quicker as a result, particularly for contacts linked to many cases. #### Less work on every page Two background checks that ran on every page load have been retired, so each page you open now has less to do before it appears. The [Time Recorder](/user-documentation/time-recorder.md) and the message dialog continue to work exactly as before. #### Faster exports, custom field tables and saving Several other areas have had the same treatment: * Exports containing custom field tables load their rows in bulk and resolve linked contacts and cases in one pass. * The same applies to custom field tables retrieved through the API and through Case Connect. * Saving a case writes only the custom field values that have actually changed. * Screens with several file upload fields fetch their document labels once and share the result between them. * The **Docs & Comms** tab has considerably less to do each time it loads. ### New #### Preview now opens in Microsoft 365 The **Preview** option on a document in Docs & Comms now opens it in Microsoft 365 for the web. You see the document exactly as it is, with its real formatting, and you can move straight into editing it from there. Preview appears for documents Microsoft 365 can open. For anything else, download and the version history are available as before. See [Previewing a Document](/user-documentation/the-case-tab/previewing-a-document.md). #### More flexible data uploads The uploader used for incoming data from forms and external systems has had a run of improvements, including support for JotForm submissions: * Contact **Title**, and a client / non-client flag, can be mapped from the incoming data. * Where a client is not supplied explicitly, the uploader uses the contact it has just matched or created, so the submission still lands in the right place. * Cases can be found by case type and case number, as well as by case number and ID. * How email addresses are created for new contacts is now configurable, and duplicate checking can be skipped where the sending system already guarantees uniqueness. * Custom field IDs, mappings and client references are all checked up front, with a clear message naming anything that needs adjusting. See [Incoming Webhooks](/developer-documentation/webhooks/incoming-webhooks.md). #### Clearer diagnostics The error log now records the full chain of causes behind an event, including validation detail. This mostly matters to us, but it means that when you raise something with support we can usually see what happened without asking you to reproduce it. ### Improved #### More reliable date entry This is the change most people will notice day to day. Dates typed directly into a date or date/time field are now checked as you enter them: * What you type is matched against your account's date format, with an inline prompt on the field if it does not fit — so the date that is stored is always the one you meant. * Shorthand such as 1/1/25 is accepted and expanded to the full format, and two-digit years are interpreted consistently. * Saving waits until any flagged date has been confirmed, so a case is only ever saved with the dates you intended. Your regional date format is set in [Localizing AgileCase](/administrator-documentation/system-settings/localizing-agilecase.md), and the fields themselves are covered in [Date Picker](/administrator-documentation/types-of-custom-field/date-picker.md) and [Date/Time Picker](/administrator-documentation/types-of-custom-field/date-time-picker.md). #### Postcode lookup The postcode lookup on address forms has moved to a current provider, and is available on both the contact form and the new person dialog. #### Smaller refinements * Documents with a question mark in the filename open and attach as normal. * A document uploaded through a File Upload custom field records the field it came from. * Case Connect links are checked for a valid format before being opened, so a mistyped or truncated link gives a clear message. * The custom fields tab refreshes after a script displays a message, so anything the script changed is visible straight away. * AI templates can pass a link to a PDF as well as the file itself, and the tokens used by each interaction are recorded against the case. ### Worth knowing Two things have changed alongside the performance work, and both may be visible to you: * **Documents on hidden fields.** Where a [File Upload Control](/administrator-documentation/types-of-custom-field/file-upload-control.md) was set not to be visible, documents uploaded through it were filtered out of the Docs & Comms list. Producing that filter meant reading the whole custom field table every time the tab opened, and setting it aside is a large part of why the tab is now quick. Those documents now appear in Docs & Comms alongside the rest. Case and document permissions are unchanged — this affects the list only. If hiding them matters to your account, tell us and we will prioritise the rewritten version. * **Adding a contact** returns you to the first page of the contact list, which keeps the list quick to refresh however many contacts you hold. A small number of panels that used to refresh themselves now update when the page is refreshed. We are reviewing these and will bring back the automatic refresh where it is genuinely useful. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.agilecase.com/release-notes/2026/june-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.