SaaS / Hosted Monthly Release Notes - July 2021 (10.7.005 - 10.8.000)

Hierarchies feature now supports user-created text and memo fields

Case administrators can now add any user-created text and memo fields to a hierarchy.

Group leaders who have permission to access the Hierarchies feature on the Case Setup page can add only the user-created text and memo fields that they have access to.

Imports: Users can map fields to binders and issues

When importing flat files or MDB files into Nuix Discover, users can now map fields to binders or issues. In the Import window, on the Field Map page, users can click the Case field column and select Binder or Issue, as shown in the following figure.

Import > Field Map page showing Binder or Issue selection
  • To map fields to binders and issues when importing an MDB load file, on the Import > Fields page, select Custom map imported fields to case fields.
    • Fields must be the PICK type to be mapped to binders.
    • Fields must be the TEXT type to be mapped to issues.
  • If a user selects the Binder or Issue and one does not already exist, the application creates it.
    • Binders created through Imports are always shared binders. They are not security binders or mobile binders.
    • Permissions are not assigned for new binders or top-level issues.
  • When updating existing documents, the application treats binders and issues the same as one-to-many fields.

Ingestions: Documents with “un-executed code” messages no longer coded as Corrupted

The application will no longer code documents with Corrupted in the [Meta] Processing Exceptions field if they generate only the following messages during import:

  • PDF Portfolio contains un-executed code that may generate text.
  • PDF contains un-executed JavaScript code that may generate text.

These messages appear in the [RT] Ingestion Exception Detail field.

Note: If the import process results in one or both of these messages along with any other error messages, the application will code the affected document as Corrupted.

Disable downloading external resources during text extraction

The following new case option, shown in the following figure, is available on the Portal Management > Cases and Servers > [Case] > Case Options page:

Disable downloading external resources during text extraction

Select this option to block external web calls during text extraction when HTML links are encountered, for example, when using the Predictive Coding feature.

Portal Management > Cases and Servers > [Case] > Case Options page

Note: This option is cleared by default.

Connect API Explorer: Use importJobAddDocuments mutation to populate All Custodians, All Evidence IDs, or All File Paths

When using the importJobAddDocuments mutation, if the fields array for a document is imported with a name value of All Custodians, All Evidence IDs, or All File Paths, and the action field is set to InsertUpdate or Append, any values not already coded for the document are added to the document.

Note: Users cannot delete the All Custodians, All Evidence IDs, or All File Paths values from a document using the importJobAddDocuments mutation.

The following is an example of how to add the All Custodians value to the name field for a document using the importJobAddDocuments mutation.

Sample document details mutation:

mutation SampleDocumentDetails{
  importJobAddDocuments(caseId: 5,
  input: {
    rdxJobId: 52080,
    documents: {
      documentId: “ACTEST_00000001”,
      fields: {
        name: “All Custodians”,
        action: Append,
        values: “Sample Custodian”
      }
    }
  }){
    documentCount
  }
}

Sample results:

{
  “data”: {
    “importJobAddDocuments”: {
      “documentCount”: 1
    }
  }
}

Connect API Explorer: Include reaction event in importJobAddMessageEvents mutation

When using the importJobAddMessageEvents mutation, if the value Reaction is entered in the type input field, the content of the message event is included as a reaction to the conversation. These reactions appear immediately after the parent message as defined by the parentEventID field. If the message has both replies and reactions, all reactions appear first.

Note: Be aware that some replies may also have reactions, and reactions are not counted in the message counts.

The following is an example of the message event import job to input the message events and retrieve a total count of those events.

Sample mutation:

mutation MySampleMutation {
  importJobAddMessageEvents
  (
    caseId: 5,
    input: 
    {
      rdxJobId: 52090,
      messageEvents:
      {
        eventId: “12001”,
        parentEventId: “Parent120”
        conversationId: “121212”,
        content: “”:like:“,
        type: ”Reaction“
      }
    }
  ) 
  {
    messageEventCount
  }
}

Sample results:

{
  ”data“: {
    ”importJobAddMessageEvents“: {
      ”messageEventCount“: 1
    }
  }
}

Notification about browsers

On August 17, 2021, Microsoft will end support for Microsoft Internet Explorer (IE) 11. As of this date, Nuix Discover will no longer support Internet Explorer. This will, for example, affect Microsoft Office Online Server, which is used in the Office Online viewer in the View pane in Nuix Discover.

Please plan to move to one of the following supported browsers before this date: Google Chrome or (Chromium-based) Microsoft Edge, both of which support the Office Online viewer feature.

