Release 13.1 (beta)

Article summary

Did you find this summary helpful?

Thank you for your feedback

Date of Release: 30 April 2024

General Remarks

This release introduces beta support for text file pattern matching via the Embedded Engine Word Search library.

UTF-8 and ASCII encoded text files are now supported in Word Search. Users can dictate whether a text file is blocked or written out using policy configurations.
- A new textSetting ('require') policy must be present and matched for valid text files to be written out.
- The existing 'disallow' policy may be used to block files where other patterns are matched.

The JavaScript wrapper is currently excluded from the release package. This will be reintroduced in a subsequent release.
Archive Manager and Word Search Java wrapper compatibility is currently limited to JRE8.
PDFs generated via the MS Outlook Adobe plugin are not supported.
Word Search analysis XML no longer reports structural content or changes.
Processing times may be impacted by changes made to licensing functionality.
Processing files using multiple threads is not supported. Spawning multiple processes is advised in order to facilitate parallel processing.
Word Search
- 'text' or 'regex' can not be the same for 'require' or 'allow'/'disallow' as this will regenerate the file and ignore the 'disallow' or 'require' setting
- | symbol at the start or end of 'require' can potentially cause the Engine to hang
- The following symbols when present in <text> policy are not supported: ^ < > \ & ( ) [ + . ?
- The following symbols when present at the start of a <text> policy are not supported: \ < > ^ $ ? [ + * ( ) .
- The following symbols when present at the end of a <text> policy are not supported: < > & $ ^ | ( ) + .

Was this article helpful?

Table of contents