News and Guidelines

I recently worked on a Nintex Form and Workflow project for a large company who was made up of several smaller subsidiaries. Each subsidiary had multiple offices that were scattered across North America – for a total of 56 offices. This caused problems when trying to publish the workflow. Update (07-28-15)I got official word from Nintex support about the issue. Here is what they said."A SharePoint limitation has been hit. Workflow XAML failed validation due to the following errors: Exceeded maximum XAML element depth; maximum is 125.https://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx Under [Workflow limits] / Maximum depth of a workflow sub-step in xaml (workflow complexity).  If you were to try the same workflow in SPD the same error will occur." 

Nintex Workflow for Office 365 now offers the Filter action. The Filter Action will be a powerful addition to your workflows, allowing you to terminate a workflow if a condition is not met. For example, a car dealership wishes to tweet when a used car is delivered to their lot so their twitter followers may track any in-demand cars. A user on their mobile phone can enter the following information, where they can choose if the 'Car Type' is New or Used using Nintex Mobile. Since the user is out in the field, we want the workflow to start on new item creation, but we only want the workflow to run if the Car Type is 'Used Car'. Filter Action to the rescue!!  Let's look at how to configure the new Filter Action to terminate the workflow if the Car Type is not 'Used Car'. An expression is set to look for the value of 'Car Type' for the current item, and progress if the value of 'Car Type' equals 'Used Car'. If the car type is not 'Used Car', the workflow will terminate and a tweet will not

There are actions inside Nintex Workflow that expect a specific data type.  If you're dealing with performing mathematical or datetime calculations or comparisons, the variables or values must be in the format that are required in those actions. That is the whole purpose of the Convert Value action.  It allows you to convert values stored in Text variables into other types of variables. Imagine querying a database or a SharePoint list and getting the data back.  In some cases, data is stored as text and you want to be able to perform calculations or comparisons.  It is important that you have an action such as the Convert Value action to be able to handle this type of conversion. Even though I've mentioned numbers and datetimes above, there are other variable types the Convert Value action supports.  Specifically, converting Boolean, DateTime, Number, Integer and Guids. Below is a screenshot of a Convert Value action converting a typed in piece of text into a Boolean (Yes/No) variable.

Hi Community, i try to explain my problem and apologising for my poor english i made some screenshots, so mabee someone can understand my question. I have a library “CheckBoxTest” with 2 columns type “Yes/No” (Daten1 and Daten2): Now i created a Nintex Form with nothing than default settings:  And a Workflow returning the values of Daten1 and Daten2: As you can see i tried to insert a “Commit pending changes” action to have the value of Daten1 and Daten2 set correctly but it doesn’t work. The Return of the Uploaded File is:So it doesn’t return the check true like I set, but it returns the default value set to false. How can I get the “real” value of my Daten1 and Daten2 without using a “Pause for …” action? Someone maybe has an idea? An possibly not having to change the column type and to use the Choice Control.Thanks everyone UPDATE: Answer provided by Henning Eiben​ OK, I missed, that the workflow is starting automatically - and that it's a library and not a list. That does make a si

Another foundation level video that I created for Nintex Workflow Designer for O365.  

This is the second foundation level video that I created for Nintex Workflow Designer for O365.  

Here is the first of several foundation level videos that I created on the topic of Nintex Workflow Designer for O365.  

We at Slater Hill Inc recently came across an issue with a customer who wrote Powershell scripts to automate the deployment of a Workflow 2013 for SharePoint solution (including Site Columns, Workflows with complex Task Forms, Constants, and so on).I have read about (and experienced myself) the problem of automatically publishing a Workflow from an exported NWF file (using the Nintex workflow web service, with or without Powershell) and finding the workflow in the Unpublished state at the destination. The most common cause, according to the community, is a problem with the Columns on the List hosting the workflow.In our case, however, all of the scriptically-deployed Site Columns appeared to be in place and working fine. We opened the Workflow in the designer and went over it with a fine-toothed comb, removing suspect Actions, reimporting Task Forms from the DEV environment, fiddling with the Workflow Properties -- no luck. Trying to publish the workflow would result in the dreaded "So

