SaaS / Hosted Monthly Release Notes - March 2022 (10.10.001 - 10.10.002)

Improved Nuix Discover login experience

In previous versions, SaaS users who inadvertently navigated to the Login Service URL received an error message.

Nuix SaaS Administrators have now configured the login experience such that users who go to the Login Service URL are redirected automatically to the appropriate portal URL.

View pane: Keyword summary

This release includes a new Keyword summary feature that enhances review productivity. You can now review hits in a document in a more efficient manner and focus your review on the specific content immediately around the keyword highlights enabled in the formatted and unformatted content views.

To use the Keyword summary feature:

  1. In the View pane, in Formatted content or Unformatted content view, on the toolbar, click Keyword summary.
  2. View pane showing Formatted or Unformatted content
  3. The layout changes and the application displays collapsed sections for only those parts of the document that contain hits. The layout also includes line numbers.
  4. View pane showing collapsed sections of content

    Note: If a document does not contain hits, the application does not collapse the sections, but does display line numbers.

    Each section includes a number next to the header of the section to indicate the number of collapsed lines, as well as the following buttons:

    • Expand more button Expand more: Expands the section with several lines before and after a hit, providing additional textual context of a hit in the document.
    • Collapse button Collapse: Collapses the section. This button appears in place of the Expand more button after clicking that button.
    • Expand all button Expand all: Expands the entire section and allows you to view all content in a section.
    • Collapse all button Collapse all: Collapses the entire section. This button appears in place of the Expand all button after clicking that button.
  5. To revert to the standard view, on the toolbar in the View pane, click Keyword summary.
  6. View pane showing the Keyword summary icon

Conditional Coding: New Binders - Custom field for conditional templates

If your administrator added the Binders - Custom field to a conditional template in the Conditional Coding pane, you can now code documents to the binders included in this field.

Conditional Coding pane showing the Binders - Shared and Custom sections

Translate: Italian available as a target translation language

You can now translate documents into Italian using the Microsoft or Google translation services available in the Translate tool or the Translate pane on the Documents page.

Case Setup > Conditional Templates: Add a Binders - Custom field

On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, you can now add the Binders - Custom field to a conditional template.

To add a Binders - Custom field to a conditional template:

  1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Binders - Custom.
  2. Click the Add field button.
  3. Coding fields page showing the Add field button
  4. In the Binders - Custom window, select one or more binders and then click Save.
  5. The Binders - Custom window for saving selected fields
  6. The Binders - Custom field is then available in the Conditional Coding pane for the template, and reviewers can code documents to the binders in this field.
  7. Conditional Coding pane showing the Binders - Shared and Custom sections

Additional notes about the first release of this feature:

  • You can add only one Binders - Custom field to a coding template.
  • To change the binders included in the Binders - Custom field, you must delete the field and add a new one. In a future release, this field will be editable.

Case Setup > Issues: Enhancements to cloning issues and child issues

You can now clone child issues as well as top-level issues. Previously, you could clone only top-level issues.

A Clone button is now available on the toolbar.

Case Setup - Issues page showing the Clone button

Previously, the Clone issue button was available next to the issue on the Case Setup > Issues page.

Case Setup - Issues page showing the Clone issue icon

Note: You can clone only one top-level issue at a time. If you clone an issue, the application also clones the child issues and its subissues.

To clone a top-level issue:

  1. On the Case Setup > Issues page, select a top-level issue.
  2. Case Setup - Issues page showing the selection of the top level issue
  3. On the toolbar, click Clone.
  4. In the Clone issue window, confirm or modify the issue name.
  5. The cloned issue appears in the list.

To clone a child issue:

  1. On the Case Setup > Issues page, click the link for a top-level issue.
  2. On the Child Issues page, select a child issue or issues.
  3. Note: When you select a child issue, the application automatically selects any subissues of the child issue.

  4. On the toolbar, click Clone.
  5. In the Clone issue window, confirm or modify the issue name.
  6. Click OK.
  7. The cloned issue appears on the Case Setup > Issues > Child Issues page.

Case Setup > Issues: Move issues

You can now move top-level issues and child issues.

Note: If you move an issue, the application also moves the child issues and its subissues.

To move a top-level issue:

  1. On the Case Setup > Issues page, select a top-level issue.
  2. Case Setup - Issues page showing selection of the top level issue
  3. On the toolbar, click Move.
  4. In the Move issues window, select a top-level issue or child issue destination for the issue you want to move.
  5. Move issues window showing the selected issues to be moved and their chosen destination
  6. Click OK.
  7. The issue moves to the destination you selected.

