Nintex RPA LE release notes

Nintex RPA Central 2.14.0 and Nintex Bot 17.15.0: February 7, 2024

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.14.0 resolved issue and enhancement

Scheduled bots now run on the correct dates, per the schedule configuration. The Nintex RPA Central Scheduler has been re-architected to better handle all schedule iterations. For more information on scheduling botflows, see Configure a botflow.

Nintex Bot 17.15.0 enhancements, resolved issues, and known issue

Enhancements

Improvements in the Nintex RPA Chrome Extension prevent the Select Item and Search actions from failing and timing out.
A new Ignore Invisible Elements legacy targeting rule ensures that Nintex Bot only considers visible elements (elements that can be seen) and disregards all invisible elements (elements that have "visible:hidden" and/or "display:none" style properties) during action execution. When selected, this setting disregards all cached/invisible elements in the dom as these elements can be the original target (the target element used to create the action). Selecting this setting can improve reliability during the action execution when interacting with elements that look identical but are actually overlaid. Note that this feature is only available for targeting using Google Chrome technology (Google Chrome and Microsoft Edge). For more information, see Build Pane.
Two new Send Value action settings allow you to adjust the automatic speed of sent values. The Keystroke delay setting sets the automatic delay of the speed of the keyboard in milliseconds. The Use Virtual Key Codes setting allows applications to receive the physical key on which a user strikes on the keyboard to produce the results on the screen. These features are useful when you have a target that is sensitive to how and what is being sent to it and it will block what it does not recognize, or it will erroneously acknowledge valid input as invalid.
Improved Unlocker. For more information, see Unlock.
Improved smart targeting for emulators.
The Get Info action is enhanced for Chrome Elements to allow users to get the Elem's ID, Elem's Class, and Elem's Name.
Improved UIA targeting with the Mouse Sequence action.

Resolved issues

You no longer receive an unnecessary error if the user requires local admin rights for an Unlock action.
You no longer receive an error when using variables in the Resume action.
Recent botflows are now correctly sorted and listed in order on the Home Screen.
Botlfow imports are now saved to the correct botflow record even when the botflow name already exists in the Nintex RPA Central database.
You no longer receive a misleading "Database does not contain records error" when importing data results with duplicate field names in different cases.

Known issue

Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex Bot 17.14.0: September 7, 2023

Product release downloads on Nintex Customer Central

Note: Use Nintex Bot 17.14.0 with Nintex RPA Central 2.13.0, which was released on May 10, 2023. For information on this Nintex RPA Central version and the download links, see Nintex RPA Central 2.13.0 resolved issue and Download files.

Nintex Bot 17.14.0 improvements, resolved issues, and known issue

Improvements

Enhanced support for ITI Navigator Dynamic custom controls. These enhancements allow you to click a button and select a combo box item using one Select Item action. Other UIA list box targeting improvements allow you to successfully get list items using the Select Item action. In addition, improvements in the Nintex RPA Chrome Extension prevent the Select Item and Search actions from failing and timing out.
Changed the default registry key for Google Chrome and Microsoft Edge to support NativeMessagingHosts. This change prevents an error stating that the Nintex RPA Chrome Extension is not installed or cannot be connected to when it actually has been installed.
Google Chrome interactions on certain pages are now more consistent.
The browser name that is targeted is now displayed in the action details.
Improved performance with scripts.
Increased consistency in targeting.
You can now clear a list when a SQL query returns no result.
You now have the ability to enable legacy smart targeting rules. The new Apply Fallback Legacy Targeting check box in the Rules window allows you to enable old targeting rules when the Nintex Bot selector fail to find the target. Previously, when the selector failed to find a target, Nintex Bot attempted to find the target using the Best Match targeting rule. However, using this rule could find the wrong target instead of actually failing the action as intended. For more information on this new option, see Build Pane.
Optimized table searches in Google Chrome. Prior to this improvement, searches could take several minutes; now, they can take less than one second.
Token expressions for selectors are now supported. This improvement allows selectors to include either variables or database fields only. You must insert the variable or database field in the correct space within the selector.
If you are using AWS for email services, you can now create an AWS email account that can send emails using Nintex Bot. For more information on setting up this account, see Create an Amazon Web Services (AWS) email account.

Resolved issues

The target technology will now determine which Adobe application will be used with the Open PDF action. Previously, the default Adobe application was Adobe Acrobat and PDFs would not open when only Adobe Reader was installed.
The Close Me action now works correctly in botflows run from Nintex RPA Central.
Smart targeting now works correctly in the Jack Henry and Xperience applications.
Nintex Bot now displays the correct email information when the Show View action is run from Nintex RPA Central.
The Get List action now works correctly with tables.
Tasks reports no longer display with the action details and target information text overlapping.
You can now successfully target OCR actions in Microsoft Edge.
You can now search for an element in a highlighted drop-down menu in Navigator. Previously, you received an error stating that no matches were found when the target was highlighted.
You can now copy and import tasks that include Else If actions and the actions will remain associated with their If, Else, and End If actions from the source botflow.

Known issue

Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.13.0 and Nintex Bot 17.13.0: May 10, 2023

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.13.0 resolved issue

Scheduled bots no longer get stuck in a queued state. They now run as scheduled.

Nintex Bot 17.13.0 improvements, resolved issues, and known issue

Improvements

Improved browser actions in IE mode.
You can now press Ctrl + E when to edit the current row in a List form. Previously, you had to either right click and select Edit Row or click the pencil icon in the row column.

Resolved issues

Nintex Bot no longer greys out when using screen targeting.
The Nintex RPA Chrome Extension alert popup is now handled correctly using UIA technology, not Google Chrome technology.
Formulas now work correctly, even when a bracket is in the parameter.
Click actions (bypass mouse and manual clicks) now work correctly in Google Calendar Extension Manifest V3.
Scheduled botflows now complete successfully when diagnostics are on.
When spanning bridged tables, the Move Highlight action now finds the correct table.
The Mark Read action now correctly marks emails as read.
The botflow bulk export feature no longer crashes Nintex Bot.
Excel actions are now displayed when targeting Microsoft Excel windows.
The Unzip action now works correctly.
The field sizes that you set up in the Open Data action now behave correctly.

Known issue

Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.12.0 and Nintex Bot 17.12.0: February 8, 2023

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.12.0

General improvements and bug fixes.

Nintex Bot 17.12.0 improvements, resolved issues, and known issue

Improvements

You can no longer run the Set Mode action in tiny mode. Previously, running this action in tiny mode resulted in unreliable communication between Nintex Bot and Nintex RPA Central.
A new Chrome Request Timeout override in the botflow Settings allows you to lengthen the timeout time for websites that slow down the JavaScript engine in the browser.
You now have the ability to enable smart targeting rules. This feature allows you to manually change the order and priority in which selectors are used, manually edit the selector, turn on/off bridged tables, and manually ignore a selector. For more information, see Build Pane.
Improved diagnostic reporting.
You can now execute a bulk export and a bulk import of botflows from the Botflow Menu. For more information, see Menu Bar.

Resolved issues

Botflows no longer stop and Nintex Bot no longer becomes unresponsive when executing the Open Data action. Additionally, to help diagnosis issues when running the Open Data action, you can now select an error handling option (Run error task, Stop on error, Ignore errors); the default option for new actions is Run error task.
You can now successfully target Google Chrome. Be sure to install the updated Nintex RPA Chrome Extension to take advantage of this fixed issue and other targeting improvements in Google Chrome. This updated Nintex RPA Chrome Extension is Nintex RPA LE's first Manifest v3-compliant extension.
The Unlock action no longer fails when Credentials are populated by the Set Credential action, which is populated through a variable.
You can now save email attachments from senders. Previously, you could not save email attachments that had unsupported characters in the filename.
List lookups embedded within formulas now function properly.
The gear icon is now visible, allowing you to successfully change your Nintex RPA Central URL in Nintex Bot during the installation process.
Formulas, including nested ones, now work correctly.
Dataset schema fields are now configured correctly.
You can now successfully retrieve emails from a shared Microsoft Exchange Online email account that uses full OAuth authentication. For more information, see Email Accounts.
You can now successfully execute a Move Highlight action on a bridged table.

