News and Guidelines

For users of the Salesforce echo system, there are often scenarios where data is required to complete a process within a Salesforce app. Whether it’s Sales Cloud, Service Cloud, CPQ or a third-party application, this need continuously pops-up and can halt a process. The problem is, ideal providers of this data are often non-salesforce users. A manual process often is created to request the data from a non-salesforce user, provide them to a salesforce user and then enter the data manually into Salesforce. The manual process could be in the form of emails back-and-forth, a portal (which is costly), or God forbid…. pen and paper! In the day-and-age of automation, it is assumed that there should be some way of streamlining such a process. Well, there is…… In comes Nintex Workflows. Nintex provides an inherent custom e-form capability within it’s workflow platform that can help with this pain-point in a cost-effective manner. These e-forms are drag-and-drop configu

The reason I'm writing this is to start addressing a challenge that Cassy Freeman posted in response to my video stating I'll try and help any Nintex customer do more with the platform.  View those videos here - https://www.linkedin.com/in/eharris04/detail/recent-activity/shares/   While this is a challenge for sure, I think I can tackle it in pieces to help everyone out and make some progress. The first thing I did was take a look at what I thought were the most common actions being used in on-premises. This is 100% my opinion so take it for what its worth, but here is the list of actions I chose starting out and some notes about them. On-Premise Action Name

With the multitude of updates that have come out of product teams this month, I thought it prudent that Nintex Mobile have a say in there as well.. Now there are a few updates for the Mobile clients this month, but the one I'm going to focus on, is one that I have been a big supporter of for some time, and I'm super excited about it.. For a long time, I've been saying, wouldn't it be great if you could track your assets with Nintex Mobile.. You go to all the trouble of putting barcode's on everything, but then you either have to buy a fit for purpose device to read those barcode but then what ?? so lets put this in the picture.. Your the IT goto person on the floor. You have been called out to a customers / users PC.. Firstly you want to get the info of this PC.. How much RAM, processor, owner, software installed etc.. Each asset has a barcode, which has been registered with the companies Service Catalog (One would hope

