SaaS / Hosted Monthly Release Notes - November 2021 (10.9.001 - 10.9.002)

Note: The permissions set by your administrator may determine access to certain features.

Updates to the Load search file tool: Support for the MD5 hash and page label fields

When using the Load search file tool on the Tools menu on the Documents page, you can now search for documents that include a list of hash values by selecting the [RT] MD5 HASH field in the Field list.

You can now also select the Page Label field from this list.

Load search file page showing selection of Page Label

Note: Previously, you could select the Document ID or Entity ID, as well as the Main ID, options under ID Type, as shown in the following figure. These options are now available in the Field list, shown in the previous figure.

Load search file page

Chat: Updated behavior for importing and displaying join and leave events

When a “join” or “leave” event is provided in a chat document, it is included as part of the conversation in the View pane in the Documents window as follows:

  • Join and leave events in chat documents are displayed as regular messages, except:
    • If no “sender” value is provided:
      • For a join event, the message text is “JOINED: {recipient}.”
      • For a leave event, the message text is “LEFT: {recipient}.”
    • If a “sender” value is provided:
      • For a join event, the message text is “JOINED: {recipient} added by {sender}.”
      • For a leave event, the message text is “LEFT: {recipient} removed by {sender}.”
  • The user listed to the left of the messages in the View pane is the recipient (the user who joined/left).
  • If a join or leave event has multiple recipient values, the application creates a separate join or leave message for each recipient. Each message will have the same “sender” value.
  • Join and leave events appear in the summary table at the top of the View pane as follows:
    • JOI column header: Number of join events for each recipient.
    • LEF column header: Number of leave events for each recipient.
    • In Formatted content view, to highlight the join and leave events in the conversation as well as messages, select the JOI or LEF column header in the summary table. To highlight only join or leave events, select the value in the JOI or LEF column. An example is shown in the following figure.
    • Chat conversation example

Manage Documents > Imaging - Automated: Updated Slipsheet count link to include additional documents with slipsheets

On the Manage Documents > Imaging – Automated page, when a user clicks on the link for a value in the Slipsheet count column, the search results that appear on the Documents page now include the search strings “Imaging Warnings” IS “Slipsheet - User-specified” and “Imaging Warnings” IS “Slipsheet - Imaging Failed”. In previous versions, these search strings were not included when a user clicked on the link in the Slipsheet count column.

Portal Management > Processing: Updates to the Daily Case Metrics job

When a scheduled Daily Case Metrics job runs on the last day of the month, the job now includes all stages, that is, the same stages as a full Gather Case Metrics job. So, the Daily Case Metrics job updates all of the “active” statistics and the statistics for Orphan (GB), Missing (GB), File transfer data (GB), and Archive data (GB).

Portal Management > Reports: New non-billable column on the Usage and Hosted Details pages

On the Usage and Hosted Details pages, the Non-billable column now appears by default next to the Case column, as shown in the following figure.

Hosted Details page showing non-billable cases

You can filter the results in this column. By default, the column is not filtered. Set the filter to No to show only cases that are billable.

If you select Yes, the non-billable cases appear in this column and a dot indicates that the case is non-billable, as shown in the following figure.

Hosted Details page showing billable cases

Connect API Explorer: Update to the importJobAddDocuments mutation for identifying page number when applying annotations

The importJobAddDocuments mutation has a new filePageNumber field, which replaces the filename field, for identifying the page number where annotations are applied. This field must contain a positive integer and must be within the range of total pages contained within the document. For example, if the document is a 5-page PDF, the filePageNumber field would contain the numbers from 1 to 5. If the filePageNumber value is set to 2, the annotation will be applied on the second page of the PDF.

Sample mutation using the old field:

mutation MyOldSampleMutation {
  importJobAddDocuments (
    caseId: 5,
    input: {
      rdxJobId: 38
      documents: {
        documentId: “Annotation_00000001”,
        pageaction: InsertUpdate,
        pages: {
          pagenumber: 1,
          path: “\\Annotation_00000001.pdf”,
          pagelabel: “Annotation_00000001”
          },
        annotations: {
          fileName: “Annotation_00000001.pdf”,
          pageNumber: 2,
          type: REDACTION,
          name: “Attorney-Client Privilege”,
          label: “Attorney-Client”,
          color: BLACK,
          x1: 100,
          x2: 400,
          y1: 100,
          y2: 400
        }
      }
    }) {
    documentCount
  }
}

