Introduction
This release contains the following:
- New features
- Policy Portal
- See recent search queries and recently viewed documents
- More guided way of using filters
- Specifying where to search
- Advanced text search
- Policy Portal
- Bug fixes & improvements
-
- Policy Management
-
- For Developers
-
- Public API changelog
-
- Document Search API improvements
-
- Bulk user management API improvements
- Public API changelog
-
For any questions, please email support@clausematch.com and we will further assist you.
New features
1. Policy Portal
The ability to search and quickly find the most relevant documents in Policy Portal is crucial. Therefore, we have started a series of improvements to our search to empower users with an improved search experience.
For the full steps on how to search documents in Policy Portal, simply follow the link below to the corresponding article:
How to Search Documents in Policy Portal
1.1 See recent search queries and recently viewed documents
Before starting a search, you will now have access to your previous search history and documents you recently opened. So you can quickly re-execute a successful search query or navigate to the desired document.
You will also be able to manage search history by clearing single items or clearing all history.
1.2 More guided way of using filters
Each document in Clausematch, besides its content, has additional metadata (for example: publication date). Now you can use this data in a more guided way to search for the documents.
Using this data in a search will allow you to specify your intent and narrow the search results.
Moreover, you can quickly identify what filters were applied and the available options for these filters.
For each type of metadata, we also provide different search options like All/Any/None/Is Empty, which will help you specify your intent with more granularity.
1.3 Specifying where to search
To reduce the noise and help you find the correct document quicker, we provide a new option that allows you to specify where you want to search: only in the document title or in the titles and the content.
1.4 Advanced text search
If you want to dive into more advanced text search mechanics, now you have a more granular control and can specify:
- The exact phrase to search by
- Keywords that should all be presented in documents
- Keywords where at least one should be presented in the search results
- And also a list of terms that you think should be excluded from the search results
Bug fixes & improvements
Important bugs that were fixed
Policy Management
- Fixed a bug that prevented merging table cells in the document title page
- Fixed a bug that caused document metadata to have incorrect values after switching templates that have a different collection of metadata
For Developers
1. Public API changelog
1.1 Document Search API improvements
Documents/search API was changed (see details in Swagger API spec)
- New query parameters: includeArchived
- New fields in response: isArchived, archivedAt, archivedBy, lastReleasedAt, lastReleasedBy, lastPublishedAt, lastPublishedBy, stage
2. Bulk user management API improvements
We introduced new possibilities to manage user authorities and groups with BULK REST Public API:
- users.bulk API behaviour has changed (see details in Swagger API spec)
- New optional fields are added to request: authorities, groups
- Existing fields were made optional: attributes, email, firstName, lastName
- User fields updated logic has changed: update is performed only if value changes