Known issue

Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.11.1 and Nintex Bot 17.11.0: December 14, 2022

Product release downloads on Nintex Customer Central

Note: Nintex Bot 17.11.0 was released with Nintex RPA Central 2.11.0 on November 17, 2022. This release combines the previously released Nintex Bot 17.11.0 version with the updated Nintex RPA Central 2.11.1 version, which includes general improvements and fixes.

Nintex RPA Central 2.11.1 resolved issue

Resolved issue

Scheduled botflows now run on the correct day and time after the Fall 2022 Daylight Saving Time change.

Nintex Bot 17.11.0 improvements, resolved issues, and known issue

Improvements

Improved Nintex Bot stability reduces software crashes.
Enhanced targeting in Google Chrome pages that contain an extraordinary number of tables. Be sure to install the updated Nintex RPA Chrome Extension to take advantage of this improvement in Google Chrome.

Resolved issues

The DOS command variable now works correctly.
You can now correctly save clipboard values to variables.
Formulas with multiple functions now work correctly.
Executing email actions no longer triggers a credential login prompt for each action and no longer causes botflows to stop.
Nested formulas now work correctly.
The Get Info action now works correctly in Microsoft Edge.
Get Mail actions using Microsoft Exchange Online with OAuth authentication now correctly retrieve emails when you use a filter on the Message Body. Previously, the custom search for email subjects stopped working when OAuth authentication was implemented.

Known issue

Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.10.0 and Nintex Bot 17.10.0: September 15, 2022

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.10.0 improvement

Improvement

Improved error messages and troubleshooting information to help you quickly resolve access and connection issues of bot clients.

Nintex Bot 17.10.0 new features, improvements, resolved issues, and known issues

New features

Ability to set up Gmail accounts with full OAuth authentication. For more information, go to Email accounts. For information on IMAP settings to receive email from Gmail accounts with full OAuth authentication, go to Email actions.
Ability to force a click action even if the control is disabled. Allowing a click when the control is disabled overrides the click behavior for UIA targets.
An Active Tab URL option is now available to use with the Get Info action for Google Chrome and Microsoft Edge.

Improvements

Improved speed and performance.
Optimized performance for targeting Google Chrome tables using selectors.
Improved UIA targeting.
Improved validation checks in the Execute SQL action form to reduce timeout errors.
Improved error messages in the Data Wizard.
Nintex Bot will now send a click even if the Google Chrome target cannot be given input focus.

Resolved issues

The RightOf Formula action now works correctly.
Corrected a Formula parameter parsing bug in the Formula builder.
Corrected the Open data action so that it runs the correct repeat settings, even when the settings are changed while a botflow is running.
The Avoid Conflicts option now works correctly in the Rename file action.
You no longer get an error when importing data from Microsoft Azure SQL while Nintex Bot is checking for the number of rows. Previously, you received an error when Nintex Bot instead checked for an error condition and then reattempted to run the query.
Microsoft Edge and Google Chrome now communicate correctly with Nintex Bot when using sessions with the same username.

Known issues

If you start two or more botflows from Nintex RPA Central or Nintex Automation Cloud on the same Nintex Bot and then you close the Nintex Bot after the first botflow has finished running, but before the second queued botflow has started, the second queued botflow will remain unresponsive in a queued state. Currently, to resolve this issue, you must terminate the botflow that remains in a queued state.
Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.9.0 and Nintex Bot 17.9.0: July 27, 2022

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.9.0 new features, improvements, and resolved issues

New features

Administrators can now retain and download audit logs. Choose the number of days that you want to retain audit logs (120 is the default) in the Audit log retention setting. Download your full audit log history to a CSV file anytime you desire. For more information, go to Audit logs.
The originator of botflow instances is now displayed on the Instances page. The source that started the botflow (username, Nintex Automation Cloud, Scheduler, or unknown) is visible in the Instance activities table.
A new Nintex RPA Central API endpoint, BotflowInventory, is available for Administrators to use to retrieve a list of botflows saved in Nintex RPA Central and their complexity data including the number of tasks, actions, variables, lists, and connections. For more information, go to Nintex RPA Central API.
A warning now displays if your license expired and your license key is invalid.

Improvements

Changing a user's role has been improved to increase the process's visibility and the feature's behavior.
Improved Nintex Bot connectivity to Nintex RPA Central.

Resolved issues

Botflows no longer get stuck in a queued state when run from Nintex RPA Central.

Nintex Bot 17.9.0 improvements, resolved issues, and known issues

Improvements

Targeting in Google Chrome, including targeting using the Search and Start Highlight actions, is improved. Ensure that you are using the latest Nintex RPA Chrome Extension in order to see targeting improvements.
Diagnostic logging flags are now pre-populated and off by default. These flags can help solve intermittent errors that cannot be easily reproduced.
New MailKit Protocol and Folder Quota UIA logging options help you resolve issues when your connection is lost and an action will no longer execute. The Folder Quota UIA setting allows you to turn on or off the call to GetQuota that could be breaking your connection. The MailKit Protocol setting creates logs in the exe directory.

Resolved issues

You can now successfully run a DOS command to log into an emulator.
The Unlocker no longer fails after completing a Microsoft Windows update.
PDF reports for Tasks now print all conditions for an If statement. Previously, if an If statement had more than four conditions, it was truncated in the PDF report.
The action culture setting for Create Variable using a text variable no longer reverts to the system culture when opening a botflow.
Fixed an issue with imported botflows that use the Botflow Directory token expression by directing it to the \ProgramData\Foxtrot Suite\Botflows\ folder. If the folder does not exist, it will be created by Nintex RPA LE.

Known issues

If you start two or more botflows from Nintex RPA Central or Nintex Automation Cloud on the same Nintex Bot and then you close the Nintex Bot after the first botflow has finished running, but before the second queued botflow has started, the second queued botflow will remain unresponsive in a queued state. Currently, to resolve this issue, you must terminate the botflow that remains in a queued state.
Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.8.0 and Nintex Bot 17.8.0: April 26, 2022

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.8.0 new feature and enhancements

New feature

You can now more easily use the Nintex RPA Central API to manage bots, botflows, users, and other related functions in Nintex RPA Central. For complete documentation on how to use the Nintex RPA Central API, including updated OpenAPI Specification v3 contracts, a sample Postman collection, and a list of featured actions and endpoints, go to the Nintex RPA Central API help topic.

Enhancements

Improved error handling and information error logging in SignalR messages.
You are now able to use a range of VPN IP addresses. Previously, you could use multiple VPN IP addresses, but not a range of them. For more information, read about how to configure a range of VPN IP addresses.
The Instances page now includes pagination to decrease page load times and to make viewing long lists of instances easier. The page now only loads a subset of the latest instances and includes automatic paging. As you scroll, more instances are returned. You can control the page size (the default is 50) by editing the SharedServiceSettings file located at /Program Files (x86)\Nintex\RPACentral\RPACentral.

Nintex Bot 17.8.0 new features, improvements, resolved issues, and known issues

Note: If you are in the banking industry and use Fiserv, you are most likely moving from Internet Explorer-based automations to Google Chrome or custom applications. We have made some enhancements for you to be more successful with both, and particularly with Navigator. Upgrade today!

New features