As a little 'evening project' I've done some research on how to update Managed Metadata with Nintex Workflow for Office 365. There is no pre-defined action in Nintex Workflow O365 that does this. I've set a constraint for myself to do this with the SharePoint 2013 REST API, because the SharePoint SOAP Webservices are deprecated. There is a lot of information on the internet that describes part of the solution, but no overall practical guide (or at least I didn't find it). That's why I wanted to share the following practical description with the community: There are just 4 steps you need to follow: STEP 1: Add a 'Build Dictionary' action to your workflow  Configure this action as follows:  STEP 2: Add a Call HTTP-webservice Action  Configure this action as follows:  STEP 3: Add a Get an Item from a Dictionary Action  Configure this action as follows:  STEP 4: Add a Web Request action  Configure this action as follows:  Of course there are some improvements to make: for instance: you sho

So what is with the title ?? Well here in the land of droughts, floods and fire we have a popular saying “White Line Fever” now it may be used in other countries, but in context here, it is associated to someone playing sport namely AFL (Australian Rules).The way it works is, let’s say Barry is the nicest bloke around town, and wouldn’t hurt a fly and goes out of his way to help the old lady across the road.. But Barry suffers from “White Line Fever”.. Every Saturday he runs out onto the Football Oval, and as he crosses the white line into the field of play, he becomes a man possessed. The Barry that you knew during week is now null and void.. All you have a hot steaming mess hell bend on getting the football at no cost.. This is white line fever.. Now whilst it might sound like a good thing, and at times the player with white line fever can sometimes spur a team on just when they need it.. Most of the time however, they are unpredictable and normally end up on the side lines because t

We are really excited this month with a new action coming out for Nintex Workflow O365, the Query List action . You may be aware of the already existing "Office365 Query List". This new one is much more user friendly and has been designed to query the list on your current site, without having to select any user or to write any CAML Query.Let's take a first tour of the features! You will find your new action in the "Libraries and List" section of the Actions ToolPane When you drag N drop the action, you will notice that you can simply select in a list one of the list or library you want to query from your current site      (don't you feel to be like on the On-Prem version already?) Filtering. It almost looks like you are creating a Sharepoint view! You can select all or a set of items based on filters (possibility to test string with ( <, >, =, Contains (yuhu!), Begins with...).  You can even filter using an OData filter string.Sorting.How rude would it be if there weren't any sor

With the release of the Office 365 Query User Profile action, it opens up a vast array of possibilities.  One main piece of functionality that you can build in to your workflow, is the ability to get the manager of the current user.  Having said that, there are a bunch of other properties you can get which can make your workflow that much more dynamic and more powerful. Not only are there the out of the box O365 user profile properties, but you can add custom ones if you need to. For this post, I'm interested in just getting the manager, since in a lot of business processes you will be building out, the manager is the person you'll be looking to assign tasks to. Workflow Designer How It Works I've made the workflow, which in some cases would be fairly simple, a little more complicated.  That's because I want to show some other functionality also. We start off with a Query User Profile.  When a workflow starts, it's in the context of the user who caused the event that started the workfl

This is the second video that I produced to help me progress in my Nintex Forms for O365 learning journey. This video covers how to add a form to a list and provides an overview of the basic product functionality, navigation, and user interface. Hope you find it useful. Enjoy!   <-- Previous: Fundamentals of Nintex Forms for O365 Video 1 Regards,Dean Virag

It is well known  that you can use or create your own custom actions to be used on our workflows.I'll try to research about all kind of custom actions, that perhaps could useful on some of our workflows.You are free to participate on these post collaborating with this list. ULS LogDescriptionThis is a sample to create a custom action so as to log exceptions on ULS.PriceFree. Developer skills needed.Referenceshttp://sharepointracks.blogspot.com/2014/08/custom-action-con-nintex-y-sharepoint.html AutoTagDescriptionWAND, Inc., a provider of taxonomies and the DataFacet Automatic Tagging Solution for SharePoint, has announced its integration with Nintex Workflow.PriceNot Free. U$S ?Referenceshttp://idm.net.au/blog/009159-wand-adds-automatic-tagging-nintex-workflow SignaturesDescriptionCoSign connector can be used within a Nintex designer as a custom action, or as a “custom task” in a Nintex “to-do” task. Within Nintex workflows:AutoSign with CoSign and Verify with CoSign are custom actions

We often get asked this question that "How secure is my data on Nintex Mobile?" or " What kind of encryption does Nintex Mobile use?"So I thought, I create a blog post to explain data security in Nintex Mobile. In a nutshell Nintex Mobile relies on the host operating system for data encryption. That means if your OS is configured to encrypt it's storage, Nintex Mobile will respect and follow that. Normally in order to enforce data encryption on mobile platform, you have to have a pin code or password configured for your device.For iOS and Windows Phone we could enforce encryption at application level. This means your Nintex Mobile data gets encrypted as soon as the lock screen (pin/password screen) appears is encrypted until the user has put the passcode for the first time after the device has been booted. For Android this could not be achieved at application level. You either need to enforce device encryption using your MDM or to manually enable device encryption under lock screen. Th

Hi all. I am very new user to Nintex Forms and Workflows for O365. As part of my learning process I like to create videos of topics as I learn them. It helps me to master content, one small chunk at a time. I would like to share my videos with the Nintex Community. This first video is a foundation setting video on Nintex forms for O365. It is designed for users with little to no experience working with forms. It presents the terms and concepts that will be used in later videos. Let me know if there are topics you would like to see presented. Enjoy!  -- Dean   Next --> Fundamentals of Nintex Forms for O365 Video 2

Products: Nintex Workflow 2013, Nintex Workflow 2010 A request came in a few days ago for a way to programmatically toggle Nintex Features for all Site CollectionsSites that utilize Nintex Workflow in a given Web Application This PowerShell script will disable and then re-enable all Nintex Features in the WebApplication (as long as they were previously enabled). PowerShell Script Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue   $NWSiteFeature = '0561d315-d5db-4736-929e-26da142812c5' $NWWebFeature = '9bf7bf98-5660-498a-9399-bc656a61ed5d'   foreach($feature in $(Get-SPWebApplication -Identity http://contoso.com).QueryFeatures([Guid]$NWSiteFeature)){   Write-Host "Processing $($feature.Parent.Url)"   Disable-SPFeature -Url $feature.Parent.Url -Identity $NWSiteFeature -Confirm:$false   Enable-SPFeature -Url $feature.Parent.Url -Identity $NWSiteFeature   foreach ($webFeature in $feature.Parent.QueryFeatures([Guid]$NWWebF

Some users that use the International version of Nintex forms, use to show the designed form on the Nintex Form Web Part. On those cases when a user saves a form, they see the following message: "Item added succesfully" , that is not a message in their language. Here is a workaround so as to change that message: Add the next sentece on the Form settings, custom Javascript section. NWF$("span:contains('Item added successfully')").html('Vare tilføjet med succes'); 

So… virtual show of hands, who here knows what the Connection Manager is? If you do, well done! What is it?The Connection Manager is a simple way to manage connections to external providers through the Workflow Designer. The current providers we have available are:DocuSign Microsoft Dynamics CRM Salesforce Where is it found? In the Nintex Live Section of the Workflow Designer Ribbon (Nintex Workflow 2013 / Nintex Workflow 2010), you will see an icon for the Connection Manager.Why is this GOOD? Back in the day (prior to the Connection Manager), a user had to enter the account used each time they wanted to fire off an action that required some sort of authentication. (GROSS!) With Connection Manager, you can store the credentials to be used for those External Provider actions (DocuSign, CRM, Salesforce). (HOORAY!) Even Better… (this is important) When setting the Connections up, you can scope it two ways:User: Limits availability of this connection to the current user account. Site: Does

This post applies to Sharepoint 2013 on Premise and Nintex Forms. I have not tested it on another versions, but I think it‘d happen the same.Currently you can use a formula on the “Calculated Value” control available on Nintex Forms.There is a particular behavior when you compare two columns of type person. The case that works as expected  I have 2 columns of type Person named PrimaryOwner and SecondaryOwner.Both of them are equally configured. Sharepoint List ConfigurationNintex Form ConfigurationAnd then I use the control named “Calculated Value” that has a formula on a Nintex form comparing those 2 fields. The result Then I added an item on the Sharepoint List setting those 2 columns with the same user.With those values the result of the calculated value is true.So far, so good. The case that doesn’t works as expected  I have the same 2 columns of type Person named PrimaryOwner and SecondaryOwner.Both of them are NOT equally configured. The difference is that I changed the property

Wouldn't it be cool if you could dynamically have an image appear depending on the country the end user is viewing the form? I thought so, so I created this cool sample form to show what can be achieved with a little JavaScript and CSS in Nintex Forms. For this example, let's imagine that we have an office in the United States and an office in Australia (oddly enough, Nintex does!). When viewed in the United States: When viewed in Australia:  To accomplish this, I used a free geoip service and stored the output of the 'country' data to a variable. The variable would then be used to determine the appropriate CSS class to apply to the label control used to populate the image. The label control has HTML embedded to apply a ID and Class. The below JavaScript can be placed in the 'Custom JavaScript' section in Nintex Forms Settings: NWF$(document).ready(function () {     NWF$.getJSON("http://freegeoip.net/json/", function (data) {         var country = data.country_name;         var ip = da

You know that looping can be an important part of any workflow.  Getting data from a SharePoint list, web service or database needs to be parsed so you can use it in your business process.  Nintex Workflow for Office 365 has had looping actions in it since its inception.  But as we always do, we strive to make things easier for everyone.  This time, we have the For Each action. There are many reasons for how awesome this action is, but I will focus on a few of them. 1. Simple iteration through each value in a dictionary of data2. You can stop the iteration once a condition is met3. No chance of an infinite loop Note: See also “Stepping through a dictionary variable” in the help. Iterating through Data One easy way to get data iterate through, is to query a list.  In this example, I created a list called Countries. The result of the query will go into a Dictionary variable, called dictCountries.  Notice in the above image that we have a few requirements.  The Target Dictionary is the va

Disclaimer upfront, this is not an official Nintex solution and we can't take any liability when using the provided solution parts. Also, we obviously don't provide any support for it and you use it at your own risk The solution was built using SharePoint 2013, Nintex Workflow 2013 and Nintex Forms 2013. Setting the sceneEvery company has people that regularly travel. Normally there is some kind of travel request approval process involved and a submission of expenses after the trip. The aim for the solution was to provide 2 independent solutions that still allow for interaction between them. Namely converting an existing travel request into a draft expense report to minimise work required by the person who is travelling. There is 2 parts to the solution. First, we have the travel request, where an employee can go and fill in a form, it then goes through the appropriate approval channels. Secondly we have the travel and general expense approval where an employee can create an expense r

In the April '15 update to Nintex Workflow for Office 365, the Regular Expression was made available.  As a techie, I was super excited about this as I tend to use regular expressions a lot, whether I was building on-premise workflows or I was writing code.  The Regular Expression action brings you 4 pieces of important functionality. So in effect, it's 4 actions in 1.  Here are the 4 operations.ReplaceMatchSplitExtract Different business processes will require different regular expression operations. Replace When you have string of text, and there is a part or maybe multiple parts that you want to replace with something else, this is the perfect way to do it.  Once great example, is if you have some email body template that you store in a List or Library that your workflow will be using to send out an email.  The template can have some tokens in it, that you can then use the Regular Expression action, to dynamically replaces those tokens at runtime, with real values. We'll start off w

Welcoming Switch to the O365 action family. Another logic action has been added with the latest release of Nintex Workflow for O365. The Switch action. I am sure many of you have used it on-prem in the past, but for those who are new to the Switch action, let me explain what it is and why you should use it. What is it?The Switch value is a logic action that allows you to evaluate the value of a workflow variable and perform business logic that is specific to the value of the variable. It looks like a Parallel Block action but only one branch will be processed, rather than all of them.  What is it good for?So, why would you use the Switch Action, you ask? You can already evaluate workflow variables and item properties with other actions like the Conditional Branch action. Well, let me give you three good reasons why to use the Switch action. Flatten your workflow designSometimes, when you evaluate a workflow variable, you might get more than 2 outcomes. Using the Conditional Branch acti