Product Forums

Unlocking New Use Cases with Table Forms in Nintex DataFor a long time, Nintex has been exceptionally good at orchestrating workflows.Approvals, routing, escalations we’ve got that covered.But here’s the thing we’ve heard consistently from the community “Not everything needs to be a workflow.”At time we do come across situations where you just want to capture data, maybe attach a file or two, store it safely, and move on, no approvals, no emails, no workflow entitlements quietly disappearing in the background. That’s exactly where Nintex Data Tables and Table Forms step in. And with the introduction of the new File column type, they just became a whole lot more powerful.In the PastTraditionally, Nintex didn’t offer a native way to store persistent data with files.So, if you wanted to:Capture a signature Upload inspection photos Store feedback attachmentsYou usually had to:Push the file into a Document Management System (SharePoint, Box, Google Drive, OneDrive etc.) Trigger a workflow j

I wanted to reach out and see if people have developed forms that eitherconstruct a document from the questions and responses provided from a submission, which gets created, then goes through conversion (to be a PDF) to then be appended to an email action and whether or not it works and if there are better ways / connectors to leverage such a request.I have a form and workflow from another application that I need to rebuild into Nintex however this 1 item is a blocker for us. The other application has a native action to construct s ‘Summary Document’ and it can be provided as a word/csv/excel or PDF. It is derived from the contents of the form/workflow upon submission.I am trying to avoid the following as well:create and store file in external repository call file from external repositoryEssentially I require a form that afterwards will generate a file and send that to the recipient / user with all the details that could be displayed in an email.Additionally the file may also need to b

I wanted to see whether or not the community has encountered this and or has a ‘solution’ for this problem I currently have.I want to see in the User management side of Nintex on the Tenancy, if a user is allocated to an assign task action and or multiple and in what projects?I know that there are some other forms and workflow engines that have this capability to “see” what each user is allocated to and where. 

I wanted to reach out and see if people have developed forms that eitherconstruct JSON text strings in the workflow and create a text/JSON file appended to an email action and whether or not it works and if there are better ways / connectors to leverage such a request.I have a form and workflow from another application that I need to rebuild into Nintex however this 1 item is a blocker for us. The other application has a native action to construct JSON from the contents of the form/workflow upon submission.I am trying to avoid the following as well:create and store file in external repository call file from external repository 

Update 10 July 2026: Package Now Available Nintex DocGen for Salesforce Package 21.12 and above are now available on Salesforce AppExchange. Customers should upgrade to the latest version and complete the required reauthorization steps.  Refer to the help document for detailed instructions.  Salesforce is strengthening security standards across the AppExchange ecosystem. As part of this change, all AppExchange applications, including Nintex DocGen for Salesforce, are required to adopt enhanced OAuth security controls including PKCE and Refresh Token Rotation. What this means for youA Salesforce administrator will need to complete the following:Upgrade the Nintex DocGen Managed Package to the latest version. Transition to the new “Nintex DocGen for Salesforce Modern” Connected App by copying the existing Connected App configuration to the new app. Reauthorize the Nintex DocGen connection. The integration user used for scheduled or automated document generation must also b