When you log in to Nuix Discover, if you are using a browser other than Google Chrome or Microsoft Edge, Nuix Discover takes you to a page with a notification about supported browsers.

SaaS / Hosted Monthly Release Notes - June 2021 (10.7.003 - 10.7.004)

Search for entity IDs using the Load search file tool

You can now search for a list of entity IDs using the Load search file tool on the Tools menu on the Documents page. Previously, you could search only for Document IDs or Main IDs. As the source, you can now enter text. Previously, you could upload only a text file.

Use the following procedure to search for entity IDs.

  1. On the Tools menu on the Documents page, select Load search file.
  2. In the Load search file window, on the New Search page, in the Results with this entity list, select a data model entity, for example, Person, as shown in the following figure.
  3. Note: Document is the default selection.

    Load search file window New Search page showing Results within this entity selection

    Note: After you select an entity ID, the option under ID Type changes to the entity type that you selected, as shown in the following figure.

    Load search file window New Search page showing Source option
  4. Under Source, do one of the following:
  5. Note: For either method, each line must contain a single entity ID or an entity ID range. To load a range of IDs, provide the first ID and the last ID of the range, separated by a vertical bar (|). Example: Person-02068|Person-02077.

    • To upload a .txt file, leave the Text File option selected, click Browse, select a file, and then click Open.
    • Note: The file must be in a text (.txt) format.

    • To enter text for your search, select Enter Text, and then enter text in the box, for example, as shown in the following figure.
    • Load search file window New Search page showing Source text
  6. Click Next.
  7. The results appear on the Results page, as shown in the following figure.

    Load search file window Results page

    Tip: You can click the link for the documents to access them on the Documents page.

    If any documents were not found, you can view the results on the Not Found page.

  8. Click Finish.

Manage Documents > Ingestions: Improved error handling in Ingestions

If an Ingestions job encounters only empty files, the Standardizing Data stage fails with the following message: “Error occurred: Nothing to process. Warning: The join order has been enforced because a local join hint is used.” The overall status of the job is Completed with Warnings.

If the application completes an ingestions job with unprocessed files, and the unprocessed files are resubmitted but contain no data, the application finishes the resubmission job as described above, and the job’s Properties page displays the statistics from the initial job.

Manage Documents > Renumbering: Capture all jobs in the Renumbering ID field

The Renumbering ID field now captures the Job ID of all Renumbering jobs. In previous versions, only the latest job was retained.

Manage Documents > Renumbering: Users can modify settings for the “Document ID plus page number” endorsement option

In previous versions, on the Endorsement page in the Renumbering window, when the user selected Document ID plus page number for one or more of the header or footer values, the application previously added the number to the Document ID in this format: -00001 (a hyphen with a five-digit padded page number).

With this release, users can modify the character that appears before the page number (the hyphen) by entering a character in the Character before page number box, as shown in the following figure. Users can also modify the number of padding digits by entering a new number in the Page number padding box. For example, if the character is “_” (underscore) and the padding is 4, the page number part of the endorsement would be “_0001”.

Renumbering > Endorsement page

Notification about browsers

On August 17, 2021, Microsoft will end support for Microsoft Internet Explorer (IE) 11. As of this date, Nuix Discover will no longer support Internet Explorer. This will, for example, affect Microsoft Office Online Server, which is used in the Office Online viewer in the View pane in Nuix Discover.

Please plan to move to one of the following supported browsers before this date: Google Chrome or (Chromium-based) Microsoft Edge, both of which support the Office Online viewer feature.

When you log in to Nuix Discover, if you are using a browser other than Google Chrome or Microsoft Edge, Nuix Discover takes you to a page with a notification about supported browsers.

SaaS / Hosted Monthly Release Notes - May 2021 (10.7.001 - 10.7.002)

Browse: All Custodians

The Browse pane now includes a section named All Custodians, as shown in the following figure.

This section appears by default for new users and is located under the Assignments section.

Note: If a user does not have access to the All Custodians system field, the All Custodians section appears, but does not contain any values.

Browse pane showing All Custodians

Existing users must add the All Custodians section to the Browse pane.

Use the following procedure to add the All Custodians section to the Browse pane.

  1. On the Documents page, in the Browse pane, on the menu on the toolbar, select Options.
  2. In the Browse settings window, select the check box next to All Custodians, and then click Save.
  3. The All Custodians section appears in the Browse pane.

Case Setup > System Fields: New fields for chat

