Release Notes

Nimonik releases features, bug fixes and performance improvements on a rolling basis. We have no downtime during releases. This page contains the past six months of changes as well as upcoming changes that may affect usage of the web or mobile application.

Please see our Change Management Policy here for further details.

Level Description Examples Customer Notification
1 Very substantial changes that will change the core functionality of the platform. Removal of Incidents module with no replacement Minimum 6 months
2 Significant changes to the products that will alter documented workflows, how-to guides, and support manuals. These changes will substantially change the way users interact with the software. Removal of Scheduler module and replacement with Internal Documents Minimum 2 months
3 Small changes to functionality that will affect the workflow and the way the platforms are to be used Deployment of Internal Actions, Change of terminology on certain buttons Minimum 2 weeks
4 Bug fixes, security patches, upgrades to underlying software, and minor improvements to the web portal Upgrade MySQL, Change a drop down to multi-select, Addition of new filters on a report, etc. None – Release Notes

Upcoming Changes (next six months):

  • Freeze panel and column headings at top of the CO page when scrolling (Level 3): Key search, filter and edit tools. and column headings will be added to a panel that will follow the user as they scroll down the page. This will allow users to search, filter, and perform bulk actions without scrolling up.
  • Show CLCOs in all available languages (Level 2): On the library page and in COs, users will be able to see CLCOs in all available languages. In COs, users will be able to track alternate language CLCOs for changes.
  • Improve CO creation workflow (Level 3): The CO creation workflow will be updated to include custom field and system field selection.
  • Major CLCO page improvements (Level 2): The CLCO page will be updated to match the CO page. This will include moving to a more tabular format, allowing users to sort and filter by column headings, frozen panned, more rows per page, and more.
  • Major Improvements to Library/Add Documents Page (Level 2): The add documents page will be removed, and users will be able to add documents directly from the library. Additional information will be added to the page, including document description,  global uses, and version information. The page will also be cleaned up to improve readability.
  • Action Page Improvements (Level 2): We will be making the following changes to the internal and external action pages to improve usability:
    1. Bulk action closure: The checkboxes on the page will be used to select actions. Selected actions can then be closed in bulk
    2. Single action page: Open and closed actions will all be displayed on a single page. Filters will allow users to determine which actions (open, closed, or all) will be displayed
  • Search Improvements (Level 3): Global search will be introduced with robust filters that will allow users to obtain precise results.
  • Template Archiving (Level 3): Account admins will be able to remove outdated templates from the templates page without deleting them. This will allow them to maintain a cleaner templates page while still being able to run reports on archived templates.
  • Convert Corrective Actions to Internal Actions (Level 2): Audit corrective actions and effectiveness assessments will be moved from the external actions page to the internal actions page. This migration will introduce two key functionalities
    1. Create internal actions for audits (audit corrective actions)
    2. Create internal actions for existing internal actions (effectiveness assessment)
  • API integration for CO module (Level 1) We will expand our API to include CO and CLCO data

Upcoming Changes (next six weeks):

  • Sort and Filter by Column Headings in CO (Level 3): Users will be able to click on column heading to open a menu that allows them to:
    1. Sort in ascending or descending order (done for system fields, coming soon for custom fields)
    2. Filter based on column contents
  • New Clause Classes: Users can now filter CLCOs for the following clause types:
    1. Obligation
    2. Applicability
    3. Information
    4. Obligation for Government
  • Library Page Improvement (Level 3): When users first arrive on the library page, no documents will be displayed. Once they use the search bar or filters, matching documents will be displayed. This will dramatically improve the speed of the library page, particularly for accounts that subscribe to multiple jurisdictions

September 2022 Changes

  • Add two decimal places to calculated scores: Calculated scores, such as compliance level, will now have two extra decimal places. Fore example, a score of 55% will now be 55.00%
  • Allow account admins to edit and delete internal documents: Account administrators can now edit and delete the internal documents in their account (more info)
  • Tighten user restrictions for COs: While restricted users will still be able to assess documents and issue internal actions, they will no longer be able to do the following (more info)
    1. Create new COs
    2. Access the Edit page of existing COs
    3. Add and delete CO custom fields
    4. Show and hide CO system fields
  • Sort COs by column : Users can now click on some CO column headings to sort COs (more info)
  • Allow Account Admins to Delete CLCOs: Account administrators now have the option to delete CLCO records and all associated actions (more info).
  • Include custom fields in exports of internal actions report: When you export this report, any custom fields associated with your audit template internal actions will be included (more info).
  • Various fixes, updates, and performance improvements
  • Improvements to document processing tools

