Contextual search engine #
The basic mechanism for finding information is the contextual search engine. It can be found on the top bar of the system under the magnifying glass icon. When you select this option, a screen will appear with a window for entering search phrases. You can search for single words as well as whole sequences and initiate by confirming with enter. In the default layout, you see all items found. The system displays a fragment of the metadata of the found objects that contain the search phrase. This allows you to read the context in which the search term occurs, making it easier to find the item you are looking for. The search ignores case sensitivity and automatically matches different grammatical forms of words (e.g. tree, trees). The current language of the application influences the search results. Where possible, grammatical variants of a word are also taken into account. The searched information is sorted from the most relevant to the least relevant.
We can quickly limit the scope of the search by selecting the type of item we are looking for. We can choose from all types of documents from the applications available in the system. After clicking on one of the names, the system limits the list to elements of the selected type. Additionally, we can apply filters by date and sorting of the results.
The following rules can be used to define the search results, making the search engine a powerful tool for searching our Navigator365 system:
Automatic operator recognition:
OR: To find results containing any of the words, use the or sign.
Example: quick or fox – Will find documents containing the words quick or fox.
Inverted commas (‘…’): Use inverted commas to search for the exact phrase.
Example: ‘quick fox’ – Will find documents containing the exact phrase quick fox.
Exclusion (-): Use a minus to exclude specific words.
Example: ‘quick – fox’ – Will find documents containing quick but not containing fox.
Expert search: To use this, add the ‘advanced:’ snippet at the beginning, and find guidance on SQL syntax here.
Enhanced charts #
The data presentation attribute charts have been expanded with new options. As of version 2.3, new chart types are available: line, bar, pie, funnel, pyramid, doughnut, stacked bar, area and radar. In addition, it is possible to add more than one data series to create charts comparing two data series on one chart.
Asynchronous process #
From version 2.3, it is possible to set up a process as asynchronous. In practice, this means that when I upload invoice scans and the processing starts, I don’t have to wait for the process to finish. The process will run in the background, and the user will be able to continue using the system (no waiting bar will appear). This setting is available in the general tab in the process.
Improved trash bin function #
The system’s trash bin function has been changed. Currently, the system does not ask each time a document is deleted whether to delete it permanently. As a rule, each document is deleted to the recycle bin and there is an option to restore it. A message at the top of the screen also gives the option to undo this action immediately after deletion. The Trash Bin automatically deletes documents older than 30 days and it is available to examine in the system application.
Preview of html and xml files #
The ability to preview html and xml files in the attachments field has been added. The need for this enhancement arose because with the introduction of the KsEF (electronic invoicing) service by the Ministry of Finance in Poland. Navigator365 was unable to read those files sent via KsEF. From now on, the user can view directly in Navigator365 what invoice files have been received.
New action – Fetch document #
The action retrieves a specific document from a list of documents for use later in the process. The configuration includes the selection of the list from those available in our application. We can add filters to narrow the list and select a specific document. The user can then use the document data in further steps of the process, e.g. in the Change field value action or by mentioning fields with data from this document.
