Skip to main content

Following on from the success of January 2017 Mission‌ "What is your Nintex New Years Resolution", which was all about what bad habits you have when using Nintex that you would like to dispel of, we have created a positive spin in this months mission!

 

So what do you have to do to get the loot?  Simple really, share your quick top tip for any of the products in the Nintex suite, easy right?! 

 

top tip may

A simple couple of lines as a comment below about your top tip will do the job.  For your trouble, you pick up the badge pictured, and 100 points!

 

Why are we doing this?  In the hope that your top tip might be something that users in the community have never even heard about - and imagine if you could save them time and less headaches by simply sharing yours...

 

 

 

Here is mine:  Use the "Log in history list" action.  Simple enough I know, but for the first eight months of developing workflows I didn't know it was there and I used to bombard myself with emails trying to debug my workflow and get the values from my variables!

Thanks ‌! I love the use of Workflow constants, and particularly the "Credential" type. For each of my site collections, I get a Generic Service Account created and load it into the manage workflow constants at the site collection level and since a GSA in our company has annual password resets so I do not have to manage so frequently.

Great tip!


As a addition to the tip of Enrico Knapp‌ - I would put the descriptive text in the top, and move the OOTB label to the bottom. The top-label will be used in the workflow details, and instead of a dozen "Update item" entries, this would be much cleaner to view.


Enable verbose logging in dev-environments!

As an alternative to using "log in history list", you can also leverage the power of verbose logging! I have this enabled in the central administration on my dev-environments and disabled in CA in production. This way I can leave the setting enabled in the workflow, and since it's disabled in CA in production it wont to any harm!

Instead of writing out all potentially interesting variables and settings - just have them at your fingertips:


My top tip is using Commit Pending Changes to execute batched operations! This little gem of a post saved my 2013 butt more than once >>>> Designing your Workflow - Commit Pending Changes Action NW2010 & NW2013

Shout out to ‌ for the post!


Done here >>>  


‌, you didn't know the Log History was there? That is the best troubleshooter we have out there. I really wish they'd add more actions for testing.


...and they work for SharePoint 2013.


This is also great for reducing what is logged.


Yeah, I'm following same practice for my nintex workflow. It would easy to track the workflow history.


Done


We used these Top Tips to build out content of the last Nintex User Group - UK‌ meetup, and it was a great exercise for everyone to discuss and debate some points, thank you so much to the community. 

Here is the slides where we collated most of the points above (in sway):  Nintex Community Top Tips - from May Mission  

You may wish to re-use it for your teams.

‌   ‌  ‌  ‌  


Reply