Nintex RPA release notes

Nintex RPA Central 2.4.0 and Nintex Bot 17.4.1: August 20, 2021

Follow this page and the Nintex RPA Community blog to stay updated on product release information.

Important: 
  • August 20, 2021, product update - We released an updated version of Nintex Bot (17.4.1) and Nintex RPA Chrome Extension (1.2.0.0) that resolves the web table and targeting issues with Google Chrome and Microsoft Edge that we recently communicated to you. If you already upgraded to Nintex RPA Central 2.4.0, then you do not need to download and install Nintex RPA Central at this time because there are no new updates. If you already upgraded to Nintex Bot 17.4.0, then you should download and install Nintex Bot 17.4.1 to ensure that you do not experience any of the issues identified in Nintex Bot 17.4.0.

  • August 16, 2021, product update - We discovered that Nintex Bot 17.4.0 contains some changes that cause targeting issues with Google Chrome and Microsoft Edge. Some of these changes that caused the instability in our web table targeting were to support what we internally call Shadow DOM, a construct in some web pages that have additional, hidden web pages behind what you actually see. These enhancements are being removed from 17.4.0 and the Nintex RPA Chrome Extension because they caused unforeseen problems targeting standard web tables. We will continue to enhance and refine our targeting to support Shadow DOM in the future, but if you are waiting for this enhancement, open a Nintex Support case to get help building botflows that interact with these types of web pages.

  • August 13, 2021, product update - We released a new Nintex RPA Chrome Extension version (1.1.0.2) and encourage you to update to that version.

    If your botflows are not running as expected with Nintex Bot 17.4.0, contact Nintex Support. At this time, if you need to design new botflows or edit existing botflows with new Chrome actions, we suggest that you wait for the next Nintex Bot release, which is expected to be released soon.

    You may choose to go back to a previous version of Nintex Bot (be sure to uninstall 17.4.0 prior to installing a previous version). However, if you have upgraded to Nintex RPA Central 2.4.0, you should remain on that version regardless of the Nintex Bot version that you choose to use. If you were previously running Nintex Bot 16.x and Nintex RPA Central 1.x, contact Nintex Support.

  • August 11, 2021, product update - Nintex Bot 17.4.0 may not work with web tables in Google Chrome or Microsoft Edge properly at this time. We are working to address this issue and release an updated Nintex Bot version soon. In the meantime, we released a new Nintex RPA Chrome Extension version (1.1.0.1) and encourage you to update to that version to resolve a targeting issue with Google Chrome and Microsoft Edge.

Nintex RPA Central 2.4.0 new features and resolved issues

Important: You must update all of your Nintex Bots to version 17.4.1 in order to use the new Participant role and botflow permission features available in Nintex RPA Central 2.4.0.

New features

  • You can now assign users to a new Participant role. Unlike Designers and Administrators, Participants can only view and run published botflows with manual start events. This new feature provides you with tighter security for your botflows and may change the access strategy that you use for designing and running botflows. For more information, go to User management.

  • Administrators are now able to assign botflow permissions to individual users and groups of users (all designers and all participants). Users who have access to botflows can interact with them based on their role. For more information, go to Botflows.

Note: To support backwards compatibility and ensure that your current users can access all of the botflows that they have been able to in previous versions, all current Designers are given permission to all existing botflows after you upgrade to Nintex RPA Central 2.4.0. After upgrading, Nintex recommends that you review your organization’s botflow access strategy, assign users who only need to run botflows to the new Participants role, and then review your list of botflows and assign appropriate permissions to them.

Resolved issues

  • Nintex RPA no longer experiences issues with a local host installation and CPU usage.

  • Botflows with schedules now correctly display the start dates after upgrading.

  • Start Botflow actions used in Nintex Workflow Cloud workflows are now more reliable.

  • Delays updating a botflow’s name and description on older hardware or slower domains no longer occur.

Nintex Bot 17.4.0 and 17.4.1 enhancements and resolved issues

This section includes all of the enhancements and resolved issues in Nintex Bot 17.4.0, which was released on August 11, 2021, and Nintex Bot 17.4.1, which was released on August 20, 2021. Nintex Bot 17.4.1 includes all of the enhancements and resolved issues that were also in Nintex Bot 17.4.0.

Important: You must update all of your Nintex Bots to version 17.4.1 in order to use the new Participant role and botflow permission features available in Nintex RPA Central 2.4.0.

Enhancements (17.4.0 and 17.4.1)

Redacted enhancement (17.4.0 and 17.4.1)

  • On August 13, 2021, when Nintex RPA Chrome Extension 1.1.0.2 was released, support for Banno Banking software had to be removed. This support will be reintroduced in a future release.

Resolved issues (17.4.0)

  • Botflow email actions that are set up to receive emails without authentication no longer require an SMTP password for login (but do require an email account).

  • The Set Field action no longer fails after you execute the Toggle Record action.

  • You can now successfully import data when adding custom fields in the Data Wizard.

  • You no longer receive a System.IndexOutOfRangeException error when playing an action that runs through all records within a range.

  • Botflow instances that are closed and reset no longer erroneously get stuck in a running state. This fix ensures that you can terminate botflow instances, if necessary.

  • Nintex Bot no longer gets stuck in a queued state when starting and targeting fields in Google Chrome. This fix allows you to successfully use Nintex Bot with Google Chrome.

  • Email actions in a loop correctly return contextual information from each email.

Resolved issues (17.4.1)

  • CSV imports with rows that have no commas no longer fails. The remaining fields are populated with an empty value, not the duplicated value.

  • Nintex Bot now works correctly with web tables in Google Chrome and Microsoft Edge.

  • Targeting issues with Google Chrome and Microsoft Edge have been resolved.

  • Nintex Bot no longer incorrectly reports an offline status in Nintex RPA Central.

Download files

Repackaging

The following MSI packages are provided for your convenience:

System requirements

General

  • Nintex RPA Central and Nintex Bot must be installed on a computer that is part of a network domain.

  • Nintex RPA Central requires access to a Nintex URL to verify licensing. Without this access, Nintex RPA Central will not be allowed to run.

  • If a firewall is in place, configure it to allow HTTPS traffic on port 443 to access the following URL: https://wus-api-rpa.nintex.io

Recommended

  • 2.0 gHz processor or higher

  • 4 CPU cores or more

  • 16 GB RAM or higher

  • 500 MB hard drive space or higher

  • 1024x768 display resolution or higher

  • Dual monitors

  • Local administrator rights

Minimum

  • 1.8 gHz processor

  • 2 CPU cores

  • 3 GB RAM

  • 300 MB hard drive space

  • 1024x768 display resolution

  • Local read, write, execute, delete rights

Supported operating systems

Nintex Bot 17.4.1 and Nintex RPA Central 2.4.0 only support 64-bit operating systems.

  • Windows 10

  • Windows 8.1

Supported servers

  • Windows Server 2019

  • Windows Server 2016

Supported browsers

  • Internet Explorer 11 (Nintex Bot only)

  • Google Chrome

  • Microsoft Edge

For more information, read about web browser support in Nintex RPA.

Previous releases