News

This blog post will kick off a small series that I have in mind about how Foxtrot RPA and Nintex Workflow Cloud are Better Together. The intention is to provide ways to integrate the tools until we get built in functionality on both ends.  I will focus on ways to do this using each tool’s built in functionality, rather than any extensibility capability, to emphasize the “no code” philosophy that Nintex aims for. I will try to update all posts in this series with links to other posts for easy reference. Starting a Botflow from a Workflow (with an Email) Workflow Waiting for a Botflow to Finish-------

I am sharing one of the possible ways to Trigger Foxtrot RPA from Nintex Workflow Cloud. Before we get into the scripts on how to do that, maybe it's a good idea to explain a bit further in the following paragrah, on how from the architecture perspective this is done. ArchitectureAssuming you have a troop of robot soldiers (i.e. FoxBot) lead by a commander (i.e. FoxHub), ignoring the number of soldiers you need to have to form a troop, in our scenario it could be as little as 1 or 2. Since the army is deployed to the battlefield, the location of the army is changing (i.e. without a fixed IP), we are not able to reach out to the Commanders to send orders. Since we are not suppose to enter the military zone, central general office can only use special communication where messages are being broadcasted over the encrypted radio frequency, and the army should have worker on duty to pick up and decrypt the message(s). As

Part 1 - Overview Part 2 - Accessing Your Tenant Part 3 - Users and Roles Part 4 - Adding Custom Connectors

Newer versions of Nintex Forms* use the modern People Picker control by default.*Used by Nintex Forms 2013 (2.2.0.0 and higher) and Nintex Forms 2010 (1.4.0.0 and higher). You can import the legacy People Picker control for use with these versions of Nintex Forms: Nintex Forms 2013 (2.2.1.0 and higher) and Nintex Forms 2010 (1.4.1.0 and higher).To import the legacy People Picker control 1.       On the Central Administration home page, click Nintex Forms Management.2.       On the Nintex Forms Management page, click Manage Form Controls.3.       Under the Form Control Types table, in the I

 Nintex workflow designer and Nintex forms designer looks for the servers running Microsoft Sharepoint Foundation WebApplication Service. This also applies to Sharepoint 2016 and 2019 servers setup using Min-Role. If the server has this service listed as "Microsoft Sharepoint Foundation WebApplication Service" running , it is considered as a Web Front end and handles the user traffic and needs to be licensed.   For example, if the workflow designer is loaded from a server running the Microsoft Sharepoint Foundation WebApplication Service and it is not listed on the Nintex workflow license then you would recieve an error that this server is not licensed. This applies to Nintex Forms Designer as well.  Here's a screenshot of Nintex Forms Designer being loaded from a server that is not listed on the License.  

We often see requests of how to pause a workflow for less than 5 minutes. Until now this has not been possible as the pause action relies on the SharePoint Workflow Timer Job to wake the workflow instance back up (occurs every 5 minutes) after the indicated amount of time. Utilizing PowerShell you can effectively pause a workflow all the way down to 1ms. While a PowerShell script is running it will hold up the progress of the workflow until it completes. To set this up you simply need to set the PowerShell action to execute this command: PowerShell Script [System.Threading.Thread]::Sleep(20000)  Note: 20000 would be a 20 second pause. Here is a screenshot of the action blocking fo

