News

I came across this issue on a few environments lately where ALL workflows in a farm on premise stopped working. Or more specifically, all workflows reported "Failed to start" when triggered to run.  It appears that it is being caused by a .Net Update. One of my colleagues Ozell Walcott found this post from Rodney Viana who details the issue and solution at https://blogs.msdn.microsoft.com/rodneyviana/2018/09/13/after-installing-net-security-patches-to-address-cve-2018-8421-s…  I have not run the powershell script linked in the solution.  Recent update by the original posterImportant - Recent update by

See post on SimplifyingProcesses.com Planning for BPM implementation In Part One of this blog series, I attempted to identify a common problem with digital transformation efforts – they are often driven by technological advancements instead of supported by them. This can result in several negative, unintended consequences (monetary losses, increased cultural resistance to change, and processing errors and defects which require human resources to repair). If we are to avoid jumping the gun in implementing a new technology and thus, experi

You asked, and we listened! Another huge improvement to the Nintex Workflow Cloud Forms designer Introducing the ability to divide the designer into six columns. Importance/ Objective:With this new addition to the Nintex Workflow Cloud forms designer, users will no longer be limited to just 4 columns, which has placed a slight constraint on process designs. Live Use Case: In this example, Vadim Tabakman is the incredible owner UnBeadable Fashion Car Services. As part of being in SOC compliance and keeping up with the Excellence of Services to work at UnBeadable Fashion Car Services, he requires that all of his mechanics perform daily inspections on all vehicles serviced at his place of business. His all-star employee Will Knowles will be performing a routine vehicle inspection on a 2015 Mercedes-Benz. Before we fill out the inspection form, lets

How to execute a SP2013 REST API request with Nintex Workflow​With all the Nintex Workflow actions, we can achieve lots of great workflows. Sometimes, we'd like to build more complicated, technical, reusable workflows. For these workflows, we need more actions and possibilities that can be achieved by calling SharePoint ASMX web services or SP2013 REST API requests.As the ASMX web services are deprecated in SharePoint 2013 and SharePoint Online, it is recommended to use SP2013 REST API instead when it is possible (not all functionalities of the ASMX web services are available in SP2013 REST API).I'd like to help you building your SP2013 REST API requests.There are two categories of SP2013 REST API requests :POST : to update, create or remove information in SharePoint, GET : to retrieve information from SharePoint.The process to execute these two types of requests is different. How to execute a GET

You've asked, and we listened! Introducing Mobile Task for Office 365  What’s newTask participants can now view and respond to workflow tasks via the Nintex Mobile app. What's all the big hype about: In this digital transformation era that we are living in, time is of the essence, so why waste another minute of it, if you don’t have to? Workers need access to information, enterprise business applications and process that they heavily lean on to function on a daily basis. From the Manager who has 15 direct reports, to the VP who has 2 departments that they are in charge of overseeing, to the Safety Operations Manager who has to approve 50 safety inspections at a given time, guess what, this new feature was created just for you!Task assignees will now have full accessibility to all their tasks and can action from any device including the newly updated Nintex mobile app. 

