In the summer release, the BRIX ECM team focused on everyday user tasks: we simplified file and version management, enhanced search capabilities, expanded process automation, and added powerful new tools for contract management.


Here is a common daily scenario. An employee works on a document and saves several intermediate drafts. Colleagues only need to see the final version, but at the same time, earlier drafts must stay in the document history in case anyone needs to refer back to them.
Previously, file versions lacked a full status model, making it tricky to instantly tell which draft was active and which was obsolete. This created a risk of accidentally picking the wrong file version and cluttered the revision history.
Now, every file version carries a clear status: Current, Outdated, Draft, or Deleted.
Using the All Versions widget, you can quickly filter file versions by status. Drafts remain hidden from other users on view forms and approval tasks until marked as the Current version. Meanwhile, an Outdated version can easily be reactivated or used as a baseline for a new draft.
This gives you full control over the file lifecycle, keeps working drafts separate from final deliverables, and prevents costly mistakes. Authors can refine drafts in peace while colleagues always see the latest approved version—with the safety net of reverting to earlier iterations whenever needed.

Deleting a file version shouldn't mean losing it forever. It’s essential to retain the ability to restore a document if a version was removed by mistake or is needed for historical auditing.
Previously, deleting a version resulted in immediate, permanent loss. Users had to double-check every action because recovering a deleted version was impossible.
Now, deleted file versions move to a dedicated tab inside the Document Versions widget.
From there, you can restore them at any moment—or permanently purge them with an extra confirmation step if they are truly no longer needed. This soft-delete mechanism protects your team from accidental data loss and makes version control safer and far more predictable.

A standalone file rarely exists in a vacuum—it almost always belongs to a contract, project, service request, or other business entity. When a colleague receives a direct link to a file without context, it can be difficult to figure out what it relates to or where to find associated data.
Previously, users had to manually search the platform for the specific record a file was attached to. This added extra steps, especially when documents were shared directly without background details.
Now, a Linked Item hyperlink appears on the file sidebar. A single click opens the parent contract, project, or service request card, giving you immediate context.
This eliminates unnecessary search steps and ensures nobody works on a document without seeing the full picture.

When reviewing lengthy PDF documents, finding specific information can be tedious: scrolling through files with dozens or hundreds of pages takes up valuable time.
Imagine opening a 100+ page contract and needing page 37, as referenced in a colleague's comment or the table of contents.
Previously, you had to manually scroll until that page finally appeared.
Now, simply enter the target page number into the standard PDF viewer, and BRIX instantly jumps right to it. No more endless manual scrolling to locate key clauses.

When you need to review multiple files in a row, returning to the main document list to open each file individually wastes time and slows the work down.
Inside the Files app, you can now toggle between open files using your keyboard arrow keys. Navigation occurs directly within the viewer screen, eliminating trips back to the parent file list.
This familiar keyboard shortcut streamlines document and image reviews by cutting out repetitive clicks. It’s especially convenient when browsing files sequentially—like auditing a set of attachments or quickly comparing images side by side.

During document approvals, stakeholders often need to do more than read a file and click Approve. Making an informed decision may require logging risk assessments, adding comments, or recording key parameters that should remain attached to the document.
Previously, modifications made on custom approval task forms created in advanced mode were not saved to the system. As a result, custom forms couldn't be used to gather and store supplementary data during approval steps.
Now, participants can update editable fields directly on the custom task form, and all entered values are saved automatically. This works seamlessly for both app context fields and process context fields.
Approval tasks become active data collection points rather than simple decision checkpoints. For example, an approver can log vendor compliance risks during review, and those entries automatically persist on the document page for all future participants.

Consider this scenario: one employee sets an approval route after receiving a contract from an external system, while another opens the final decision task to review all prior approver comments and decisions.
Previously, approval route widgets couldn’t be embedded on custom business process task forms, restricting how these custom workflows could be designed.
Now, both route creation and route viewer widgets can be placed directly on custom task forms. If approvers aren't known ahead of time, users can build the approval path mid-process—while the viewer widget lets decision-makers inspect the full approval history before signing off.

A typo in a document's registration number might only be spotted after the record has been officially registered. When that happens, you need a way to fix it quickly without disrupting normal document control routines.
For document categorization folders using manual numbering, editing a registration number post-registration was previously impossible—requiring users to unregister and re-register the entire document. Post-registration edits were strictly limited to auto-numbered folders.
Now, records managers can update the registration number directly on the registered document page, with no re-registration needed. This simplifies document categorization management and eliminates tedious corrective work.

Complex business documents often need to list multiple assigned users, multiple attached files, or several category values inside a single table row. Previously, presenting multi-value fields within document tables was difficult to pull off.
When generating documents from templates, values from fields set to "multiple" could not be rendered directly inside table structures.
Now, multi-value fields—including users, files, categories, and other types—can be output directly inside table rows during template generation. You can easily list multiple responsible managers or attach several supporting files to a single line item without breaking document formatting.

It’s hard to remember the exact wording of a document every single time, and a slightly off search term or typo often meant returning zero results on your first attempt.
Previously, full-text search offered no way to control how strictly the system matched search terms against document content. Users had to adapt their queries precisely to what the search engine expected, even when they wanted broader results.
Now, you can toggle Fuzzy Search on or off directly within full-text search settings. When enabled, the engine accounts for partial matches and minor typos; when disabled, it strictly returns exact phrase matches.
This lets you tailor search behavior to the task at hand—whether that's casting a wide net for relevant materials or narrowing down results to exact phrases.

When running full-text searches, it helps to type out your complete query without distraction—especially for complex, multi-word terms. Automatic results updating while you're mid-sentence can be jarring.
Previously, search triggered automatically after entering just a few characters. The system continuously rendered intermediate results, forcing users to click back into the search bar to finish typing.
Now, search runs exclusively when you press Enter. You can construct your query, double-check the phrasing, and execute the search exactly when you're ready. Combined with optional fuzzy search, this gives you total control over how and when your results appear.

Integrating contract data via Web API doesn't always require pulling down the entire record history. In some cases, fetching a few specific fields is enough; in others, you need all connected child records in a single payload without making follow-up calls.
Previously, data fetching options for contracts were rigid, leading to redundant API calls and unnecessary data processing on the integration side.
Now, the Web API supports two flexible loading modes matching standard apps: you can request only specific fields or retrieve all associated data in one go. This allows developers to optimize integrations for specific scenarios, cut API overhead, and boost performance.

When setting up contracts, it is essential that data from different sources link together correctly. If field types do not match, an administrator might be forced to change app structures even when the existing architecture already fits the business scenario.
Previously, an App type field in a contract source could not be mapped to an Arbitrary App type field on the contract itself. Because of this, teams had to look for workarounds or alter app architecture to get things working properly.
Now, these field types can be directly mapped when configuring a contract source. Linked items display correctly in the contract without requiring additional changes to app structures.
This makes working with contracts more flexible and reduces the amount of technical rework required during system setup.
As a result, it is easier for administrators to adapt contracts to the existing app architecture, while essential data remains accessible to users in a familiar format.