The following two new system fields are populated in Nuix Discover for chat items promoted from Nuix Workstation or Nuix Investigate:

  • [Meta] Chat Conversation Start Date: This is the date of the first message in all parts of the conversation. For a conversation that is not split, or the first part of a split conversation, this will always be the same as the [Meta] Chat Start Date.
  • [Meta] Chat Conversation Start Time: This is the time of the first message in all parts of the conversation. For a conversation that is not split, or the first part of a split conversation, this will always be the same as the [Meta] Chat Start Time.

Renumbering: Documents with a page count of 0 or null are excluded from the renumbering job

If you run a renumbering job, if documents in a job have records with a page count of 0 or null, they are excluded from the job.

A new status named Has no page count is now available on the Exclusions page in the Renumbering window, under Documents that must be excluded, as shown in the following figure. If the application detects documents that do not have a page count, a number appears in parentheses next to the Has no page count line and the document is excluded from the renumbering job.

Renumbering windowshowing new status named Has no page count

Portal Management > User Administration: Organization selection required if organization security is enabled

As a portal administrator, when you add a new user, if organization security is enabled for the portal that you manage, you must select an organization or suborganization.

Portal Management > Cases and Servers: Bulk edit cases

System administrators can now change the following properties for multiple cases in one action:

  • IP Address Rule
  • Database Server
  • Analysis Server
  • Image Repository
  • Index file Repository
  • File transfer Repository
  • Archive Repository

Note: This feature is available only for cases with a status of valid or inactive.

Use the following procedure to change the settings for multiple cases.

  1. On the Portal Management > Cases and Servers page, select one or more cases.
  2. On the toolbar, on the More menu, select Bulk edit, as shown in the following figure.
  3. Cases and Servers page showing Bulk edit selection

    The Bulk edit window appears, as shown in the following figure, and displays the IP Address Rule page.

    Note: The settings on most of the pages in the Bulk edit window follow the same pattern, with the exception of the File transfer Repository page. The default option for all pages in the Bulk edit window is No change.

  4. To change the setting on the IP Address Rule page, do the following:
    • Select Replace with, and then select a new value from the list.
    • Note: The IP Address Rule settings are the values that are allowed for all of the organizations that are linked to the selected cases.

    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

      Bulk edit window IP Address Rule page
  5. To change the setting on the Database Server page, do the following:
    • In the navigation pane, click Database Server.
    • On the Database Server page, select Replace with, and then select a new value from the list.
    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

  6. To change the setting on the Analysis Server page, do the following:
    • In the navigation pane, click Analysis Server.
    • On the Analysis Server page, select Replace with, and then select a new value from the list.
    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

  7. To change the setting on the Image Repository page, do the following:
    • In the navigation pane, click Image Repository.
    • On the Image Repository page, select Replace with, and then select a new value from the list.
    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

  8. To change the setting on the Index file Repository page, do the following:
    • In the navigation pane, click Index file Repository.
    • On the Index file Repository page, select Replace with, and then select a new value from the list.
    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

  9. To change the setting on the File transfer Repository page, as shown in the following figure, do the following:
    • To override the existing setting, select Override with, and then select a value from the list. Or, to add a new value, select Add new value, and then select a new value from the list.
    • Note: You can select multiple values when you override the settings or add a new value.

    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

      Bulk edit window File transfer Repository page
  10. To change the setting on the Archive Repository page, do the following:
    • In the navigation pane, click Archive Repository.
    • On the Archive Repository page, select Replace with, and then select a new value from the list.
    • To save your changes and exit the window, click Save.
    • Note: When you click Save, the application creates a case edit job.

Notification about browsers

On August 17, 2021, Microsoft will end support for Microsoft Internet Explorer (IE) 11. As of this date, Nuix Discover will no longer support Internet Explorer. This will, for example, affect Microsoft Office Online Server, which is used in the Office Online viewer in the View pane in Nuix Discover.

Please plan to move to one of the following supported browsers before this date: Google Chrome or (Chromium-based) Microsoft Edge, both of which support the Office Online viewer feature.

When you log in to Nuix Discover, if you are using a browser other than Google Chrome or Microsoft Edge, Nuix Discover takes you to a page with a notification about supported browsers.

SaaS / Hosted Monthly Release Notes - April 2021 (10.6.005 - 10.7.000)

Notification about browsers

On August 17, 2021, Microsoft will end support for Microsoft Internet Explorer (IE) 11. As of this date, Nuix Discover will no longer support Internet Explorer. This will, for example, affect Microsoft Office Online Server, which is used in the Office Online viewer in the View pane in Nuix Discover.

Please plan to move to one of the following supported browsers before this date: Google Chrome or (Chromium-based) Microsoft Edge.

