News and Guidelines

Though I have been working with Nintex Forms and Nintex workflows for a long time I didn't happen to realize how versatile and fun to work with repeating sections on the forms in conjunction with Nintex workflows. Long story short, I always had this common requirement from Infopath form days till a new project I implemented purely with Nintex, that is none other than having an ability to report and update the repeating table rows using spreadsheet view in the SharePoint. Until I come across a great post written by Vadim Tabakman parse repeating section data I felt it is not possible help clients with such requirements without code, but Vadim Tabakman's posting changed the way how I looked at NIntex F

Products: Nintex Workflow for SharePoint (2016, 2013, 2010) Avoid “All” and “Item” Content Types To prevent lengthy content type evaluation when saving or publishing reusable workflow templates, avoid selecting “All” or “Item” for the content type. Instead, create a content type based on Item and then select the created content type when defining the reusable workflow template. For instructions on creating content types, refer to the SharePoint documentation. More Information For more information about reusable workflow templates, see “Set Title and Description for Reusable Workflow Template” in the Nintex Workflow Help (2016 |

Thanks to Sean Fiene‌ for assistance. Below is an example of how to perform Validation on specific controls based on their dates. The goal: If start date is less than or equal to 11 days from today andor If start data is more than 7 days before end date than prevent the form from being submitted. Step 1:Create a list with a “Start Date” and “End Date” column of data type “Date and time”. Step 2:Open Nintex Forms and choose “Forms Variables” from the ribbon bar. I named my variable ‘varStartDate” Type: Integer Connected To: Not Connected Recalculate formula on view mode: No Recalculate formula on new mode: Yes Recalculate formula on edit mode: Yes Formula: dateDiffDays(Current Date, StartDate)

There is currently a .Net update that has caused disruption on SharePoint 2007,2010,2013 and 2016 platforms.  After applying .NET Security Only patch to resolve CVE-2018-8421 (Remote Code Execution Vulnerability) , all SharePoint "out of the box" & Nintex Workflows fail to execute and the log will show an error like the below: ULS Log: System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file Publishing a Nintex workflow   ResolutionMicrosoft link to issue & resolution. Microsoft related u

When i am developing forms for applications, i like to have as much information on the new item form as possible. Workflow can update the item after submission but I think it adds to the user experience to see important information on the form. Whether it is a unique reference number as described here: Ensure Unique Reference On New Item‌ or other information.Another piece of important information, especially in an application that requires line manager approval is, yep, you guessed it, the line manager.With Nintex Forms People Picker API, described in detail here: People Picker Extensions - Nintex Forms‌ we can add the line manager to the people picker control,In my example i have an employee people picker field default to current user and a Client ID JavaScript variable name of varCurrentUser

I had these notes stored from a couple of years ago - they helped me at the time with a problem I had been banging my head with for ages, but I haven't needed to use them since.  Not sure if any use to anyone, but in the process of getting all my blog posts in one place, and what better place than the Community  Believe it or not, this is not straight forward.  For this blog I will paint the picture.  I have a request list which uses Managed Metadata to store Business Units.  I have a list on another site which stores approved and completed items from the original request list.  On this list, the same Business Unit Managed Metadata column is used.  I tried using the "Create item in another site" action in Nintex Workflow but could not just simply map the field from one list to the other.  Instead I had to query the TaxonomyHiddenList of the target site collection to get the ID and GUID for the term.  To

This is just a reminder for me (if I need it in the future) or whoever need it so as to lose time I lost trying to do it. I tryied to customize a task form with Nintex Forms and I received this message.      Please update to the current version of Nintex Forms for Office 365 You are using an older version of Nintex Forms for Office 365 Update to the most recent version to customize task forms   And I asked myself how could I update it. Because I didn't remember a Sharepoint feature to update installed apps. And after some time I solved it with the next steps: In order to add the app to your Office 365 tenancy, you will need to add the app. This tutorial will take you through the process of adding the app.In your Office 365 site, click on the Settings icon and click on

If I could fill the title with exclamation points, I would. The lookup() runtime function for Nintex Forms for Office 365 is now available. For those of you that have used Nintex Forms for SharePoint 2010 or 2013, you know how powerful this function is, and for those just new to Nintex Forms, let's take a look at what you will be taking advantage of soon! In this example, I want to build an order form that will include a Lookup control pulling Item Names (Title Column) from an Inventory list. In the order form, I want to have read-only values for the item color and the item number. Let's start building! Here is an overview of the Inventory List. Notice the column names and values:Now that we have built an Inventory List, we need to create a list to contain the order form and open the Nintex Forms Designer. I've replaced the Title single line text box contro

In Nintex 2010, 2013 and 2016 for SharePoint (Standard version even) on-premise of course, there was a possibility to use excel services to query and work with the xlsx and xls files' data. However, insharepoint online there is no such powerful mechanism. Moreover Nintex products for SharePoint Online (neither nwc‌ nor nintex for office 365) don't have any "ootb" actions that would fill that gap. So in the end, there is no straightforward way to achieve it. The most common workaround is to convert the XLSX file into a plain, csv file and then to work with the data from the file using collections (I will write about it in second post). Recently I have realized, that there is a set of excel‌ actions in microsoft flow‌! All of us, who has SharePoint Online, has also a free version of Flow available.  Just be aware, that in the free version Flow does not triggers itself once an event occurs. It just repeatedly checks whether an action occurs

You can use the NWAdmin PowerShell snap-in available through the SharePoint 2013 Management Shell on your SharePoint 2013 server with Nintex Workflow installed. You can use NWAdmin and the ExportWorkflow and DeployWorkflow commands to export and deploy a Nintex workflows using a script. You can use the command in migration scripts to move your Nintex solution, in scripts to move your workflows from a development to production environment, or any other situation where programatic access to the workflow will make your work easier. In this post we will walk through how to access the NWAdmin PowerShell tool on a SharePoint server with Nintex Workflow installed, and then export the workflow, and then deploy the workflow to a new list. Contents Export a workflowYou can use PowerShell to export

If you observed that below Nintex Timer Jobs not running on your Nintex 2016 farm  follow the below steps:Nintex Connector Subscription Synchronization Nintex Connector Workflow Manager Nintex Connector Workflow Synchronization Nintex Peak Usage SynchronizationMake Sure that you have Central Admin Site running on Application Server, If not follow below steps:Moved Central Admin site to Application Server Stop and Start all Nintex Services on all server Restart SharePoint Timer Service on all server Activated Nintex for all web application Deactiv

To have external connection working, Follow below steps:Turn on External Settings from Nintex Administration Turn on all Nintex Actions Perform IISRESET for immediate availability of actions in workflow. Make sure that you have root site collection created in web application Now you are able to have DocuSign Connection Support‌Nintex for SharePoint‌

We've had a couple of people request the ability to pull back information on the workflows in their farm. This script will return the results of all workflows found inside of the Nintex databases associated with your farm. There are a couple of things to note: Workflows that have been designed, but never run will not show in the results (no record of them in the Nintex DBs) If you have performed a recent purge on the Nintex databases, the workflows may not show up. If you receive errors when running the script, please allow it to run to completion. The script uses what It finds in the Nintex DB and resolves certain information (SiteID > Site collection URL, Etc.) and may error if a Site Collection/Site/List and/or workflow is not found. This will not affect the results of the workflows that are found.  PowerShell

Nintex Workflow Cloud Release 54 comes with very good news for those of you using Nintex for BOX.Now, the actions in the BOX connector accept the File or Folder ID as parameters to identify and work with files and folders. And, as you can see in the examples below, the new feature has been added to the actions, it’s not replacing the previous option of the action working with the objects paths. So, if you were already using BOX actions in your workflow with paths don’t panic, you won’t have to change anything. This new feature comes as a response to the feedback we’ve received during the last months from customers and partners asking for a way to interact with BOX objects using the file and folder ID. From here I’d like to thank my product team at Nintex, for the great job they’ve done here and the quick reaction to the BOX and Nintex user's request (myself included

 Nintex is pleased to announce the acquisition of Promapp, a business process management software company which provides partners and customers new tools to better optimize business processes through a market leading visual process mapping solution.  The full press release is available at https://news.nintex.com/2018-07-31-Nintex-Acquires-Process-Management-Leader-Promapp . Further details are available at  https://www.nintex.com/workflow-automation/process-mapping/. 

A sandwich PDF is a scanned document that contains an invisible text layer exactly over the image text. Text layer is produced by OCR (optical character recognition) using open source software tesseract. So PDF ist searchable for text and text can copied and pasted in another document. prerequisitesPowerShell workflow action (I use dataone PowerActivity, it should also be possible to other actions like NTX PowerShell Action - Stable Release from Aaron Labiosa ) tesseract (GitHub - tesseract-ocr/tesseract: Tesseract Open Source OCR Engine (main repository) ,  windows installe

Hello! The requirement for doing this was as follows. I have a few lists across various sites that have near to 20,000 items in them. Absences and training registrations for example. When staff leave the company, I wanted to move their relevant items out of the main list into an archive list. I built a site workflow for each of these lists (they reside in different sites ) that allowed me to enter the users logon and items matching the logon would be copied to the archive and deleted. Hence the reason for this post. I wanted to build a parent site workflow, which would allow me to choose the logon as normal and then pass that logon to each of my site workflows and run them, rather than me running each one individually. So I'd not done this myself before so I'm sharing my findings after using the following resource...https://community.nintex.com/docs/DOC-1048 

This update is to comment on the document: Manually Update O365 Apps But since I couldn't add any comments to the document I wanted to blog the quick second step needed with modern site. You will not see update link like the following in modern site modeBut you will see it like this in modern sitesSo in modern sites, you cannot update the app as easily. The best way is to use the link in the bottom left corner of the site page to "Switch to classic mode". Then you can easily click the Update link and follow the steps from the original document. Summary:The O365 App will sometimes require the update to be manual

Hello All! So I have come across some questions and discussions around the out-of-the-box web parts that Nintex provides for reporting and I wanted to dive.Before we go on this adventure, but sure to check out Enable Reports on your Nintex Workflows​ by Emily Billing​, it will help provide some background!Also, these web parts are a part of the Enterprise Edition. Turning On Your ReportsSeems silly, but make sure it is plugged in...At a minimum you will need to turn on Nintex Workflow and Nintex Workflow Reporting Web Parts at the Site Collection level.You may want to turn on Nintex Workflow Enterprise Reporting

Products: Nintex Workflow 2016, Nintex Workflow 2013, Nintex Workflow 2010 A common cause of workflow failure is size. Additionally, large workflows can cause widespread performance issues in your SharePoint farm. This article provides instructions on how to locate large workflows. Run the below (attached as well as a *.txt file for your convenience) PowerShell script (PowerShell ISE works well) from a SharePoint Server: PowerShell Script Add-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue   #Workflows that are larger (in Kb) than threshold will be returned. [int]$threshold = 500   function Get-WorkflowFolders { PARAM ( [Parameter(ValueFromPipeline=$true)] [Microsoft.SharePoint.SPWeb] $SPWeb ) BEGIN {   }

This is just a quick tip. I was working on several forms that all had Nintex Mobile layouts. For several of these forms I used Preview mode so I could test the form, but not publish the changes to the user. To preview a form, select the Preview button on the Nintex Forms Design Ribbon. The preview settings dialog will appear before the preview is displayed. Then choose the device type of Nintex Mobile App. Forms designed for the Nintex Mobile App are not available for preview directly within the Nintex Forms Designer as it cannot render an accurate preview. When a mobile layout is specified as the device layout to preview, the platform and mode are not longer relevant. This worked great without issue until I realized later that I had a couple of previews left over and wondered why they didn't go away after I published the form. I couldn't find anything in the designer to remove the Mobile App previews. I forgot this simple note in the Forms User Guide:

Once in a while you may end up having orphan Nintex Workflow tasks in your environment. Normally you wont end up in this situation in you production environment as this is normally as result of playing with the workflow or the list.But anyway we don’t live in a perfect world and things like this happen which can be really annoying. Specially if you are using Nintex Mobile to respond to your tasks. One symptom is that you keep getting the tasks even though you delete local storage.So here I show you how to delete the orphan tasks for good Navigate to your SharePoint site. Choose to edit the page. Select insert => Web Part. From the Categories column select Nintex Workflow 2013(or 2010) and from Parts column select My Workflow Tasks

If you are wondering what “lar, doce lar” means, this is the exact Portuguese translation for “home, sweet home”. Obviously, the context of this article has nothing to do with the pleasure of being returning home, but the he Lean, Automate and Robotize (LAR) approach can and should be just as sweet and can also avoid some painful experiences in the future.Before we get deeper into the topic, bear in mind that LAR is the result of my own experiences around automating business processes, and it is not a known term in the community. While I do not have the ambition to push one more acronym into our work routine, I do hope, for the sake of security, efficiency and cost reduction, the approach gets implicitly adopted as a best practice.There is of course a bunch of articles mentioning that the processes should be optimized before being automated, but with the hype around Robotic Process Automation (RPA), we need to revisit the subject as RPA can also offer a risk for your p

Even a short workflow can generate quite a few variables. When you assign a variable to tasks, the names are presented in alphabetical order. The variables list itself displays the order in which they were created. This makes it difficult to find a particular one to delete for example while refactoring or just coming up for a name for a new variable.It was such an exercise that prompted me to write the attached script which sorts the variables into order, either by Name or Type and Name.After exporting the workflow to the filesystem, the script edits the workflow and always writes it to Sorted.NWF – so that the original file is preserved should you need to revert to it.Trying to use pure xml defeated me, so I used the brute-force method of extracting the WorkflowVariables section and converting it to an xml object, sorting it and pasting it back into the workflow file.Usage:Assume the script is in

Repeating Section of Nintex Form is always a popular topic among the communities. I was trying to help a partner looking into issues he encountered implementing the solution proposed by Ayman El-Hattab​ in his great post of Displaying Repeating Section Data in List Views, The Easy Way!, if you did a quick search, you may find many other great posts such as ... Nintex Forms/Workflow - Parsing Repeating Section Data by Vadim Tabakman​