Archive

Need some help with a time sensitive request.  I have a list library with a Nintex form.  The form is a questionnaire that a user fills out.  Once the form has been completed the user needs to be able to open a document (or template) with the data gathered and print this document.I have a list library and a document library.  How do I copy the data from the list library to the document library?  My plan is to store the document template in the document library, copy over the data from the list library and open the document template that should have the questionnaire data populated.Have and am trying to use Copy Item workflow, but keep getting this error:"Workflow StatusThe workflow could not copy the item. Make sure the source and destination lists have the same columns and column settings."I have validated the list library and the document library have the same columns and column settings, but still get this error.

Originally published 11 July 2016July, 2016 release:  Nintex for SharePoint 2016 We have released the latest version of Nintex Workflow and Nintex Forms for SharePoint Server 2016!  The announcement came at the Microsoft Worldwide Partner Conference (WPC) in Toronto, where Nintex made a number of product announcements.New FeaturesThis latest release  improves user experiences, includes the capability to start a workflow from a non-SharePoint environment, and gives customers a flexible workflow platform that can scale as part of their on-premises deployment or through a hybrid implementation of SharePoint Server 2016 and Office 365.How can I get it?Existing customers can upgrade to Nintex for SharePoint 2016 as a part of their software assurance from the Product Download space, while new customers can purchase it through a partner.Product Downloads can now be found within your Customer Central site under 'Product Releases' in the left hand navigation. If you are using your corporate ema

v4 is a bug fix for K2 Five based on V3 share by  @JPSwaynos in Digital Signature v3 Bug: Unable to get File output value.Investigation: There is a change in SourceCode.Forms.AppFramework.Logging class in K2 Five.Fix: Comment the logging line and output error in the form itself. Build info  Tested on K2 Five (5.0001.1000.0) Built with Visual Studio 2015

This broker provides an easy way to bulk upload an Excel spreadsheet with a 2D table of values (with header) into a SmartObject

Originally published: 4 February 2013 There is a known SharePoint bug which can affect some Nintex Workflows and cause them to freeze under certain conditions.How the bug is definedWe believe the root cause of this issue is a fault with the SharePoint workflow engine. The bug causes workflows that have delay activities to fail and then wake up from a paused state and lose their workflow context.When a parallel block is in another parallel block and one branch sets a variable and the other reads it, the reading branch doesn’t read the latest value of the variable.OrHaving a delay inside a parallel (in your example this is a task reminder) OR “while” loop (which are both Windows Workflow Foundation activities) suffer from the issue. More technicallyWe believe this issue is caused by a race condition and is therefore, intermittent. However, this is exaggerated when the servers that are running workflow are under load. The issue is that if a workflow process is hydrated in the w3wp.exe pro

Originally published: 4 February 2013 Are your workflows freezing, or take longer then they should to continue? This may be due to the SharePoint timer service. Please see below for issues and troubleshooting.All delay actions utilize the SharePoint timer service.  If there is a greater issue with this service it can affect any action that utilizes delays. The effect on these actions might be they do not continue at the expected time, or they never continue.The following action may be affected:·Pause for (NW2007 = Delay for) ·Pause until (NW2007 = Delay until)·Task reminder·Complete workflow task·Delegate workflow task·Loop (when Safe Looping is enabled)·State machine (when Safe looping is enabled) Issues and Trouble shooting Issue 1 – The “Pause for” action never continuesTroubleshootingPlease follow these steps if you experience issue 1.1. Restart the SharePoint Timer Service2. Hot FixThis .NET hotfix was released by Microsoft for delays in workflows:* Ensure Windows 2003 SP 2 is ins

You can use a Windows Communication Foundation (WCF) client to hit the Nintex Workflow SOAP endpoints. With Visual Studio, you can add the Nintex service as a resource and then build a client. In this post, I show you how to add the resource, create your client, configure your bindings, and then use the export and publish endpoints to retrieve a workflow file and add one to an existing SharePoint list. In this post we will walk through building a client from scratch. Visual Studio will help with the behind the scenes code to build the proxy and client. You can also download the complete project from the Nintex Platform SDK. This is what might be called a beta topic. I'm looking for feedback on how to make this subject clearer and more useful to you. Please feel free to send me your feedback or include your feedback as comments to this post. Thanks, MattTable of Contents Export and publish a workflow overviewThe following lists covers the major steps for creating a SOAP client, bounding