When you log in to Nuix Discover, if you are using a browser other than Google Chrome or Microsoft Edge, Nuix Discover takes you to a page with a notification about supported browsers.

Imaging: Support for HEIC and HEIF files

The Imaging feature now supports High Efficiency Image Container (HEIC) and High Efficiency Image Format (HEIF) file types.

Imports > Flat files: Create source and attachment relationships for any Document ID option

When performing an import using a flat file, you can now create a source and attachment relationship for any of the Document ID options on the Document ID page in the Import window:

  • Existing Document ID
  • Note: Previously, the Source and attachment relationship list, shown in the following figure, was available only if you selected Existing Document ID under the Document ID options.

  • Get Next - Levels Based
  • Get Next - Sequential
Import > Document ID page showing ID selections

If you select the Get Next - Levels Based or Get Next - Sequential option under Document ID, and select Parent Doc ID, Attachment Doc IDs, or Family Range in the Source and Attachment relationship list, a new Source and Attachment Document ID list appears, as shown in the following figure.

Note: The options in this list are based on the column names of the load file. This setting determines which field to use as the initial document ID when determining source and attachment relationships.

Import > Document ID page showing Source and Attachement Document ID selections

Note: The Source and Attachment Document ID list does not appear if you select None or LFP in the Source and Attachment relationship list. It also does not appear if you select the Existing Document ID option under Document ID.

After you run the import job, the settings you applied on this page appear on the Imports > Properties page.

Note: The Connect API Explorer already supports creating source and attachment relationships when you assign sequential Document ID values.

Imports: [RT] DPM File ID and Evidence Job ID fields prevented from being imported

Nuix Discover now prevents you from importing the following fields:

  • [RT] DPM File Id
  • Evidence Job ID

Note: If you try to import these fields, Nuix Discover displays an error message.

Ingestions: Upgrade to Nuix Engine 9.0 and OpenJDK 11

Nuix Discover now supports Nuix Engine 9.0 and OpenJDK 11.

Productions: Redaction label font size option

When creating a production, you can now set a font size for the redaction label. The Font size setting is available on the Manage Documents > Productions > Redactions page, as shown in the following figure.

Note: Previously, the font size you set for endorsements controlled the font size for footers, headers, and the redaction label. Now, you can set a different font size for the redaction label than for footers and headers.

Redactions page showing Font size
  • The default font size is 18 and can be any font size between 6 and 72. A value is required.
  • The application applies the font size setting to all redaction labels.

Email headers skipped during text extraction

For the Predictive Coding and Production features, Nuix Discover is now configured (by default) to skip email headers for .msg files during text extraction.

Email headers skipped during indexing

Nuix Discover is now configured (by default) to skip email headers for .msg files during indexing.

Note: To apply this change, you must reindex your case.

This change was available as of 10.6.004.

SaaS / Hosted Monthly Release Notes - March 2021 (10.6.003 - 10.6.004)

Chat: Support for Microsoft Teams chat data imported from Nuix Workstation

Nuix Discover now supports Microsoft Teams chat data imported from Nuix Workstation using the Promote to Nuix Discover feature in Nuix Workstation. You can review Microsoft Teams chat data as documents in the Nuix Discover application, as shown in the following figure.

You can review chat documents (conversations and messages) in the View pane in Formatted content view.

Tip: For best results in the List pane, set your search preferences to include sources and attachments.

List pane showing chat data

In the View pane, in Formatted content view, message replies are indented and appear immediately underneath the message that was replied to, as shown in the following figure.

Message replies example

In addition to messages, you can view the names of participants, attachments, images, videos, dates and times of the thread, the number of messages in the thread, and other metadata in the All Values template in the Conditional Coding pane, as shown in the following figure.

Conditional Coding pane showing All Values template

Nuix Discover groups Microsoft Teams chat messages into documents in two ways: by channel, when possible, or by the participant list.

Note: In Microsoft Teams, channels are dedicated sections within a team to keep conversations organized by specific topics, projects, disciplines, or other categories.

The Nuix Discover application splits messages into documents based on the settings on the Manage Documents > Ingestions > Advanced settings > Chat Data page, as shown in the following figure.

Advanced settings > Chat Data page

If the application splits messages into multiple documents, those documents will have the same value in the [Meta] Conversation Index system field.

Manage Documents > Imports: View Microsoft Teams chat jobs

On the Manage Documents > Imports page, administrators can view the import jobs from Nuix Workstation, as shown in the following figure.

Tip: Click a link in the Documents column to view the documents on the Documents page.

Imports page showing import jobs

Manage Documents > Ingestions: NIST list updated - December 2020

