Upcoming Event - Nintex Automation K2: Back to basics
Connect with peers and experts to ask questions, share insights, and find solutions for Nintex products.
Recently active
Sentiment and Severity AgentHelp Support teams, triage incoming requests accurately and quickly. Read moreInvoice & Purchase Order Matching AgentFinance – Accounts Payable, perform an accounts payable invoice and purchase order match. Read more
Today, Nintex is announcing End of Life (EOL) for our legacy Nintex Process Discovery product. Per our standard support policies found at www.nintex.com/legal, Process Discovery will officially reach EOL on May 1st 2027, and we will make support available to active customers for two years with our End of Support date in May 2028. Our Nintex Process Discovery customers can upgrade to Nintex Process manager to continue utilizing their Nintex-based process documentation and management capabilities. If you are an existing Process Discovery customer, your account manager will reach out to you to review these End of Life details and discuss any transition plans to Nintex Process Manager. Please note that this End of Life announcement for Nintex Process Discovery does NOT affect any other Nintex process products. Nintex Process Manager and the Process Capture identification capabilities will continue to be fully supported.
If you’ve ever been handed a giant PDF, a 20‑page policy, or a massive core process Visio diagram and told: “This is one process... can you put it into Process Manager?”…you already know where this is going.These large assets are almost never one process.They are Groups of processes.And honestly? They’re often a great start, just not structured in a way we can use directly.In the past 12 months I’ve seen more and more organisations wanting to “lift and shift” big documentation sets into Nintex Process Manager. Teams want to speed up onboarding, get their frameworks into shape, and make use of their existing documentation.The challenge?Big documents and big Visio flows carry a lot of value, but not in a format that Process Manager can use.So I built a Copilot agent that helps me unpack these documents in a structured, APQC‑aligned way, and convert them into clean Group structures + draft Process Prompts. I then feed these into Nintex Process Generator to create high‑quality draft proced
Hi everyone,As part of our ongoing efforts to improve your experience and better support your needs, we've divided the Skuid NLX, SFX & EXP forum, into dedicated product forums!👉 Start exploring here:NLX > Nintex AppsSFX > Nintex Apps for SalesforceEXP > Stays here! This is also the place where you can find older topics related to Skuid NLX and SFX. These new spaces will make it easier to find what you need and connect with others focused on the same area.We encourage you to:Post new questions or feedback in the new forum Share your tips and experiences Help others in the communityBy using the new forums, you're helping keep our community organized, relevant, and even more helpful for everyone.See you there!
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?
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.
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. 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 22 January 2026 Contact Support for this Fix Pack Fix Pack 02 10 February 2026 Contact Support for this Fix Pack Fix Pack 03 26 February 2026 Contact Support for this Fix Pack Fix Pack 04 6 March 2026 Contact Support for this Fix Pack Fix Pack 05 11 March 2026 Contact Support for this Fix Pack Fix Pa
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. 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 30 June 2026 Contact Support for this Fix Pack Fix Pack 02 5 August 2026 Download Fix Pack 02 Prerequisites and DependenciesThe Fix Packs are only compatible with Nintex Automation (5.9) products. Because Fix Packs are cumulative, each new Fix Pack contains the updates and fixes that were included with the previou
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.
Hi Team,I am working on migrating one of our application to use the Nintex K2 Automation and sunset the K2 blackpearl. SourceCode.Workflow.Management.WorkflowManagementServer managementServer = (WorkflowManagementServer)getK2ConnectionObject(K2ConnectionType.WorkflowManagementServer, null); if (managementServer.RedirectWorklistItem(formattedFromUserNTLogin, formattedToUserNTLogin, wi.ProcInstID, wi.ActInstDestID, wi.ID)) { itemsRedirected++; }I want to use the SmartObject API to redirect Work List Item instead of the dlls. How i can achieve that any help would be appreciated.
We recently adopted Nintex and have been developing some workflows. For various reasons, we aren’t yet ready to federate our active directory to Nintex. However, I want to start adding some users so we can do testing and then move the flows into production.Adding 40-50 users one at a time seems like a lot of work and I would like to be able to upload a csv file with their data instead. I thought I saw how to do that somewhere but cannot find it now. Was I just dreaming or is this possible?Thank-you!Chris
With salesforce release for step up authentication our docgen packages which have reports to populate template failed with error message even after upgrade to latest package.
Subject: Need Help Creating My First Nintex Workflow (Form Submission and Email Notifications)Hello Everyone,I am new to Nintex Automation Cloud and am currently trying to build my first workflow. I have made some progress, but I am struggling to complete the workflow successfully and would appreciate any guidance, tutorials, or resources that could help.What I have completed so far:Created my Nintex Form. Configured the workflow Start Event.I am trying to achieve:Send an email to users with a link to access and complete the Nintex Form. When the user submits the form, store the form data in SharePoint. Send an email notification to me when a submission is received. Include key data from the submitted form (SharePoint columns) in the notification email. Ideally, send a confirmation email back to the user after successful submission.I am having difficulty understanding how to pass form data into the workflow and access SharePoint column values within the workflow. Also, how to configu
I got this field renderer from Skuid several years ago (pro hours). It stopped working with version 17.11.20 last week. Any ideas?Symptoms: In Read/edit mode, the page loads but most fields are not editable, with or without the renderer.If set to load in Edit mode, the page will not load.Footnote: This is for a Salesforce Digital Experience site.This code takes values from a multi-select picklist from one record and display those values as single select values in another record. var test = skuid.model.getModel('Organization');console.log(test);const FieldRenderer = skuid.component.FieldRenderer;return new FieldRenderer({ // readModeStrategy: "virtual", // read: function (fieldComponent) { // }, editModeStrategy: "virtual", edit: function (fieldComponent) { let h = fieldComponent.h, context = fieldComponent.cpi.getContext(), { field, model, row, value } = context, sourceModel = skuid.model.getModel('Organization'), source
Issue DescriptionWhen you save a document as a PDF, the operation may fail and display an error message.Error Message:The following error occurs: “'The PDF could not be saved' "Invalid length for a Base-64 char array or string.”ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 34. 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.
Issue DescriptionWhen you run the Refresh All operation for SharePoint, an error may occur and prevent the operation from completing successfully.Error Message:The following error occurs: “Error converting data type nvarchar to datetime.”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.
DescriptionThis Fix Pack introduces Microsoft Graph support for email functionality, enabling integration with modern Microsoft 365 authentication and Exchange Online services.This enhancement extends Microsoft Graph support to the following areas:Workflow Mail Events Workflow Task Notification Emails SmartForms Email Actions K2 Studio (thick client) Mail Events Exchange Online integrationResolutionThe 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.Additional InformationNintex Help for latest version of K2:https://help.nintex.com/en-US/nintexautomation/userguide/current/Content/K2-Management-Site/Feature…Microsoft article:Retirement of Exchange Web Se
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
