News

IssueI just discovered that renaming a repeating section on a form is not something that you should do if you already have items submitted into a list. Below is what the repeating section looked like originally.And this is what was displayed after I changed the name of the repeating section and re-published. RecoveryThe fix is to change the repeating section back to its original name. After doing that, the contents displayed correctly once again. So, if you (or someone else on your team) renames a repeating section, please be sure to capture its original name before you publish the change.

In this blog post I'd like to show how you can use the data submitted by Hawkeye beacons to create meaningful Power BI dashboards.  The emphasis being on pivoting the table data to use the beacon properties as columns. Before you create a Nintex Hawkeye Process Lens, you need to add some beacons to the processes you want to analyse.  These process beacons will log additional data and properties about the item based on what business rules were applied by the workflow.  In my example, I transmit the following properties using workflow beacons:Buyer Name City Country Purchase Classification Gender Purchase Amount Requested Discount Percentage Discount Amount Discount Applied Approval Status Once my workflow is running, Nintex records all this process beacon data and allows me to create a process lens in Hawkeye and export the Power BI template to Power BI Deskt

Nintex Forms 2013, Nintex Forms 2010If your SharePoint farm is enabled for Nintex Live access to Nintex Mobile, then users can register with Nintex Live​ for remote access to Nintex Mobile. When a user registers with Nintex Live, a Microsoft account is associated with the user’s SharePoint account. By default, new Microsoft account associations are enabled for access to Nintex Mobile. For information on enabling Nintex Live access to Nintex Mobile, see the installation guide (2013 | 2010). Steps for managing

Question: I would like to have a repeating section in my leave request form that contains 4 fields.  When I put the fields into the repeating section, the fields lose their link to the list columns in SharePoint.  Could you direct me to a video or send me some documentation on setting up repeating sections?  Also, is it possible to have each repeating section create a new entry into the SharePoint List? I’m going to be build 3 separate forms (leave request, compensatory leave earned, and overtime earned) that are attached to 3 separate lists in SharePoint.  Can one workflow be configured to process items from all 3 lists? Answer:  For question 1, they can extract the information from the repeating section using a workflow then use that workflow to push the information in to a separate list.  I’ve included links below for the process to extract the data an

This post intends to show printing correctly filled out Nintex forms without validation error summary messages and highlighted fields. Nintex form validation warnings were still visible when I printed the successfully validated form that pictured below.  I have added the lines of JQuery codes that before the window.print() call listed below.        NWF$('.nf-validation-summary').css('display','none');       NWF$('.nf-error-highlight').removeClass('nf-error-highlight'); Finally, I have printed the correctly submitted form without any validation warning on the printout that shown below. 

Question:  Can I use “Is Edit Mode” to lock a form during editing? For example – someone submits the form and the workflow sends it to a group for review – group is Reviewer A, Reviewer B, Reviewer C. If Reviewer A opens the form can it be locked so Reviewers B and C cannot not edit it simultaneously. Answer:  Because there is no Check In / Check Out functionality on SharePoint lists, this one would need to get a bit creative.  There are a couple of ways you can go about it, but this is the way I would set it up: Cr

This month marks a new milestone for Nintex as we introduce Nintex Document Generation for O365. Personally I am super excited about this. For years I've built workflows and then had to craft something to wrap the outputs up in nice way. Now in office 365 land with the absence of Sharepoint Word Services in O365, crafting that output document has become that much harder. With the rollout of the next version of Nintex Workflow for O365, all Nintex O365 customers will get Document generation action with some trial Doc Gens right out of the box.  Let me introduce this new capability by way of a story............... As a Business Analyst for Crestan, I need to create a solution that allows Safety Inspectors to fill in a form on their mobile. The inspection information not only needs to come back into SharePoint but it also nee

(Community manager's note: If you'd like to learn about the value of Workflow Constants, please see Tomasz's post in the Nintex Product Blog‌: Did You Know: Workflow Constants ) There are a lot of challenges when migrating Nintex from on premise to Office 365, even using Sharegate to help you. The most important one in case of Workflow Constants is… there is no such feature available in Nintex Workflow for Office 365 at all. And that basically means migrating them requires many manual operations. When attempting to do a migration with Sharegate, application will show you all the issues it finds in the process, also telling you, that you do have Workflow Constants used by your workflow that are not supported in migration. Workflow will be migrated, however won’t be published, as it contains references to variables

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