The Ingestions feature now uses an updated version of this list, released in DECEMBER 2020. For more information, go to https://www.nist.gov/itl/ssd/software-quality-group/national-software-reference-library-nsrl/nsrl-download/current-rds.

Manage Documents > Ingestions: Cellebrite XML processing updates

Ingestions chat processing is now available for XML exports from Cellebrite Physical Analyzer, up to version 7.39. Exports to XML for later versions may be supported but have not been verified.

When a user exports from Physical Analyzer, additional files are commonly created and contain information that is duplicative of the information in the XML file. These additional files include files with names such as “chat-1.txt.” Additional files appear on the Manage Documents > Ingestions > [ingestion job] > Unprocessed Files page.

Note: If a user selects these files to reprocess, the application will return an error for the job in the Standardizing Data stage. We recommend that you do not attempt to reprocess these additional files.

Connect API Explorer: New and updated mutations when importing chat data

The Connect API Explorer contains a new mutation for importing conversations and messages, and a new field for the importJobAddDocuments mutation when importing documents that are attached to message events.

The following new mutation is for importing conversations and messages.

  • importJobAddConversations: Adds conversations to an import job. The following definitions are recommended when using this mutation.
    • conversationId: A unique identifier that should be the same for all message and conversation records that are part of the same channel or chat conversation. All messages with the same conversationId values are combined to create the chat document.
    • documentId: Because multiple conversation records are combined into a single document, the imported documentId will not match the combined documentId.
    • channelName: Used to populate [Meta] Chat Channel.
    • platform: Used to populate [Meta] Chat Platform.

Sample mutation:

mutation SampleMutation{
  importJobAddConversations(caseId: 10,
  input: {
    rdxJobId: 100,
    conversations: {
      conversationId: “123456789”,
      channelName: “General”,
      documentId: “ABC123XYZ456”,
      fields: {
        name: “Custodian”,
        values: “MyCustodian”
      },
      participants: {
        id: “User1”
      },
      platform: “Microsoft Teams”
    }
  }){
    conversationCount
  }
}
  • importJobAddMessageEvents: Adds messages to an import job. The following definitions are recommended when using this mutation.
    • eventId: Unique id for the event record.
    • parentEventId: If messages are replies to other messages, the original message and all replies should have the same value for parentEventId.
    • type: This will be used in the future for other type of message records, such as reactions.

Sample mutation using the isMessageEventAttachment field:

mutation SampleMutation{
  importJobAddMessageEvents(caseId: 10,
  input: {
    rdxJobId: 100,
    messageEvents: [{
      eventId: “987654321”,
      conversationId: “123456789”,
      content: “Hi, do you have a few minutes?”,
      eventDateTime: “2021-03-15T08:29:43Z”,
      parentEventId: “987654321”,
      recipients: {
        id: “User 2”
      },
      sender: {
        id: “User 1”
      },
      type: “message”
    },
    {
      eventId: “876543210”,
      conversationId: “123456789”,
      content: "Sure, give me a call.”,
      eventDateTime: “2021-03-15T08:29:54Z”,
      parentEventId: “987654321”,
      recipients: {
        id: “User1”
      },
      sender: {
        id: “User2”
      },
      type: “message”
    }]
  })
    {
    messageEventCount
  }
}

The following new field is used when importing documents that may be attached to message events.

The new isMessageEventAttachment field in the importJobAddDocuments mutation is set to True when the document is attached to a message event. The parentId value for the document record should match the eventId value in the message record.

    Support for Microsoft Internet Explorer 11 ends on August 17, 2021.

    • On August 17, 2021, Microsoft will end support for Microsoft Internet Explorer (IE) 11 for O365.
    • As of this date, Nuix Discover will no longer support Internet Explorer.
    • This change will, for example, affect Microsoft Office Online Server, which is used in the Office Online viewer in the View pane in Nuix Discover.
    • Please plan to move to one of the following supported browsers before this date: Google Chrome or (Chromium-based) Microsoft Edge.

SaaS / Hosted Monthly Release Notes - February 2021 (10.6.001 - 10.6.002)

Manage Documents > Imports: Option to automatically ignore unmapped fields in imported flat files

When creating a new Imports job using a flat file, users can choose to ignore imported fields that they do not want to map or match to existing import fields. This functionality allows organizations to map only the fields they need and ignore the rest.

Field Map page showing New field

To access this functionality, go to the Manage Documents > Imports page and click Add. In the Import window, on the Field Map page, the following message appears: Update all Action values of New to Ignore if no Case field is chosen. Click the Apply button to ignore fields that have no value in the Case field column.

Import page showing Action column