Sample mutation using the new field:

mutation MyNewSampleMutation {
  importJobAddDocuments (
    caseId: 5,
    input: {
      rdxJobId: 38
      documents: {
        documentId: “Annotation_00000001”,
        pageaction: InsertUpdate,
        pages: {
          pagenumber: 1,
          path: “\\Annotation_00000001.pdf”,
          pagelabel: “Annotation_00000001”
        },
        annotations: {
          pageNumber: 1,
          filePageNumber: 2,
          type: REDACTION,
          name: “Attorney-Client Privilege”,
          label: “Attorney-Client”,
          color: BLACK,
          x1: 100,
          x2: 400,
          y1: 100,
          y2: 400
        }
      }
    }) {
    documentCount
  }
}

Connect API Explorer: Update to the importJobAddDocuments mutation with new notes field

The importJobAddDocuments mutation has a new notes object that will specify what notes will populate in the document.

Required fields:

  • Id: A unique integer value assigned to each individual note within a document.
  • noteText: Contains the text of the note.

Optional fields:

  • category: A category identifying the note. If the entered category does not already exist, the new value will create a new category. If no value is provided, the category will be Uncategorized.
  • userName: The name of the user who created the note. If this name matches a known user, the userId: is automatically populated with the note. Otherwise, the user performing the import is assigned to the note.
  • dateStamp: The date the note was last modified. If left blank, the date will populate with the current date and time.
  • isPrivate: Indicates whether the note is a private note.
  • parentNoteId: The ID of the parent note for a note that is a reply.
  • noteTextHtml: Contains the text of the note with the HTML formatting.
  • isAnnotation: Indicates if the note is an annotation that will appear on a specific page of the document.
  • pageNumber: For notes that are annotations, this value indicates the page record on which the note is located.
  • filePageNumber: For notes that are annotations, this value indicates the page of the file on which the note is located.
  • Coordinates:
    • x1: The x1 coordinate for the note.
    • x2: The x2 coordinate for the note.
    • y1: The y1 coordinate for the note.
    • y2: The y2 coordinate for the note.

Sample notes mutation:

mutation MyNoteSampleMutation {
  importJobAddDocuments (
    caseId: 5,
    input: {
      rdxJobId: 300,
      documents: {
        documentId: “Annotation_00000001”,
        pageaction: InsertUpdate,
        pages: {
          pagenumber: 3,
          path: “\\Annotation_00000001.pdf”,
          pagelabel: “Annotation_00000001”
        },
        notes: {
          id: 10,
          noteText: “Sample note text”,
          x1: 10,
          x2: 20,
          y1: 10,
          y2: 20
        }
      }
    }) {
    documentCount
  }
}

Connect API Explorer: importJobAddConversations mutation has new chatHistoryStart field

The importJobAddConversations mutation contains a new chatHistoryStart field that identifies the date and time of a participant’s earliest access to messages in a chat. The chatHistoryStart field is optional, and if provided, all conversation records that are part of the same overall conversation will have the same value for a participant.

Sample chat participant mutation:

mutation MyChatMutation {
importJobAddConversations (
  caseId: 5,
  input: {
    rdxJobId: 10,
    conversations: {
      conversationId: “Conv123456”,
      participants: [
        {
          id: “test1@nuix.com”,
          chatHistoryStart: “2020-02-03T13:49:06.846Z”
        }
        ],
      channelName: “TestChannel”,
      documentId: “DocID00001”,
      fields: {
        name: “Custodian”,
        values: “Test1”
      }
    }
  }) {
    conversationCount
  }
}

SaaS / Hosted Monthly Release Notes - October 2021 (10.8.005 - 10.9.000)

Chat: When sorted by Document Title, conversations now appear in order, regardless of length

In previous versions, when viewing a chat conversation in the View pane on the Documents page, if you looked at a set of documents that represented all of the parts of a conversation and sorted by Document Title, the conversations would not appear in order if there were more than nine parts. This behavior occurred because the first number that appeared in the Document Title was not padded.

In this release, if the Document Title reads “Part X of Y,” the X value is padded to the same number of digits as the Y value. As a result, conversations with more than nine parts are displayed in order.

