News and Guidelines

Part 1 - Overview Part 2 - Accessing Your Tenant Part 3 - Users and Roles Part 4 - Adding Custom Connectors Part 5 - Building a Workflow Part 6 - Additional Resources Prepare for SuccessYou must use a work email for this step (a non-gmail, hotmail, yahoo, or outlook.com email) The email used to create the tenant will be the Nintex Workflow Cloud tenant admin once the setup is complete Setting Up Your TenantAfter you fill out the trial form, Nintex provisions your Nintex Workflow Cloud tenant and sends you two emailThe first email will ask you to create a password to access your tenant The second email will let you know the URL for your new Nintex Workflow Cloud tenant First Sign-InUse the URL from the second email to sign-in to your tenant with the password that you created with the first email  Check for SuccessDo you have access to your Nintex Workflow Cloud tenant?   Previous Step Next Step Nintex Workflow Cloud - Part 1 - Overview Nintex Workflow Cloud - Part 3 - Us

Part 1 - Overview Part 2 - Accessing Your Tenant Part 3 - Users and Roles Part 4 - Adding Custom Connectors Part 5 - Building a Workflow Part 6 - Additional Resources OverviewNintex Workflow Cloud empowers anyone in your organization to unlock the transformational business benefits of human-centric workflow automation. Using just clicks—not code—you can easily extend and connect the content repositories and systems of record your business runs on with the people who make the decisions your business relies on to succeed. As your business evolves, Nintex Workflow Cloud gives you the visibility and process intelligence to take control of your workflow challenges—no matter how sophisticated—allowing you to move faster, do more, and achieve better results by making work, less work.   Current Step Next Step Nintex Workflow Cloud - Part 1 - Overview  Nintex Workflow Cloud - Part 2 - Accessing Your Tenant 

Part 1 - Overview  Part 2 - Installing the Apps  Part 3 - Building Your First Workflow  Part 4 - Working With Forms  Part 5 - Additional Resources Continue the Nintex Journey Nintex Learning Center Recommended CoursesThe Nintex Learning Central provides users with a self-service, on-demand learning environment to help users get the most out of the Nintex Platform. Here are some recommended courses for those learning to use Nintex for Office 365:Introduction to Nintex Learn the basics of the Nintex Platform. You'll also learn the basic capabilities that serve as the building blocks for solutions in Nintex for SharePoint, Nintex for Office 365, and Nintex Workflow Cloud. Nintex for Office 365 - Basic Learn the basic features and functions of Nintex for O365. You will learn how to use entry-level Nintex Workflow actions and Nintex Forms controls to build basic solutions that address real world business problems.  >>Visit Nintex Learning CentralNintex Customer CentralProvid

Part 1 - Overview  Part 2 - Installing the Apps  Part 3 - Building Your First Workflow  Part 4 - Working With Forms  Part 5 - Additional Resources Prepare for SuccessYou must have at least the following permissions to complete this step:Full Control on the List Contribute on the Site Read on the Site Collection For more information, see Understanding Permission Levels in SharePoint. Making a Simple FormLet’s build a Nintex Form which sits on and populates a SharePoint list. We’re going to create a Customer Evidence Nomination Submission form. You will need to create a custom SharePoint list for this form to sit on with the following fields:Account Management Name: Single line of text Company Name: Single line of text Products: Choice – Checkbox, with the following fields:  Nintex Forms for Office 365 Nintex Workflow for Office 365 Nintex Live Nintex Mobile Additional Details: Multiple lines of text Type of Customer Evidence: Choice – Checkbox, with the following fields: Ca

Part 1 - Overview  Part 2 - Installing the Apps  Part 3 - Building Your First Workflow  Part 4 - Working With Forms  Part 5 - Additional Resources Prepare for SuccessYou must have at least the following permissions to complete this step: Full Control on the List Contribute on the Site Read on the Site Collection For more information, see Understanding permission levels in SharePoint.  Building an Approval WorkflowAccessing the designerNow that you know what permissions users need to build and use workflows, let's get a feel for how to access the Nintex Workflow Designer, and see exactly how easy it is to build your first workflow.From your Site Contents, create a new Document Library.Click on the Library tab, and select Nintex Workflow in the Ribbon to open the Nintex Workflow designer. On the Workflow Gallery page, click New list workflow. Adding an Assign a task actionThe first workflow action you use is the Assign a task action. In an approval workflow, this action assign