To move a child issue:

  1. On the Case Setup > Issues page, click the link for a top-level issue.
  2. On the Child Issues page, select a child issue.
  3. Note: When you select a child issue, the application automatically selects any subissues.

  4. On the toolbar, click Move.
  5. Child Issues page showing a selection of issues and the Move button
  6. In the Move issues window, select a destination:
    • A new top-level issue.
    • An existing top-level or child issue.
    • Move issues window showing the selected issues to be moved and their chosen destination
  7. Click OK.
  8. The issue moves to the destination you selected.

Case Setup > Hierarchies: Preview a hierarchy

On the Case Setup > Hierarchies page, when you add a hierarchy, you can now preview the hierarchy before you save and run it to make sure that the hierarchy field and delimiter are useful.

The preview is limited to 10,000 documents and 1,000 nodes.

Note: You do not have to preview the hierarchy. After you set the properties for the hierarchy on the Properties page, you can skip to the Security page.

Add Hierarchy - Preview page showing a preview of the hierarchy

The hierarchy preview is available only when you add a new hierarchy. You cannot preview a hierarchy that you previously added. You can view the hierarchy in the Hierarchies section in the Browse pane on the Documents page.

Case Setup > System Fields: Italian now available as a target translation language

Italian is now available as an item for the Translation Languages field. If you grant a group permission to this field, group members can translate documents to Italian using the Translate tool or the Translate pane on the Documents page.

SaaS / Hosted Monthly Release Notes - February 2022 (10.9.005 - 10.10.000)

Load search file tool: Search for [RT] Family MD5 HASH

You can now search for the [RT] Family MD5 HASH field, as shown in the following figure, when using the Load search file tool, which is available on the Tools menu on the Documents page.

New Search page from the Load search file tool

Tools menu: Renumbering tool

The Renumbering tool on the Tools menu on the Documents page is now located in the Processing group, as shown in the following figure. You can still search for the Renumbering tool using the search box.

Note: This change was implemented in Nuix Discover version 10.9.003.

Processing group

Case Setup: Search Term Families: Hyphens now retained in search terms

On the Case Setup > Search Term Families page, when you include a hyphen in the Term label of a search term, for example, first-class, the application now retains the hyphen for the Term query, as shown in the following figure.

Terms page showing the search terms

Previously, when you saved the search term, the application retained the hyphen for the Term label, but removed the hyphen from the Term query, as shown in the following figure.

Terms page showing the selection of a search term

To ensure that hyphens are retained, a portal or system administrator must also check that one of the following two options are selected under Hyphens on the Portal Management > Settings > Indexing: Options page (for the portal) or the Cases and Servers > [Name of case] > Indexing: Options page (for the case), as shown in the following figure.

  • Treat as searchable characters
  • Apply all rules
  • Indexing Options page

As an example, if you select Apply all rules, three entries are in the index for any text that includes a hyphen, and first-class is indexed as follows:

  • first-class
  • firstclass
  • first class
  • Note: This has always been the case. This information serves only as a reference in the context of this update.

Manage Documents > Ingestions: Bloomberg Mail XML files and TAR attachments no longer create duplicate documents

When you ingest Bloomberg Mail XML files (that is, not chat) and corresponding attachments (TAR), the application no longer ingests the TAR file separately.

Note: TAR is short for Tape Archive and is a file in the Consolidated Unix File Archive format.

Previously, the application ingested the TAR file separately, which resulted in duplicate email attachments in Nuix Discover after ingestion.

Case Setup > People Identity: Updated user interface to enhance performance

The interface for the Case Setup > People Identity page (also referred to as the “Names Normalization” feature) has been updated to enhance performance when loading identities for large cases.

Previously, this page included a banner that displayed the following message, as shown in the following figure: New people names have been added. Click Normalize to normalize the people names to an identity. View non-normalized names.

People Identity page showing a banner message

As of version 10.10.000, the following changes have been made, as shown in the following figure:

  • The red banner and message no longer appear.
  • The page now includes three tabs:
      • Non-normalized: This tab displays the list of non-normalized names in the selected document set.
      • Normalized: This tab displays all normalized names in the selected document set.
      • All: This tab displays all normalized and non-normalized names in the selected document set.
      • People Identity page showing no banner and three new tabs

    The Download report and Assign identity buttons on the toolbar apply to the currently selected document set and tab.

Transcripts: Transcript search error now resolved: Requires reloading of affected transcripts

Previously, an error occurred when using the Find feature in Transcripts. The hits went to the wrong page or line number.

This issue is now resolved; however, you must reload any affected transcripts that you loaded into the case for Nuix Discover versions 10.5.001 through 10.9.004.