Example:

  • Previous versions: Part 1 of 12
  • This and future versions: Part 01 of 12

Portal Management > Cases and Servers > Cases > Case Options: New case option to disable PDF compression for exports

A new option named Export - PDF compression is now available on the Portal Management > Case and Servers > Cases > Case Options page.

Note: This option is selected by default.

If selected, PDF documents are compressed before being exported in order to reduce the size of the export. In certain cases where PDF exports are running but stop progressing, clearing this option may help resolve the issue.

SaaS / Hosted Monthly Release Notes - September 2021 (10.8.003 - 10.8.004)

Manage Documents > Automated Imaging: User interface changes to Settings

This release includes two user interface changes to the Manage Documents > Imaging-Automated > Settings window.

  • On all pages of the Settings window, to validate the required settings, you must click Save on each page of the window.
  • On the Excel page, in the Margins section, the settings for each of the options have changed from radio buttons to lists, as shown in the following figure.
  • In the updated user interface, a list with the following two options appears for each of the Margin settings: Original and Custom. If you select Custom, a text box appears to the right of the list. Use this text box to specify the margin size.
  • Excel page

Manage Documents > Imports: Delimiter for imported or new one-to-many fields defaults to a semicolon

On the Field Map page in the Import window, when you set the Action to Import to or New for one-to-many fields, the value in the Delimiter column now defaults to a semicolon ; (59), as shown in the following figure.

Field Map page

Note: Cloned import jobs retain the original delimiter settings.

Note: System administrator tasks are performed by Nuix SaaS administrators.

Portal Management > Cases and Servers: Edit the billable status for multiple cases

On the Portal Management > Cases and Servers page, you can now edit the billable status for multiple cases.

Use the following procedure to edit the billable status for multiple cases.

  1. On the Portal Management > Cases and Servers page, select one or more cases.
  2. On the toolbar, from the More menu, select Bulk edit.
  3. In the Bulk edit window, on the Billable Status page, select the Replace with option, as shown in the following figure.
  4. Note: If you select the No change option, the non-billable status is not changed for any cases.

    Billable Status page
  5. In the list, select Billable or Non-billable.
  6. Click Save.

Portal Management > Reports: New column for Parent Organizations

On the Usage, Hosted Details, and Users pages in the Portal Management > Reports section, system administrators can now configure the table to display the Parent Organization column and information. This column does not appear by default.

The previous Organization column is now used to display information about a suborganization of the parent organization.

If configured to appear in the table, the Parent Organization column appears to the left of the Organization column, as shown in the following figure.

Usage page

Connect API Explorer: Generate levels based on Document ID in importJobCreate mutation

In the importJobCreate mutation, there is a new LevelBased option within the documentIdType field. When creating an import job that is LevelBased, the specified docId will be the selected levels, with each separated by the character indicated in the levelSeparator field. After the last level, the levelSeparator character is added and a sequential padded number is added to each document.

For example, if three documents are loaded to level Imports/API/0001, and the levelSeparator is the period character, and the levelBasedPadding is set to the number four, the docId values will be Imports.API.0001.0001, Imports.API.0001.0002, and Imports.API.0001.0003.

Note: The levelSeparator value can only be a single character and must be allowable in a docId. If a character is not entered, the default is a period.

The levelBasedPadding value can only be between 3 and 6. If a value is not entered, the default is 4.

Sample mutation:

mutation MySampleMutation {
  importJobCreate (
    caseId: 5,
    input: {
      levelSeparator: “.”,
      levelBasedPadding: 4,
      documentIdType: LevelBased,
      level: “Imports/API/0001”
    }
  ) {
    rdxJobId
  }
}

Notification about browsers

On August 17, 2021, Microsoft ended support for Microsoft Internet Explorer (IE) 11. As of this date, Nuix Discover no longer supports 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 as soon as possible: 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 - August 2021 (10.8.001 - 10.8.002)

View pane > Chat: Join and leave events displayed

If an administrator configures the Connect API importJobAddMessageEvents mutation to include join and leave events for imported chat messages, these events now appear in the View pane, as shown in the following figure.

Join events and counts appear in the JOI column. Leave events and counts appear in the LEF column.

Join event and counts

Manage Documents > Imports: User interface usability enhancement