Portal Management > Cases and Servers: Case creation date and time

The creation date and time for a case now appear in a new column on the Cases and Servers > Cases page, as shown in the following figure. This column is still available on the Cases and Servers > Deleted Cases page.

Cases page showing the Creation date column

SaaS / Hosted Monthly Release Notes - January 2021 (10.5.011 - 10.6.000)

Imaging: Support for Microsoft Publisher and Microsoft Project files

The Imaging feature now supports the .pub (Microsoft Publisher) and .mpp (Microsoft Project) file types. Once imaged, you can view these files in the View pane (in the Image viewer and in the Office Online viewer).

Note: Only files created using Microsoft Publisher 2000 or later are supported.

SaaS / Hosted Monthly Release Notes - January 2021 (10.5.009 - 10.5.010)

New search operator: not w\0

Nuix Discover now supports the not w\0 search operator.

For example, to find all documents that include Word01 or Word02 or Word03 but exclude documents that include Word04, you can run the following search:

Word?? not w\0 Word 04

The application finds all words in the index that meet the criteria for Word?? and excludes words after the not w\0 proximity operator (in this case, Word 04).

OCR: Updated OCR engine

Nuix Discover now uses ABBYY FineReader Engine for Optical Character Recognition (OCR) processing. This update affects the OCR processing option on the Tools menu on the Documents page, the Production Print feature, and the Exports feature.

The requirements and options available for OCRing image files in each of these areas have not changed. Only the OCR engine has changed. The following differences are due to how ABBYY processes files:

  • ABBYY cannot access secured PDF files.
    • If a user submits a secured PDF for OCR using the Tools menu on the Documents page, an error appears. In this instance, the Document OCR Status field contains the word Error and the Document OCR Error Details field contains the following message: Exception: ERR_IMAGE_PDF_OPERATION_NOT_PERMITTED.
    • If a user produces a secured PDF as an image but no endorsements (redactions, headers, footers) appear on the image and the option to embed text in PDFs is selected, then a message appears on the Production > History page indicating that an error occurred during processing. Users can click a link on the page to access the rendition documents that generated the error. The Document OCR Status field for those rendition documents contains the word Error and the Document OCR Error Details field contains the following message: Exception: ERR_IMAGE_PDF_OPERATION_NOT_PERMITTED.
    • Note: If endorsements are applied to the image, ABBYY attempts to make the file searchable.

    • If a user exports a secured PDF file, ABBYY is unable to embed text in non-searchable pages within the file if the following conditions exist:
      • The option selected for image format is Convert to Searchable PDF or Embed Text in Existing PDFs, and
      • No endorsements are applied on the image.
      • If non-searchable pages are present in the PDF, a message appears on the Export > Warnings page indicating which documents contain searchable files that were not exported.

  • ABBYY recognizes text within files using languages selected by users. Users must select at least one language. While selecting all languages that may be present in the document set could provide more accurate results, we recommend that users select no more than 10. Selecting more languages increases processing time and may result in lower quality results.
  • If a user submits a document for OCR using the Tools menu on the Documents page and any page in the document fails in the process, the application does not create a .txt file. Additionally, if the option to embed text in a PDF is selected, the application does not return an updated PDF file. The same is also true if a user chooses to embed text in a PDF using the Production Print or Export features.
  • Note: In previous versions, the application was able to work around these issues using Nuance, but there are no workarounds with ABBYY at this time. However, we have found that ABBYY does not encounter errors on pages that Nuance was unable to successfully OCR. For example, Nuance failed to OCR any pages that were missing content. ABBYY does not encounter this failure.

Case Setup > People Identity (Names Normalization)

Enhancements have been made to Names Normalization jobs so that non-similar names are more likely to be linked to different identities.

Manage Documents > Imports: New default delimiter on the Field Map page

When creating a new Imports job using a flat file, on the Field Map page, the default Delimiter value is now "; (59)" when one of the following is selected in the Case field column:

  • People - To
  • People - CC
  • People - BCC

Manage Documents > Ingestions: NIST list updated - September 2020

The Ingestions feature now uses an updated version of this list, released in September 2020. For more information, go to https://www.nist.gov/itl/ssd/software-quality-group/national-software-reference-library-nsrl/nsrl-download/current-rds.

SaaS / Hosted Monthly Release Notes - December 2020 (10.5.005 - 10.5.008)

Password requirement indicators on the login page

When you change your password in Nuix Discover, the application now displays the password strength requirements, as configured by your administrator, and alerts you if passwords do not match. An example is shown in the following figure.

Nuix Discover login page showing the password requirements.

