Skip to main content
Nintex Community Menu Bar

News

Stay updated with the latest announcements, product updates, and community highlights from Nintex.

  • 1,245 Topics
  • 3,875 Replies
1245 Topics
P
Nintex Employee
pamela_denchfieNintex Employee
posted in News
Error 12031 When Saving or Publishing Reusable Workflow Templates

Products: Nintex Workflow 2013, Nintex Workflow 2010 Summary The error message “12031: Unknown” appears when a reusable template is saved or published. Symptom When saving or publishing a reusable workflow template, the system does not respond for five minutes, and then the error message “12031: Unknown” appears. Cause The Nintex Workflow publish or save process is timing out, likely due to delayed propagation caused by a lengthy content type evaluation. Resolution To reduce the time required for content type evaluation, create a content type based on Item and then select the created content type when defining the reusable workflow template. For instructions, refer to the SharePoint documentation. More Information For more information about reusable workflow templates, see “Set Title and Description for Reusable Workflow Template” in the Nintex Workflow Help (2013 | 2010). For more information about the evaluation process that Nintex Workflow uses for content types, see the following M

50
P
Nintex Employee
10 years ago
Dan_Stoll
Nintex Employee
Dan_StollNintex Employee
posted in News
Taking Office 365 for a spin with Nintex Mobile.

Hazaa !! I hear the crowds say.. Here it is Nintex Mobile Version 3 .. But why the fanfare? Well, Nintex Mobile now also supports Nintex Forms for Office 365. So let me take you on a little journey to show you what this means and how to get started. Let’s take a look at a health and safety check list “Slips, Trips and Falls” .. Firstly, we need to build out the list.Now there is nothing special about this list.. But it is in the context of its usage. A majority of “Slips, Trips and Falls” aren't happening in the office around your computer. They are happening out on construction sites, factory floors, and generally away from the office. Getting timely information, which also tends to be more accurate if recorded at the time of the accident is imperative in the modern workforce for a number of reasons which we don’t need to get into. One of the things that businesses are starting to do, is to move to the cloud. This is great, but it requires you to be connected to the internet to proces

20
W
10 years ago
A
Nintex Employee
alex_burtonNintex Employee
posted in News
Using Skip to Stage in Nintex Workflow for Project Server

The Skip to Stage capability of Project Server allows an administrator to skip a workflow to a particular stage, usually as a result of modifying the existing workflow, or swapping to a different workflow and needing to skip over some of the business logic or steps. The steps below are from Nintex Workflow for Project Server 2010, but also apply to Nintex Workflow for Project Server 2013.Sam Chung wrote an excellent blog post on this over at the Project Programmability blog back in February 2010, and the same concepts apply to Nintex. Consider the flow chart below which outlines a simple Project Server workflow scenario.Should the administrator wish to skip this workflow to the execution stage, and skip the approval, it is not possible as the workflow has not been coded to allow it. This is where the Skip To Stage information comes into play. When an administrator chooses to skip to a specific stage using the Server Settings > Change or Restart a workflow, the workflow is initiated

130
A
Nintex Employee
10 years ago
M
marty
posted in News
PowerShell cmdlet to provision Nintex Workflow Constants

If you are building Nintex Workflows, and especially if you are deploying them across multiple environments, then you should be considering using Nintex Workflow constants. These constants are remarkably useful to make your Nintex Workflows portable, so that they can easily be deployed into multiple environments without confusion or wasted effort. Any workflow parameters which are specific to the environment in which the workflow is running, or which are likely to be changed by the business at some stage, should be built into your workflows using these constants.  Many of our clients are looking to improve their processes for deploying and managing SharePoint and Nintex based functionality, and the critical aspects tend to fall around governance and repeatability. So in the interests of repeatability, here's a PowerShell cmdlet to create a new Nintex Workflow constant.  With this script you can specify any type of constant, including credentials which are useful for service accounts. Y

530
M
10 years ago
Sidebar Buttons
Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status

Badges

Show all badges
Terms & ConditionsCookie settings