News

Installation process:No Problems at all. Easy peasy lemon squeezy. Activation:We are used to that.Had to activate all workflow Actions. They all were disabled first.There won't be a Workgroup Edition I heard. Is it still necessary to activate the site Feature then? New Action design:Fancy lookI am glad you did not rename them so I still find them using the search box.Will there be one design for the same Actions across all platforms? (<SP2016, SP2016, O365) Webparts:I am glad, Nintex Forms and Workflow Webparts still will be available. Nice!  Overall:Good, stable, solid Impressi

Hi Nintex Community, Today's SDK update contains a short sample that uses a C# console application for updating your Form XML with Xpath.  Using this technique you can update a bunch of forms all at once. Since the forms are in XML, you can update the values of elements such as image URLs, label text, CSS, and so on.     In working with the Nintex Form XML I ran into two tricky issues. The first is that the XML uses a multiple of namespaces within in the same file. Namespaces are one of the more, to me at least, painful things to deal with in writing Xpath queries. Luckily, the .

To followup with further functionality from Using the Format this Value Feature , on-premise formatting of dates can be accomplished within actions on the fly. In the previous post we see how we can specify a return value for Person or Group values from fields or variables. Here I wanted to quickly show that this is also available for Date fields and variables as well. In this example I am using a Set Variable action to set a Single Line of Text variable the value of a DateTime workflow variable. By selecting the ellipsis to the right of the variable drop down I can then specify the return type to save to the text variable. The available options are As String, ISO Formatted, Long Date, Long Time, Short Date, and Short Time. 

Well I just rolled back an old Alpha that was incomplete and have installed the beta.. So far so good.. Easy install, activation etc.. Pretty happy so far. Firstly, everything Nintex all in the 1 spot... awesome..New Help feature, to help documentation up to dateIf you get lost here (as I did), you'll find safe looping under 'Security'I imported over a form directly from 2013.. Perfect, and look no Nintex Live Forms.. Just External Forms..  Over