Part 1 - Overview  Part 2 - Installing the Apps  Part 3 - Building Your First Workflow  Part 4 - Working With Forms  Part 5 - Additional Resources Prepare for SuccessYou must have at least the following permissions to complete this step: Site Collection Administrator Note: If you do not have Site Collection Administrator permissions, please have your Site Collection Administrator perform the steps below before moving to Step 3.Adding the Nintex for Office 365 Apps Find apps in the SharePoint  StoreYou can install the Nintex Workflow and Nintex Forms for Office 365 apps from the SharePoint Store.  Access the SharePoint Store:Navigate to your Site Contents and select add an app. Select the SharePoint Store link (from the left-hand menu). In the store, type "Nintex" into the search box at the top right-hand corner of the page. This finds both the Nintex Workflow and Nintex Forms for Office 365 apps. These apps can be added to the site in any order, as there is no dependency betwe

Part 1 - Overview- Part 2 - Installing the Apps  Part 3 - Building Your First Workflow  Part 4 - Working With Forms  Part 5 - Additional Resources  OverviewNintex for Office 365 empowers your team to automate their own processes through intuitive, browser-based, drag-and-drop workflow and forms designers built for the Office 365 platform. Build workflows and forms that connect and interact with your existing Office 365 applications. Integrate your workflows with cloud services such as Adobe Sign, DocuSign, Dropbox, Yammer, and Twitter. Surface your processes through powerful forms that are available wherever you work, whether through the web or a mobile device. Build forms in Office 365 without code, customizing branding and presentation logic and connecting the forms with your workflows. Pre-requisitesYou will need an Office 365 subscription that includes SharePoint Online, and supports the SharePoint Online App Model, as well as Workflow Manager. All of the Office 365 Busine

