<< Click to Display Table of Contents >>
Category |
Enhancement |
Version Added |
Administrative |
•Removed MS Access as a valid Case List and File Type Management database option from Explore Environment Settings in the LAW Configuration tab. •Answer Center links in Help > About in Explore and Explore Web updated to Explore 7.0 Answer Center. For legacy versions of the Answer Center, please contact Support. •CloudNine Early Data Analyzer is now CloudNine Explore. |
|
•Removed/updated outdated documentation in installation directory. |
2.5.0.72 |
|
Analysis |
Two additional options have been added to the Analysis Import settings in Explore: •Auto-assign suspect extensions - will identify a corrected file extension based on the File Type Management database and header information inside the document •Identify hidden text content - finds hidden text during import and tags it within the extracted text |
|
•File format processing library upgraded to provide better extraction of file metadata, and support for additional email file types. •For 7.6, updates to the metadata extraction library now allow processing of additional file types and variations. This update may result in a change to hash values from previous versions. |
||
•Explore now creates GUIDs for documents on import, providing an easy way to identify documents across Explore, Turbo Import, LAW, and CloudNine Review. Customers can also export and use the Explore-created GUID to track documents exported to external systems. •Improved processing and handling of encrypted PDF files. Metadata and searchable content will now be extracted from these file types. •Modified NSF processing to extract inline images from NSF emails as separate files. This change is isolated to NSF emails with inline images. |
7.3.229 |
|
•In 7.2 the hashing logic for emails was modified slightly to provide improvements in speed and efficiency; as a result, email hash values may change between prior versions and 7.2. •Improved performance during Email Hashing processing. •Improved performance during Deduplication processing. |
||
•Emails from MBX or DBX mailstores can be analyzed using multiple agents for files that contain (by default)1000+ emails per container. •Emails from OST or PST mailstores can be analyzed using multiple agents for files that contain (by default)1000+ emails per container. |
||
•Improved PDF encryption detection - CloudNine™ Explore will now extract content and metadata from PDF files that do not require a password and read permissions-encrypted PDF documents that do not require a password to open. •Updated File Identification Engine library to incorporate new file type processing. |
2.6.0.96 |
|
•Added a new exception category for mail store parsing errors where CloudNine™ Explore is unable to read an entry from a PST file. |
2.5.0.72 |
|
•Expanded extraction functionality to include password-encrypted ZIP and 7zip archive formats •CloudNine™ Explore will now use the address from the MAPI property "Return-Path" if the sender address is X400 type, increasing the frequency of capturing an smtp address instead of an exchange address. •User Interface option to limit number of agent processing attempts. Users are no longer locked into waiting for 5 full attempts to complete for each failed source. •Additional checks for the presence of Lotus Notes to ensure that CloudNine™ Explore does not attempt to process Notes database files, and “hang”, if Notes is not found. Appropriate exception messages were updated to reflect this situation. •CloudNine™ Explore will now parse headers to get SMTP address if address type is x400, providing easier to read email address information. *NOTE - Customers should expect that hash values may change for these specific email types. We have provided a case property to control this behavior to allow addresses to be backwards compatible. •NDL (Notes Document Link) files will now be processed as text (xml), preventing failures resulting from CloudNine™ Explore being unable to locate the "linked" Notes database. |
2.5.0.64 |
|
•Certified desktop Office 365 for use with CloudNine™ Explore •Added support for documents created by Google Docs. •Documents created using Google Docs do not contain metadata and thus CloudNine™ Explore will not be able to extract metadata information during document import. |
2.4.0.22 |
|
•Improved PDF Portfolio processing to better handle newer PDF structures. •Improved analysis performance on sMIME file types. •Improved PPTX analysis performance. •Improved 0-byte attachment file handling. |
2.3.0.69 |
|
API |
•Explore Export API updated to provide access to more fields. |
|
Case Management |
•The Exceptions tab is updated to display exception categories organized by severity. Only categories with exceptions now appear. |
|
•Simplified the Case Manager tab in Explore Desktop. Case entries are now sorted by Last Opened to consistently show recently used cases at the top of the list. •After upgrading Explore to 7.3, the management and case databases will require updates. Management updates can be applied via the LAW Configuration Utility or by opening LAW or Explore. Case updates can be applied by simply opening a case, and users will be prompted before the case updates are applied. While updates are pending, no work will be able to be performed on these cases. Inactive or legacy cases do not need to be updated until work on them is required. NOTE: Explore will now check the version of the database against the program version - older versions of Explore will not be able to open cases created in version 7.3. |
7.3.229 |
|
•Improved performance on Delete Sources process to prevent SQL timeouts. |
2.5.0.72 |
|
Compound Documents |
•Ability to find/extract embedded documents that were added as a "package" embed type |
2.5.0.64 |
Configure Environment |
•LAW configuration settings have been moved to a new tab in Environment Settings, making it easier to share data across cases and also with LAW. |
2.5.0.64 |
•Users can have CloudNine™ Explore automatically generate and send email notifications to specific email recipients when Inventory, Analysis, OCR, Indexing, Near Duplicate Detection, Email Threading, and/or Export jobs are completed. |
||
•Hashing of emails and related documents is no longer performed as part of Analysis, but is now a separate process performed by agents invoked by the CloudNine™ Explore Service. •Users can customize the metadata fields – both in terms of which fields are included, and in which order they are applied – that are used to generate the hash values for emails in a case. This change will trigger a re-hashing of all emails in the case. This cannot be done for any case created in a version of CloudNine™ Explore prior to 2.3.0.69. •The functionality to create and modify the email hash configuration for a case has been added to the Analysis tab of the New Case Settings and Case Settings dialog box. •The functionality to create and modify the Global Email Hash Configuration Templates has been added to the Environment Settings dialog. In addition, it is important to note that a template at the global level has a unique name, while the case-level configuration does not. Users can also delete templates, as well as creating and/or modifying them. (If cases have already been created based on a particular template, and that template is deleted, those cases are unaffected.) •Legacy: When CloudNine™ Explore 2.3.0.69 is first installed, (or a user upgrades to 2.3.069 from a previous version) a template named Legacy is automatically created in the Management database. This template has the same metadata fields, and field order, as the (non-modifiable) email hashing that is used in current production and earlier versions of CloudNine™ Explore. The Legacy template cannot be modified; it also cannot be deleted. |
2.3.0.69 |
|
Explore Web |
•Added a new "Hit Counter" for Saved Searches in Explore Web to show keyword hits and associated family record counts. •Removed the Filter Analysis tab from Explore Web. An improved feature set will be introduced in a future release. •Added Linear Review as a First-Pass review option for Explore Web. Users can now review specific tag sets/subsets in bulk. •Users can now sort Review Sets chronologically by date order. |
7.3.229 |
•Added EDFolder as an Export field as EDFolderPath •.DAT files are exported in UTF8 with Bom format |
||
•LAW Direct Export and Native Export provide a setting for date sorting. |
7.5.51 |
|
•Explore-created GUID field is available for native export. |
7.3.229 |
|
•Emails from MBX or DBX mailstores can be exported in EML, HTML, or MHTML formats for Native, Native Subsets, and LAW Direct Exports. •Modified mailstore folder names for LAW Direct Export output to more closely match LAW mailstore folder naming. Note: Impacts new cases only, existing cases will continue with current behavior. •Modified behavior on LAW Direct Export for emails with no subject. These records will be named "No Subject/Filename" on import to match LAW naming. •On LAW Direct Export, modified path and filename fields for Lotus Notes documents to show .htm as the file extension to match LAW behavior. Note: Impacts new cases only, existing cases will continue with current behavior. •Removed LAW PreDiscovery Export from Explore export options. Affects new cases created in 7.0. •For items which match a NIST hash, the DocCat value will be updated to DENIST when exporting during LAW Direct. |
||
•Export speeds for LAW Direct Export have increased 10-12x compared to 7.0 speeds* (results may vary based on data, agent availability, and environment). |
||
•Greatly improved performance for exports with included tag field metadata. •Updated tag export behavior to reflect current case state of tagged documents. Exporting documents will result in the current tag values being retrieved and placed into the load file at the time of export generation. *Note - as a result of this change, changes made to tag states post-export may cause regenerated load file tag data to not match previous export sets.* |
2.6.0.98 |
|
•Improved error handling and performance for several key Direct export scenarios. •Added Native Export functionality to choose how documents are grouped together when numbering them for export. •Added Native Export functionality to concatenate existing export fields to new custom, user defined fields. •Users can now configure formatting for date-related fields (for Native export) by selecting from a pre-defined set of available date formats. •Reorganized Native Export settings to allow for needed expansion, including updates to the user interface. •Reorganized Direct Export settings to allow for needed expansion, including updates to the user interface. •Added Direct Export functionality to choose grouping criteria for document export. |
2.6.0.96 |
|
•Option to Export ONLY top-level items for Native Export - produce native emails without extracted attachments. •Updated the field selection window in Export to display the EDRM alias and DAT short alias. •New "export status" indicator information to Export UI shows details on export errors, export state, and export failure causes. •CloudNine™ Explore can now re-generate load files based on previous export sets. •Modified Export behavior to be more fault-tolerant during native file extraction and continue on processing other •Expanded "Include Native placeholder" function to include creating a placeholder for missing source files. •Provided control options to handle duplicate documents when exporting thru LAW Direct - prevent duplicative data from being written to LAW cases. •Updated the Export function to support Access or SQL for LAW caselist formats. *NOTE - CloudNine™ Explore is able to read the LAW Case list from either MS Access or SQL during LAW Direct Export, but cannot export to MS Access DB. |
2.5.0.64 |
|
•Improve error handling and recovery for the whole export, agent, batch, and individual documents •Include native placeholders for extraction errors. Previously, the placeholders were automatically generated for contained/embedded/attached files that have an error during export. Now the option can be enabled or disabled. •Stop was added on exports. Allows the ability to stop exports for changes or to export another export. •Include text Header Format- allows choices in how the text files will be formatted upon export. The Header Format check box presents two options for user selection, Standard Email header, no Edoc header or Legacy Email and Edoc headers. The default setting for existing cases is Legacy Email and Edoc headers, while new cases will be set to Standard Email header, no Edoc header. |
2.3.0.69 |
|
File Engine |
•Update to FiEngine 3.22.1.0 to reduce additional false PowerShell identifications. |
|
Filters |
•Added exclusionary search filtering - users can now exclude searches as a saved-search filter (i.e. Search A not Search B). |
7.3.229 |
•Filter Processing Level - Setting for new cases that allows a reduction in the number of filters for a case for faster processing. |
2.3.0.69 |
|
Import |
•Administrators can now import CSV and DAT files into CloudNine™ Explore using the Add button on the Import tab. After import into CloudNine™ Explore, these files are also available in CloudNine™ Explore Web. This enhancement includes a new Load File Import Errors category on the Exceptions tab. Use this category to view any errors that occur when importing CSV and DAT files. |
2.2.2.37 |
•Null characters are now removed from email metadata during ingestion. This enhancement, which applies to all methods of export from CloudNine™ Explore to CloudNine™ LAW, helps to prevent issues when importing email into CloudNine™ LAW |
2.1.0.105 |
|
Installation |
•LAW/Explore 7.10 was created to work with a new Cloud Server, allowing clients to be able to Activate, Refresh and Deactivate their soft license keys. •Windows Server 2022 Certifications •SQL 2023 Certification
|
|
•Microsoft Windows 11 certified for use with CloudNine™ Explore. |
||
•New LAW/Explore installer. Sentinel Protection Server and Sentinel RMS License Manager installs are provided separately. |
7.5.51 |
|
•Certified TLS 1.2 protocols for use with Explore 7.3. •Upgraded .NET Framework to version 4.8. |
7.3.229 |
|
•Microsoft Windows Server 2016 is certified for use with CloudNine™ Explore. |
||
•A 64-bit CloudNine™ Explore service will be installed on 64-bit operating systems which allows CloudNine™ Explore to run more than 32 agents if the server hardware supports it. |
2.2.2.34 |
|
•The analysis, export, and file extraction CloudNine™ Explore agents now process in 64-bit in addition to the indexing and searching agents, which were enhanced to process in 64-bit in a previous release. This enhancement may allow some very large files to be processed and may result in a performance improvement. oIf the operating system running Early Data Analysis is 32-bit, all agents will run as 32-bit. oLotus Notes files are still processed in 32-bit due to a limitation with these types of files. oUsing 64-bit processes allows CloudNine™ Explore to process PST files and other archival files larger than 20 GB. |
2.1.0.105 |
|
Language Detection |
Language detection is now completed by a separate 32-bit agent that falls under Analysis. When the new language detection agent is processing, it is displayed on the Global Dashboard. •Because the new language detection agent falls under Analysis, the maximum number of agents set for Analysis in the Case Settings dialog box on the Analysis tab directly affects the language detection agents. The maximum number of agents for Analysis is the maximum number of agents that can be used for language detection. •To improve performance, CloudNine™ Explore will only evaluate the first 200 MB of a document to identify the language used. If a document is less than 200 MB, the entire document will be evaluated. •Because CloudNine™ Explore now automatically evaluates the first 200 MB of a document to identify the language used, the Limit content analysis to [number of KB] KB of file box has been removed from the Analysis tab on the New Case Settings dialog box. |
2.1.0.105 |
LAW Direct Export |
•Explore's LAW Direct Export now automatically sorts documents populated in LAW by chronological order within their folder, oldest to newest. |
7.3.229 |
•Explore now offers output folder controls for LAW Direct Exports, providing flexibility in structuring LAW folders by custodian, source, and/or Import Sessions. This replaces the grouping options in previous Explore versions. |
||
Lotus Notes and email attachments |
•You can now use the source application to view files attached to Lotus Note emails. |
2.1.0.105 |
Metadata |
•Added option to extract custom metadata properties for MS Office documents. •Added option to extract EXIF metadata properties from TIFF and JPEG image files. •Updated CloudNine™ Explore's formatting for Powerpoint, Publisher, RTF and other Office file types' standard metadata to more closely match LAW's standard metadata. |
|
NIST |
•Updated NSRL/NIST link in LAW and CloudNine™ Explore. |
|
•Moved NIST configuration (from filter settings) to Environment Settings dialog - all "global" configuration settings are now in one place. |
2.5.0.64 |
|
•Updated the NIST loader to support the latest file formats from NSRL (iso and zip) |
2.4.0.22 |
|
•If a child record is identified by the NIST filter, it will no longer be excluded. With this enhancement only parent documents will be considered for NIST filter. |
2.2.2.22 |
|
OCR |
•Expanded OCR control on what level you would like the PDF automation to run at |
|
•Expanded OCR automation on PDF's that contain images |
||
•In the OCR File Types option menu, PDF file types are now consolidated into one option. |
||
•Excluded encrypted documents from OCR eligibilty - encrypted docs will no longer be added to the OCR queue, which will reduce your resulting OCR processing error counts. |
2.5.0.64 |
|
•OCR using Abbyy now supports more than 16 agents per server (up to a maximum of one agent per cpu core). |
2.2.2.34 |
|
Performance |
•NSF items will now be OCR'd using 1 agent per NSF mailstore, instead of 1 agent for all NSF mailstores. •NSF items will now be exported using 1 agent per NSF mailstore, instead of 1 agent for all NSF mailstores. •Multiple agents/processes can now simultaneously ingest content from RAR, Zip, 7Zip, Forensic Image, and PDF Portfolio files. •CloudNine™ Explore can now reference SQL-based LAW File Type Management Databases. |
2.6.0.96 |
•Because analysis is now completed using 64-bit processes, if CloudNine™ Explore is installed on a 64-bit machine, it can now use all of the available memory to process large files except for Lotus Notes files. If installed on a 32-bit machine, performance is unchanged. |
2.1.0.105 |
|
Processing |
•Improved performance when extracting large files from archive containers. |
|
•Added support for newer PDF filetypes. See the Answer Center for more details. |
||
•Replaced existing Count value in search reports with Parent and Attachment Hit values - see your search hits |
2.5.0.64 |
|
Reports |
•Import, Search, Filter Summary and Export reports updated to disclude containers when reporting the total count and size of all files in a family. Export report updated to display Total Export Items with a count and size for filtered items. |
|
SQL |
•Explore now supports custom SQL logins for processing and case access/management. |
|
•SQL 2017 is certified for use with CloudNine™ Explore. |
||
Tagging |
•From the Explore Web Search tab, users can now apply a bulk tag to search hits and/or family records associated with search hits. |
7.3.237 |
Copyright © 2024 CloudNine™. All rights reserved.
CloudNine™ LAW | CloudNine™ Explore | CloudNine™ Explore Web | CloudNine™ Concordance® |