Some it's needed to cut the file extension from a file name.Here are 2 steps to do it.We 'll use the actions named:Regular Expression Get Item From Collection Log To History List ( to show results )   Used Variables     Use the following variables for this sample  Action 1 - Regular Expression Action Configuration Set the String attribute with your filename. In my sample I am getting it from a Sharepoint Column name named "ItemwithExtension"Then set the String operation to "Extract" The pattern used is [^/]*(?=.[^.]+($|?)) with ignore case checkedFinally set a collection variable ( varWi

Hi Nintex Community,       Today's SDK update contains a sample for adding a custom inline function to your Nintex Forms. You can use the Nintex PowerShell cmdlets (via  SharePoint 2013 Management Shell) to add, manage, and review custom inline functions for your forms. The update also contains reference topics for the Nintex Forms Po

Hi Friends,This is a strange problem that I have solved. Observation is required till now.Problem:In my current project I have to develop a User Approval workflow with Reviewer Approval in parallel. For reviewer level I don't have any problem but the problem starts when I tried to implement User Level workflow where it's a State Machine flow with 10 states. Now due to byte constraint i.e. of workflow size I need to break that user level workflow in two sections. And the second part of Level workflow(say Level2) will be kicked off only after a column is modified into the current list by Level user first workflow(say Level 1). Actual problem starts from here. I found that Level2 workflow sometime getting kicked off and sometime not after Level1 workflow. Very strange and really the situation becomes unpredictable. Solution:I keep on thinking why its happening and then went to Mother workflow template and re-ar

DISCLAIMER/WARNING: Running this, or any derived "fix" workflow on every item in a large list will be a significant load on your environment. When extending or modifying this workflow for your list, consider batching your "fixes" or putting looping logic in the existing workflow such that it will process every item in your list in order. Also: always remember to test your workflow and keep backups of data! I ran across an interesting situation in the course of my casework and made a fix that I felt might help others as well. ProblemI've got Cascading drop downs set up in Nintex Forms, but there was a small problem where the columns (configured as "Single Line of Text") type fields are "disconnected" from the Form in that editing the data outside of Forms doesn't reflect in the Form!Alternate problem that brought you hereI made text c

Hi Nintex Community,Today I am posting reference topics about the Nintex Forms On Prem 2013 Web Services API endpoints as well as a code sample that contains a WCF client and a console application.Earlier today I also posted a blog post that contains a somewhat informal walk through of implementing a nearly bare-bones custom control using the Nintex.Forms.Sdk assembly. For the discussion, I implemented the <input type="color"> control. The control is based

Hi Nintex Community,I'm a new(ish) programmer/writer at Nintex. Well, I'm not so new, but I still have bubble wrap clinging to my legs. I'm working with Dennis Kennedy to write developer-focused content and code samples. My focus is everything Forms. I'll be posting new material for Nintex Forms On Premises 2013 over the next month or so. Much like the work Dennis did, I'll be regularly expanding the material in the Forms portion of the SDK.To introduce myself, I've been a technical writer for the last fifteen years. I've documented ultrasound machines, the Microsoft Kinect SDK, the back end infrastructure of eCommerce sites, and the web services that connect wrist bands worn at a certain popular park to an array of services that provide everything from banking and to access to hotel room accommodations. I'm from the Pacific Northwest in North America, and have been lost in the woods more than a few times. I also have a sick fascinat

For two different projects this week, i have faced the same case about document generation.The goal wass to generate a document using the document generation feature including a lot of variables. Obviously the first thought for my customer was to one workflow variable per variable he wanted to display in the document (Because the Document generation feature can only display workflow variables). Obviously he had 20 "set variables value" actions before his document generation that were only used for that! The best approach, in fact, is to create a dictionnary, and to set each variables as an entry:You only consume one action "generate dictionnary" The designe is much simpler! What happens when you are back to Word? Your dictionnary variable will appear as a normal variable, and when you select it, you will have to e

I had a requirement whereby no users would have access to input into a list in SharePoint, but that my workflow needed to create an item in it.  Perfect for using a web service call with a service account I thought!I created a service account and added the credentials into my workflow constants for the site.To start with in my workflow I created a build string action to create the XML to pass into the web service call:Originally I only needed to add text fields in to the list, so I hooked up my web service call as follows:Call web service action URL = Web URL/_vti_bin/lists.asmx Username and password = managed credentials input earlier of the service account web method = UpdateListItems Editor mode = SOAP builder listName (string) = Requests updates (xml) = vMTextBatchXML (the XML we created earlier)

For any form or workflow logic around user filtering and person or group value matching you will eventually run into working with the SharePoint claim. The actual value of the user within SharePoint. So as I respond to those posts I came across two blogs that explain what the formatting actually means for the claims and why i:0#.w|domainuser is used. I hadn't seen these before and I thought it to be helpful to post the explanation here to help others. Joe Davies​Wictor Wilen​ SharePoint 2013 and SharePoint 2010 display identity claims with the following encoding format:<IdentityClaim>:0<ClaimType><ClaimV

In Nintex Workflow for Office 365, use dictionary variables for the “Field names” and “Field values” selections shown in the action configuration settings dialog box for DocuSign Populate Template.   When building dictionaries for names and values, key each dictionary identically; that is, use the key of the name (first dictionary) for the corresponding key of the value (second dictionary). In the example dictionaries below, the key “(0)” is used for both “Date Applicable” (FieldNames dictionary) and {Current Item:Modified}‍ (FieldValues dictionary). 

All hail the Manager functionality in Nintex Workflow for Office 365.  As with most of you, you're probably excited as I am about this little nugget.  Although there was a work around, using the Query User Profile action, this release now gives us 3 workflow context properties about the initiators manager, that will make life so much easier.  the Query User Profile is still useful, in that you can get the manager of other users, but if you want to deal with the initiators manager, which is most workflows, then these properties are perfect. Here are the three properties:Manager login nameManager display nameManager email address First of all, in order to get this to work, you will need to request your system administrator to grant Nintex Workflow access to the User Profiles (this only needs to be done once per site, then it'll be in effect for all workflows created on the site thereafter -

I had a co-worker ask if it was possible to restrict list file attachments to just PDF files. After a quick review of the attachment settings in Nintex Forms Designer O365 I was pleased to report the answer as Yes, and so much more! Here is what I discovered about the Nintex Forms file attachment validation settings. Below are the default settings of the attachment validation section. Minimum AttachmentsUse the Minimum attachments field to specify whether a file attachment is required or not. A value of 0 in the field indicates that file attachments are not required. A value of 1 or more indicates that an attachment is required. Note: Nintex Forms will automatically add the red asterisk (*) to the label when the value of the Minimum attachm

The principle of Continuity states once the eye begins to follow something, it will continue traveling in that direction until it encounters another object.A good example is a line with an arrow at the end of it. The symbol indicates that the user should follow the line and see where the arrow is pointing. The pointing finger also provides the same functionality. See Figure 1 below.Figure 1: Symbols to direct the user's eye toward an object. The Grid LayoutOne of the most common examples of continuity in form design is the grid layout. Grids are most useful in bringing order to a layout, but also useful in indicating context. (Source: Andy Rutlage – Gestalt Principles). Question:  What are you left with when you open a form in Nintex Form designer and clear all of its contents?Answer: A grid.

I have a customer that wanted to use a Nintex form on his mobile device(s) to capture and annotate photos and then add them to a SharePoint list along with information about the photos such as location taken, notes, etc. The customer owns a Samsung Galaxy S6 Edge phone and a Microsoft Surface Pro 4 running Windows 10. So, I created a Nintex form that accepts attachments and published it to the Desktop layout, the Nintex Mobile Phone layout, and the Nintex Mobile Tablet layout. I then downloaded and installed the Nintex Mobile App on a Samsung Galaxy S6 Edge and a Microsoft Surface Pro 4 tablet to test. After a bit of configuring, I was able to access the mobile form from both devices. During testing I was disappointed to discover that the attachment functionality works differently on each device. Nintex Mobile Phone LayoutThe attachment functionality on the Nintex Mobile Phone app worked exactly as I was hoping.

This is the third post in my series about the Gestalt Principles as relates to form design. In this post I talk about the Gestalt Principle of Similarity. Of all the Gestalt principles, the principle of similarity is probably the easiest to understand. It states that elements within an assortment of objects are perceptually grouped together if they are similar to each other. To put it in simpler terms, things that are similar are perceived to be more related than those that are dissimilar. Think Twins!!I am an identical twin, so I completely understand this principle as I have been living it all my life. The most memorable question ever asked of my brother and me was “Are you all twins or brothers?” Our answer was always “Yes.” As Figure 1 shows, similarity can occur in the form of size, color, shape, shading or other qualities.

Better to use a "for each" loop when Possible. You might be thinking that you need to use a Loop because you're not certain of the number of executions.  You may have a better idea than you think of the number of executions something will take . I will present an example of a Parent/Child Process that utilizes a State Machine to illustrate this in another article. After some bad examples of Safe Looping Executions times, I determined there had to be a better way.  In a large facility, I wouldn't want to disable Safe Looping because Nintex will be used by a large range of users with different skill levels.  In short, I want the safety provision provided by Safe Looping for the general user population. Infinite Loops can bring a machine to its knees. I began playing with the "for each" loop for a particular application that I had of creating 30 list records. Since I knew I needed to loop 30 times, I added 30 Numbers to a dummy list.  (The list

I recently posted about the Nintex Workflow DocuSign Connector. The post was targeted at using document templates that live at DocuSign, where Nintex Workflow passes in details to fill in fields in the template, before the document is sent to a user for signing. In some cases, you may already have documents that require signing.  These documents don't live at DocuSign, but instead, live in a Document Library in SharePoint.  In this situation, how would you build a workflow that makes it easy to send out the document for signing?  This is topic of this post.  Adhoc Document Signing.  The ability to select a document, start a workflow on it, and send it to a user to get signed. I‌ntroducing the DocuSign Send Document Action Rather than using the DocuSign Populate Template action, here we will focus on just th

Hi Folks, Are you a veteran (or active duty)?  Want some top notch free online IT training?Lynda.com, a LinkedIn company, is a leading online learning company that helps anyone learn business, software, technology and creative skills to achieve personal and professional goals. I personally have used Lynda.com for years and it is some of the best training content I have ever found. If you are a veteran, Lynda.com is offering 1 YEAR of free access to their library. It is an enormous catalog of training content. This is an amazing offer and I hope that many folks here at Nintex Connect take advantage of it.To get access, go to the following link: https://veterans.linkedin.com/These folks have great SharePoint training in their library. If you are self taught, this is a great opportunity to fill in any knowledge holes!

Found this picture I took at InspireX and shared with my team and wanted to share it with you! I recently started to expand our training to involve our Business Analysts so that they can assist in getting other areas on board with Nintex. I use this image (and phrase) throughout as it drives home the idea that Nintex does not require you to be a technical savant and code solutions.  It empowers users to see and hear this as it removes the notions that it is too complex or difficult to do themselves, and once they see how easy it is to demo, that is when I see all the gears starting to move about their ideas and what they want to automate!  So what else do you guys use in your trainings? I am putting together a training packet and will most likely share it once I have it completed to get some feedback!

1. March Mission - Scavenger Hunt!https://community.nintex.com/message/33821#comment-33821https://community.nintex.com/message/33805#comment-33805 2. Mohamed Gathoo, Eric Rhodes, Mike M, Vadim Tabakman, Palesa Sikwane, Andrew Beals,

This is the second post in my series about the Gestalt Principles as relates to form design. The introductory post can be found here​. In this post I talk about the Gestalt Principle of Proximity. Proximity is all about whitespace - the area of blank canvas between objects. To me, whitespace is one of the most important elements of good form design, as the good use of whitespace makes a form look clean and easy to use. Principle of ProximityThe principle of Proximity states that when an individual perceives an assortment of objects they perceive objects that are close to each other as forming a group. In Figure 1 below, the stars on the left are grouped closer together horizontally, so we tend to first see them grouped as rows. While the stars on the right are closer together vertically,