August 2022 Changes

  • Allow users to customize audit scoring : Users can now set assessed compliance and compliance impact for the blue, green, red, and yellow audit assessment options on the template edit page. When score is calculated, the risk is multiplied by an audits items assessed compliance and compliance impact to produce a score (more info).
  • Update scoring calculations: Scoring calculations have been adjusted to work with assessed compliance and compliance impact (more info).
  • Allow users to specify which CO columns are visible: Users with editing rights can now use the ‘Show/Hide System Fields’ page to adjust the columns that appear in COs (more info).
  • Add tooltips to risk matrix to indicate colour: Tooltips indicating cell colour have been added to the risk matrix to make Nimonik more accessible for users that may be visually impaired.
  • Add column to corrective actions report that shows assessment: The thin coloured line that used to indicate audit item assessment in this report has been replaced by a dedicated column. This column contains a coloured circle indicating the selected assessment option with a tooltip for users that may be visually impaired.
  • API changes for scoring calculation updates: API endpoints related to audit scoring have been updated to work with assessed compliance and compliance impact. If you are interested in learning more about Nimonik’s API capabilities, click here.
  • [BUG] General users can see management reports by entering URL: General and restricted users can no longer access any reports other than the all new and updated documents report. A report option has been added to the top menu to allow them to access this report more easily.
  • Audit scoring terminology update: A number of terms related to audit scoring have been updated. Notably ‘weight’ (formerly risk) and ‘compliance level’ (formerly score). For more information on audit scoring, click here.
  • [BUG] Red-Line Comparison not working for certain clauses: A minor bug was causing red-line comparison to be unavailable for certain clause level updates. The issue has now been corrected.
  • Set assessed compliance and compliance impact for pink assessment option: Users can now set assessed compliance and compliance impact for the pink assessment option. This change will facilitate customizations to audit scoring (more info).
  • Add links to help page on audit scoring: Wherever users can see or adjust audit scoring, we will not be showing a link to the help page that explains how calculations are done.
  • Add tooltips to show how scoring is calculated: In reports where audit scoring is shown, a tooltip has been added that displays the equation used to calculate it
  • [BUG] Custom fields not being included in search results correctly: Due to a bug, only custom field text that was populated using the bulk edit feature was being included in search results. Now search will include matching custom field content that was added both individually and in bulk
  • Various fixes, updates, and performance improvements
  • Improvements to document processing tools

July 2022 Changes

  • CO Custom field order should match directory: The order of custom field in COs is now the same as the order set by account administrators on the custom field directory page (more info).
  • Bug fix: Select all is not working as expected when one or more filters is applied (CO/CLCO): Selecting all after applying a filter to documents or clauses, would select all clauses in the CO or CLCO, not just those that matched the filter criteria. Now selecting all will select all documents or clauses on the page, with the option to select all documents or clauses matching current filter criterial.
  • Add tooltips to the coloured circles on the CO assessment option settings page: Tooltips indicating colour were added to the page to assist users that may be visually impaired.
  • Replace Assessment colour indicator in document and clause assessment report with assessment option titles: The coloured circles that appeared in this column were replaced with the corresponding assessment option titles. This change was made to make the report clearer and more accessible for users that may be visually impaired.
  • Various fixes, updates, cleanup, and performance improvements
  • Improvements to document processing tools

June 2022 Changes

  • Use Directory Custom Fields with COs and CLCOs: User can now select directory custom fields to be included in their COs. As part of this change, existing CO custom fields were converted to directory custom fields and the ‘manage custom fields’ page was introduced (more info)
  • Introduce multiple choice type custom fields: A new type of custom field was introduced that allows users to choose from a set of pre-selected options (more info)
  • Allow users to reorder directory custom fields: Account administrators can now re-order directory custom fields by dragging and dropping them. The order in which custom fields appear in the directory will determine their order in COs (more info)
  • Allow account admins to determine which custom fields appear on the audit index page: Account administrators can now use the ‘Add/Remove Custom Fields’ option to display custom fields on the audit index page (more info)
  • Bug fix: changing Assessment will close CLCO external actions: Changing a clauses assessment was closing all outstanding external actions. This was corrected, and there is no longer any link between external actions and clause assessment.
  • Various fixes, updates, and performance improvements
  • Improvements to document processing tools