I wanted to be able to do a Group Count on a set of items in a library (I actually wanted to save the values and counts to a list so that I could attach a chart control – but that’s another story).There is no way of doing a Group By in the Query List task, so I had to come up with this.Retrieve all my key values into a collection, then create a list of those unique key valuesIterate through the unique values and remove them from the original list – the number of items matching the key value is the number of items removed from the collection – the difference between the counts before and after the deletion.In pseudocode, the process is thisQueryList : get all ‘key values’ in range into collection AllKeysCollection: Remove duplicates from AllKeys into collection UniqueKeysForEach string Key in UniqueKeysCollection: Count AllKeys into number TotalCollection: Remove by value Key from AllKeysCollection: Count AllKeys into number CountMath: Total – Count into number KeyCount{do something wit

OFFICE 365 Recently, I had the need to hide/show panels based on a value or values of a choice control. Online I saw multiple posts on how to accomplish this using simple rules; however, they did not explain how this would affect the user when accessing the form in read-only. For this post, I'll be referring to the following setup:A choice control with three options: Panel A, Panel B, and Panel C Three panels, each corresponding to the options listed on the choice controlThe expected behavior is as follows:A user sees only sees the panels the correspond to the options selected in the choice control. When the recipient or user opens the form in read only, he/she should see the panels that were selected in the choice controlSolution 1:Create three formatting rules, one for each panel. The formula is as follows: Choice != 'Panel A'. Lastly, the Hide checkbox should be checked.ISSUE: When selecting only one of the options from the choice control, the rules work as expected; however, if the

This works with on-prem Nintex Workflow 2013Problem:  Upon archiving a document I use workflow to update the date/time field of when the archive happened.  When user wants to un-archive the document, I need to clear the date field to display as empty (or null). Resolution: Create variable vDateArchivedDate as Date and Time with blank default date Use Convert value action input "1/1/0001" and store in variable vDateArchivedDate Use Set field value to update the date column with workflow data > vDateArchivedDate

Recently I needed to create a schedule of dates, one week apart. I created a loop and added 7 days in each iteration. I noticed it took a very long time, so I added a Log in History task in the loop and saw that each iteration was taking 5 minutes. I realized that this was down to ‘Safe Looping’.This protective feature places some safety measures against the hazards of an infinite loop by adding a hidden delay..I didn’t want to disable this option, mainly because of the maintenance overhead involved, so I looked for another option.I realised that the Collection iteration (For Each) didn’t have any such restriction, so all I needed was to create a collection with the number of entries that I wanted to loop for.The Regular Expression task with the Split operator is the easiest way to create a collection; it simply splits text based on a character. All I had to do was to create a string with the right number of delimiters.This is where I got the idea for this article https://community.nin

The action Assign Flexi Task is under development for O365.Recently, the Task Outcome for Assign a Task was released.The Delegation of a Task becomes then more intuitive.Here is how I have implemented it. 1. Let's create a new Site column for the Task Outcome.Go to Site Settings of your Site Collection and under Web Designer Galleries, click Site columnsClick Create and name it like you wish. I have name it Task Outcome Approve.For The type of information, tick Task Outcome.For Group, the best practice is to create a New group to store your customized columns. I have name it My Company.For Type each choice on a separate line: addApprovedRejectedDelegatedRemove the Default valueClick OK 2. Add a new Site column DelegatedTo to the Workflow Approve content type.In my case, I have create a column of type Person or Group but it can be a lookup column from a list containing the names of the PersonFor Group, select the Group you justhave created.Click OK 3. Create a new Site Content Type.Go t

Applies to: Nintex Workflow and Nintex Forms for SharePoint 2016, 2013, and 2010 Note: The Nintex external platform includes the following external services: Nintex Live (connector actions), external forms (live forms), Document Generation, and External Start. OverviewIf you are running a previous version of Nintex Workflow for SharePoint, and are not yet ready to upgrade your installation to the latest product version, you can install the latest SSL certificates for the Nintex external platform using one of the following methods:Method 1: Automatically install the new certificates by running a script on the Central Administration server. Method 2: Manually download the certificates from the Digicert website, then upload and install each certificate in Central Administration.  This article describes both methods. PrerequisitesEnsure that you have a version of Nintex Workflow or Nintex Forms for SharePoint installed older than:Nintex for SharePoint 2016, version 4.3.3.0Nintex Workflow f

Dear all:I have been very confused about this topic for months:How to navigate from a parent form to child form and come back? How to navigate from a child form to a new one child form keeping the parent link? How to validate child form data before come back in both cases?I think I have now a good approach to do it without javascript.  How buttons workFirst of all, I would like to describe how buttons are working under my understanding, in the case of validation and redirection:Save and submit button / Save button:Both buttons have redirection parameter. You can build the URL dynamically, using a list field value and run-time functions. You can't use calculated fields or control values, this is a very important point.In the case of validation, both buttons can validate data, including list required fields and validation rules in the form. Save and continue button:Save and continue button hasn't redirection parameter. After saving data, the action is refresh page and you are in the same

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 Forms. Though the idea of parsing data taken from his post, I wrote the workflow steps in little different way to not to use the loop action instead stick to for each action due to loop action being dependent on turning off safe looping setting which I personally dislike taking that setting

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 | 2013 | 2010). For more information about the evaluation process that Nintex Workflow uses for content types, see the following MSDN article: http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.spcontenttypecollection.bestmatch

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)  Under the Formula Builder we choose “dateDiffDays” under the Runtime Functions tab and “Current Date” under the Common Tab. The “StartDate” is located under Named Controls tab and will vary depending on what column you are referencing in your list.Step 3:Select the “End Date” control and cli

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 update information:Microsoft .Net 3.5 Information.Microsoft .Net 4.X.X information.

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 have a manager people picker field with a Client ID JavaScript variable name of varLineManager Add this code to the custom JavaScript section of form settingsNWF.FormFiller.Events.RegisterAfte

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 find the hidden taxonomy list, simply use "Lists/TaxonomyHiddenList/AllItems.aspx"

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 Add an app. 

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 control and added a List Lookup control with the following settings:Next, we are going to use the output of our List Lookup control ("Ite

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 and in case it's "check" does not happen in the

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 a workflow from SharePoint as a workflow file.To export a list workflow you will need to have the following pieces of info:Source site URL Workflow name Filename and path where you would like to save t

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 Deactivated External Settings from Nintex Administration Activated External Settings from Nintex Administration Turned on all Nintex actions IISRESET on all SharePoint Server.Now you will see all Nintex Timer jobs are running. Support‌Nintex for SharePoint‌ #Nintex2016