I have a workflow where I need to send 10 tasks at the same time.  I have set up a parallel action with ten nodes (tasks) but I can’t save it or publish it.  I get an error that states: soap:ServerServer was unable to process request. ---> Failed to publish workflow: Error in the application.  What is the maximum number of nodes I can place in a parallel action?

IntroductionI've been on several collaborative calls with Microsoft investigating paused/failing timer jobs and decided to share the process used to track a rogue workflow that is running amok. If you are seeing workflow timer jobs across your entire farm fail one by one in succession, then it's likely there is a particular workflow being rehydrated that is causing your workflow timer job to pause or fail. Once this timer job pauses/fails, the workflow failover timer job will pick up this rogue workflow and execute it again on the next available timer job in the load balancer pool, thus leaving you with no workflow timer jobs running on your farm. NOTE: This guide should not be used to troubleshoot all issues with workflow timer jobs. Please review the following document first: Workflows not continuing - Timer Service and Delays Additionally, a workflow timer job can pause, fail, or run for a long time if you have large amounts of workflow data. The following documentation should be ad

I recently upgraded to the newest version of Nintex for SharePoint 2016 in an attempt to see if it would correct a few other issues I was having, but failed to respect the fact that the Nintex Forms javascript code-base was updated... resulting in a LOT of broken things. This was totally my fault, but the frustration of trying to figure out what in the heck was changed and where has made me think that creating some type of community documentation of any found changes might be worth while. I know that the changes I'm listing here are not going to be useful / used by a lot of people, but if you happen to come across any changes in your own work, and subsequent workarounds / fixes, please share them here so that we can create some type of log. ♥♥♥ If you're interested in seeing which changes are happening between version, and would like to make that a regular part of the patch notes, consider adding a few votes to my suggestion here: Publish JavaScript Change Logs In Patch Notes, or Put N

Original publish date: 06-26-2015We're very excited to announce our latest innovation - Nintex Add-in for Outlook!Nintex Add-in for Outlook is a brand-new way to experience Nintex from Outlook.  Make your users more productive by interacting with Nintex Workflows in the context of email, seamlessly inside of Outlook. With Nintex Add-in for Outlook, users can:Quickly and easily respond to Nintex Workflow tasks from within Outlook Add comments to tasks providing context to decisions Rapidly progress a workflow without having to transition to a browser Increase productivity whether using Outlook on the desktop, the web, or even a smartphone or tabletNintex Add-in for Outlook activates when receiving any “LazyApproval” email from Nintex Workflow.  Simply open the Nintex Add-in, enter a comment if desired, and select your choice from the list of options.  Nintex Add-in for Outlook works with existing workflows without requiring any updates to Nintex Workflow software or to the workflows the

TopicHow to do a clean install  of Nintex Solutions after a failed installation. Also Applies for : Nintex Workflow 2010 , Nintex Worklfow 2016 InstructionsGo to Services.msc » Stop these services on all servers where it is running. Nintex Live Relay Service Nintex Live Workflow Queue Service Nintex Workflow Start Service In Cent. Admin, retract all Nintex Workflow and Nintex Forms solutions in the following order, waiting for each one to retract before moving to the next: nintexworkflow2013enterprisefeaturesbackwardscompat.wsp (Used if you have any sites running in 2010 mode, Retracts from each web app, then Central Admin web app). nintexworkflow2013backwardscompatibilityui.wsp (Retracted globally, used if you have any sites running in 2010 mode). nintexworkflow2013enterprisefeatures.wsp (First all web apps, then Central Admin App) nintexworfklow2013.wsp (First all web apps, then Central Admin App) nintexworkflow2013core.wsp (Retracted globally). nintexforms2013backwardscompat

This short video demonstrates how to import and export a workflow, and is applicable to Nintex Workflow for Office 365, Nintex Workflow 2013 and Nintex Workflow 2010.   

