Complete our Nintex Community Survey
Connect with peers and experts to ask questions, share insights, and find solutions for Nintex products.
Recently active
Note: The deadline to upgrade has been extended to July 31st 2026We are excited to announce a significant upgrade to our Single Sign-On (SSO) implementation. We will transition from a third-party vendor to an internally managed service for SSO. This change is designed to enhance your experience by offering improved stability, performance, and flexibility.Who needs to make this change?Only SAML federated customers need to perform the upgrade. WAAD federated customers are not affected.Why are we making this change?By bringing SSO in-house, we can: Ensure Greater Stability: Control over the service allows us to address issues more quickly and ensure consistent uptime. Enhance Performance: Optimized architecture tailored to Nintex’s environment reduces latency and ensures seamless user experiences. Increase Flexibility: An internal service allows us to respond more effectively to customer needs and implement feature updates at a faster pace. Additionally, the current third-party soluti
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
We're excited to introduce the Organization Portal, a new portal to help organization admins manage their Nintex organization more effectively.Many Nintex customers have more than one tenant, but what you might not be aware of is that those tenants are part of the same organization. Some settings are shared between all tenants in the organization, such as SSO or SCIM. Until now, those features have been configured from within a tenant, but they affect all tenants, leading to potentially unexpected impacts.The Organization Portal is our first step in exposing the concept of an organization to all customers and making it easier and clearer the impact of changing organization-level features.Who has access to the Organization Portal?To access the Org Portal, you need to be assigned a new role: Organization Admin. The Organization Admin role will replace domain verification as a method for getting additional permission to manage SSO or SCIM.All existing domain verifiers have been assigned t
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!
Update 10 July 2026: Package Now Available Nintex DocGen for Salesforce Package 21.12 is now available on Salesforce AppExchange. Customers should upgrade to this 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 Managed Package upgrade to the latest version of Nintex DocGen for Salesforce will be required.After the upgrade, customers will need to transition to the new “Nintex DocGen for Salesforce Modern” Connected App. The upgrade process will include: Upgrading the Nintex DocGen Managed Package Copying your existing Connected App configuration to the new app Reauthorizing your Nintex DocGen connectionThe integration u
Hello,I am looking some guidelines on setting up 3 state approval workflow.Condition: If all required fields are completeStep 1: Send email to the person for review as task with pending status and set document as draftStep 2: Once the reviewer complete the task, it send email to first approver to review the documents, once approved it goes to step 3 and remain the document status to draftStep 3: Send email to the 2nd approver and once the task is complete the documents will publish it as major version.
Hi everyone! I have 2 custom controls which problems right now. Is it necessary to have .aspx format file for custom control? Do you guys know how to solve this issue? All the forms and views that are using these custom controls cannot be opened. This is custom control .dll files that are impacted:1) K2Field.ListSequenceDisplay.dll2) K2FormProgressSteps.dll
Hi Team, I have been struggling to find a suitable way to ‘generate’ a unique form code for ‘booking number’ or a dedicated ‘reference number’ when requested by stakeholders/customers.At first - needing to leverage another system to do a count (SharePoint Online) to provide a number in the line and using format date, did work BUT if someone else submitted a form before you the count number was used and therefore would not be unique causing some duplication. The way to combat that was to enforce a unique field validation on the associated SharePoint column (i.e Title / Booking Number). This kind of worked but would cause the Nintex workflow to FAIL as SharePoint would say no.Instead of making the simple form and workflow complex (could add a Loop N and delay etc) i opted for another way which I think worked a treat especially as i needed to display the Booking Number on the form and have it throughout the process for emails and such. This was a pain point to start with as the original c
I was hoping that NAC had something equivalent to “try/catch” blocks in C++ or Java.I’ve reviewed the Nintex documentation and several Nintex Community articles, but I haven’t found any way to “catch” an exception. For example, I’d like to be able to capture the error text and send an email. Before the workflow dies.Q: Is there any way to accomplish this in Nintex Automation Cloud?
Our Nintex Automation Cloud tenant has a million workflows. Including a bunch of component workflows.If this were C++, C# or Java, I’d have different namespaces (or packages), group my classes into different source directories, and define my class methods into different class files.The only mechanism I could find for “reducing clutter” in NAC workflows is “tags” and “filters”.Q1: Is there any better way to “reduce clutter” than to declare (ad hoc) “tags”, and manually “filter” on them?Q2: Is there any way to separate different workflows to different “groups” (so everything doesn’t all display all together on the “All workflows” page)?Q3: is there any way to define a “default filter” that’s active whenever a user logs on to the NAC tenant (so they don’t have to manually choose filters)?Thank you in advance!
I’m working on an inspection checklist that allows the user to upload multiple photos so they can be renamed and inserted into a report document. My current approach is to use a repeating section with the inspection location (single-choice) and file upload (restricted to image). My assumption was that I could traverse the resulting collection, extract each row as a collection, then parse out the contents of that row. Unfortunately I can’t extract the row as a collection, just as a chunk of json code, which isn’t terribly useful.Is what I am trying to do even possible or should I go straight to plan B (which is to make each row a pair of stand-alone controls vs the repeating section)?Thanks!
Steps to duplicate: Create a dropdown and link to a field in the Sharepoint list that contains 4 items Add a new entry to the Sharepoint list so it now contains 5 items (or whatever, the exact number does not matter) Open the form in New mode or Edit mode results: the new item does not show up Open the form in Designer results: the new items does not show To get the item to show must Re-Publish the form!!!!!! NOT the best way to keep up with users adding/removing items. I ASSUME this is a BUG - as the from is supposed to be LINKED to the field it should update itself?
We have a form that has 20+ questions where the answer can be ‘Ok’ or ‘Defect’ and a further 8 questions with ‘Yes’ or ‘No’ answers. We then convert the form into a PDF and we would like to send the PDF document to a number of email addresses if 1 or more answers have ‘Defect’ and/or 1 or more have ‘no’ as the answer. Branch by condition has a max 10 conditions, what is the simplest way to set this up to send on the above conditions but only send once?
How as an admin could we redirect a task that was originally assigned to one user, and re-assign it to a different user after it's been sent out?I have the option to complete the task myself, but that is not what I’m looking for.
Thank you for your assistance. This is Fukushima from Kaneka.I apologize for the inconvenience, but could you please provide guidance on the following?* Is there a planned End-of-Life (EOL) for Nintex Workflow for SharePoint Server 2016?* If I proceed with the Annual Software Assurance Renewal procedure this August,if support ends according to Nintex's support policy at EOL, is it possible that support will end by August 2027?
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 configure
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
We are happy to announce the release of Nintex RPA 26.6!26.6 focuses on improving stability, clearing technical debt and improving the install & upgrade experience, making it the most stable version yet. 🆕 What’s newSupport for Azure SQL database Support for Windows Server 2025 Auto run wizard at Assistant start Seamless DAC install and sync from server to client Lots of bug fixes and minor enhancements And more…📝 Check out the full release note.📥 Available for download now from Customer Central.
Hello,I'm trying to configure the mail server in the Nintex RPA Console, but I'm unable to complete the configuration.When I click Test Notifications, the test fails and the following error is displayedCould you please help me identify the cause of this issue and advise how to resolve it?I have attached a screenshot of the error.Thank you.
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 have our images on a local webserver, The images do not render on the form and the browser shows this message: It gives the image url and then says its blocked from origin 'https://static.nintex.io' has been blocked by CORS policy: Permission was denied for this request to access the `local` address space.We have tried adding https://static.nintex.io to the local network settings of the browser but it still blocking the images.How are people handling form images? Will Nintex provide an image repository?Any assistance would be appreciated.
Salesforce is strengthening its secure-by-default architecture by enforcing a mandatory, time-based step-up authentication framework. This security control is intended to provide additional protection against unauthorized data exfiltration.The specific feature is called Step-Up Authentication for Reports. It requires users to complete an additional identity-verification challenge when exporting or printing reports if a configurable amount of time has passed since their last successful step-up challenge. What Is Affected?This change may affect Nintex DocGen for Salesforce customers who use Salesforce Reports as part of their document-generation processes.Without the necessary updates or a temporary extension, report-based DocGen processes may be interrupted when Salesforce begins enforcing the step-up authentication requirement.This change may also affect other processes or integrations that use Salesforce Reports, report exports, or report-printing actions within your Salesforce org.T
Issue DescriptionWhen you apply formatting to input controls such as Picker, Drop-Down, Text Box, and Text Area controls, the configured format may not be applied consistently to watermark text at runtime. As a result, the watermark for some controls may be displayed using different formatting, causing the form to appear inconsistent.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 13.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 upgrade and reconfigure Workflow email notifications to use Microsoft Graph instead of Exchange Web Services (EWS), all Workflow email steps fail after the configuration is completed.Error Message:The following error occurs:“The request body must contain the following parameter: 'grant_type'.”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 13.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.ConsiderationsWhen you copy HTML into K2 Studio, ensure that the HTML is correctly formatted before saving or deploying your Workflow.HTML elements that contain line breaks within their opening tag may not be parsed correctly. As a result, portions of the HTML can be rendered a
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.