May 2022 Changes

  • Send weekly email summary of Internal actions: Nimonik will now send a weekly email summarizing outstanding internal actions. The specific contents of the email are determined by user type (more info).
  • Remove “Selected Clauses” Feature from CO page: The selected clauses feature allowed users to see the first five assessed clauses of a CLCO on the CO page. This feature was removed because it was not very useful (most CLCOs have hundreds of clauses) and to improve the performance of the CO page.
  • Add column showing closure status to action reports exports:  A column was added to the internal and external actions reports that indicates whether each action was closed on time, closed late, is overdue, is pending.
  • Show audits dates: Audit start date, audit date, audit completion date, and the final corrective action closure date were added to the audit page, the audit index page, audit reports, and audit exports (more info).
  • Bug fix: Prevent SSO users from changing their login info: If an SSO user edited their email address or name, they would no longer be able to access their account through SSO until the changes were undone. To prevent this, user information can no longer be edited by users that have logged via SSO.
  • Make teams behave like users in CO responsible party and user-type custom field drop-downs: Only teams that have been granted access to a CO will appear in its responsible party and user-type dropdowns.
  • Move CO Category and Sub Category to Columns: Category and sub category were converted to columns in COs. Their values can now be edited in the same way as text type custom fields (more info).
  • Make CO and CLCO tables 100% width: The width of the CO table was expanded to occupy the entire page. This will allow users to see more information without scrolling.
  • Increase number of rows on CO/CLCO page to 100: The number of rows per page was increased from 30 to 100. This will allow users to see more content without changing page.
  • Add Document Status column to COs: The ‘Status’ column indicates whether a document is proposed, in force, repealed, etc.
  • Allow users to select which custom fields are visible in audits: Users with editing access to an audit template can now select which custom fields will be included in the audits generated from it (more info).
  • Add custom fields to audit template internal actions: When an internal action is created from a template, the selected custom fields of that template will now be included in the action (more info)
  • Use directory custom fields for audits: Users can now select directory custom fields to be included in their audits at the template level. As part of this change, all existing audit custom fields were converted to directory custom fields (more info).
  • API changes for audit custom field improvements: API endpoints were added and adjusted to accomodate directory custom fields. If you are interested in learning more about Nimonik’s API capabilities, click here.
  • Show final corrective action closure date: A new date was added to audits that indicates when the last corrective action was closed (more info).
  • Various fixes, updates, and performance improvements
  • Improvements to document processing tools

April 2022 Changes

  • Add description to company custom fields: Users can now add a description to custom fields that will appear as a tooltip in COs (more info).
  • Change title of ‘Facilities Managed’ section on edit user page: There were two sections on the user edit page titles ‘facilities’ one to display the facilities that had been shared with the user, and the other to display the facilities that they could manage. The title of the second section was updated to ‘Facilities Managed’.
  • Add user and risk type custom fields to custom fields directory: Account admins can now create and edit risk and user type custom fields in the directory (more info)
  • Add tooltip to Responsible Party Column header in COs and CLCOs: An explanatory tooltip was added to the responsible party column header in COs and CLCOs
  • Various fixes, updates, and performance improvements
  • System upgrades
  • Improvements to document processing tools

March 2022 Changes

  • Create Custom Field Directory: Create a central directory when account administrators can create and manage custom fields for the entire account (more info)
  • Remove the Delete and edit option on single documents in COs: CO documents can now be edited only using the bulk edit interface.
  • Allow users to clear risk column values in COs and CLCOs: Add a clear option to the edit modal for the risk column.
  • Remove Scheduler Module: The scheduler module has been completely removed from Nimonik. For more information on how your data will be migrated, click here
  • Include Risk, Likelihood and consequence in CO exports: If a CO includes a risk column, exports will contain three additional columns. One for the numerical risk value, one for the selected likelihood, and one for the selected consequence.
  • Show document extract on document page: Nimonik is now using artificial intelligence to generate document extracts. When available, these extracts will appear on the document page (more info)
  • Remove Incidents Module: The incidents module has now been removed from Nimonik. The owners of accounts that were using this module should have been sent an export of all of their incident data by their Nimonik account manager.
  • Add Responsible Party filter to COs and CLCOs: A dropdown has been added to the CO and CLCO pages that will allow users to filter by responsible party (more info).
  • Add User-Type custom field filters to COs: Dropdowns have been added to the CO and CLCO pages that will allow users to filter by user-type custom fields (more info)
  • Allow account admins to transfer permissions from one user to another: An option has been added to the edit user page of general and restricted users to transfer their permissions to a different user or team. When deleting a user that has permissions, a prompt will appear that will allow users to transfer their permissions first (more info)
  • Include Connected Custom Fields Data for CLCOs in Exports: Connected custom field contents will be included in all CO exports.
  • Include Clause type in CO exports: Clause type (obligation, non-obligation) will be included in all CO exports.
  • Bug: Checkboxes do not work on document search results: The checkboxes that allow users to select documents were could not be used when viewing search results. This has now been corrected.
  • Various fixes, updates, and performance improvements
  • Improvements to document processing tools
Contact us