Document created by Emily Billing on Sep 15, 2014 This short article describes how you can split a Nintex Workflow to improve workflow performance. Given that there could be thousands of combinations and permutations of workflow designs, it’s very difficult to describe one way to split one complex workflow into separate parts. Therefore, a general approach is offered by way of a relatively simple example. For example, this simple workflow has two approval stages:There can be any extra amount of actions, however the essential part is that the workflow has two stages, the initial approval and then the second level approval. If this workflow was having issues, the logical step would be to split up the workflow into two workflows; ‘stage 1 approval’ and ‘stage 2 approval’. To do this, you first need to determine where the second approval process begins. This is where it is best to divide the workflow. In this simple scenario, the workflow can be divided into two workflows, each containing

Document created by Emily Billing on May 25, 2014 In some instances it may be necessary to increase performance by using a Call Web Service action to speak to another workflow. Extremely large workflows can be difficult to edit and may run slower than a smaller workflow designed for a specific process. In these cases, splitting the workflow into separate workflows and having the first workflow call the second and so on can increase performance. This can also be an advantage if there is an error; the workflow can be restarted from a certain point rather than from the beginning. Why use a Call web service action instead of a Start Workflow action? The Start Workflow action allows the user to start a workflow on the same list item only. This is useful in certain situations but more often than not starting workflows on different list items is required. Also, if the workflows are part of a larger process, passing variables between the workflows is essential. This can be achieved using the C

Looking for Nintex for SharePoint 2016 guidance? See the following link.http://help.nintex.com/en-US/nintex2016/current/Default.htm#cshid=backuprestore This article provides guidance on data management procedures for Nintex Workflow (2013 and 2010), specifically backup and restore functions that are compatible with SharePoint’s own framework and processes. The target audience are system administrators of SharePoint and Nintex Workflow. See also Database Design Guide: Nintex Workflow. Supported Backup and Restore MethodsThe following backup and restore methods are supported for Nintex Workflow 2013 and Nintex Workflow 2010.Restoring from the Recycle Bin; see Microsoft article: Manage the Recycle Bin of a SharePoint site collection. Note: You can restore subsites, lists, document libraries, and other SharePoint elements directly from the first and second stage recycle bins. Restoring subsites; see “Restoring a Site via Site Export/Import” below. Note: Avoid using stsadm commands; workflo

