News and Guidelines

After running into a few issues or errors while building workflows, I wanted to start documenting my resolution to those errors. Almost all were errors that I caused. The trick was determining what I did. I will try to add to this list as they come up, but here is the first one. Error publishing workflow. Workflow XAML failed validation due to the following errors: Object reference not set to an instance of an object. HTTP headers received from the server - ActivityId: a41a30d5-c786-4546-bdde-e03903af1796. NodeId: . Scope: . Client ActivityId : ede2f19c-7043-1000-b4b2-37a9eab76b50. The remote server returned an error: (400) Bad Request. This error occurred when I was publishing a workflow. The background to this workflow is that I exported it from one site and attempted to import it to another site. I thought I had the field names exactly the same from the source list to the destinati

Sweat drips steadily from your brow as your deadline draws near; months of hard work are moments from fruition, and all that is needed now is your client's signature. Just as you prepare to send them the fruits of your labor, you receive an error: “One or both Username or Password are Invalid”. All the more maddening is that you just confirmed your DocuSign login credentials! While undoubtedly frustrating, this is also an easily resolvable issue, obfuscated by the fact that it's technically neither your username or password causing the error, but mismatched API keys.  In order to resolve, the issue, you'll need to open both your DocuSign Account page, as well as your Drawloop Admin Third Party Integrations screen. 1-Open the DocuSign Admin site. You can navigate here by opening "DocuSign for Salesforce"-->"DocuSign Admin"--> "DocuSign". Once you select "DocuSign", you will be taken to your DocuSign page. In the top right corner, select

For those of us who tried or in the process of evaluating integrating Nintex Workflow Cloud into your solution(s), eventually you will get to the question "Why should I integrate Nintex Workflow Cloud?" especially if you code your solution from scratch using platform such as .NET or Java, writing code will be the default way to support any business logic or process(es) of the solution you are building with such platform. Here is my two cents worth for that question. Before we get into discussing why, let us get few more examples here. Take another solution platform for the same question - Sharepoint, which is considered as COTS (i.e. commercial out of the box solution) for intranet/collaboration portal. We do not expect lot of coding or customization, by default Sharepoint supports document management with its content type of Document Library, supports creating of custom records using Custom List, when come to automating a document or record created in

Nintex is becoming ubiquitous in the global IT landscape as adoption increases in their cloud offerings building on top of their highly successful on-premises solutions. Because of this, knowledge of good workflow design and development practices specific to Nintex is paramount.Here below is a short list of key tips to help optimize performance and maintainability of your solutions. Tip #1 - Use Workflow ConstantsOne of the best features with Nintex on-premises is their ability to store credentials for a service account as a workflow constant. When a credential has been created, you can use those credentials without having to know the name and password of the account. The credentials are stored in the Nintex Workflow configuration database and are encrypted with DES encryption. Workflow constants

Video Link : 1353 Hi All! Wanted to do a quick walkthrough on how Reusable Workflow Templates work within Nintex Workflow for SharePoint. Hope this helps in your workflow designing, and if you have any questions, please shoot me a message, or post it in the comments below. Also check out my other videos over on my site Working On It! As a note:  

I had this question asked to me about permissions for Office 365. I found this very helpful table in the O365 help guide​. So if someone asks you, just toss this into an email.This topic lists the minimum permissions required for operations with Nintex Workflow for Office 365.Operation Minimum permissions Install Nintex Workflow for Office 365 Site collection administrator Open the Nintex Workflow designer List: Full control Site: Read Site collection: Read Publish a workflow

I am going to demonstrate a Production Planning process that is powered by Nintex Workflow in this blog post. Before we get further into the production planning process, let us recap what we have gone through together in my previous sharing in Part 1 of GKK Compressor Industry (i.e. RFQ to Quotation process). In the Sales and Marketing division, Product Catalog is being used to create RFQ, which in turn generates quotations issued to customers. Every quotation issued to customer updates the Sales Forecast with the increased number of compressor model to be delivered. Being a Lean Manufacturing, Production Planning is crucial to GKK Compressor Industry, the critical success factor is produced only what is needed to be delivered on time. It keeps no unnecessary inventory to minimize the waste of inventory space. Tentative Production Plan is

Author Palesa Sikwane Long Description Do you need to scan through a SharePoint Sites contents and apply some logic based on the existence of a content type? Or maybe even go as far as scheduling this? Then this post is for you! Dependencies Nintex® Workflow 2010 Nintex® Workflow 2013 or Nintex® 

Yo yo, greetings everyone! What if you got a requirement to Start a Task Process for a Group of users in Parallel (all at once),from a matrix containing the structure of your users as well as what they should/can approve. Sounds pretty simple right? But with Nintex Workflow for Office 365 you get the following Task Actions and each of them have specific functionality:  1. Start a Task Process which is aimed towards Assigning a task to a group of Users, and allows workflow designers to specify task assignment criteria(Assign tasks all at once or in serial) as well as completion criteria (Wait for all responses, Wait for first response, Wait for specific response or Wait for percentage of a response). You may read up more on this action here2. Assign