Products: Nintex Workflow 2013, Nintex Workflow 2010 A common request we see is "How do I cancel/terminate a group of site workflows that are in a state of 'Error Occurred'?" This article provides instructions on how to accomplish this. Run the below (attached as well as a *.txt file for your convenience) PowerShell script (PowerShell ISE works well) from a SharePoint Server: PowerShell Script Add-PSSnapin Microsoft.SharePoint.Powershell -ErrorAction SilentlyContinue function Cancel-SPWorkflow(){ PARAM ( [Parameter(ValueFromPipeline=$true)] [Microsoft.SharePoint.Workflow.SPWorkflow] $SPWorkflow ) BEGIN {   } END { } PROCESS {         [Microsoft.SharePoint.Workflow.SPWorkflowManager]::CancelWorkflow($SPworkflow)

If you notice a broken link on the community but found it from Google or from a bookmark, please do the following actions:Document the URL that you were expecting to work Visit the community and paste the expected terms in the Search bar to see if it brings up the correct post or blog Click here to complete a form to submit the results: If the page is not found at all, submit that to us as "not found" If the page does work but has a different URL, then submit that to us as "OLD & NEW URLS" Happy Navigating the community and helping us improve it. Thanks,Eric

I wanted to post this up here to help you figure out what the best way to create a post, ask a question or just reply to a post on the community. The process is quite simple, but instructions are always helpful: Choose the forum you want to post in (i.e. Nintex for SharePoint Server) Click on "Create a Post" and type in the subject and check if something similar already exist. This is important so please check if something does exist and help keep the content clean. If it truly does not exist, scroll to the bottom, select "my topic hasn't been posted before" > Continue and Post Type your question or statement and provide any links, images or videos as needed Choose the correct label and add any custom tags as needed Ensure the email option is selected so you get notified if someone replies to your post Some things to note:You c

The Dictionary variable type, although the concept is not new, is new in Nintex Workflow for Office 365 for those who are more experienced with the on-premise version of Nintex Workflow, which instead of a Dictionary, there was a Collection variable.  To move your mind into the concept of the Dictionary, takes a little getting used to when you've being working with the collection (or an array of data).  But hopefully this serious of posts will shed some light on the subject and make it a little easier to grasp and utilize in your business processes. What is a Dictionary? I'm sure most of your have opened a dictionary book before.  Remember those things called books?  Oh wait, ok... http://www.dictionary.com .  You probably know that. The concept of the dictionary is that in effect it's based on Name/Value pairs.  Based on the name, you can pull out the value

When building a Nintex Form, you will inevitably be presented with a need for certain fields to have validation rules on them.  It could be a simple rule like the field needs to have data in it.  Or it could be that the field must be between 0 and 10. In this post, we'll be talking about taking the validation to a next level, and we'll be using Regular Expressions to validation fields.  Specifically, the need to have some fields that have numbers and numbers only and others that have alpha characters and no numbers. The example provided in this post will show you on-prem Nintex Forms, but the same functionality will work for Nintex Forms for Office 365. Numbers OnlyFirstly, since you probably already have a control on your form for this, I want to point out that we won't be using the Rules engine in Nintex Forms.  Although that is very powerful, there's no way in those rules to do this type of validation. Instead, doub

We have worked in a solution for the annually employee’s performance review process. The whole solution is powered by Nintex Technologies for SharePoint 2010 (I know, caveman here, sorry!), but that was not even the worst part. We faced few problems related to the fact that the form was pretty large and some users will need to have the form opened for a long period of time - typically during a manager/employee meeting that can last one or two hours. The issue is that SharePoint, by default, has the form digest value set to 30 minutes. This means that after this period, when one attempts to submit the form, the user will receive a nasty error message and will lose of all the data entered. This is a terrible situation and in this article, I will try to suggest two functionalities that combined can offer a way better user experience: “Save”, “Save and Submit” and validation rules: Apparently with NF 2013 version and higher, the “Save and Continue” wou

I have been creating several forms in Nintex Mobile in my O365 tenant for some time now and wanted to add some flare by adding icons the forms. My initial attempts prove somewhat difficult so I wanted to post my results and steps taken to add icons more quickly the next time I need to.  As of this writing, (So yes, I expect this behavior to change in future updates to Nintex Mobile App), the issue I ran into was not being able to upload images to my Site Assets library on my SharePoint site and use those icons within the app. What I found was the app does not use the account that is used to log into the tenant to access the image. So this required me to upload my images to public facing locations so the app could essentially anonymously download.  So this was the next hurdle, I don't have a public facing website I can randomly upload images to. But I thought, I do have OneDrive, DropBox, and a Google account, can't I use those? What I found out was Yes, a

It's here! No longer will you need to mess around with Word Automation Services or Office Quick Parts. Dynamic Document Generation for Nintex Workflow On Premises is here, and it's PACKED with awesome new features.  If you've seen this action in eh action for Nintex Office 365, you'll be aware of the HUGE time savings and efficiency it brings to your business processes whether they be creating a purchase order from a template to send to an external party for electronic signatory; collating new starter data in a security trimmed version controlled ppt file residing on SharePoint for induction material; sending an employee offer letter to a new employee; adding sales proposal details to a template or producing a PDF version of a safety incident report;..... the list goes on and on and on! With these actions combined with electronic signatory we've revolutionised the way you work with hard copy documents which get sent in internal mail for review or worse still, to extern

As one of the community leaders, I wanted to take the opportunity to share an update about a friend and member of the community that made such a large impact on many of us.   Tom Castiglia was one of those guys that just got stuff done, helped where he could and was fun to hang around. While he wasn't the loudest person in the room, if you ever wanted to get super technical and geek out about documents, converting PDFs and OCR technology along with different solutions; he was the guy who offered a unique way to look at it. On January 26, 2019 Tom Castiglia of Scripps Ranch was hiking with friends in Lakeside in San Diego County. He told friends he was experiencing shortness of breath. Members of the hiking group navigated their way into an area with cell phone coverage and c

Recently, I came across an error using Nintex Forms for Office 365. Fortunately the error was isolated to a specific scenario and turned out to have a pretty simple solution as well. The Scenario...Using Nintex Forms on Office 365 to customize the form on a document library (not a regular list) Using the library's Upload link to select a local file that you wish to upload into SharePoint (problem did not occur when clicking Edit Properties or View Properties on an existing document) Using Internet Explorer v11 (problem did not occur with IE10 or Chrome in my testing) The Problem...In the scenario above, I was expecting to have my Nintex Form displayed in a dialog just as SharePoint normally displays the standard Edit Form.  Instead, I was greeted with this erro

Recently I've been involved in that project, where data and information that was being created for years in on premise SharePoints had to be migrated to the sharepoint online environment in office 365‌. All migration was said to be a simple, straightforward and easy due to the usage of sharegate, but... the real truth turned out to be way more dark.Before the real migration started I sat down and started reading about the process and possible obstacles. I can now divide them into 3 groups:Limitations of Sharegate Limitations of SharePoint Online Limitations of Nintex for Office 365.First things first. I will guide you through all and each from them.Limitations of SharegateSharegate is a really great tool. Honestly. It saved me dozens of hours but as well made me frustrated. But still it is great. It really allows not straightforward migrations to be possible (like from SP2007 directly to SP2013 and so on), is th

Planning ahead In addition to creating one to one mappings of Nintex and SharePoint content databases (Covered here: https://community.nintex.com/docs/DOC-1092). Workflow history lists can be created on a one to one basis for each workflow in the environment using the below steps: Navigate to Site Settings Nintex Workflow Manage workflow history lists. Click New from the ribbon and name the new History List something meaningful like the workflow name and history list. Example: ‘My Approval Workflow History List’ Open the Nintex Workflow Designer and click Workflow Settings. Select the new history list from Workflow Options and click save. When you publish/re-publish your workflow all new instances of that workflow will use the newly provisioned workflow history list. Performance Typically we start to see performance degradation w

Related products: Nintex Workflow 2016, Nintex Forms 2016, Nintex Workflow 2013, Nintex Forms 2013, Nintex Workflow 2010, Nintex Forms 2010, Nintex Live Typically when an error comes up around a missing Feature or a duplicate Content Type or Field within SharePoint, it can be difficult to diagnose what exactly is being referenced.  In order to assist with troubleshooting the issues specifically related to Nintex Products, below are Nintex Features, Content Types, and Fields along with their associated IDs. **Please note that some of the Features, Content Types, and Fields are hidden.  Hidden items are not going to be visible within the SharePoint UI. Nintex Features**Note: The feature NintexWorkflowClaimsMigration is only included in SharePoint 2013 environments Feature Feature ID

Planning ahead Speed is typically a business requirement when designing a workflow; however, sometimes the appearance of speed is just as good as the real thing. Adding a 'Pause for...' action as the first action of a workflow will actually have the illusion of being much faster to end users. Additionally, starting workflow designs with a pause has the added benefit of increased durability. PerformanceAdding a pause to the start of a workflow will force the workflow instance to immediately dehydrate and persist to the SharePoint Content Database. A workflow executed by a user will show a 'Working on it...' message to the user until completion or dehydration (This has the appearance of sluggishness). The quicker you can dehydrate the workflow, the quicker the workflow will appear to users. Reference: Workflow Scalability an

Planning AheadWhen designing a workflow it is often assumed that the actions will be processed in the exact order they are shown in the designer. While true most of the time, if your workflow is utilizing any batched actions (see below), the actions do not always execute synchronously. What is a batched action?A batched action is any action that makes a change to a SharePoint environment. These actions are added to a batch and processed together. How are batched actions handled?SharePoint Workflow Infrastructure processes activities synchronously until it reaches a point where the workflow is blocked (Task, Pause, etc). Only at this point will SharePoint commit batched actions. Processing changes to SharePoint in batches has several advantages: Processing changes in a single SQL transaction is less resource intensive than processing every change as it occurs in a workflow. When SharePoint encount

Applicable to Versions of Nintex Workflow 3.1.1.0 (Nintex Workflow 2013) and 2.4.1.0 (Nintex Workflow 2010) and earlier. Configuration Nintex Workflow solutions are deployed to SharePoint as Web Application scoped Solutions (Nintex Live being an exception). Nintex Workflow also makes use of the GAC (Global Assembly Cache) for its assemblies. When Nintex Solutions are deployed to the farm, only Web Application Servers install a copy of the Nintex Workflow assemblies into their GAC. Every server that is running the Workflow Timer Service (Microsoft SharePoint Foundation Workflow Timer Service) is going to be in a pool of servers that can/will process Sharepoint and Nintex Workflows. SharePoint uses a round robin system to determine which server will process a given workflow instance. There is no feasible way to limit/reconfigure this functionality other th

In support we field a lot of questions revolving around workflow history such as; where it is kept, how it grows over time, how to maintain it and what are some of the limits that you will run into. Today, I would like to show you where it is created, kept and how to plan for the future. General Information: There are 2 places where the workflow history is kept and accessed.      1. SharePoint Workflow History – This is kept inside of the site collection in a hidden list typically           called NintexWorkflowHistory.     2. Nintex Workflow History– This is kept inside of the Nintex Workflow database. Because there are two places the workflow history resides, this also means that there are two places you can view it. SharePoint Workflow Hist

According to Leif Frederiksen‌ last post Filtering large List Lookup dropdowns ...‌ I had the problem with a real big dropdown (nearly 20.000 entries). So the code of Leif was not suitable for me because it took too long to filter (blank out) all the entries that are not needed. I decided to do a workaround and figured out another way to solve the problem. Why not do a CAMLquery on the whole list and show only the results in the dropdown? So I have the full control of the query (i.e. "Contains"). In this example I show you how I did the search/filter for our suppliers. My users can choose a category and the search works with "contains". There are too many entries we have to deal with...

Recently, we were working for a client who wanted to migrate on-premise NINTEX Forms and Workflows into O365. But the challenges we faced while creating an Azure Security group by using Office 365 Nintex workflow. As such there is no direct component that can be used in O365 to achieve the goal as like on-premise/enterprise edition. It was very urgent from client perspective and so we can't wait for NINTEX help-desk to reply on that. We have implemented with our own ideas and thoughts and hopefully it will help you in coming days until NINTEX is providing a straight forward component in Office 365 to achieve this. Solution to Add/Edit/Delete Azure AD Groups involves a four-step process: Step 1: Having an app registration in Azure that will have the rights to create, update, delete Azure AD group.Step 2: Getting TENANT ID, APP ID, and CLIENT SECRET while registering the App.Step 3: Authentica

If you are a current DocuSign customer you are likely familiar with document and envelope Custom Fields.  These custom fields allow users to create custom versions of standard fields and save them for reuse in future documents.  Leveraging custom fields comes in very handy when automating a process using Nintex Workflow Cloud. In this brief blog post I am going to walk you through how you can leverage these custom fields within a Nintex Workflow. There are 3 components to making this work and I will walk through each below. https://support.docusign.com/guides/ndse-admin-guide-custom-fields 1.  The DocuSign Custom Field The first thing you need to do is create your custom fields within your DocuSign account.  You can use either standard fields provided to you or create custom new ones.  These field

Nintex Forms Enterprise enables your forms to connect to external data sources, such as SQL databases or web services, extending their reach by automating the inclusion of relevant information. In this post I will explain the power of SQL Request Control to query warehouse data from an external SQL Server data store in order to build a Product Order Form.The SQL Request control simplifies connecting to a SQL Server database by configuring basic information such as Server Name, Database Name and Authentication mode (Anonymous, Windows and SQL). This Control supports multiple display formats similar to Nintex Choice Control - Option buttons, Checkboxes (Multiple Selection), Dropdown list or Text/Label. The SQL Request control leverages the SharePoint Secure Store Service in order to protect the SQL Credentials, which we would also recommend are configured under least privilege principle

I have to admit that I had worked with Nintex Workflow for well over a year before I discovered these beautiful actions!  When I realised what they could do, I realised that I was repeating a lot of stuff in separate workflows unnecessarily.Using these actions together allows you to store variable values and pass them between different instances of running workflows. Where might this ability come in handy?  Well I do not like to have workflow that are too large, so I occasionally break them down into smaller and more manageable chunks as separate workflows.  I join them together using the "Start workflow" action.  Often I will require an output from the workflows I start in the main workflow they are being started from.  Here's how to grab them: Start workflow actionWhen configuring this to run, ensure you capture the instance ID in a text variable of the workflow you are starting.  This is required later when you retrieve whatev