Obtain an account with sufficient permissions. Ensure that the user account performing the installation and deployment (Windows user as well as user logged into Central Administration) is the Farm Installation account and that it is a Local Administrator on the server used for installation. If your installed version is 2.4.1.0 or previous, uninstall the current version of Nintex Workflow 2010 using Uninstall or change a program on the server on which it was installed. (This action does not affect the product's functionality). Warning: Do not retract the Nintex Workflow 2010 solutions via SharePoint administration. Retracting the solutions is not required and retraction would disrupt users currently using the product. If your installed version is 2.4.2.0 or later, skip this step. Run the new installer (.exe file) for Nintex Workflow 2010. On the Confirm Installation page, at the prompt "Do you want to add the solution to SharePoint now?," select Yes. The installer will attempt to upgrad

So I'm building a notification system, first I fetch items from the list and store it in a collection. Then I use foreach action to return each item in the collection and send approval request for each item in the list. The problem is when it comes to approval request action, it'll wait until the first item is approved then it will send the second approval.I want it to send all the request approvals at the same timeIs there a way I can achieve what I want without having to approve/reject the first item to send the rest of items approval request?

Hello, I have to copy a file from one library to a folder of another library. Is this even possible and if yes, how do I specifiy the target? If I just use the URL of the folder as target I get an error that there is no list with this name.

Intro The topic of the Nintex Form Events has been covered before, most notably in the document located here: https://community.nintex.com/docs/DOC-1217 However, there are a few shortcomings and errors with this document undoubtedly because the Official SDK Documentation Help Page contains a lot of erroneous information (https://help.nintex.com/en-us/sdks/sdk2013/FormSDK/Topics/SDK_NF_CON_NF_Events.htm): Though it would be easy to make an almost identical Blog or Document containing the corrected information, I wanted to take the time to delve a little deeper into how Nintex Forms fires its custom Events and the options it presents to you as a developer. I should also take this time to get one of the bigger caveats of this blog out of the way. This is mainly for the Classic Forms and not the Responsive Forms. While I will get into how you can utilize them in the Responsive Forms, it's a HUGE hassle and ultimately isn't supported by Nintex... sadly. Until that is the case, it won't be p

I enjoy having the ability to speak to a room and auto-magically set a cooking timer, play NPR, or check the weather. I then thought it would be amusing to be able to start a workflow as well. If I can order a pizza with my voice, I should be able to start a workflow too!  With the Nintex Workflow Cloud, the ability to externally start a workflow (Nintex Workflow Cloud External Start ) opens up a world cloud of possibilities. With the right tools, anything can become a start event. In this blog post, I'll walk you through how I wired up Alexa to successfully start a Nintex Workflow with code samples and Alexa skills kit examples. Alexa Skill DevelopmentFor demo purposes, I'll be calling into a leave approval workflow built in NWC. To build the Alexa skill that will help kick-off this workflow, we need a few important bits of information:Skill InfoSkill Type - What type of skill you're making. Select: Custom Interaction Model Name - Something of your choosing. In my case, "Time off" I

In this example, I'm going to create a color-picker custom control for Nintex Forms On Premises 2013. The color-picker control implements the HTML5 color input and illustrates how you can bind your own control using the Nintex.Forms.Sdk.dll to Microsoft SharePoint with Nintex Forms. It also demonstrates how to store and retrieve data to and from your control.  Color Picker ControlThe color picker has the advantage of only using a single HTML5 tag, <input type="color">. However, it has the big disadvantage of being an HTML5 tag not supported by Microsoft Internet Explorer. IE is the only browser that runs the Nintex Forms Designer. This means that when you design your form with the color picker in IE using the Forms Designer, you will need your users to interact with the form in a different browser that supports the tag. The color control is supported by Google Chrome, Mozilla Firefox, and Apple Safari. For a production-worthy implementation of a color picker you would naturally w

My last project required creation of a dynamic list of approvers for the approval process (a coincidence?), based on a location and volume threshold. And some other parameters, but this is not a case. At first I naturally thought about a list, that would hold such mappings for me. Then I thought to query that list within a workflow, using filtering to gather only a specific subset and then, using a state machine, to go through and assign tasks.  But there was a catch! Customer expected, that the form should allow to display that list of dynamically gathered approvers and then to show how each one expressed approval. And with the possibility to add or remove existing ones! Naturally, I decided to use the repeating section control, but I didn't know how to fill it dynamically. I managed to do that however, and the results look like this: And the source list for data lookups: How such dynamic repeating section can be made?Step by step. Let's begin! The data structureLocations (just a simp

This was inspired by Paul Crawford's post (huge thanks to you) Ensure Unique Reference On New Item, which was incredibly enlightening. And while it was almost the perfect solution for what I was looking to do (generating an incremental number that was unique and guaranteed), there were a few instances when several new forms could be created with the same value.  I attempt to solve this problem by leveraging the power of an Item's ID field, which as far as I know, cannot be tampered with, and automatically increments upon creation. Additionally, because SharePoint proper is handling the creation and destruction of these Items, it seems perfectly capable of sidestepping any concurrency issue that would arise.  So, without further ado...  My Form Information: I'm using a tiny test form that has a Title field control, and a few other controls with custom widgets on them.  Setup:  You'll wanna setup the control that targets the column you'll be generating an incremental value for. In this e

For those out here that have followed a lot of my posts on this Community or just seen some of my blog posts on my companies blog at Summit 7 Systems, I want to take a moment to say thanks for reading them.I’m encouraged by many of you to keep writing and as I aim to do better and achieve more with the tools I have, I want to share that insight with you as well.  Also a special shout out to David Deschere for being a great reviewer and always providing positive feedback on my posts. Much appreciated.To that end, I know we all are pressed for time, so I’m making this blog short and sweet.  This post will be the first of a series of post aimed at providing some basic but necessary logic and thought processes that is often overlooked or forgotten when it comes to using Nintex forms and workflows in your organization.  I will endeavor to dive deeper with each post to help users from all levels use Nintex more efficiently as we go along. Hope you enjoy this short read and that you learn or