You can now use the new Open Chrome action to start Google Chrome.
You can now use the new Open Edge action to start Microsoft Edge.
You can now convert the following browser actions into new actions for a different browser. The converted actions are saved as new tasks. Before executing converted actions, be sure to test them! For more information on converting all browser actions at once, go to Convert Browser Actions. For more information on converting individual browser actions, go to Task.
- Internet Explorer actions into Google Chrome actions. The converted actions are named using the following naming convention: [TaskName]_Chrome
- Internet Explorer actions into Microsoft Edge. The converted actions are named using the following naming convention: [TaskName]_Edge
- Google Chrome actions into Microsoft Edge actions. The converted actions are named using the following naming convention: [TaskName]_Edge
- Microsoft Edge actions into Google Chrome actions. The converted actions are named using the following naming convention: [TaskName]_Chrome
If an Open Data action is inside of a Before Task, you can now choose to run all records or run the action once when it is executed.

Improvements

The Send Credential action is now supported for emulators.
Targeting Nintex Automation Cloud forms and executing actions against Nintex Automation Cloud form elements has been optimized. Be sure to upgrade to Nintex RPA Chrome Extension 1.6.0.0 to take advantage of this improvement.
You can execute Before/After Tasks in botflows without datasets that are run from Nintex RPA Central.
Nintex Bot includes upgraded email functionality with the latest MailKit libraries, so sending and receiving email, as well as parsing your inbox, should be more reliable now.
There is a new ParseJSON function in Nintex Bot, making it easier to work with objects returned from REST calls.

Resolved issues

The Save Button variable is now set in the Prompt action.
Email accounts now correctly include the display name.

Known issues

If you start two or more botflows from Nintex RPA Central or Nintex Automation Cloud on the same Nintex Bot and then you close the Nintex Bot after the first botflow has finished running, but before the second queued botflow has started, the second queued botflow will remain unresponsive in a queued state. Currently, to resolve this issue, you must terminate the botflow that remains in a queued state.
Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

For more information, review the system requirements in the Nintex RPA LE preinstallation checklist.

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
You must use a standard dedicated Windows session for each Nintex Bot user. Nintex RPA LE does not support shared/non-persistent user sessions in virtualization technologies.
If not installed already, Nintex RPA Central installs Microsoft .NET 6.0.2, Microsoft .NET Framework 4.7.2, Microsoft SQL Server 2017 Express, and Windows PowerShell 3.0. These prerequisites are required for Nintex RPA Central.

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex RPA Central 2.7.1 and Nintex Bot 17.7.1: March 17, 2022

Product release downloads on Nintex Customer Central

Note: Nintex RPA Central 2.7.1 was released with Nintex Bot 17.7.0 on February 23, 2022. This release combines the previously released Nintex RPA Central 2.7.1 version with the updated Nintex Bot 17.7.1 version, which includes many fixed issues.

Nintex RPA Central 2.7.1 new feature, enhancements, and resolved issues

New feature

You can now add users to Nintex RPA Central from properly-trusted domains on which Nintex RPA Central is not installed. This feature is particularly beneficial if you installed Nintex RPA LE on a parent domain and have users in child domains. This type of domain architecture is common at companies that have multiple locations or branches that manage users at the location or branch level. In Nintex RPA Central, administrators can add and validate unknown domains so that they are known and users from those domains can be added. For more information, review domain requirements and learn about adding users from properly-trusted domains.

Enhancements

You are now able to use more than one VPN IP address. To add additional VPN IP addresses to your configuration and ensure that the connection is successful, read about how to configure VPN settings.
You are now able to select the time zone where you want to run botflows. This enhancement ensures that your botflows always run on time, even when time zones observe Daylight Saving Time. Previously, your botflows could run an hour off schedule in time zones that were observing Daylight Saving Time. For more information, read about how to configure botflow start events.
Support for Microsoft Windows 11. If your botflows are unavailable after you upgrade to Windows 11, troubleshoot the issue with our help.
Support for Microsoft Windows Server 2022. Windows Server 2022 offers improved performance and speed.
A new Copy URL button is next to your Nintex RPA Central URL in the About section on the License and subscription page. You can click this button to quickly and easily copy your Nintex RPA Central URL and then paste it to request access to a Nintex Bot.

Resolved issues

You no longer receive an "Unable to set the URL" error message if your server takes 30-60 seconds to restart after setting the URL based on a certificate. Previously, even if your URL was correctly set, you would receive this error if your server took more than 30 seconds to restart. The expanded timeout now allows enough time for the certificate to be bound, config files updated, and the service to restart.
Botflows no longer get stuck in a queued state when run from Nintex RPA Central or from a schedule.
Domain user validation no longer fails if the First name and Last name fields are blank.

Nintex Bot 17.7.1 improvements, resolved issues, and known issues

Improvements

You can now scroll horizontally when building PowerShell actions. This improvement makes it easier to see the code that you are writing when it includes long commands that run past the fixed edge of the window.
You can now download email files attached to an email. Note that they download in the .eml format that can be opened in Microsoft Outlook and other email applications.

Resolved issues

Nintex Bot no longer erroneously exits tiny mode.
The Wait for Target action's timing setting is now set to Wait Forever. Previously, this setting was defaulted to only wait up to one second.
DateAdd formulas are now working correctly.
Standard Get Email action messages now work correctly. These actions also now support group addresses and mailbox addresses in the To field.
Loops no longer fail with a listname when using variables to define the name of a list to loop.
Culture is now handled correctly when using the Formula action.

Known issues

If you start two or more botflows from Nintex RPA Central or Nintex Automation Cloud on the same Nintex Bot and then you close the Nintex Bot after the first botflow has finished running, but before the second queued botflow has started, the second queued botflow will remain unresponsive in a queued state. Currently, to resolve this issue, you must terminate the botflow that remains in a queued state.
Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

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

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 and Nintex RPA Central only support 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
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 LE.

Nintex Bot 17.7.0: February 23, 2022

Product release downloads on Nintex Customer Central

Improvements

Boxing in Google Chrome and Microsoft Edge is improved while using the target selector or mouse recorder in new actions. Specifically, the boxing response is faster, the box always displays around the target, the targeting response between MouseUp and the Nintex Bot preview is faster, and hover menus with both the Target Selector and Mouse Recording work correctly. Be sure to install the updated Nintex RPA Chrome Extension to take advantage of this improvement in Google Chrome.
Improved and streamlined communications between Nintex RPA Central and Nintex Bot over SignalR.
Support for Microsoft Windows 11. If your botflows are unavailable after you upgrade to Windows 11, troubleshoot the issue with our help.
Support for Microsoft Windows Server 2022. Windows Server 2022 offers improved performance and speed.
Added a new CleanRegEx formula for improved performance.
Improved Google Chrome and Microsoft Edge performance and reliability.
Botflows are executed more quickly, which decreases the likelihood of Target Not Found errors.
Ability to set the Culture setting for actions from the Quick Edit menu. If an action has a Culture setting, you can now right-click on it and easily select the Culture in the Quick Edit menu that displays. If you have selected multiple actions and at least one of the actions has the Culture setting, the Quick Edit menu will display when you right-click on that group of actions and allow you to easily select the Culture for the group of actions with the setting.

Resolved issues

Bots no longer go offline after a botflow run or after closing Nintex Bot.
Nintex Automation Cloud variables no longer get lost if there are hundreds of them.
If you are importing or opening botflows that you created in Nintex Bot 17.2.0 or earlier, the Culture setting, by default, is System. If you are importing or opening botflows that you created in Nintex Bot 17.3.0 or later, the Culture setting will not be, by default, System. To make it easier to set the Culture setting in botflows that you created in Nintex Bot 17.3.0 or later, you can now right-click on one or multiple actions and set the Culture setting from the Quick Edit menu that displays.
You no longer receive an "out of memory" error when using the Nintex RPA Chrome Extension.
You no longer receive a corrupt file error when attempting to open and split a PDF file in a botflow.
.NET emails are now correctly displayed in a split view.
Nintex Automation Cloud workflows that send a collection to Nintex RPA Central as an input variable to a botflow now work correctly.
The Open Data action now parses correctly when the delimiter is None.