Portal Management > Cases and Servers > Cases > [Name of case] > Indexing options: Message appears in banner

The following message appears on the following pages on the Portal Management > Cases and Servers > Cases > [Name of case] page, as shown in the following figure: Case indexes must be rebuilt for changes to take effect after making updates on this page.

  • Indexing: Options
  • Indexing: Noise Words
  • Indexing: Alpha Standard
  • Indexing: Alpha Extended
  • Indexing: Thesaurus
  • Indexing: Stemming Rules
  • Indexing: File Type Rules
  • Cases page showing the different indexing options in navigation

Portal Management > Cases and Servers > Cases > [Name of case] > Content: File Type Rank: Message appears in banner

On the Portal Management > Cases and Servers > Cases > [Name of case] > Content: File Type Rank page, as shown in the following figure, the following message now appears in the banner: Indexing and Enrichment must be run for changes to take effect after making updates on this page.

Content File Type Rank page showing an indexing and enrichment message banner

Portal Management > Errors: Enhanced performance and new check box to view legacy errors

In version 10.10.000, the application changed the method for storing errors and created a new table in the portal database to populate errors. This change was made to enhance performance.

To view the errors for versions up until version 10.9.005, select the See legacy errors check box, as shown in the following figure.

Note: Errors will be written only to the new table for versions 10.10.000 and higher.

Errors page indicating the See legacy errors selection

SaaS / Hosted Monthly Release Notes - December 2021 (10.9.003 - 10.9.004)

Enhancements to search settings

On the Documents or Search pages, you can now rerun and change the context of your current search to display Renditions (instead of base documents), Threading, and Sources and attachments, as shown in the following figure.

Current search criteria

Previously, the Renditions, Threading, and Sources and attachments buttons on the Documents and Search pages were non-clickable icons and indicated the search preferences settings that you set on the Search page or on the User name menu, but you could not click these icons. The icons are now clickable buttons that you can use to change the context of your current search.

After you click a button, the background changes from white to dark blue to indicate the change to your search results, for example, for Renditions, as shown in the following figure.

Search criteria for Renditions

If you select the Threading button, the Sources and attachments button appears with a light blue background, as shown in the following figure, because threaded documents include sources and attachments.

Search criteria Threaded view

Additional information

  • The application captures any changes to the search settings in the search history.
  • When you change your search settings for your current search using the buttons on the Documents or Search pages, the changes are not applied to your default search preferences that you typically set on the User name > Search preferences menu or using the Search preferences check boxes on the Search page.
  • If an orange warning icon, as shown in the following figure, appears, it is not clickable. This warning indicates that your search contains one or more documents to which you do not have access, such as when accessing a previous search result that contains documents to which you no longer have access. Contact your administrator if you think that you received this warning in error.
  • Search criteria for Renditions in all documents

Load search file tool: Not Found page now displays [RT] MD5 HASH and Page Label information

If you use the Load search file tool to search for documents or entities that contain an [RT] MD5 HASH field, if the application does not find matching documents or entities, the application now indicates that on the Not Found page in the Load Search file window (for the [RT] MD HASH field and the Page Label), as shown in the following figure.

Load search file page

Analysis > Search Terms: Counts for hits apply only to base documents

On the Analysis > Search Terms page, the counts for hits now include only hits in base documents. Previously, the counts included hits in base documents and renditions.

Case Setup > Search Term Families: Document count now includes only base documents

On the Case Setup > Search Term Families page, the Document count column now includes only base documents. Previously, the column included base documents and renditions.

Note: For this change to take effect, you must reprocess the search term families.

Manage Documents > Imports: Preserve field mapping for one-to-many case fields

In previous versions, if a load file field was mapped to multiple Nuix Discover case fields (in the Import window on the Field Map page), only the first field mapping was preserved in subsequent import jobs using the same load file. Now, all field mappings are preserved when the user submits subsequent import jobs using the same load file.

As shown in the following figure, the [Meta] Document Kind field is mapped to two case fields, [Meta] Document Kind and Document Type.

Import page

Manage Documents > Ingestions: NIST list updated - September 2021

The Ingestions feature now uses an updated version of the NIST list, released in September 2021. 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 > Productions: Allow users to select placeholder page and font size

On the Production Rules page, users can now select the page and font size of placeholder pages in the Placeholder area. To make changes to the Placeholder area, in the Rules column, select Custom Placeholder. To determine the page size, under Placeholder, select either Letter or A4. To determine the font size, select a number in the Font size list. The default values for both of the fields are taken from case settings. Any changes you make to the Placeholder area on the Production Rules page override the defaults for that production.

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.