Note: This applies to Ringtail authentication.

An administrator sets the password requirements on the Portal Management > User Administration > Account Settings page.

Translate documents into Russian

The Translate feature now supports Russian as a target language for both the Google and Microsoft translation services. Russian is also included as a choice for the Translation Languages system field. You can include Russian translations in productions.

Manage Documents > Exports > Update Image settings for exports

When converting images to PDF or from PDF to single-page TIFF, administrators now have the option to select the image size during export. When converting from PDF to single-page TIFF, administrators also have the ability to convert color PDFs to JPG files, as opposed to black and white TIFF files. You can access both options on the Image settings page in the Export window, as shown in the following figure.

Export window > Image settings page
  • To access the new Paper size option, in the Image settings window, click the Settings icon. You can select either Letter or A4. The default selection is based on default settings for Automated Imaging, but can be changed for each export.
  • Note: Only files that are converted to another file type based on what you selected in the Image format list will be affected by this setting.

  • To convert color PDFs to JPG files, in the Image format list, select Convert PDFs to TIFF, and then select Auto-detect color and render to JPG. The default selection for this option is based on the default settings for Automated Imaging, but can be changed for each export.
  • You can then enter the appropriate values in the Image resolution (DPI) and JPG quality (%) boxes. You can change the default values in these fields for each export.

Note: Footers, headers, redactions, and highlights are endorsed on the original image. If that image is converted at export (an image to PDF or a PDF to TIFF or JPG), the resulting files will have Letter or A4 dimensions. However, because the footers and headers were applied on the original image, they may not be positioned in the footer or header of the exported image file.

Manage Documents > Imaging: Support for .ics and .xps file types

The Imaging feature now supports the .ics and .xps file types.

  • An .ics file is a calendar file saved in a universal calendar format that is used by several email and calendar programs, including Microsoft Outlook.
  • An .xps file is a document that contains fixed page layout information written in the XPS page description language. This file type defines the layout, appearance, and printing information for a document. XPS files are similar to PDF files, but are saved in Microsoft’s proprietary XPS format.

Once imaged, you can view these files in the View pane (in the Image viewer and in the Office Online viewer).

Manage Documents > Ingestions: Group multi-segment AD1 files

When running an ingestions job, multi-segment AD1 files are now grouped in the same processing task.

An AD1 file is a Forensic Toolkit FTK imager Image file.

Cases and Servers: New case option to set the maximum unique word count for an index for content searching

On the Portal Management > Cases and Servers > [Case] > Case Options page, shown in the following figure, you can now use the following option to set the maximum unique word count that can be retrieved from an index for content searching: Search max unique word count.

Case option: Search max unique word count.
  • The default value is 256,000.
  • The minimum value is 16.
  • The maximum value is 4,096,000.

SaaS / Hosted Monthly Release Notes - November 2020 (10.5.001 - 10.5.004)

Tools menu: Custom tools

Your administrator can now add custom tools, for example, a calculator, to the Tools menu using the UI extensions feature.

Use the following procedure to access custom tools.

  1. On the Documents page, on the Tools menu, in the navigation pane, click the UI extensions button, as shown in the following figure.
  2. Select a UI extension tool.
  3. The tool appears in a standalone window. You can minimize, maximize, resize, and close the window. You can also reposition the window within your application browser window.

    Note: You must close the window before you can open a different UI extension tool.

    UI extension tool stand-alone window

Custom UI extensions for the Tools menu

The user interface extensions (UI extensions) feature allows application administrators and service providers to extend the functionality of the application by embedding custom third-party applications directly into the application interface. A third-party application that loads within the application is called a UI extension.

In addition to being able to add a UI extension to the Portal Home page, the Case Home page, or as a workspace pane on the Documents page, system administrators and portal administrators can now add a custom UI extension to the Tools menu on the Documents page using the Workspace tools UI extension.

Note: System administrators can add UI extensions in a portal for any organization or user, and portal administrators can install extensions for the organizations and users that they manage.

Sample UI extension applications:

  • An administrator might add a UI extension to the Tools menu to allow users easy access to external websites, for example, to an online calculator, as described in this document.
  • Note: Some websites, for example, CNN, are blocked from being added as UI extensions.

  • A Workspace tools UI extension could also be configured to submit a selection of documents in the List pane for a reporting, processing, or other task.
  • Another possible application could be a custom tool that combines multiple steps into one process. For example, you could build a custom tool that would allow you to take Predictive Coding score ranges and tag them with different review priority levels. Users could then search for documents by the review priority and tag those documents with the correct priority level.

