Product Forums

Hello Community! I like the way Radio Button controls look when the “Borderless” property is checked, but I’ve found that if the radio button is required, the validation rules don’t give it a red border because, well, it is borderless. How do you all let users know that a borderless Radio Button control is required?

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

Hi everyone! Nintex Apps 17.11.9 is live 🎉 Here's what's new across our last two releases! 💪 Page Designer performance enhancementsMultiple improvements: reduced browser memory usage, less editing lag on large pages, and faster load times on pages with many components. ⏮️ Page revision improvements Get back to work faster. Clicking Restore now auto-saves and closes the modal. 🗂️ IndexIndent guides added; right-click context menu added for Drawers, Wizards, and Carousels🔗 Full release notes💬 Share your thoughts in this community forum or feel free to message me directly.Happy building!

I am finally trying to convert to the V2 and use design system.  I want one simple thing:  I was the section header background color to be anything except white.  I followed all instructions, but my org does not have the option for changing the section header background color.  I looked in Header, Form, Nested Components under Form, and the proper place is in Header.  No ability, no option to change the color of the Header. Clone, try to update, etc.  There is no place.  Can someone tell me where it is hiding.  I am on the very latest version of NAFS (nintex apps for salesforce).  

I’m working on a flow to update a Nintex Table from a report retrieved from our ERP. Part of the flow requires that it compare a ticket number from each row of the report to what’s already in the table, so it will only add new rows.The approach I’m using is to use a Query a Table action to generate a collection of only the ticket numbers (i.e. theTableResult>Rows) then using a Check If Item Exists in Collection action from a ticket number in the report, to see whether a given ticket number is in the collection and hence in the table.The snag I’ve run into is that the Check action doesn’t seem to be correctly evaluating whether the supplied value is found in the collection. This is what the collection looks like in Log to Instance Details, along with the raw result of the Check action for ticket 71629 (supplied as a default text variable):Logging the First Row from that same table query appears to show the value correctly:In other words, it seems to work fine showing the info directl

I’m trying to generate a text variable with a custom date.I can’t use “Format date from String”: none of the built-in “Format” options match what I need.I’d prefer NOT to use a form (this will be a component workflow, invoked from an external app), so I’m not sure this documentation applies:  https://help.nintex.com/en-us/nwc/content/designer/Functions/formatDate.htmThis is EXACTLY what I’m looking for: yyMMddHHss:  I’m trying to use fn-FormatDate({Workflow:Current Date and Time},"yyMMddHHmm") in “Set Variable”.It’s printing out “fn-FormatDate(...)” instead of executing the inline function:Q: What am I missing???  

