Nintex Automation K2 Updates & Fix Packs

Important Security Update:An important security hardening update was addressed in Fix Pack 01. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement.Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 02 contains the XSLT support for Nintex Automation K2 (5.9.1). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailableInstaller Nintex Automation K2 (5.9.1) (5.0010.2000.1) is now available here (LINK) and includes support for .NET 10.Please ensure that Fix Pack 03 is also installed, as it includes additional .NET 10 support. IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be ab

Issue DescriptionWhen you upgrade the User Acceptance Testing (UAT) environment, conditional formatting in a List View may not display the expected colouurs. For example, the first row and rows on subsequent pages may display incorrect colours or no colour at all. The “In Progress” status may appear in yellow or remain uncoloured, while the “Pending” status may not display any colour.ResolutionThe fix is available in:Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Important Security Update:An important security hardening update was addressed in Fix Pack 13. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement. Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 14 contains the XSLT support for Nintex Automation K2 (5.9). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailableInstaller Nintex Automation K2 (5.9) (5.0010.1000.1) is now available here (LINK) and includes support for .NET 10.Please ensure that Fix Pack 15 is also installed, as it includes additional .NET 10 support. IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be able

Issue DescriptionWhen you convert a workflow containing a condition with multiple clauses joined by And or Or, the condition may be converted to an empty rule, causing the workflow to follow the same branch regardless of the data, without displaying an error. This can also affect comparisons such as is not equal to and contains, workflow starters, and person columns such as Modified By.When a comparison has no equivalent in K2, the comparison is left blank for manual completion instead of defaulting to equals. The workflow cannot be deployed until the missing comparison is configured.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you convert a workflow with a task assigned to a person column on a list item, the assignee may be converted as plain text instead of resolving to the intended person. As a result, the task may not be assigned to the correct user.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you convert a Nintex workflow containing an empty branch, such as an unused condition branch, a task outcome, or a Run If step without an otherwise branch, the workflow may stop on that path instead of continuing to the next action. As a result, subsequent actions may not execute.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you convert a workflow containing a Pause for or Pause until step, the step may complete immediately instead of waiting for the specified duration. No error is displayed, and the configured duration remains visible on the step, even though the expected delay is not applied.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you convert a Nintex workflow containing references such as {ItemProperty:Title}, references with different casing may not be converted correctly and may appear as plain text in K2. This can affect notification bodies, task messages, and column values.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you convert a workflow with step names containing accented Latin characters, those characters may be lost during conversion. This can affect workflow step names in languages such as Danish, German, French, and Afrikaans.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you convert a customized task notification in Nintex, the notification may remain disabled, causing the standard template to be sent instead of the customized message. References in the subject and body may also appear as plain text, such as {ItemProperty:Title}, instead of resolving to their corresponding values.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 18.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Important Security Update:An important security hardening update was introduced in Fix Pack 29. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement.Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 30 contains the XSLT support for Nintex Automation K2 (5.7). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailablePlease ensure that Fix Pack 30 is installed if you are using .NET10, as it includes all necessary support.IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be able to log into Nintex Automation Designer/Manager/Workspace/Runtime after the reconfigure completes and t

Issue DescriptionImplemented dependency updates to address potential security vulnerabilities associated with Telerik UI and maintain alignment with security requirements.ResolutionThe fix is available in:Nintex Automation (5.7) Fix Pack 31. Nintex Automation K2 (5.9) Fix Pack 18. Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Important Security Update:An important security hardening update was addressed in Fix Pack 33. We strongly recommend that all customers upgrade to this version or a later version to ensure you benefit from this security enhancement.Deprecated functionality and componentsGoogle Chrome intends to deprecate and remove XSLT support from the browser for security reasons. As a result, you may need to migrate your code before support is removed in November 2026.Fix Pack 35 contains the XSLT support for Nintex Automation K2 (5.8). If you cannot install the fix pack on time, you can use a workaround described in XSLT Deprecation in Google Chrome Browser | Community..NET 10 Support Now AvailableInstaller Nintex Automation K2 (5.8) (5.0009.1000.1) is now available here (LINK) and includes support for .NET 10.Please ensure that Fix Pack 35 is also installed, as it includes additional .NET 10 support. IMPORTANT:If you perform a reconfigure without reinstalling the fix pack, users will not be able t

Issue DescriptionWe have recently observed XSLT related warning messages appearing in some Edge & Google Chrome browsers. These warnings are caused by the Chromium XSLT field trial.  We have included a fix that will remove the Chromium warning message from our transformed dataResolutionThe fix is available in:Nintex Automation K2 (5.9.1) Fix Pack 05. Nintex Automation K2 (5.9) Fix Pack 18. Nintex Automation K2 (5.8) Fix Pack 38. Nintex Automation (5.7) Fix Pack 31.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.Considerations:For more information please navigate to XSLT Deprecation in Google Chrome Browser | Community

Issue DescriptionWhen you refresh a custom service broker from K2 Management, the [AssemblyLocation] value in [SmartBroker].[ServiceType] is cleared.ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 38.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you create a REST Service Instance using a Swagger/OpenAPI specification, a required string parameter such as issueKeyOrId in the /api/jira-api/v1/issue/{issueKeyOrId} endpoint is generated as an Object in the SmartObject instead of Text/String. When you enter a string value, the SmartObject returns an error because an Object value is expected.Error Message:The following error occurs:“SourceCode.SmartObjects.Services.Endpoints.Rest.Exceptions.RestDeserializationException: Unable to deserialize value.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17. Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.ConsiderationsAfter installin

Issue DescriptionWhen you use a workflow variable of type Date and Time, the converted workflow cannot be deployed. Saving fails with a Bad Request, without indicating the cause in the designer. This occurs whether or not a default value is set for the variable.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSwitchAdapter Switch action and leave a branch empty, the branch converts without an outgoing line. At runtime, the workflow follows that branch and stops, preventing subsequent actions on that path from running.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWBuildStringAdapter Build String action, the composed text is converted as literal text. References such as {ItemProperty:Title} and {Common:CurrentDate} are not resolved, so the variable contains the reference text instead of the actual values.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the SPSetFieldWithKeyAdapter Set Field Value or SPUpdateItemWithKeyAdapter Update List Item action, the step converts without the list, method, or column bindings. The step completes successfully at runtime but writes nothing to the list, and references in the value are treated as literal text.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSendMessageAdapter Send Notification action with a hyperlink in the message body, the link is carried across as raw markup and cannot be displayed by the designer's body editor, causing the message body to appear empty.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSendMessageAdapter Send Notification action with the {Common:AllApproverComments} reference, it converts to an unmapped placeholder. K2 has no equivalent comments field, so the placeholder cannot be mapped or used.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSendMessageAdapter Send Notification action with a person selected directly in the recipient field, the recipient is exported as a SharePoint claims login and passed as plain text. K2 cannot resolve the recipient, so the notification is not sent.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the WFIfElseAdapter Condition action to compare a SharePoint list column, the column reference is treated as literal text instead of the column value. The condition therefore does not match and always follows the negative branch.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the WFIfElseAdapter Condition action and leave one branch empty, the branch is converted without an outgoing line. At runtime, the workflow follows the empty branch and stops, preventing any subsequent actions on that path from running.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.