Known issues

If you start two or more botflows from Nintex RPA Central or Nintex Automation Cloud on the same Nintex Bot and then you close the Nintex Bot after the first botflow has finished running, but before the second queued botflow has started, the second queued botflow will remain unresponsive in a queued state. Currently, to resolve this issue, you must terminate the botflow that remains in a queued state.
Boxing may not work correctly in Google Chrome when targeting the Print dialog with UIA on Windows Server 2019. We recommend upgrading to Windows Server 2022, as it has performed very well in our internal tests and does not exhibit this issue. Windows Server 2022 also provides you with improved performance and speed.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

General

Nintex Bot must be installed on a computer that is part of a network domain.
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

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 only supports 64-bit operating systems.

Windows 11
Windows 10
Windows 8.1

Supported servers

Windows Server 2022
Windows Server 2019
Windows Server 2016

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

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

Nintex RPA Central 2.6.0 and Nintex Bot 17.6.0: November 18, 2021

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.6.0 new features and enhancements

New feature

Ability to set up or migrate your Nintex RPA Central Keys and Web databases to any edition of a licensed 2012 or above Microsoft SQL Server (Standard, Enterprise, Developer, or Web). Storing your Nintex RPA Central data on a licensed SQL Server allows you to control the connection strings and database locations and manage data in the same way that you manage other data in your line of business systems using standard SQL technology. It removes the 10 GB database Microsoft SQL Express size limit. It can also improve the performance of your Nintex RPA Central server. If you are a new user, go to Select your SQL database setup in the installation instructions to set up your Nintex RPA Central databases on Microsoft SQL Server. If you are an existing user, go to Migrate SQL Server database to migrate your Nintex RPA Central databases from Microsoft SQL Express to Microsoft SQL Server.

Enhancement

Logging is improved to now include the Nintex Bot name on SignalR connection entries. This additional logging information can help better troubleshoot Nintex Bot disconnection issues from Nintex RPA Central.

Nintex Bot 17.6.0 improvements, resolved issues, and known issues

Improvements

Improved targeting using Microsoft UI Automation (UIA) technology.
Improved targeting rule using Best Match instead of Left Match search for URLs in Google Chrome, Microsoft Edge, and Microsoft Internet Explorer.
Improved targeting for parent anchors in Google Chrome and Microsoft Edge.
Improved targeting using UIA with Tableau.
Improved targeting of highlighted table cells on web pages.
Other targeting improvements for Google Chrome and Microsoft Edge.
Improved start-up performance and speed.

Resolved issues

Date comparisons in IF actions now work correctly.
The Unlock action now works correctly on local virtual machines.
You can now successfully connect to newer (9.1 and above) versions of the Attachmate Extra! X-treme emulator.
You can now configure HTML-formatted emails with attachments.

Known issue

ShadowDOM is not working correctly; this issue will be resolved in an upcoming Nintex Bot version.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

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

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.6.0 and Nintex RPA Central 2.6.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 LE.

Nintex RPA Central 2.5.0 and Nintex Bot 17.5.0: September 29, 2021

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.5.0 resolved issues

The NetFrameworkVersionCheck custom action no longer fails during installation. This fix ensures that your Nintex RPA Central installation and upgrade is successful.
The list of security certificates displayed on the License and subscription page no longer appears in a constant loading state. This fix allows you to select a valid security certificate when you are setting up Nintex RPA Central.
You no longer receive an instance details error that states, "Dataset schema does not exist," when you create a botflow, attach a data set to it, publish and then unpublish it, clear the dataset schema to remove the dataset from it, and then republish and run it. If you continue to receive this error when running botflows from prior releases, resave your botflows to clear the datasets.
Additional logging no longer occurs. Note that the additional logging that was previously occurring contained only empty logs and no personal or sensitive data.
When editing users, the role picklist now correctly displays all three role options.

Nintex Bot 17.5.0 improvements, resolved issues, and known issues

Improvements

Nintex Automation Cloud and Universal form targeting is improved.
Targeting web pages with ads is improved. However, it is a good practice to install an ad blocker for your browser.

Resolved issues

You can now successfully bridge web table searches in Google Chrome. This fix allows you to search, move highlight, get list, and complete other actions across multiple tables on a web page that have the same number of columns. Bridging web table searches improves targeting on web pages and apps (for example, in Salesforce and Navigator). By default, this feature is turned off, but you can turn it on in the Rules window for a targeted application. For more information, go to Build Pane and Action Builder.
In Windows 10, when executing the Unlock action, if the machine is already unlocked, Nintex Bot will no longer attempt to unlock the machine anyway. For more information on using the Unlocker, go to Unlock.
You can now successfully import duplicate credentials from the same botflow.
You can now see all of the text in notifications and error messages with multiple lines. Previously, text in messages displayed above the Run Bar with multiple lines was truncated.
You are now able to send emails to multiple recipients in Send Email actions.
Trim (or LeftOf) formulas now work correctly.
Text Left Function formulas now work correctly.
The Length formula now works correctly and returns results with 0 instead of blank results.
The delimiter setting during data import is no longer ignored and defaulted to comma. This fix ensures that your imported data is formatted correctly.
The OK button in alert messages now works more reliably.
Actions no longer erroneously execute when the Run slider is turned off.
Mouse recordings now work more reliably.
You can now use tokens inside the headers of a REST or SOAP action.
You can now use variable tokens when setting the password field in the Set Credential action.
Retrieving Google Chrome targets is now more stable (Nintex RPA Chrome Extension 1.2.0.1 required).

Known issue

ShadowDOM is not working correctly; this issue will be resolved in an upcoming Nintex Bot version.

Download files

Nintex RPA Central 2.5.0
Nintex Bot 17.5.0
Nintex RPA LE Unlocker 16.5.1 EXE (64-bit)
Nintex RPA Chrome Extension 1.2.0.1 (Released October 7, 2021)

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute the Nintex Bot or Nintex RPA LE Unlocker installation to individual machines automatically across your organization.
Nintex Bot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

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

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.5.0 and Nintex RPA Central 2.5.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 LE.

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

Product release downloads on Nintex Customer Central

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 LE 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 Automation 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)

Improved performance and stability.
Additional support for SQL types. For more information, go to Data - SQL, Execute SQL, and Stored Procedure.

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

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

Nintex RPA Central 2.3.0 and Nintex Bot 17.3.0: July 7, 2021

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.3.0 improvement and resolved issues

Improvement

Improved performance stability and handling.

Resolved issues

You can now successfully delete users. Previously, when you attempted to delete a user while editing another user, the edit user fields appeared instead of the delete user fields.
Validation now properly occurs so that your new and edited botflow names are no longer truncated.
Botflow schedules are now correctly displayed with timestamps after upgrading.

Nintex Bot 17.3.0 enhancements and resolved issues

Enhancements

Increased speed and improved stability and reliability for Chrome targeting due to communication improvements between Nintex Bot and Nintex RPA Chrome Extension. This improvement prevents message loss. It requires Nintex RPA Chrome Extension 1.0.0.17.
The token and formula engine was refactored to support the native culture of the Nintex Bot machine. This improvement allows for expanded culture support, which is helpful if you're writing botflows in one system and deploying them in another culture and when you have incoming data from another culture. With this feature, you also no longer need to translate formulas manually. If you are writing botflows for use in multiple countries, the expanded culture support can save you time and effort. Changing the culture will cause the action to evaluate all tokens and formulas in a specific culture. For more information about changing the culture for a specific action, go to Formula, Create Variable, Calculate, and Set Field.

Note: All actions created in Nintex Bot 17.2.0 or below will be set to use US English so that their behavior does not change when you upgrade to Nintex Bot 17.3.0 or above.
Secure FTP (FTPS and SFTP) is now supported. For more information about creating secure FTP connections for FTP actions, go to FTP.