TopicAs per the compatibility matrix, currently Nintex Automation (5.8) and Nintex Automation K2 (5.9, and 5.9.1) are the only supported versions that support .NET 8.0.According to Microsoft, official support for .NET 8 is ending on November 10, 2026. Instructions We are releasing fix packs for supported K2 versions to upgrade support from .NET 8.0 to .NET 10.0. When these fix packs are released, this article will be updated to include the necessary fix pack level.This will be only for supported versions, so if you are on an older K2 version and require .NET 10 support, make a plan to upgrade today. Fix Packs now available for:K2 (5.9.1) Fix Pack 03 (or later)When in doubt. please refer to our compatibility matrix (https://help.nintex.com/en-US/platform/K2Support/ProductCompatibilityMatrix.htm#.NET_Core) on the latest product compatibility. Any updates to .NET  compatibility will be reflected in the compatibility matrix, as well as supported upgrade paths.

Salesforce is implementing a security change that affects OAuth refresh tokens used by integrations, including Nintex Workflow Salesforce connections. What is changing? Salesforce will invalidate refresh tokens that have not been used for 30 consecutive days. As a result, Salesforce connections in Nintex Workflow that remain inactive for more than 30 days may require reauthorization before they can be used again.  Who is affected? This applies to customers using the Salesforce connector in Nintex Workflow, particularly those who use it infrequently. What happens if a connection becomes inactive? If a Salesforce connection is not used for more than 30 consecutive days:  The refresh token may expire.  Workflow actions using that connection may pause (if error handling is enabled) or fail.  The connection may need to be reauthorized before workflows can successfully execute again.  Recommended actions To avoid disruption, we recommend one of the following: Option 1: Create a scheduled w

Hello,I’m using translations based on the ui-culture URL parameter. The translations work correctly for Forms and Views, but I’m having an issue with translating subviews.I have already added the translated keys in the Management environment, but I’m unable to see the language switch for subviews when I change the ui-culture parameter in the URL.Could this be related to how K2 handles translations? Does K2 load translations only when initializing the Views/Forms that are directly visible to K2? Is it possible that subviews are loaded using lazy loading, so their translations are not initialized when the ui-culture parameter changes?Is there a recommended solution or workaround for this type of issue?Thank you!Regards,

We recently migrated a K2 5.9 FP14 system from EWS Online to Graph and noticed issues with mails.The mails for tasks and redirects are not going through but email action ones are, has anyone had a similar issue with Graph and found a solution?We checked the HostServer and Event View logs, but no errors are showing up.

Hi Community,I'm working with Nintex Automation CE (Cloud) and have a workflow that inserts form data into a Nintex Table.As part of the same process, I'm storing file information in the table as a collection/list object. My requirement is to retrieve the file through the workflow and make it available to the end user, either by:Sending a downloadable link in an email, or Sending the file as an email attachmentMy understanding is that a downloadable link typically requires the file to be stored in a repository such as SharePoint, OneDrive, or another file storage solution that can generate a secure URL. If that's the case, I'm wondering whether Nintex Tables are intended only for storing file metadata rather than serving files directly for download.I would appreciate guidance on the following:Is it possible to retrieve a file stored in a Nintex Table and provide it to users through a downloadable link? What is the recommended or best-practice approach for this scenario? If external sto

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

Nintex for sharepoint 2019 needed setup file for nintex

Hello community - I’m getting user complains that the icon to expand/collapse views on the form are too small and difficult to click. In the legacy theme, I was able to come up with some JQuery to make the entire view header clickable to expand/collapse the view, but I’m having a hard time doing the same with the modern theme (K2 5.9). If anybody else has solved this issue, would they be willing to share their script (or other approach)? Thanks in advance!

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!

HiBecause of the upcoming deprecation of Exchange Online EWS I’m testing moving our environments over to using MSGraph.I upgraded to 5.9 successfully.  Ran the Exchange Online Migrate wizard successfully and email works.  However, it appears when I look at the Connection String editor for mail configuration that its still using EWS as it didn’t add the MSGraph settings.  I checked and the Azure Enterprise app was added successfully with the correct permissions.  The resource shows correctly in Management.  I tried following the article about manually configuring some of the connection string settings but email then failed.   Is the Migrate wizard supposed to take care of all of the settings or am I missing something?  I’ve restored the VM and retried 4 times so far without any luck. https://help.nintex.com/en-US/nintexautomation/icg/5.8.1/Content/Configure/ExchangeOnline/ExchangeOnlineManual.htm

Hello Nintex Community, I would like to know if there are any plans on the Nintex Automation Cloud roadmap to introduce:A native Workday connector for integrating with Workday HR and Finance systems. A Data Lookup capability similar to lookup actions available for other enterprise applications, enabling users to retrieve and reference Workday data within workflows, forms, and automation processes.We are exploring broader HR process automation scenarios and would be interested in understanding whether native Workday integration is being considered, or if there are any recommended approaches currently available through Xtensions, APIs, or third-party connectors.Any information on future roadmap plans, current alternatives, or best practices would be greatly appreciated.Thank you!

I have a Nintex Workflow online start form that has a People control set to allow multiple selections. Submitting the form kicks off a workflow that has a “Assign a task to multiple users” action. I would like to pre-populate a People control in the workflow task form with the selections from the People control on the start form. Anyone have a solution for this?

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 install Fix Pack 34 on an environment where the database is not named K2, an installation error occurs.Error Message:The following error occurs: “Script execute failed: System.Exception: Script execution exception: System.Data.SqlClient.SqlException: Invalid object name 'K2.SmartBroker.ServiceType'.”ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 35.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 Condition action ‘WFIfElseAdapter’, it has no conversion mapping and falls back to a generic placeholder step instead of converting to a K2 Decision.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 15.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 change the Data Source of a view generated by K2 for SharePoint, the original ListId remains referenced by the view.The original SmartObject linked to the previous Data Source remains associated with the view. Instead of displaying only the current view and its corresponding SmartObject, the view displays all folders from the original SmartObject.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 15.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.

We've published two SharePoint web parts that bring Nintex Workflow Cloud directly into your intranet, so you don't need to switch between SharePoint and a separate Nintex portal to check on work.What they do:Nintex Workflow Tasks: see your pending and completed workflow tasks right on a SharePoint page. Approve or reject tasks in place, with an optional comment, and jump into the full form when you need more detail.Nintex Workflow Forms: browse available workflow start forms as clickable cards, so starting a new request is just a click away from wherever your team already works.Both web parts use single sign-on with Nintex, so once you're logged in, sessions stay active in the background with no repeated login prompts.Setup is straightforward. Register a client app in your Nintex tenant, drop the client ID into the web part settings, and you're good to go. Full setup steps and a user guide are included.You'll find them in the Template Gallery here: https://gallery.nintex.app/gallery/t