Skip to main content
Nintex Community Menu Bar

May Mission - Quick Top Tip!

  • May 1, 2017
  • 61 replies
  • 196 views

Show first post

61 replies

kelliganp
Forum|alt.badge.img+10
  • Rookie
  • May 31, 2017

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!


Forum|alt.badge.img+7
  • Novice
  • May 31, 2017

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.


Forum|alt.badge.img+7
  • Novice
  • May 31, 2017

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:


Forum|alt.badge.img+4
  • May 31, 2017

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!


Forum|alt.badge.img+16
  • June 1, 2017

Done here >>>  


Forum|alt.badge.img+11
  • June 2, 2017

‌, 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.


Forum|alt.badge.img+11
  • June 2, 2017

...and they work for SharePoint 2013.


Forum|alt.badge.img+11
  • June 2, 2017

This is also great for reducing what is logged.


Forum|alt.badge.img+4
  • Rookie
  • June 6, 2017

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


Forum|alt.badge.img+4
  • Rookie
  • June 6, 2017

Done


Forum|alt.badge.img+7

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.

‌   ‌  ‌  ‌