Have you ever wondered if you can set a value that can be changed during signature and then update Salesforce once signatures are complete? Here is the use case. Today, I send out a document with your latest infomation from my companies CRM. You have moved since we last interacted and your data is not correct. Your mailing address has changed and you need to update it during the signature process. In this article I will show you how to accomplish this task using NintexSign and Nintex Drawloop.  There are many steps that will need to be done in order for us to accomplish this use case. We will first need to create a few text tags and there is a syntax that has to be used.  Syntax: {{FieldName/Lablel_es_:Signer#:default("Tag From Field Tagger")}}Real Example: {{OpportunityStage_es_:Signer1:default(“<<Opportunity_StageName>>”)}} To accomplish our use case we would have to create a few text tags to capture the address (4 to be

The Field Tagger is the key to using Drawloop effectively. It allows you to reach all the data in your environment and push to your template documents. Once you know the data you are trying to pull you simply select the Object and Field to reach the desired tag. Then simply copy and paste your tag into your document. *Make sure to select the correct "document type" you are adding the template tags to.  As you go through the field tagger you will see a "View All" option in the "Field" picklist towards the top. The majority of the time this is fine to use and also very helpful to grab and tag quickly. There are still reasons (you will see below) where you will still need to manually go into the "Field" picklist and select a tag specifically. Formatting and Lookup fields are good examples of this. 

Major Announcement: Nintex ProcessFest 2019!!!!!!!!!!! After a year hiatus, Nintex conference is back and going to be better than ever. Introducing Nintex ProcessFest 2019! This three-day training conference is for our devoted customers and partners. September 30th-October 4th, there is no greater place to be than right here in beautiful downtown Bellevue, where you will enjoy keynotes, hands-on learning, certifications, networking and so much fun! For more information, please visit: Nintex ProcessFest 2019 Calling All Speakers:Have a great process focused topic you would like to present at the conference, or perhaps you have a great speaker in mind?

Have you tried Nintex Sign Powered by Adobe. It’s a simple tool to use and very convenient if you are using Drawloop to generate your documents and want to capture Signatures. There are a few steps that you need to take to have data written back to the Agreements object when your data is coming from custom objects. Today, I will take you step by step to get that setup so you can capture Signatures for any of your documents.1.Create a Field on the Agreements Object. The Type will be Lookup and the object will be your custom object. 2.Now that the lookup has been created drag the Agreements Related List onto your layout. 3.In your DocGen Package you will need to create an Insert update. The Object Name will be set to Agreement The Field-Value Pairs will be set to the Lookup field you created in step. You will also need to use a dynamic tag for the ID for that custom object. EX. 

Hi all, Document generation is not for free, so putting some restrictions on this Nintex workflow action seems logical. Without proper configuration, everyone who is allowed to create Nintex workflows can add the Nintex workflow action 'Document Generation' leading potentially to unwanted document generation consumption. For on-premise, there is an option to allow who can use a specific Nintex workflow action. Below, the steps voor Nintex Workflow 2016 in Central Administration are given.Go to 'Nintex Administration'. Click on 'Action Settings' (Group 'Workflow environment'). Select the action 'Document Generation' and click in the ribbon on 'Edit permissions'. De-select 'Make this action available to all users' and add the people who are allowed to use this action. Click on the button [OK] Besides configuring who is allowed to use the workflow action 'Document Generation',

Products: Nintex Workflow 2013  A common request we see is "How do I cancel/terminate a group of list item 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($S

After creating this blog post Collection Operation - Get , i thought it would be good to look at the other Collection Operations in some detail too.As stated in the article above, the Collection Operation action allows you to interact with a Collection Variable. This can be useful in many situations. AddThis method allows you to add to a value at a specific index within a collectionOriginal Collection - Audi; BMW; VolkswagenValue to add - MercedesIndex - 2Resulting Collection - Audi; BMW; Mercedes, Volkswagen RemoveThis method allows you to remove a value from a specific index within a collectionOriginal Collection - Audi; BMW; VolkswagenValue to Remove - BMWIndex - 1Resulting Collection - Audi; Volkswagen Count

UpdatedUpdate 25/01/2019 (January 25th)We are in the final stages of preparing for a move to the new community site and there are a few things that will affect our members:We will be placing the community site into maintenance mode on 04/02/2019 (February 4th) DD/MM/YYYY. This means that the site will be inaccessible during this time and should come back up within 24 hours. We will have more information and a page to address any concerns during this window. User registration will be disabled on 30/01/2019 (January 30th) DD/MM/YYYY as we prepare for the relaunch. This means if you don't already have an account, click here to register before that day, otherwise you'll have to wait until after the new launch to sign up. Without an account, you cannot post questions or responses, so we highly encour

This is where Nintex Workflow meets Shakespeare.  Ok maybe not. But seriously, wow what a release the June 2015 is turning out to be.  Are you ready to start building complex workflow? No????  That's ok... the aim of this post is not to be complicated, but to actually reduce the size of your workflows.  That's because with the addition of the AND and OR functionality, where you previously had nested Conditional Branches, Loops or Run Ifs, now you can configure the multiple conditions into the single action. This is what the workflow could have potentially looked like before :Now that's not too bad, but imagine a big workflow and then it gets quite hard to maintainSo with this release, the above workflow design, changes to this:

Whilst there has been a height of activity with Nintex Workflow Cloud and Nintex for O365 over the past month or so.. The App Studio team have been feverishly coding away with the next amazing release that really sets Nintex App Studio apps apart. This release you will see some UI enhancements to the build process within App Studio. Which brings the new modular design framework to the product. But the biggest addition is what you can now do with Custom Content... 

Hi Everyone!  How awesome would it be if I told you that you no longer need to access the Nintex store to add Live packs as the store will no longer be available!?  It's true!  We have just released the Action Availability functionality for O365 that preloads all the available actions within workflow designer for you. Well, if you're like me, then you're probably asking yourself:Who does this feature apply to?    What's the value add? Where can I go navigate to start using this feature? Why is this feature important? There are several reason why this feature is important and adds value, such as:Eliminates users from having to access the Nintex store to add actions. Disable unnecessary actions that do not apply to your workflows. All your workflow actions can be accessed from one location.Now!  Let's walkthrough the following scenario of an Admin user

Hi everyone, I am back again, with a Part 2 continuation from my previous blog post: Promapp is your BEST Friend: https://community.nintex.com/t5/Community-Blogs/Promapp-is-your-BEST-friend/ba-p/91497 Today will start to move beyond the Process Management phase, and into Process Automation. What is Nintex Process Automation: Being able to utilize advanced workflow, document generation, e-signature, and digital forms to quickly streamline and automate processes across teams and systems of record. History:In my previous post, we covered Process Management, by mapping out the Employee Onboarding process in Promapp. The Employee On-boarding process, still ranks as one of the most manual business processes. Some people would

I recently had a customer who wanted status indicators in his list.  While this can be done using JavaScript, one of my co-workers had come across a simpler approach by using a calculated column that points to the images that already exist in SharePoint.   That worked well and his list views now had a nice indicator related to the status of each item.  Here is a sample of the list view:Instructions for this approach will be in at the bottom of this post.  It's really easy, I promise! I thought it might be a nice touch to include those icons in the form as well.  Here is a sample:I was surprised that the image controls lined up so well when switching between statuses. Here are the steps that I used:Set up your list with choice column that wil

I Recently had a request to get a Project Manager name that is linked to a project when the user selects a project number from a drop-down control. I managed to get the Project managers name using this formula : lookup("Project List", "Project_x0020_Number", parseLookup(Project), "Project_x0020_Manager"). The only issue was I was also getting the ID along with the name. e.g.  234;#Joe Soap. So, to fix this I used a regular expression to remove the ID from the front of the Project Managers name. Steps I took:1. I created a Form Variable. The formula I used to get the project managers name is : lookup("Project List", "Project_x0020_Number", parseLookup(Project), "Project_x0020_Manager") "Project List" - is the name of the list that has the project number and project managers name in it."Project_x0020_Number"  - is the Project number for the Project. "Project" is the name of my drop down contr

DownloadNintex Workflow Analyzer - Download: Workflow Analyzer Change Set 29292 ChangesNot Applicable Bug FixesAdded null check to ActionCount() in NWFContext class. Change Set 2929 Source CodeGitHub - modembug/WorkflowAnalyzer 

Section Replication Can be usuful when you are trying to gather data that is 3 levels deep! The way this works is you have to create Relationships in the Document Package. You have to set the relationships Copy Type for the child as Section, the grandchild to Table, and the great grandchid to Row.  Below is a Sample of the Relationships setup (Account/Section, Opportunity/Table, OpportunityLineItem/Row)Once you have the relationship setup you will need to get your Word Template Setup. Most customers have the developer tab hidden from their ribbon. This must be added in order for this to work.  Adding the Developer Tab to Microsoft Word RibbonFile > Customize Ribbon >

To show a guide to fill in complex forms, a tool tip is often not enough. Formatted instructions may be displayed in a separate dialog by clicking on an info button: It's a floating window that contains a title bar and a content area. The dialog window can be moved, resized and closed with the 'x' icon by default or by pressing escape key. How can that be done in Nintex Forms? First of all create an info button:I used File:Information green.svg - Wikimedia Commons as button image. Here is the client click coding: NWF$("#Topic_1_help").dialog({    title: "Topic 1",    hide: {        effect: "fade",        duratio

What would be the best ways to return to current form when you press Cancel button? I was looking for the confirmation message on cancel button as well. After struggling to get perfect solution on this forum, I managed to find workaround below on this issue. 1. Disable existing/default Cancel button by adding below rule on the button.2. Create a JavaScript button called "Cancel" and add JavaScript function name, "DoRedirect()" under Advanced -> Client click field   

We can simply extend the recent release of Nintex Mobile Signature Control to work with desktop/browser. This exercise I will show how I did it combining the blog post Sign your name across my heart from Dan Stoll​ and my previous post on Embedding Signature Pad in Nintex Form. The outcome will be a form supporting the capturing and displaying of Signature on both Nintex Mobile or Desktop form. The Signature data is save as base64 image data in a multi-line of text list column (i.e. "Signature" in this case). Here are the steps I followed: 1. Create a custom list for the purpose. We are going to have only two columns defined, one for the Title (i.e. Single line of text), and the second for Signature

This is a generic title to solve a specific issue in a Workflow Task list on SharePoint online.Apparently, there is still a open issue in a Workflow Task list with people whom can edit and save Task even they are not the assignee.On February 2015, I posted this question:"Is it possible to let people who needs to Approve/Reject to give only editable access to their Workflow Tasks in O365 (Assign Item Permissions in Assign a Task is not available ... yet). It seems from what I have read from different sources, that they need to have at least Contributor access.But I cannot find a way to avoid them to be able to edit/read the other Workflow Task in the list.I have tried also to update permissions after/while task is created but if I try after, this is not possible a the workflow is blocked until Task is completed. I have also tried parallel but it seems that I cannot get the stored Task ID in the parellel branch as it is empty and I suppose out of con