Resolved issues

Chrome Print Dialog targeting now works correctly.

The screen is no longer black when the Action builder is displayed and you are running in Bot mode.
The Clear Dataset Schema menu is no longer active when opening a new botflow.
The About screen has been updated with the latest support contact information.
The Get List action will now show the correct number of records in the information bar when targeting Excel.

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

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 v17.3.0 and Nintex RPA Central v2.3.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

Nintex RPA Central 2.2.0 and Nintex Bot 17.2.0: June 8, 2021

Product release downloads on Nintex Customer Central

Nintex RPA Central 2.2.0 improvement and resolved issues

Improved performance stability and handling.
Unauthorized users are no longer able to access Nintex RPA Central pages. If an unauthorized user attempts to access a Nintex RPA Central page, they will receive a message stating that their access is denied.
When editing users, the role picklist is no longer truncated.
You can now run a botflow immediately after publishing it.
The Output File button is now disabled if an instance is terminated and no records were ran.

Nintex Bot 17.2.0 enhancements and resolved issues

Note: Windows Server 2012 is no longer supported in Nintex Bot. We recommend that you only run Nintex Bot on a client machine in Windows 10 or Windows 8.1. For more information, see System requirements.

A new library, MailKit, has been implemented to allow for connections to email servers that require higher security protocols (TLS 1.2).
Dataset field names can now include commas. If you include a comma in a dataset field, ensure that the entire field is enclosed in double quotes (") so that Nintex Bot interprets the field as one field and not separate fields.
The Go To Website action now correctly chooses the current tab in the current window (requires Nintex RPA Chrome Extension 1.0.0.16 or above; for more information, see Download files).
The Execute SQL action no longer overwrites a data file when the “Overwrite” option is not selected.
Nintex Bot no longer fails to find the library used to connect to MySQL databases.
Files are now correctly deleted when you use the Delete File action with a wildcard in the filename and you also select to “Include Subfolders.”
You no longer receive an error stating that the Nintex RPA Chrome Extension is out of date when you target Microsoft Edge.
Nintex Bot no longer fails to target a newly opened Microsoft Excel workbook when using the Create Workbook action.
Setting data fields with values that contain apostrophes will no longer fail.

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

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 v17.2.0 and Nintex RPA Central v2.2.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

Nintex RPA Central 2.1.0 and Nintex Bot 17.1.0: May 5, 2021

Nintex product releases downloads

Nintex RPA Central improvement and resolved issues

• Improved orchestration of Botflows with large Datasets.

• Added a new Instances Details page.

• Fixed an issue where a user was unable to use a deleted botflow name as new botflow name.

Nintex Bot performance improvements and resolved issues

• Added support for orchestration of Botflows with large Datasets (requires RPA Central v2.1.0).

• Added support for Adobe Reader DC targeting.

• Fixed an issue where the target drop zone control would disappear unexpectedly.

• Fixed an issue where Nintex Bot was encountering connection errors to the Nintex RPA Chrome Extension.

• Improved stability of bot communication with RPA Central when running a botflow.

Download

• Nintex RPA Central v2.1.0

• Nintex Bot v17.1.0

• Nintex RPA LE Unlocker 16.5.1 (64-bit)

Repackaging

The following MSI packages are provided for your convenience:

Nintex Bot v17.1.0
- Prerequisites:
  - Microsoft OLE DB Driver for SQL Server version x64
  - Microsoft Access Database Engine 2016 Redistributable (x86)
Nintex RPA LE Unlocker 16.5.1 (64 bit)
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Visual C++ 2017 Redistributable Package (64-bit) - Get It Here
  - Expand 'Redistributables and Build Tools'
  - Download 'Microsoft Visual C++ Redistributable for Visual Studio 2017'
    - For 64 bit operating systems, select 'x64' and Download

System requirements

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

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 v17.0 and Nintex RPA Central v2.0.0 only support 64-bit operating systems.

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11 (Nintex Bot only)
Google Chrome
Microsoft Edge

Nintex RPA Central 2.0.5 and Nintex Bot 17.0.6: April 19, 2021

Nintex product releases downloads

Note:

This release requires Nintex RPA Central 2.0. If you have not upgraded to Nintex RPA Central 2.0, Nintex recommends planning a maintenance time window to:

Cancel all botflow instances.
Unpublish all botflows that are scheduled to run within your planned maintenance window. You can also back up or export key botflows.
Upgrade Nintex RPA Central and Nintex Bots.

This release also does not include support for processing Datasets in Nintex RPA Central. However, you can still process datasets with Nintex Bots. If you have a job with a dataset that was configured in Nintex RPA Central 1.X, and you are upgrading to Nintex RPA Central 2.0, the botflow will stop working. You can let Dataset jobs complete first before upgrading to Nintex RPA Central 2.0.

Nintex Bot: performance improvements and resolved issues

Fixed an issue where some previously created Click actions were converted to Screen Targeting actions in Nintex Bot v17.0.4 and 17.0.5. As a result, the actions did not behave as expected.
- Botflows that were not opened in Nintex Bot v17.0.4 or v17.0.5 will not be affected.
- Botflows that were opened and saved in Nintex Bot v17.0.4 or v17.0.5 will have the broken actions restored to their previous working state.
Fixed an issue where the Toggle Record action would not behave as expected.
Fixed an issue where a Move Highlight action could fail to move a highlight to the right (requires Nintex RPA Chrome Extension v1.0.0.15).
Made improvements to the mouse recorder for Chrome targets (requires Nintex RPA Chrome Extension v1.0.0.14).
Optimized target response times for MS UIA targets.
Fixed an issue where the Open App action was unable to open Google Chrome.
Enhanced Chrome/Edge targeting to support list box controls for the Select Item and Search actions.
Made improvements to the SQL Data Import to better handle SQL data types.
Made improvements to the SQL Connections for Azure SQL databases.
Fixed an issue where the recent botflow list on the home screen would not display properly.
Fixed an issue where customers with Enterprise licenses, randomly would be presented with a message that a feature was unavailable.
Fixed an issue where in some unique cases, a botflow would be started from RPA Central and then considered Complete, although the bot did not run the botflow.
Improved targeting for all technologies while using the selector tool.
Added a new Screen Target mode to target a specific point on the screen when using the seletor tool.
Added support for SQL Server 2019 and SQL servers using up to TLS 1.2.
Added support for Azure SQL databases.
Improved stability of communication between Nintex Bot and Edge.
Improved startup time of Nintex Bot.
Fixed an issue where the Go To Record action would not display the record in the data view.
Fixed an issue where in some cases, customers would see an inaccurate “Feature Unavailable” message.
Fixed an issue where the Move File action would fail to overwrite an existing file.
Improved messaging for Excel related errors.

Nintex RPA Central: resolved issues

Fixed the ability for Administrators to delete users.
Fixed an issue where duplicate users could be added.

Download

Nintex RPA Central v2.0.5
Nintex Bot v17.0.6 (requires Nintex RPA Central v2.0.0)
Nintex RPA LE Unlocker 16.5.1 (64-bit)

Repackaging

The following MSI packages are provided for your convenience:

Nintex Bot
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Access Database Engine 2016 Redistributable (32-bit regardless of operating system bitness) - Get It Here
Nintex RPA LE Unlocker 16.5.1 (64-bit)
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Visual C++ 2017 Redistributable Package (64-bit) - Get It Here
  - Expand 'Redistributables and Build Tools'
  - Download 'Microsoft Visual C++ Redistributable for Visual Studio 2017'
    - For 64 bit operating systems, select 'x64' and Download

System requirements

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

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 v17.0 and Nintex RPA Central v2.0.0 only support 64-bit operating systems.

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11 (Nintex Bot only)
Google Chrome
Microsoft Edge

Nintex RPA Central 2.0.2 and Nintex Bot 17.0.3: February 4, 2021

Nintex product releases downloads

Note:

This release requires Nintex RPA Central 2.0. If you have not upgraded to Nintex RPA Central 2.0, Nintex recommends planning a maintenance time window to:

Cancel all botflow instances.
Unpublish all botflows that are scheduled to run within your planned maintenance window. You can also back up or export key botflows.
Upgrade Nintex RPA Central and Nintex Bots.

This release also does not include support for processing Datasets in Nintex RPA Central. However, you can still process datasets with Nintex Bots. If you have a job with a dataset that was configured in Nintex RPA Central 1.X, and you are upgrading to Nintex RPA Central 2.0, the botflow will stop working. You can let Dataset jobs complete first before upgrading to Nintex RPA Central 2.0.

Nintex RPA Central: performance improvements and resolved issues

Enabled deleting botflows.
Fixed an intermittent bug in starting scheduled botflows.
Fixed a bug on visual display of scheduled start date/time on user interface.

Nintex Bot: performance improvements and resolved issues

Enhances the Get List action for tables based on Microsoft Dynamics (requires Nintex RPA Chrome Extensionv1.0.0.13).
Improved messaging when Nintex Bot is unable to save a botflow to the repository.
Improved Nintex Bot startup and botflow list rendering performance.

Download

Nintex RPA Central v2.0.2 (Released 14/12/2020)
Nintex Bot v17.0.3 (requires Nintex RPA Central v2.0.0)
Nintex RPA LE Unlocker 16.5.1 (64-bit)

Repackaging

The following MSI packages are provided for your convenience:

Nintex Bot
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Access Database Engine 2016 Redistributable (32-bit regardless of operating system bitness) - Get It Here
Nintex RPA LE Unlocker 16.5.1 (64-bit)
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Visual C++ 2017 Redistributable Package (64-bit) - Get It Here
  - Expand 'Redistributables and Build Tools'
  - Download 'Microsoft Visual C++ Redistributable for Visual Studio 2017'
    - For 64 bit operating systems, select 'x64' and Download

System requirements

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

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 v17.0 and Nintex RPA Central v2.0.0 only support 64-bit operating systems.

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11 (Nintex Bot only)
Google Chrome
Microsoft Edge

Nintex RPA Central 2.0.1 and Nintex Bot 17.0.1: January 17, 2021

Nintex product releases downloads

Note:

This release includes an upgrade to Nintex RPA Central v2.0, which requires all Nintex Bots to be on v17.0. Before you upgrade, Nintex recommends planning a maintenance time window to:

Cancel all botflow instances.
Unpublish all botflows that are scheduled to run within your planned maintenance window. You can also back up or export key botflows.
Upgrade Nintex RPA Central and Nintex Bots.

Nintex Bot: performance improvements and resolved issues

Enhances the Get List action for Chrome tables that require scrolling to get all the rows.
Fixes an issue where a Click action targeting the Desktop would result in a “Target not found”.
Fixes an issue where Chrome actions would not error correctly when Chrome is not running.
Other minor fixes and improvements.

Download

Nintex RPA Central v2.0.1 (Released 14/12/2020)
Nintex Bot v17.0.1 (requires Nintex RPA Central v2.0.0)
Nintex RPA LE Unlocker 16.5.1 (64-bit)

Repackaging

The following MSI packages are provided for your convenience:

Nintex Bot
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Access Database Engine 2016 Redistributable (32-bit regardless of operating system bitness) - Get It Here
Nintex RPA LE Unlocker 16.5.1 (64-bit)
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Visual C++ 2017 Redistributable Package (64-bit) - Get It Here
  - Expand 'Redistributables and Build Tools'
  - Download 'Microsoft Visual C++ Redistributable for Visual Studio 2017'
    - For 64 bit operating systems, select 'x64' and Download

System requirements

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

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 v17.0 and Nintex RPA Central v2.0.0 only support 64-bit operating systems.

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11 (Nintex Bot only)
Google Chrome
Microsoft Edge

Nintex RPA Central 2.0.0 and Nintex Bot 17.0.0: December 2020

Nintex product releases downloads

Important:

This release includes an upgrade to Nintex RPA Central 2.0, which requires all Nintex Bots be on version 17.0. Before you upgrade, Nintex recommends planning a maintenance time window to:

Terminate all botflow instances.
Unpublish all botflows that are scheduled to run within your planned maintenance time window. For more information, see Edit a botflow in Nintex RPA Central. You can also back up or export key botflows. For more information, see Backup and restore and Botflow Menu.
Upgrade Nintex RPA Central. For more information, see Install Nintex RPA Central.
Upgrade Nintex Bots. For more information, see Install and configure a Nintex Bot.

This release does not include support for processing datasets in Nintex RPA Central. However, you can still process datasets with Nintex Bots. If you have a job with a dataset that was configured in Nintex RPA Central, and you are upgrading to Nintex RPA Central 2.0, the botflow will stop working. You can let the dataset job complete first before upgrading to Nintex RPA Central 2.0 or you can upgrade to Nintex RPA Central 2.1 or above (recommended).

Nintex RPA Central: new features

Faster and easier Nintex RPA Central and Nintex Bot installation.
Improved and enhanced feature functionality; botflow scheduling, Instances, and more.
Improved Nintex RPA Central navigation.
Intuitive user experience.
Unified experience within the Nintex process platform portfolio.

Nintex Bot: performance improvements and resolved issues

Improved targeting and action execution for applications with Microsoft UIA framework, such as WPF and XAML apps.
Chrome and Edge browser modals such as sign in popups and print dialog screens can now be targeted.
Fixes an issue where a botflow running from Nintex RPA Central could not be paused more than once.
Fixes an issue where an unreadable .rpa file is created when importing legacy .fox or .fsp files.
Improves the speed at which a bot runs a botflow from Nintex RPA Central.
New color theme has been added to align with new Nintex process platform (Raspberry and Orange themes have been deprecated)
Other minor fixes and improvements.

Download

Nintex RPA Central v2.0.0 (Released 14/12/2020)
Nintex Bot v17.0.0 (requires Nintex RPA Central v2.0.0)
Nintex RPA LE Unlocker 16.5.1 (64-bit)

Repackaging

The following MSI packages are provided for your convenience:

Nintex Bot
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Access Database Engine 2016 Redistributable (32-bit regardless of operating system bitness) - Get It Here
Nintex RPA Unlocker 16.5.1 (64-bit)
- Prerequisites
  - Microsoft .NET Framework 4.7.2
  - Microsoft Visual C++ 2017 Redistributable Package (64-bit) - Get It Here
  - Expand 'Redistributables and Build Tools'
  - Download 'Microsoft Visual C++ Redistributable for Visual Studio 2017'
    - For 64 bit operating systems, select 'x64' and Download

System requirements

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

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 v17.0 and Nintex RPA Central v2.0.0 only support 64-bit operating systems.

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11 (Nintex Bot only)
Google Chrome
Microsoft Edge

Nintex RPA Central 1.4.7 and Nintex Bot 16.6.11: November 2020

Nintex RPA LE: performance improvements and resolved issues

Improvements made to the Get List action to better handle Chrome tables that require scrolling to get all rows.
Minor improvements to the way bots connect to Nintex RPA Central. Fixes an issue where the list of drop-down options was not populated in a Select Item action when targeting a drop-down within a highlighted cell.
Improvements made to the Wait for Target action in Chrome.
Fixes an issue where the Close Database action would fail to delete the database when that option was selected.
Fixes an issue where the “Marked” and “Unmarked” record tokens would show incorrect numbers when an MDB or DBF is loaded.
Fixes an issue where the “Remove Spaces” option in the Get Value action would not behave as expected.
Fixes issues related to importing an Excel or CSV file with date and/or number fields

Nintex RPA Central: performance improvements and resolved issues

Fixes an issue where if connection between Nintex RPA Central and Nintex Bot would be lost right before a schedule, the same job instance would get re-created multiple times until Nintex RPA Central can communicate with Nintex Bot.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.4.6 and Nintex Bot 16.6.7: November 03, 2020

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue that prevented Nintex RPA LE from creating a Click action when targeting a Windows target.

Nintex RPA Central: performance improvements and resolved issues

Fixes an issue where if connection between Nintex RPA Central and Nintex Bot would be lost right before a schedule, the same job instance would get re-created multiple times until Nintex RPA Central can communicate with Nintex Bot.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.4.5 and Nintex RPA 16.6.5: October 21, 2020

Nintex RPA LE: new features

Enhanced Chrome/Edge targeting experience

Targeting errors now provides more informative messaging when Nintex RPA LE cannot communicate with the Nintex RPA Chrome Extension.
Nintex RPA LE will now add any missing registry keys.

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue where an Open Data action would error on a bot when importing from a CSV or Excel file.
Fixes an issue where using a data field token in an action would error on a bot.
Fixes an issue where Excel actions would error on a bot.
Enhances handling of 64-bit versions of Office 2019 and Office 365.
Enhances the Get List action for Chrome targets to handle tables which require scrolling to get all available rows (requires Nintex RPA Chrome Extension v1.0.0.11).
Fixes an issue where unpublished botflows with schedules were running.
Enhances the data engine to allow for Zero Length fields.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.4.4 and Nintex Bot 16.6.3: September 30, 2020

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue found in Nintex Bot v16.6.1 where Microsoft Excel actions fail when running in a Nintex Bot (triggered by a Nintex RPA Central job).
Execution speed enhancement for the Get List action when targeting Google Chrome (requires Nintex RPA Chrome Extension v1.0.0.10).
Fixes an issue in the Wait for Target action where choosing Wait to disappear fails for Google Chrome targets.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.4.4 and Nintex Bot 16.6.1: September 17, 2020

Nintex RPA LE: new features

Added support for UIA Table Highlighting.
Added Tree support for the Search action using UIA targeting.
Click action now supports custom X/Y screen coordinates. To do so, target the desktop when creating the Click action.
Added RPAEngine.GetVar support for the C# action, VB.Net action, and Python action.
Added a new “Date Numeric” special token for variables.

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue for targeting speed when using the Nintex Bot Selector tool.
Fixes an issue with Microsoft Access 2016 Redistributable when opening Access (.accdb or .mdb) files using the Data -> Open Data menu item or an Open Data action.
Fixes an issue with Microsoft Access 2016 Redistributable when importing a Microsoft Excel (.xlsx or .xls) or CSV files using the Data -> Open Data menu item or an Open Data action.
Fixes the Open Workbook action failing with the error 'Element not found' or 'Cannot load library.'
Fixes an issue with the Open data action on an Excel file (.xlsx or .xls) to import any record.
Improved performance when importing records from a Microsoft Excel file.
Fixes an issue with Google Chrome targeting within Citrix environments.
Fixes an issue where Google Chrome targeting would be turned on for apps other than Google Chrome or Microsoft Edge.
Fixes an issue with targeting nested tables in Google Chrome and Microsoft Edge. This is fixed with Nintex RPA Chrome Extension 1.0.0.9.
Fixes an issue where the pause button was not stopping Google Chrome or Microsoft Edge actions.
Fixes an issue when using the Exact option for the Google Chrome Close action and Switch Tab action. This is fixed with Nintex RPA Chrome Extension 1.0.0.9.
Fixes an issue where Copy File action and Move File action were not behaving as expected.
Fixes an issue with Nintex RPA Central URL validation.
Fixes an issue where the Start preference for Open Last Botflow was not working.
Fixes an issue where an innocuous message box is displayed when importing a botflow.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.4.0 and Nintex Bot 16.5.5: June 29, 2020

Nintex RPA LE: new features

Microsoft Edge Support

Supports targeting the new Chromium-based Edge browser.
Targeting Edge will work the same way as targeting Chrome and has all the same features.
Added a new Zoom Edge action.
Note: The Zoom Edge action requires Microsoft Edge browser v83 or higher, and the Nintex RPA Chrome Extension v1.0.0.8. See Nintex RPA Chrome Extension for Microsoft Edge.

Nintex Bot Preferences settings

For customers upgrading from Nintex Bot version 15 or earlier, this is a welcome addition to Nintex Foxtrot version 16 or later.
Open Preferences from the Account menu to set Nintex Bot preferences as default behaviors.
Import preferences from older versions of Nintex Bot by selecting Import from the Preferences menu.

New Browser Tab Actions

Note: You must have Nintex RPA Chrome Extension v1.0.0.8 installed to use these features.

Close Tab – Closes the specified tab in a Google Chrome or Microsoft Edge browser window.
New Tab – Creates a new tab in a Google Chrome or Microsoft Edge browser window with the ability to specify a website to load into the new tab.
Switch Tab – Makes the specified tab the active tab in a Google Chrome or Microsoft Edge browser window.

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue where the Get List Info action was not saving to the specified variable.
NLTM authentication has been added in the REST action and SOAP action.
Fixes an issue where logging into Nintex RPA LE with an authenticated user while in the Microsoft Windows session of an unauthorized user would cause Nintex Bot to become unauthenticated with Nintex RPA Central.
Fixes an issue where a user could not resume a Bot if it was in an error state.
Fixes stability issues with PDF connections.
Asia Pacific region is now available for Workflow connections.
Fixes an issue where the Get Info action performed on a browser window would cause the window to go into a restored state.
Fixes an issue where the Prompt action would not save to a data field.
Fixes an issue where the Get Info action was missing entries when choosing a highlighted target in Google Chrome.
Better error handling when saving a botflow.
Improved targeting for Xperience.

Download

If you require the download links for this version, contact Support.

Nintex RPA Chrome Extension for Microsoft Edge

After installing Nintex Bot, in order to support Microsoft Edge automation:

Start Microsoft Edge.
Click the meatball icon on the top-right corner of the Microsoft Edge browser, and click Extensions.
Click Chrome Web Store. You are redirected to the Chrome Web Store.
Click Allow extensions from other stores, and click Allow when prompted.
Using Microsoft Edge, go to https://www.nintex.com/chrome.
Click Add to Chrome to install the Nintex RPA Chrome Extension.
When the Add "Nintex RPA Chrome Extensionn" to Microsoft Edge message appears, click Add extension. The Nintex RPA Chrome Extension icon displays in the Microsoft Edge toolbar.
Close Microsoft Edge and Nintex Bot.
Restart Microsoft Edge and Nintex Bot. Nintex Bot can now target and automate elements within Microsoft Edge webpages.

The requirements for targeting with Google Chrome and Microsoft Edge are:

Nintex Bot version 16.5.5 or higher.
Nintex RPA Chrome Extension version 1.0.0.7 or higher.
Google Chrome Version 83 or higher.
Google Chrome Zoom set to 100%.
Windows Display Scale and layout set to 100% (Settings->System->Display).
Windows Display Make text bigger set to 100% (Settings->Ease of Access->Display).

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.3.4 and Nintex Bot 16.5.3: May 28, 2020

Nintex RPA LE: performance improvements and resolved issues

Speed improvements to the Open App action.

Fixes speed and reliability issues related to the following actions:
- Copy File
- Move File
- Delete File
- Rename File
- Copy Folder
- Move Folder
- Delete Folder
- Rename Folder
Fixes an issue where the Recent list of botflows on the Home screen was not updating properly.
Fixes an issue where the Wait for Target action would fail for Google Chrome targets.
Fixes an issue where setting a Nintex Bot variable in a Python script would fail when using the Variables view.
Fixes an issue where the “Save to” name in the Duplicate List action was not evaluating correctly.
Fixes an issue where a copied Else If action would never execute.
Fixes an issue where incorrect error line numbers were being reported to Nintex RPA Central.
Fixes an issue where the Query List action could not save the output list if the overwrite checkbox was not checked.
Fixes an issue where Nintex Bot would fail to connect to certain emulators.
Added enhanced support for Send Value, Send Credential, and Click actions for BlueStacks Android Emulator.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.3.3 and Nintex Bot 16.5.1: May 11, 2020

Nintex RPA Central: new feature

Added support for Bot Edition license.

Nintex Bot: new features

Improved REST and SOAP actions

Support for adding custom headers.
“Content Type” and “Accept” options in the UI have been replaced with header configurations.
UI has improved visual flow.

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue when saving a botflow with an invalid botflow name.
Fixes an issue when opening Microsoft Access data files.
Various improvements for Nintex RPA LE running on 64-bit machines.
Improved responsiveness while using the target selector tool.
Improved responsiveness while targeting Google Chrome.
Nintex RPA LE Unlocker has been improved to work better on Windows 10 machines.
Nintex Bots will now show action error messages in the Info Bar.
Fixes an issue where using the RPAENGINE.SETVAR() function in a C#, VB.NET, or JScript.NET action would not set the variables consistently.
Fixes an issue where targeting Google Chrome would cause Google Chrome to close.
Fixes an issue where using a Send Value action would send the value to the address bar in Google Chrome (using Nintex RPA Chrome Extension v1.0.0.6).
Enhances the Workflow Connection to specify the region hosting the Nintex Automation Cloud tenancy. The specified region can be North America or Europe.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

Nintex RPA Chrome Extension for Google Chrome

After installing Nintex Bot, in order to support Google Chrome automation:

Start Google Chrome.
Using Google Chrome, go to https://www.nintex.com/chrome.
Click Add to Chrome to install the Nintex RPA Chrome Extension for Google Chrome.
Close Google Chrome and Nintex Bot.
Restart Google Chrome and Nintex Bot. Nintex Bot can now target and automate elements within Google Chrome webpages.

The requirements for targeting with Google Chrome are:

Nintex Bot version 16.5.0 or higher.
Nintex RPA Chrome Extension version 1.0.0.5 or higher.
Google Chrome Version 75 or higher.
Google Chrome Zoom set to 100%.
Windows Display Scale and layout set to 100% (Settings->System->Display).
Windows Display Make text bigger set to 100% (Settings->Ease of Access->Display).

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.3.2 and Nintex Bot 16.5.0: April 13, 2020

Nintex RPA LE: performance improvements and resolved issues

Fixes an issue where Botflow Reports would show as a blank page.
Fixes an issue where importing an exported botflow would fail.
Fixes an issue where an error would not show in RPA Central when a data set used in a job had an incorrect data type.
Fixes an issue where a breakpoint in a botflow would cause the script to shutdown.
Fixes an issue where a stop task action would stop the bot from running any additional records.
Fixes an issue where List row values with a comma would not show correctly in Excel when exported as a CSV file.
Fixes an issue where attachments in the “Reply” Action would not work if there was a comma in the attachment’s name.
Added Google Chrome extension.
Adds double byte character support for REST action responses.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

Nintex RPA Chrome Extension for Google Chrome

After installing Nintex Bot, in order to support Google Chrome automation:

Start Google Chrome.
Using Google Chrome, go to https://www.nintex.com/chrome.
Click Add to Chrome to install the Nintex RPA Chrome Extension.
Close Google Chrome and Nintex Bot.
Restart Google Chrome and Nintex Bot. Nintex Bot can now target and automate elements within Google Chrome webpages.

The requirements for targeting with Google Chrome are:

Nintex Bot version 16.5.0 or higher.
Nintex RPA Chrome Extension version 1.0.0.5 or higher.
Google Chrome Version 75 or higher.
Google Chrome Zoom set to 100%.
Windows Display Scale and layout set to 100% (Settings->System->Display).
Windows Display Make text bigger set to 100% (Settings->Ease of Access->Display).

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.3.0 and Nintex Bot 16.0.11: March 18, 2020

Nintex RPA LE: new features

Compatible with Nintex Gateway
You can now export the currently open botflow to a .rpa file

Nintex RPA LE: performance improvements and resolved issues

Nintex RPA LE informs the user if Nintex RPA Central cannot be reached.
Fixes an issue where botflows would not open correctly.
Fixes an issue where executing a Close Me action on a bot would cause the job in Nintex RPA Central to stay in a running state.
Fixes an issue when opening a botflow with an Unlock action, a popup message would display stating that the Unlock action was blocked.
Fixes an issue where trying to run a job from Nintex RPA Central on a machine set to a language other than English would fail.
Fixes an issue where the “Other” delimiter option in the Open Data action was not working.
Fixes an issue where Rows couldn’t be edited in Lists when more than seven columns are used.
Fixes an issue where importing data from a .txt file would fail when using a Data Template.
Fixes an issue where emails would be deleted when moving them to a folder with a non-English character.
Fixes an issue where the “Keep Open” option was missing when adding a row to a list.

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Central 1.1.4 and Nintex Bot 16.0.4: January 14, 2020

Nintex RPA Central: new features

First release of Nintex RPA Central

Download

If you require the download links for this version, contact Support.

Repackaging

If you require the MSI package links for this version, contact Support.

MySQL

When using MySQL with Data - SQL or SQL you will be prompted to install the connector.

Navigate to the connector download.
Select Product Version 8.0.17 and select the 393.4M download.
When running the installation, select Custom.
Select Connector/NET 8.0.17 - x86 from the Available Products list and move it to the Products/Features To Be Installed list.
Click Next and Execute to complete the installation.
Navigate to C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2 and copy Renci.SshNet.dll to C:\Program Files (x86)\Nintex\RPA.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Foxtrot 15.1.13: June 15, 2022

Note: The Unlocker was updated on June 28, 2022, to include the SoftwareSASGeneration registry key component. Download the latest version of the Unlocker, version 15.1.14, to get this Unlocker component.

Resolved issues

The Unlock action no longer fails after completing a Microsoft Windows update. Previously, the Unlocker could not find a file after a Microsoft Windows update and users received a warning message.
Support for Attachmate EXTRA! X-treme version 9.6 was added.

Download files

Repackaging

The following MSI packages are provided for your convenience.

Note:

You may want to use MSI packages if:

You need to distribute Nintex RPA Foxtrot or the Nintex RPA Foxtrot Unlocker installation to individual machines automatically across your organization.
Nintex RPA Foxtrot users do not have local full administrator rights for security reasons.
You want to use a program like AdminStudio or a mobile distribution manager (MDM) to distribute product installations.

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA Foxtrot 15.1.12

Nintex RPA Foxtrot 15.1.12 resolved issues

You can now successfully add custom fields when importing data.
The "Go to..." record functionality now works correctly.

Download Files

Repackaging

The following MSI packages are provided for your convenience:

System requirements

Nintex Bot and Nintex RPA Central 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

Minimum

1.8 gHz processor
2 CPU cores
3 GB RAM
300 MB hard drive space
1024x768 display resolution
Internet Explorer 11
Local read, write, execute, delete rights

Supported operating systems

Windows 10
Windows 8.1

Supported servers

Windows Server 2019
Windows Server 2016
Windows Server 2012

Supported browsers

Internet Explorer 11
Google Chrome
Microsoft Edge

Nintex RPA LE release notes

Nintex RPA Central 2.15.0 and Nintex Bot 17.16.0: August 21, 2024

Nintex RPA Central 2.15.0 resolved issues

Nintex Bot 17.16.0 enhancements, resolved issues, and known issue

Enhancements

Resolved issues

Known issue

Download files

Repackaging

System requirements

General

Recommended

Minimum

Supported operating systems

Supported servers

Supported browsers

Previous releases

Nintex RPA LE releases

Nintex RPA Foxtrot releases