For detailed information about UI extensions, see the following topics in the Nuix Discover online help.

  • UI Extension SDK: The UI Extension SDK provides an API that UI extensions can use to communicate with the application. The UI Extension SDK also includes steps to build and configure an extension, reference documentation, and an example extension. To get access to the UI Extension SDK, contact Discover.Sales@Nuix.com.
  • Administer UI extensions: This topic describes how to add a UI extension to the Case Home page, the Portal Home page, and as a workspace pane on the Documents page. The following procedure describes how to add a UI extension to the Tools menu manually.

The workflow consists of the following main steps described in more detail in the following sections:

  1. Manually add a UI extension to the Tools menu
  2. Enable a UI extension for an organization and cases
  3. Set group security for a UI extension
  4. Test the UI extension on the Tools menu

Manually add a UI extension to the Tools menu

Use the following procedure to manually add a UI extension to the Tools menu.

Note: To install a UI extension using a manifest file, see the above-mentioned topics in the online help.

  1. On the Portal Home page, under Portal Management, click UI Extensions.
  2. On the UI Extensions page, on the toolbar, click Add.
  3. The Add UI extension window appears, as shown in the following figure.

    Add UI extension window
  4. On the Settings page, in the Settings editor area, leave the Basic option selected.
  5. Note: If you are using a manifest file, select Advanced. The advanced procedure is not described in this document. For more information about how to add a UI extension using a manifest file, see Administer UI extensions in the Nuix Discover online help.

  6. Type a Name for the UI extension.
  7. In the Location list, select Workspace tools.
  8. Under Default window size, you can set the following:
    • Width: The minimum value for the width is 200 pixels and the maximum value is 1280 pixels.
    • Height: The minimum value for the height is 150 pixels and the maximum value is 768 pixels.
    • Require document selection: If the tool involves working with documents, select this option to require document selection before using the tool.
    • Display the OK and Cancel buttons: This check box is selected by default. Clear the check box if you do not need to include OK and Cancel buttons in the window, for example, when adding a calculator tool.
  9. Type an optional Description of the extension. The description appears on the UI Extensions page.
  10. Scroll down to display additional settings, as shown in the following figure.
  11. Add UI extension window showing description
  12. In the URL box, enter the URL of the web application that you are adding as an extension. The URL must include http or https.
  13. Note: Some websites, for example, CNN, are blocked from being added as UI extensions.

  14. In the Authentication secret box, click the Generate a random authentication secret button.
  15. Click Next.
  16. On the Review page, review the settings for the extension, and then click Save.

Enable a UI extension for an organization and cases

System administrators can enable UI extensions for the organizations in a portal.

Note: For portal administrators, when organization security is enabled, the list of available items depends on membership in a provider or client organization.

Use the following procedure to enable a UI extension for organizations.

  1. To access the UI extensions that are installed in the application, on the Portal Home page, under Portal Management, click UI Extensions.
  2. The UI Extensions page appears.

  3. On the UI Extensions page, shown in the following figure, click the name of an extension.
  4. UI Extensions page
  5. In the navigation pane, click Organizations.
  6. Depending on which organizations you want to enable the extension for, do the following:
    • To enable the extension for a single organization, hover over the row for the organization, and then click Allow.
    • To enable the extension for all organizations, click the Allow button in the heading row.
  7. After a UI extension is enabled for an organization, system administrators and portal administrators can enable the extension for the cases that are assigned to the organization. In the navigation pane, click Cases.
  8. Depending on which cases you want to enable the extension for, do the following:
    • To enable the extension for a single case, hover over the row for the case, and then click Allow.
    • To enable the extension for all cases, click the Allow button in the heading row.

Set group security for a UI extension

To allow groups in a case to access a UI extension on the Tools menu, administrators must grant access to the following security option on the Security > Features page in the case: UI Extension – [UI Extension Name]. Example: UI Extension - Calculator.

Test the UI extension on the Tools menu

Use the following procedure to test the UI extension.

Note: Some websites, for example, CNN, are blocked from being added as UI extensions.

  1. Log into a case.
  2. On the Documents page, on the Tools menu, in the navigation pane, click the UI extensions button, as shown in the following figure.
  3. Select a UI extensions tool.
  4. Ensure that the tool appears as expected in the standalone window.
  5. UI extensions tool stand-alone window

New portal option to address potential performance issues when streaming media files

Web servers become highly consumed by the FFmpeg process running at 100% when streaming media files, which causes performance issues in the environment. To address this issue, a new setting named View pane media thread count is now available on the Portal Management > Settings > Portal Options page to allow system administrators to limit the number of allowed threads.