When you add an import job using the Import window in the Manage Documents section, you can now click outside of the Import window and the window will no longer close. To close the window, you can click Cancel or submit the job.

Important: Previously, if you clicked outside of the window, the window closed. You could, however, click the Add button on the toolbar on the Manage Documents > Imports page to retrieve your in-progress settings. That is no longer the case.

Use the following procedure to retain the in-progress settings for your Import job.

  1. In the Import window, on the Schedule page, select Place on hold, and then click Save as draft, as shown in the following figure.
  2. Schedule page

    The window closes.

  3. To continue with the import job settings, on the Manage Documents > Imports page, in the Name column, click the link for your draft import job.

Manage Documents > Imports: New level separator for levels-based Document ID

The new Level separator option, shown in the following figure, is available on the Document ID page in the Import window, if you select Get Next - Levels based under Document ID.

This option uses a period by default, but you can replace the period with a different single character.

Note: If you provide a disallowed character, the application notifies you.

Document ID page

Tip: This setting is used to separate the levels in the Document ID. To view the format of the Document ID, click the View Document ID link.

After the job completes, this setting also appears on the Properties page of the import job.

Portal Management > Cases and Servers > Cases: Non-billable column

A new column named Non-billable is now available on the Portal Management > Cases and Servers > Cases page.

You can filter the column to display billable or non-billable cases, as shown in the following figure.

If a case is non-billable, a black dot appears in this column for a case or cases.

Note: A system administrator can select the Non-billable option on the Properties page for a case.

Cases page showing non-billable option

Portal Management > Errors: New option to view errors for the last one (1) day

On the Portal Management > Errors page, you can now view errors for the last one (1) day, as shown in the following figure.

Errors page showing view errors for last one day

Portal Management > Settings: New portal option for authentication to a secured Elasticsearch cluster

The following new portal option, shown in the following figure, is available on the Portal Management > Settings > Portal Options page: User audit log service Elasticsearch API key

The user audit log service now supports using an Elasticsearch API key and ID for authenticating to a secured Elasticsearch cluster. To connect to a secured Elasticsearch cluster, enter the Elasticsearch API key and API ID as a JSON string into this setting.

Use the following procedure to configure this option.

  1. On the Portal Management > Settings > Portal Options page, in the User audit log service Elasticsearch API key box, provide a JSON string {“ElasticsearchApiKey”:“*******”,“**ElasticsearchApiId”:“*******”} containing the Elasticsearch API key and API ID to use for authentication.
  2. Portal Options page
  3. Click Save.

Connect API Explorer: Import binders using the importJobAddDocuments mutation

The importJobAddDocuments mutation contains a new binders object allowing users to populate existing binders as well as create new binders. If the user provides a binder value that matches an existing binder, the document will be added to the existing binder. Otherwise, a new binder is created. Permissions will not be assigned to any new binders generated, are set as shared, will not be security override type binders, and will not be mobile binders. If a binder name already exists, a new binder will not be created.

Sample mutation:

mutation MySampleMutation{
  importJobAddDocuments(caseId: 4070,
  input: {
    rdxJobId: 4128,
    documents: {
      documentId: “ACTEST_00000001”,
      binders: {
        values: [“Binder 1”,“Binder 2”]
      },
      fields: {
        name: “All Custodians”,
        action: Append,
        values: “Custodian from API”
      }
    }
  }){
    documentCount
  }
}

Connect API Explorer: Import issues using the importJobAddDocuments mutation

The importJobAddDocuments mutation contains a new issues object allowing users to populate existing issues as well as create new issues. If the user provides an issue value that matches an existing issue, the document will be added to the existing issue. Otherwise, a new issue is created. Permissions will not be assigned to any top-level issues.

Note: The issue values field should contain the full issue path, where the issue depth is indicated with the backslash or forward-slash characters, as shown in the following sample mutation.

Sample mutation:

mutation MySampleMutation{
  importJobAddDocuments(caseId: 4070,
  input: {
    rdxJobId: 4128,
    documents: {
      documentId: “ACTEST_00000001”,
      issues: {
        values: [“Top Issue/subissue 1”,“Top Issue/subissue 2”]
      },
      fields: {
        name: “All Custodians”,
        action: Append,
        values: “Custodian from API”
      }
    }
  }){
    documentCount
  }
}

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 - 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