Dear Team,I am writing to request your assistance with an issue I am encountering while working with our mock SAP setup. Please find the details below, along with the attached Swagger file for your review.---1. Context- We are using the attached Swagger file to create a mock SAP environment.- I am using Nintex Workflow to retrieve data from this mock SAP via the defined API endpoints.2. Issue DescriptionWhen I retrieve data for a specific object (e.g., object code OC"), the HTTP response returns a "value" field that contains two (2) items. However, instead of mapping each item into its corresponding column, the system displays the entire "value" array as a single combined string in one field.Expected behaviour:| Column | Data || Value 1 | Item 1 from the response || Value 2 | Item 2 from the response |Actual behaviour:| Column | Data || Value 1 | Item 1, Item 2 (both items combined) || Value 2 | Item 1, Item 2 (both items combined)|In summary, the data is not being itemised or segregat

Hi everyone, I have a problem when the user does not receive the email. I'm enabling the SmartAction btw for user interacting with K2 server. I have setup the username, password and EWS url in K2 Connection String Editor. I have also setup in K2 setup manager and all are working properly. Just that when I check in the log, it keeps using the SMTP instead. Besides that, I also did some editing in K2HostServer.exe.config based on Nintex Support request. Note: EWS email and SMTP are different. 

We have some docgen packages that are triggered by an outbound messages. Since, last couple weeks none of these packages triggered - did not create documents.Is there any update that went through in last 15 -20 days?

Not entirely sure why I’m getting status of NotFound for this Xtension. We were testing ability to export a workflow from one Nintex tenant to another using a workflow rather than manually doing it.  I have checked everything - region is fine. Other actions within this Xtension works just fine so what is the issue with this particular action that it cannot recognize a workflow ID? It’s published and in DEV. I republished in PROD and still returning NOTHING.  

We created a workflow with a start form that includes Text – Long controls populated by rules. This creates an issue when users select “Copy form data” to reuse information from a completed form in a new submission. Because those text controls were populated by rules in the original submission, their values do not carry over to the new form. I have two questions:Do you have any suggestions for resolving this issue? Is there an action that allows a user to select a specific point to restart the workflow? In other words, is there an action that can move or jump to a defined step in the workflow?

Hello,I tried to set up a kind of workflow protokoll for the users which is directly visible at the relevant list item. I added a multi line text field to the SharePoint Online list, with the option “Add changes to existing text”. When updating this field via a Nintex Workflow, it overwrites the existing text instead of adding it. Is there any chance to add the next comment without first reading the content of the field, adding the new comment via “build a string” and storing the whole new content back in the field? Or does Nintex simply ignore the option “Add changes to existing text” and I have to do it like I described above?Thanks for any ideas!Marion

If a risk portfolio is no longer required, but has risk with overdue signoffs, can the portfolio be deactivated and the signs automatically removed from the dashboard or do signoffs need to be completed before deactivation?

Hello Community - how do you all validate non-required calendar controls on your K2 forms? I’ve found that if the user manually types in an invalid date, the form does properly highlight it but it still passes the validate condition because the value behind the scenes in the control is blank. This is find for when the field is also required, but if it is not there is no way for the form rules to know that the control has invalid data. I’ve ended up building some javascript to see if any calendar control has that invalid class on it and set an is valid checkbox accordingly, preventing the user from saving/submitting if this check box is not checked. That seems like a strangely convoluted work around for what seems to be a simple issue. Am I overlooking something? Please share your solutions to this scenario. Thanks!

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. 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 the below error will occur:“HTTP Error 500.19 - Internal Server Error” NOTE:  If you have client tools installed, please do a manual IIS Reset after installing the Fix Pack. Fix Pack Release Date Download Link Fix Pack 01 23 October 2024 Contact Support for this Fix Pack Fix Pack 02 30 October 2024 Contact Support for this Fix Pack Fix Pack 03 8 November 2024 Contact Support for this Fix Pack Fix Pack 04 20 November 2024 Contact Support for this Fix Pack Fix Pack 05 12 December 2024 Contact Support for this Fix Pack

Issue DescriptionWhen you upload files larger than 1 MB, an error occurs.Error Message:The following error occurs: “Error reading HTTP body”ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 34.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. 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 the below error will occur:“HTTP Error 500.19 - Internal Server Error”NOTE:  If you have client tools installed, please do a manual IIS

Issue DescriptionWhen you use the Tab key to navigate a form and select a value in a drop-down list, pressing Tab does not submit the selection. Instead, focus moves to the browser, requiring you to tab through the browser controls before returning to the form. On the second attempt, the selection is submitted and focus moves to the next control.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 14.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 from Exchange Web Services (EWS) to Microsoft Graph, emails sent from a Distribution List may no longer be delivered successfully.Error Message:The following error occurs:“"Error","General","1","GeneralErrorMessage","MsGraphMessageDestination","1 SourceCode.MessageBus.MsGraphDestination: Email Send Falied, Error: Status Code: NotFoundMicrosoft.Graph.ServiceException: Code: MailboxNotEnabledForRESTAPIMessage: The mailbox is either inactive, soft-deleted, or is hosted on-premise.”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 14.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 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. 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 the below error will occur:“HTTP Error 500.19 - Internal Server Error”NOTE:  If you have client tools installed, please do a manual I

Issue DescriptionWhen you upgrade your environment, button icons may no longer display on Runtime Forms that use the legacy responsive themes (Blue Void, Grey Void, or Lithium).ResolutionThe fix is available in:Nintex Automation K2 (5.9.1) Fix Pack 02.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 deploy or validate new or existing workflows, you may encounter Application Lifecycle Management (ALM) errors on the Task Reminder step because the To field in the task recipient email is now validated as a required value.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 14. Nintex Automation K2 (5.9.1) Fix Pack 02.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.