Products: Nintex Forms 2013, Nintex Forms 2010 There have been several requests recently for the ability to have custom validation in Nintex Forms using JavaScript and/or how to submit a form via JavaScript. Here you will find an example of how to accomplish this. Here is a sample JavaScript that can be inserted into 'Custom JavaScript' in your form settings:    JavaScript //Sets fields in parameter to have a red background. function showInvalidFields(fields){ 

When I first started using using NWC back in the early preview days, the first workflows that I created used various Start Events from both Nintex (Public Web Form, Nintex Mobile, Scheduled Start, External Start) and some external connectors (like Salesforce & Dynamics CRM). As I jumped into NWC and started creating some workflows, I would pick a particular start event (say Public Web Form) and implement my workflow logic. Then I might decide that I want to test the same workflow logic but using a different start event, perhaps Nintex Mobile or Salesforce.  However, one cannot simply change Start Events if there are any references in the workflow to the Start Event variables.  These need to be removed before you can change the type of Start Event. After developing a few processes with Nintex Workflow Cloud, I realized the best bet is to always put your core workflow logic in a workflow using the External Start Event.   Then you can creat

This Quarter's Nintex Workflow Hero is IMS Electronics Recycling.  Later today at this month's Workflow Hero's live webinar, we will showcase their Nintex for O365 success story hosted by yours truly.  See how they were able to adapt to change and growing compliance requirements saving their organization over 5k+ sheets of paper AND 1,256 hours PER YEAR! Be sure to check out their case study right here | IMS Electronics Recycling Nintex Workflow Hero Story Not able to make today's Webinar?  No worries!  You will be able to access the full Nintex Workflow Hero series.  Just visit the Nintex Workflow Hero's landing page for all webinar's past and present and while you are there, register for upcoming live webinars for Nintex Workflow Cloud and Nintex App Studio.  Probably the only binge watching you will

Sometimes when you use an Action Set to execute and/or group some actions, it appears when part of the main flow.   It happens that when you have actions nested inside others, you'll have the possibility to mark them to run as the workflow owner only from the principal one. Only actions at the root path of the workflow will have the Run as Workflow Owner option.  If you have an action in any branch, this option will not be available.

Well over a year ago we released our beloved Document Generation (DocGen) feature in Office 365. Everyone was super excited getting their hands on the new feature and starting to automatically create Word, PowerPoint and Excel documents as part of their workflows. And it was indeed an amazing new world that we entered. Creating sales contracts involves a lot of manual work and using DocGen it made everyone's life so much easier. Over time people got more creative and demanded more functionality. And Nintex listened, releasing an on-premises version last December. This feature built on the feature in Office 365 but took to the next level. Lots of new things that were available to workflow pros:Generation Types: Generate a single PDF file that can consist of up to 20 document templates Generate up to 5 separate PDF files - allows output of multiple files Generate up to 5 separate documents and keep them in their original file type

Hi all, during last years, several times I've encountered projects when the best suitable action in order to ask a user to do something in a workflow was a Flexi task action with just one outcome.. If the customer is using also Nintex Forms and because Outcome is a mandatory field, their following question is always: "Is it possible to autoselect the only option?" and "Is it possible to make it hidden?" Until the use of the new Responsive Designer (at this moment available only for Nintex for O365), the only option in order to achieve this is the use of javascript, and I want to share with you how I do this:Add a class to the decision field (in my case "decision") Go to Form Settings and in Advanced Javascript put the following script:NWF$(document).ready(function(){NWF$('.decision input').attr('checked','checked');//NWF$('.decision').h

IntroductionNintex for 365 does not currently support versioning for workflows. Importing a workflow on top of a current workflow and publishing with the same name will result in irretrievable loss of the current workflow. Up until now Nintex for 365 has not allowed the importing of a workflow over an existing workflow by blocking publishing under the same name. This however, prevents customers from following their workflow (software) development and release processes and has attracted many votes on the Nintex Uservoice site.Nintex has released a change to the interface for importing that allows the user (with several warnings), to import a workflow on top of an existing workflow and publish under the same name. The possibility of inadvertently over-writing and therefore losing a workflow still exists.Nintex suggests the following process to manage workflow versions in a controlled way that will also allow retrieval of an inadvertent

