A Search Field is used in Log Views in order to facilitate search conditions and can also be used for applying restrictions. Another powerful use of Search Fields is the ability for users to perform Group By operations. An example can be; 'List all business transactions grouped by Order Number'.
Values for the Search Field comes from the use of Search Field Expressions. There can be any number of Search Field Expressions set for a given Search Field. There can be more than one value extracted from a Search Field Expression. This may be useful when dealing with batches and messages with more than one entity (like multiple orders). The Web Client provides a test bench for testing Search Field Expressions. These tests actually make API calls to the Logging Service in order to ensure proper operation for real life messages.
Any logged message may be reprocessed and additional Search Fields on existing data can be added to Nodinite. From a support and maintenance perspective this means that you can find messages based on added criteria in a very late stage. You do not need to know, design and code in advance to find the data you are looking for.
If old data already exists and you want to be able to search according to the new settings for the Search Field, a re-index user initiated operation must be executed. The re-index operation is based on Message Type.
There are no prerequisites on the logged data and the values can origin from:
- Message Body
- Context Values
- Flat File
Writing your own Search Field Expressions Type Plugin provides additional support for:
- Encrypted messages
- ZIP files
- Special cases, for example: 'Get last 2 characters on line 3 in reverse and with uppercase'
- Custom .NET code based