This is a simple trick that I've been using for a while that allows you to have some of the Draft capability without having to turn on Content Approval and versioning. Which let's be honest is a little much in some cases. The trick is to use 2 buttons on a form, one "Save as Draft" the other "Save and Submit". In the list, create a hidden column and call it "Draft".  This column needs to be a "Single line of text" field (It doesn't need to be hidden this is just my preference.) Now lets configure those buttons.Firstly let's configure the "Save as Draft" button. Under 'Advanced' connect the button to the new field 'Draft'Once you have connected that, type "yes" into the field 'Value returned'

If you wanted an action to do something that is not original provided by Foxtrot actions, what will you do? Well, I came across this challenge shared by a partner questioning if Foxtrot can call an external function provided by a dynamic link library file. The answer to me is obviously yes as you may use the advance actions such as C#, VB.NET, VBScript, etc. This is what i am going to share providing a step by step instruction on how I did that using the VBScript action of Foxtrot. First thing first, I don't think you should take any DLL and include it in your project without knowing the source, that would be too risky to do that. So we going to start building a simple dll for the testing purpose, and later to include this dll in our VBScript action call. 1. Create a C# Class Library project with your Visual Studio. I named my project FoxFunctions as captured in the screen below

Since my previous sharing on Why Should I integrate Nintex Workflow Cloud?, I've been thinking to invest more time in giving additional example(s) on how I have used NWC API to integrate the workflow into the project I have been helping out for a partner. As the project is still in stealth mode, I thought maybe I can still share pieces of concepts or works we have done bringing over the NWC tasks to a custom portal built on Node JS. Nintex Workflow Cloud has been a great platform for us to automate business processes, due to it's focus not as an end user portal to host business data. Integration scenarios always brought to attention on how to leverage the NWC workflows in a custom portal. In this article, I am trying to share an actual example on one of the projects using Node JS. The portal's events of adding

The Office 365 REST API provides a very useful way to interact with SharePoint data from any system able to create REST API requests. And one of those systems is our beloved Nintex Workflow for Office 365. In this post, we'll see how to use the Office 365 REST API to create SharePoint lists from a Nintex Workflow.As in every REST API request, the first thing you need to do is to have a look at the reference documentation of that API, to understand the list of requests available and the values you need to provide for those requests. In our case, you can start with the SharePoint REST API documentation in this link.Now, let's focus on the request we want to create. The following example, taken from the previous link, shows how to create a list: 

When deploying Nintex App Studio apps to iOS there are really good walkthroughs in the following posts.Generating a distribution certificate‌Generating a provisioning profile ‌Introducing Nintex App Studio‌ But I use a regular developer account with Apple when testing an App before deploying it using the Apple Developer Enterprise Program  There are very minor changes to the steps to follow when deploying the app using a non Enterprise account. The simple ben

Assigning a task in Nintex Workflow Cloud or NWC is a great way to speed up the part of a business process where a human interaction is needed to get to the next step. Examples like approvals for quotes or verifying/capturing data are just a couple examples where this action can be a great value.  Once dragged onto the canvas you can select what type of task you want to run.  Express approval will allow you to use a '"lazy approval" process where one can simply respond to an email to interact with the workflow. This is great for approvals (for example a leave request) but can really be used for anything where a free will decision is needed. 

Using Dan Stoll‌'s excellent walkthrough in Nintex App Studio for the win‌ I started looking at the new custom content functionality in Nintex Mobile App Studio.  It was all going absolute great guns; I had a custom home page with links that would open various apps on my phone (to call, text, read documentation etc) but I had this rather odd issue when I clicked on the sms link that was constructed similar to that below:<p><a href="sms:+1-111-222-3333&body=Love%20your%20work." class="button">SMS JOGA HQ</a></p> My android phone (used for testing only - I am an apple girl through and through) kept giving me this error once I returned to the app from sending a message:I did a search on here and on Google for

A while back you may have heard that Nintex aquired Enablesoft and now offers a RPA solution with Foxtrot. If you have not, go read this article, we'll wait. Since then we have been busy getting Foxtrot integrated with all of the other great products that Nintex has to offer and some of them are being released next month! Here is a quick breakdown of all of the new updates coming to Nintex Foxtrot! BrandingBranding may not seem that glamorious, but have you ever used a set of products that did not feel consistent or look like they all belonged together? Well we wanted to make sure that Nintex Foxtrot got the same amazing look and feel that our other products have so we updated them. You can now change the theme of your Nintex Foxtrot tools to the Nintex colors! Also,

LIke all good stories, this one has a beginning, a middle and an end. In this case data capature, data process and data reporting. facilitated by the Nintex platform for Microsoft Dynamics 365.Before we can jump into the data capture, we'll need to set a foundation for the solution. A connection to a Dynamics 365 environment. Pretty quick and easy to do here in Nintex Workflow Cloud. Setup a connection as follows:Give your connection a sensible name; add the CRM tenant URL; login with relevant credentials - remember, the account you use here relates to the levels of information y

So one of the questions I am often asked is from folks that would like to automate a process that is task driven but does not necessarily conform to a simple Approve / Reject set of outcomes. In Nintex Workflow for Office 365 there aren't the same task actions as there are on premises. That being said, you will just need to roll up your sleeves, build a new content type and you'll be all set. Not sure exactly how to go about building that content type and configuring the Assign Task action to create this single outcome effect? Not a problem. Below are the steps necessary to make your dreams a reality!* *Please note that you will need appropriate site owner permissions to accomplish these steps and I cannot guarantee ALL of your dreams will come true. At least the ones that involve tasks assigned with Nintex Workflow.  Navigate to Site settings

Description:  How to add Adobe Sign text tags in the Nintex Document Tagger for electronic documents requesting information and signature to use in a one step process. Scenario: Customer X has an incorrect address on-file with Company Y and needs Customer X to update this information.  Company Y sends Customer X an electronic document requesting for their most current address and signature.  Let's walkthrough the following scenario of how we would set this up within our workflow. HOW TO SETUP TEXT TAGSDocument TemplateOpen your template where you will want to add your Adobe Sign text tags. Once tags have been added, save file to your document library.                                           TEMPLATE

 Looking for the old Product Downloads page? 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 email to access Community, you can use the same email to sign into your Customer Central site. If you do not have access to Customer Central, please reach out to your Nintex administrator and they should be able to add your user to Customer Central via the Contacts section of the site. If you have any questions or feedback, please email

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.