My farm is up to 170 Nintex content databases and I have been remiss in cleaning up old workflow data and history. Part of the reason for this is that we have a legal requirement to preserve some workflow data and try as I may I was never able to get a decisive answer to 'Exactly what data needs to be preserved?". Performance has been off lately so I decided to at least trim down the data from the maintenance workflows that we run. These are workflows that load a list from AD or changes the title of a list item. Nothing business critical and nothing that will land me in jail if I delete it .(kidding...I think). You can tell how large your Nintex tables are by opening up SQL Server Management Studio, expanding a Nintex Content DB and highlighting 'Tables'. I'm on SQL Server 2014 but this is in earlier versions as well. Now in the ribbon Select 'Object Explorer Details' or simply hit the 'F7' key. Take a look at your WorkflowProgress and your WorkflowInstance tables. Som

The Requirement :To implement a department hierarchy structure using Employee information maintained in SharePoint Lists.Solution and Implementation:So rather than implementing a pure jquery solution , I saved myself some time and instead used Nintex runtime functions to retrieve the user profile properties from the user profile (sync to active directory).Please refer my blog-post to see the implementation :Using Nintex and Jquery to create a department hierarchy structure in SharePoint on-premise Final Result Please add in your feedback if any !

Dears, Many Nintex customers working on Microsoft SQL Server are asking me how to trigger a Nintex Workflow (NWC) when an item/row is added to the database. After looking at the "Start event" action settings in my NWC, Microsoft SQL Server connector is missing:   On the help portal for NWC, you can go to the following page related to Microsoft SQL Server connector and see that the feature is not yet available:  One of the solution is to use the "External Start" event:   You can refer to the blog post created by Renai Bell in order to 

I recently put together a slide deck to present to the team I am part of to offer understanding of the different ways to manage workflow tasks when offering support to users in the business.  The main driver for this is that we always get calls from users "never receiving" the email notifications sent from Nintex.  My thoughts on whether they are "not received" or more simply "deleted" shall be kept quiet here...  users eh!  Anyway, prompted by a question recently posted on the community I thought it might be a good idea to put the information in one place on here too. Nintex Workflow Web Part - My Workflow TasksThis web part can be added to a page in any site and can be scoped to look at tasks assigned to the logged on user as the site, site collection or farm* level.  This will include tasks assigned to SharePoint groups the user is a member of (only when individual tasks are assigned in the task config in the workflow action).

In the following sections we will compare the features of Nintex workflow document generation options. Currently we have the following options available:Update Document Workflow Action. Generate Document (the new document Generation Feature)Update Document Workflow ActionThis workflow action can be used to update values in multiple 'content controls' within a Word document. and you need to set the content controls in the word document using the Developer ribbon. “Content Controls” names in the word document should be matched in the Nintex “Update Document” action, any misspell will result in not filling the control with the right values. Each “Content Control” should be addressed in the action, otherwise it will not be filled.

We all know we are here because we work on something that is related to Nintex Workflow or Forms, and the reason we use Nintex Workflow or Forms is because it makes our life easier. Things have changed a lot these days, trending towards the cloud, hybrid environment becoming very common that most of us are working on both on premise platform and at the same time on the cloud. Regardless of which platform you use, you will find Nintex helps. Part 1 of GKK Compressor Industry blog series, I am going to share exactly how I use my hybrid environment to save the efforts for my recent investment - GKK Compressor Industry. GKK Compressor Industry is "Lean Manufacturing" produces world class compressors. Moving towards a Six Sigma company, Simplifying Processes and

Hi Friends, It has been an amazing August. I got to spend some time with the folks over in the Bellevue office and was fortunate to have enjoyed a bit of sunshine while I was there. Lots of things coming down the release pipe in the coming months. However I want to focus on the now; the 2 releases we did for August culminated in an epic feature roll out. I believe this is one of our biggest release months we have done in the history of Nintex Workflow Cloud. Collapse and expand actions - manage navigating large workflow designs by collapsing and expanding branching and containerized workflow actions. In addition, the collapse and expand state of an action is retained on save and publish. Something to think about - you might want to keep sections collapsed / or placed in "Action sets" to help make the workflow more readable / understandable when a user opens it, rather than being show the entire workflow design at first open.

In the support organization, there are frequently customer requests for how to properly refresh Test / Dev Environments with Production data.  The steps below can be used as an example for how to migrate content.  These steps are some basic guidelines around the process for migrating data from a Production Farm to a Test farm, but as all SharePoint farms are different, you may need to adjust these accordingly to meet your specific business needs.  Production Farm StepsBackup Your DatabasesIf you wish to preserve the current workflow history and state, it is recommended that you stop the target Web Application Pool(s) in IIS along with the SharePoint Timer Service in Services.MSC prior to performing backup operationsSharePoint SharePoint Content Databases Nintex Form

Related links Did You Know: The Magnificent Flexi Task – BehaviorDid You Know: The Magnificent Flexi Task – Reminders and Escalation Did You Know: The Magnificent Flexi Task – Communication Methods  The Flexi task is one of the most popular workflow actions and we are eagerly awaiting its arrival in the o365 version.  For something so powerful, how much of it do you really know?  How many of the options have you used? Today I want to concentrate on the behaviour section: