All archived community articles, forum posts and groups.
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
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
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
- Introduction - I have been wanting to make this blog post for a little while, and even though (due to time constraints) it probably will not be as thorough as I had originally planned, it will ultimately serve the purpose of introducing the community to a few advanced approaches to using the Nintex Form rule system. Though you will need a comfortable understanding of javascript to get the most benefit from this, but if you're curious and aren't keen on programming, don't let that stop you from learning! The Rule system, as it stands, is a good tool to validate control inputs and to alter the appearance of controls based on the Form's state. However, as I found myself enjoying their usefulness, I also found myself wishing that I could do other simple and useful things with them such as populating a field based on the amount of choices, normalizing the inputs of a field, or doing some type of advanced validation based on wild requirements. Though I cannot account for all of the ways
In this post I look at taking a function, adding it to a custom action, and making it available in Nintex Workflow 2013. This is the third post in my series, "Function to Microservice with the Nintex Workflow Platform," which looks at how you can move your function as portable unit in the Nintex Workflow Platform.I'll walk you through installing a custom action. You can use custom actions to provide the functionality found in many open-source libraries, in your own console applications, or to integrate your workflow data with web services or other remote resources. In this walk through, I'll use the function from the first post in this series. That function uses the Newtonsoft JSON library to convert an XML string into JSON, or to convert a JSON string into XML. We will build out the templates from the Nintex Workflow 2013 Software Development Kit. In a previous post, Create a Custom Action for Nintex Workflow 2013," I looked at creating a custom action that calls the Merriam Webster
Did you know you can create a custom action in Nintex Workflow 2013 using Visual Studio and the Nintex 2013 Platform SDK. With a custom action, you can:insert your function into a Nintex workflow pass data from the workflow into your function return information processed by the function to the workflow where it can be used by workflow actionsThe process of building out the custom action, deploying, and testing it takes some time. My record time so far is about 10 hours (while plugged into headphones, drinking a steady flow of black coffee and Coke 0, and not talking to anyone.) So settle in when you're ready to tackle this approach and brew up your favorite coding beverage to help you along. Although I provide an example Visual Studio solution of a custom action, this topic will walk you through the process I used in building a custom action using the Nintex Platform SDK. In creating your own custom action you will need to read the comments in the code templates to get all of the detai
KBT145392PRODUCT: K2 blackpearl 4.7BASED ON: K2 blackpearl 4.7 NOTE:This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties. LEGACY/ARCHIVED CONTENTThis article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.IssueWhen opening a SmartForms Client Event within Visual Studio or K2 Studio, the following error message appears: "SourceCode.HostClientAPI at SourceCode.Hosting.Client.BaseAPI.SCConnectionStringBuilder.ParseConnectionString(String
