Product Forums

Hi everyone,I'm currently building a workflow in Nintex K2 and would like to generate a PDF document from a Word template, similar to the Generate Document feature in Nintex Workflow Cloud (NWC).For example:K2 SmartForm → Workflow → Populate Word template → Generate PDF → SendIs this feature available in Nintex K2?If not, what is the recommended way to achieve this in K2? If there is a guide or example that I can follow, I would really appreciate it.Thanks!

Hi all,I want to ask regarding the generate document feature that exists on NWC. Does it work on Nintex K2? Because I need to generate document from template. I know this feature works on Nintex Cloud because I’ve used it before, how about K2?

On-Prem K2 5.9, using on-prem AD as user manager.Currently K2 API website is load balanced via AWS ALB (which has problem with Kerberos), would need to switch to NLB, but K2 documentation doesn’t mention supporting Windows Auth for the REST API calls.Is there a plan to support OKTA for Oauth?This is specially for the Tasks API.Alternative is to build a separate API using the .NET 4.8 SDK...

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 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.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 installing the Fix Pack, selecting Edit before refr

when I press enter, although my textbox has value but it cant pass to value to my Smartobject but same input when i click to other place or press tab it will show the correct stepwhat i do for this is when user key in the asset disposal number, it will pass the number to the smart object and return true or false value. once the data label change, it shows true value, the system will block. the correct example shows at 2nd picture.however, if the user press enter, this validation will not work

I just wanted to gauge people’s opinions and experiences with the newer K2 Workflow Designer.We’ve had so many problems with K2 Studio workflows over the summer, including issues with what should be very basic functionality. For example, hyperlinks in an email body are no longer being accepted in some of our workflows, resulting in failed workflows with errors stating that there is no connection string for the destination user. Remove the hyperlinks from the email and the exact same steps work perfectly. The errors don’t even match the issue...When we raise tickets with K2, we’re told that development of K2 Studio workflows is no longer supported because it is considered legacy, and the recommendation is to move to the newer Workflow Designer.Fair enough — so I’ve been trying to migrate some of our existing workflows to the new designer.Unfortunately, the experience so far has been extremely poor.Window panes regularly freeze or become unresponsive. When editing an email body, if you e

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.

Issue DescriptionWhen you run a workflow that sends emails, the workflow fails and an error occurs.Error Message:The following errors occurs:“Send email failed due to: Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.”Thereafter,“"no connection string”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.

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 DescriptionWhen you change the font family of a dropdown, the watermark font updates correctly, but its color changes to match the control instead of remaining grey.When you change the font family of a text box or other control, the watermark remains grey, but its font remains Open Sans instead of matching the selected font.When Use Legacy Theme is unchecked, the control and watermark fonts update correctly, but the watermark color changes instead of remaining grey.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 migrate to SPFx, a workflow configured to start when a document is uploaded may start multiple instances for documents that were uploaded previously and already have a K2 workflow instance running. The workflow then stops starting new instances for newly uploaded documents.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 host your K2 database on Azure SQL, you may experience high CPU usage on a SQL instance.ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 37.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.

Hi everyone,I’m currently developing a workflow in Nintex K2 and I need the workflow to retrieve data from a SharePoint Online list.I’m quite new to K2 and I’m not sure what the correct integration/setup process is between K2 and SharePoint.My requirement is basically:SharePoint Online List → K2 → SmartObject → K2 WorkflowI would like to use the SharePoint list data inside the workflow, for example to retrieve/list items and use the column values in the workflow.I have access to K2 Management, and I can see SharePoint-related Service Types such as SharePoint Site Collection and K2 for SharePoint, but I’m unsure which one should be used and how it should be configured.My main questions are:What is the recommended way to connect K2 to an existing SharePoint Online site/list? Do I need to create a Service Instance in K2 Management using the SharePoint site URL? Which SharePoint Service Type should be used? What authentication method should be configured for SharePoint Online? Does K2 for

In my Nintex RPA embedded wizards, I’m programmatically opening and closing a couple of apps (MS Edge, and Outlook).I want to use an Advanced Command to open the URL (Edge) or run the app (Outlook).I also want to be able to add a keyboard shortcut to maximize the window (Alt-Shift, x)For example: PROBLEM: I can’t figure out how to do the “open” (Advanced Command) in the same step as the “Alt-Spacebar, x” (a core action).My workaround is to:  1) run the advanced command, then  2) record the new window, and finally  3) add my keyboard shortcut to the newly recorded Step 2.Q: Is there any “better” way to accomplish this?