Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Top 5 mistakes people made with Nintex Workflows in 2014

If you're like me, and enjoy working with others, then Nintex is one of the best tools to use for organizations using SharePoint. After a fantastic year with several clients, I decided to go back through my projects and help tickets to see what were the top five things I saw being used incorrectly with Nintex. It i definitely not comprehensive, but it can help shed light on things you should probably avoid if at all possible when build or using Nintex Workflows.

Oh and because this is not comprehensive, share things you've seen and maybe we can build an even bigger list for people to avoid in 2015 (yes this is repeated in the presentation for emphasis).

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

Top 5 mistakes people made with Nintex Workflows in 2014

  1. 1. Top 5 Nintex Workflow Mistakes Users Made in 2014 …and you don’t need to be a doctor to avoid these! 1/8/2015@eharris04 This was put together by Eric Harris a SharePoint Consultant & Business Analyst Follow Me: @eharris04 | LinkedIn Profile | eharris04@hotmail.com
  2. 2. Eric Harris SharePoint Consultant & Business Analyst Connect with me: @eharris04 | LinkedIn Profile | eharris04@hotmail.com Instead of trying to figure out the top things that you could do right with Nintex and SharePoint, why not with some humor see the top 5 things that you should avoid. Its always good to learn from others mistakes, but repeating them is just shameful and worth noting. Well, that is if you care to not troubleshoot it later . About me: I’ve been doing workflows and Nintex since its conception and over the years have become fond of such a critical business tool that has revolutionized how users build workflows. But enough about me…on to the top 5..
  3. 3. #5 – Repeat that… Problem: Because Nintex is so easy to use, anyone with access and the right permissions can start with no formal training. The problem is that unless people think about it from some form of development, they will find a certain way of doing things and repeat that for everything else. Those repetitive patterns may be good for a few things, but over time, can become detrimental by using an action incorrectly or rather just the wrong way. How to avoid this? • Properly understanding the actions you are using • Identify the real problem you are trying to solve or the process you are trying to automate. • Know that not every solution is made for every problem. 1/8/2015@eharris04 | eharris04@hotmail.com
  4. 4. #4 – Have it your way Problem: I have seen users not understand the kickoff or starter actions and that results in a workflow running at the wrong time or running every time an item changes which can drastically bloat the workflow history database. Its not always good to give your users a workflow their way. It can lead to, well the picture sums it up. I’m sure Burger King meant to tell consumers something different…But!!!! It is helpful to plan the kickoff of a workflow just as much as planning what the workflow will do when running. Tip: Remember to walk through your own logic after you create your workflow. Ask questions such as “how many times will this run?” and “how many items will this run for?”. 1/8/2015@eharris04 | eharris04@hotmail.com
  5. 5. #3 – Hmm… Spam! Problem: I can not count the number of workflows I have seen created to simply send an emails to people. While this is indeed something that workflows can do, people should be careful how many alerts, emails or notifications are being sent at the time intervals. Not only can you clutter your Exchange Server, but there is such a thing as “spamming your users”. Tip: Before designing a workflow to just shoot an email to someone, seriously consider if you can utilize built in alerts for the list, library or item. If that doesn’t cut it, see if the native “three state” workflow or approval workflows can be used. SharePoint has built in functions to do basic things like alerts, so take a look at the wheel before you attempt to rebuild one. 1/8/2015@eharris04 | eharris04@hotmail.com
  6. 6. #2 – To infinity and beyond Problem: A loop within a loop is usually not a good thing. Sometimes it might be necessary to loop and do a separate loop for a shorter function, but this should be an exception, not the norm. Tip: If you ever feel that you need to use loops, write out your logic on a white board and map it out as a flow chart and have someone else walk through the logic with you. Also look at putting in logic to stop the loop or jump out of it. This could save you time and prevent you from creating a workflow that crashes your SharePoint site/farm. 1/8/2015@eharris04 | eharris04@hotmail.com
  7. 7. #1 – Hoarding… Problem: This is number 1 because it has the must unforeseen impact on SharePoint. When users use the simple action of “Log to workflow history”, they do not understand that they are creating a copy of the information stored within the database itself. While this is not terrible, I have seen a single workflow with multiple loops and over 15 different steps being logged for error checking using log to workflow history. That logging inevitably wrote over 67,000 items to the database every time it ran (no exaggeration). Tip: Planning is the best thing. If you do use ‘log to workflow history”, just be sure to remove or disable it before allowing the workflow to run in a production state. Also use the built in “Purge Workflow History” feature to trim down your database after you’ve developed a workflow. That’s just a good practice overall. 1/8/2015@eharris04 | eharris04@hotmail.com
  8. 8. The End So sad that its over, but don’t repeat it without leaving a comment with things you've seen and maybe we can build an even bigger list for people to avoid for 2015!

    Be the first to comment

    Login to see the comments

  • rickgsmith66

    Aug. 26, 2015
  • LynneMesulam

    May. 4, 2020

If you're like me, and enjoy working with others, then Nintex is one of the best tools to use for organizations using SharePoint. After a fantastic year with several clients, I decided to go back through my projects and help tickets to see what were the top five things I saw being used incorrectly with Nintex. It i definitely not comprehensive, but it can help shed light on things you should probably avoid if at all possible when build or using Nintex Workflows. Oh and because this is not comprehensive, share things you've seen and maybe we can build an even bigger list for people to avoid in 2015 (yes this is repeated in the presentation for emphasis).

Views

Total views

7,768

On Slideshare

0

From embeds

0

Number of embeds

51

Actions

Downloads

0

Shares

0

Comments

0

Likes

2

×