Recently active topics

We are currently using Nintex for Sharepoint 2016 on premise and seeking to migrate our workflows to Nintex Workflow asap with Sharepoint 2016 out of support 3 months ago.We have a total of 133 active workflows to be migrated, of which 34 are simple workflows with one action.The approach we plan to use is as per the Nintex CE platform help.1.Run the workflow extraction script2. ​​​​​​​Import package file3. Upgrade the workflows4. Review and update workflows in Nintex Workflow5. Review task forms6. Publish workflows We are planning to migrate our Nintex for Sharepoint 2016 forms to Sharepoint SE, but migrate the workflows only to Nintex Workflow.My understand from watching Migrating to Nintex Workflow: Webinar Series and other community articles is that step 4 and step 5 could take some time to reconfigure workflow actions that are not compatible with Nintex Workflow. We will also need to open all task forms and review the form controls and configure any controls that require configurat

We switched over early to the new CE platform.  While pulling up instances in workflow tracking using custom dates, I noted that it would only display ~30 days-worth, even when I chose a range of 90 days. There was no ability to move to additional “pages”.  This is a bug in my opinion.  Either the range needs to be limited to 30 days (definitely not preferred), or a full range of instances for 90 days needs to be displayed -- whether on one page or multiple pages.

Agents are one of the core concepts behind agent-powered solutions, but what exactly is an agent, and when should you use one? In our latest Agent Designer learning video, we cover:  What an agent is  How agents differ from traditional AI capabilities  When to use an agent versus a single AI task  The types of business problems agents are designed to solve  The difference between an Agent and an Agentflow  Where Agent Designer fits into the overall experience  Whether you're just getting started with Agent Designer or looking to better understand agents, this video provides a practical introduction to the fundamentals. Watch the video here: We'd love to hear about the use cases you're exploring with Agent Designer in the comments. 

I have upgraded Nintex Automation K2 from version 5.6 → 5.8 → 5.9.The upgrade completed successfully without any errors.The web site is running normally, and users can: Create SmartForms Run workflows successfully However, I found an issue after the upgrade:When I try to log in with some test users (for example: k2test1), they cannot access the Workspace page(e.g. https://k2test.xxxxx.com/workspace).The following error message is displayed: Not authorizedYou do not have permission to view the page that you have requested.The administrator of this SmartForms environment has restricted access to this page.If you believe that you should have access to this page, please contact your SmartForms administrator. Important details: k2test1 is a normal user (no special permissions) Before upgrading to K2 5.9, this user could access Workspace normally After testing multiple users, I found that: Some users get "Not authorized" Some users can access Workspace without any issue No c

I’ve noticed this a lot across all of our servers lately.  K2 5.9 FP13 and later. It happens after a server restart or an IIS Restart.  Antimalware Service Executable often causes CPU to go to 100% for about 5-10 minutes and K2 Management says Smartform warming up and the timer keeps resetting.  About 50% of the time after that K2 Management will not work after the restart with an error similar to the one below. Server ErrorCould not load file or assembly 'SourceCode.Forms.Controls.Web.ControlPack.Choice' or one of its dependencies. The system cannot find the file specified.(http 500 error)Refresh Page? Redoing an IIS Restart will eventually work but in the meantime its another 10 minutes of downtime. I’ve been querying possible solutions like excluding temp directories and such but the only thing that seems to work in testing is excluding w3wp.exe.  However that doesn’t appear to be a secure solution.  Any recommendations?

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.

Is there a workaround (rules or something) to disable ability to add/remove rows in a repeating section after default has been set? We just need people to add additional information to existing rows, not add/remove anything.  Please advise! 

error try to get to https://xxxxxx.workflowcloud.com/same error try to login tohttps://customer.nintex.com/

TopicDAC Versioning IssueWhen attempting to upgrade the DAC from the 25.11 version to the 26.6 version, the DAC upgrade fails.The issue is caused by WiX detecting version 26.7.2511 as a newer version than 26.6.10000.2.The 25.11 DACs were incorrectly released with version 26.7.2511.The 26.6 DACs were released with version 26.6.10000.2.As a result, WiX considers the 25.11 DAC version to be newer than the 26.6 DAC version, preventing the upgrade from proceeding.Instructions First, uninstall the existing 25.11 DAC, and then install the 26.6 DAC.Uninstalling the 25.11 DACPlease perform the following steps:Stop all Nintex services and related processes that are currently running.Open Programs and Features.Locate and select Nintex Dynamic Advanced Commands.Right-click the application and select Uninstall.Restart the RPA Server.After the restart, verify that the DAC folders have been removed from the installation directory.Once the 25.11 DAC has been successfully uninstalled, proceed with the

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.

I want to understand how to setup my folder structure so as to remove deduplication of processes shared between different departments.

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.

 I have a repeating section on start form which contains read-only short/long text controls.The default value of the repeating section is an external data’s records collection.The external data is a data lookup to a sharepoint list, getting columns:Control/field mapping is working for:ObjectiveDetails ObjectiveMetric ObjectiveName ObjectiveID ReviewIDControl/field mapping is not working for ObjectiveComments. I have tested:Renaming the field in Sharepoint and on the form control Creating a new repeating section in the same form Creating a new repeating section in a start form on a separate testing workflow Using label type form control instead of long text Setting the first ObjectiveComments as default value in a label outside of the repeating section (worked)I am going to use a workaround of having the ObjectiveComments displayed in a label using the field from a separate external data variable which filters by current row ObjectiveID, but would like to check if this is a bug to be re