Skip navigation
All Places > Getting Started > Blog > 2017 > February

Have you ever gained sudden ownership of an abundance of Nintex workflows and forms? I have - over 350 of them - huge, undocumented monoliths, tiny stand-alone notifications - it's a bouquet of Nintex goodness and for the most part I have wrangled the workflows into a state of subservience. Generally, I only interact with these when I need to: maybe there's an error, maybe there's a change request - that's when I swoop into action.


But this story isn't about when things go well.


This is a story of how on February 21st at 3:28PM, the click of a vague button on an inconspicuous page by a well-meaning end user cost me over 5 hours of work.








What Havoc Did This Cause?


This workflow resets all of the document number references for a project. This means that all of the document numbers generated after 3:28PM were erroneous and had to be changed via individual workflows on each record, which also have their own sub-processes to run.  Oh, and, I didn't find about this until the next day.




How Can This Be Improved?


Ideas that would've made this button less tempting:


  • A title of the workflow that this would trigger.
  • A description of what the workflow does.


Some ideas that would've prevented this issue:


  • Audience targeting. This is in a web part, it could have been visible to only particular groups.
  • Limiting which workflows end-users can run.


Ideas that would have lessened the impact of this issue:


  • A notification at the end of the workflow to let the Nintex Admin know when this has been run, since it should be done only a few times a year. The faster we can react, the less mess there is to clear up if it's run accidentally. 
  • A requirement to gain permission at some point in the workflow from the Nintex Admin or another user to reset it, with a description of what will happen if "Yes" is chosen.
  • A workflow that undoes whatever that previous workflow did. (In my dreams.. maybe some day!)


Anything Redeeming About This Approach?


The requirement for a "Yes, I understand" to be checked to prevent accidental "Start" clicks is a great idea when you have that big tempting start button out on a page.  I also think that having a simple way to run daily workflows, like this one, is great. ... Daily workflows, mind you. Not annual ones. 



Final Thoughts: Don't Cry; Laugh!

Admittedly, when I figured out what had happened ... I laughed really hard. The fact that this button existed in the first place and that the end user not only clicked it, but also checked the "Yes, I understand" box without any idea what it was... you have to admit, that's pretty funny! 




I'd love to hear your thoughts! Have any of you ever run into some questionable workflow practices? 

The other day I overheard someone needing to encode/decode a URL string inside of a Nintex Workflow (and again at the Nintex 2017 InspireX during a presentation on Azure Functions). Presently this is a non-trivial task (more information here), so I decided to simplify the process a bit by creating a set of REST web service endpoints that would handle the encoding/decoding process.

These web services can easily be called from the Nintex Workflow Web Request actions in On premises products as well as O365.

To use these web service endpoints, configure a 'Web Request' action to POST application/json content to these endpoints:



To use the endpoints POST the following JSON:

{"value" : "Url To Encode/Decode"}


In our organisation we have the nintex workflow actions tightly controlled as follows:

  • Untrained users:  no access to any actions
  • Trained users:  access to subset of actions
  • SharePoint support users:  full access to all actions

The reason for this is governance (which I will get round to blogging about one day I am sure).  We do not allow the trained users any actions that can loop that with poor configuration could maybe bring down the environment or affect the performance in some way.



These trained users almost always have a requirement for a "reminder" workflow of sorts, to notify people when a document is due for review, or if a task is outstanding and x days overdue (like many users on the community).  Anyone on the community with this requirement will have been sent by me to my blog post Site Workflow - Document Review Date Approaching Reminders or to the solution on Nintex Xchange™ Document Review Reminder Process.  However, these users are not allowed any looping actions so are unable to use the for each and so, at the moment, have to come to SharePoint support staff to get the solution they require.


Solution - Site Workflow UDA

Inspired by Nintex Xchange™ and a UDA solution posted by Vadim Tabakman I decided to see if I could create a site workflow UDA whereby the UDA could do the looping for the user and it therefore wouldn't matter that they do not have access to the actions inside the UDA.  This is one of the best things about UDAs - it's a fantastic way of empowering your users to do something cool without "letting" them develop it themselves.  This way you have control of these more complex actions and can be confident that the environment won't be impacted by their configuration.  Well, if they do impact environment performance, then you know who is to blame - haha.

I called the UDA "Notification Date Reached UDA" and configured it as follows:


List NameTextInputThe name of the list that the items need to be pulled from when meeting the date specified, I.e. "Procedures"
Date Field NameTextInputThe name of the date field in the {List Name} to compare with the specified date
Email SubjectTextInputSubject of email to be sent
Email To FieldTextInputThe name of the column used to locate the recipient of email
Email MessageTextInputBody of email to be sent
ErrorTextOutputTo be used to store any error messages
Number of Days AfterNumberInputIf date comparison is not for today, but for x number of days after the event
Number of Days BeforeNumberInputIf date comparison is not for today, but for x number of days before the event



vCollReturnedIDsCollectionInside the UDA, the query list of the specified list name will return 0 or more items and store the IDs into the collection
vDateComparisonDate and TimeThe date calculated based on the parameters above to compare with the list and filter the returned items
vTextCurrentIDSingle line of textThe current item in the collection (stored as text for the CAML query) used to query the given list name to find the {Email To Field} value
vTextNotificationContactSingle line of textUsed to store the value for {Email To Field}



I do some checking of the "number of days after" and "number of days before" parameters.  If both are zero then it would indicate that the user would like to match for items where {Date Field Name} = today's date.  So in this instance I set variable value vDateComparison = Common:CurrentDate.  If both parameters are not zero then it would imply that the user either wants to send a notification x days before the {Date Field Name}, or x days after.  This logic does just that:


OK, so now we have our comparison date I go ahead and query the specified list matching where the specified date field = specified date.  I do this using CAML query and return the IDs into the collection variable vCollReturnedIDs:

Using for each to loop through my collection, I use the current item in the collection (vTextCurrentID) and query the specified list again to get the specified {Email To Field}. This is again done with a CAML query as follows and outputs the variable vTextNotificationContact:

Still in the for each I send an email to the variable value returned using the subject and message body specified in the parameters.  Job done.


Using this UDA

To use the UDA I created a brand new site workflow, added the UDA and configured it as follows:

and the list looked like this:


When I run the site workflow today (20/02/2017) I get three emails!




Ok so this is early days and there are many! 

  1. The fact that I need to use the internal names in my parameters (because of the CAML query).  I don't want these users to loop for fear they don't understand looping, so do I think they will know how to find the internal name of a column?!
  2. This is only bringing back some dynamic data from the list - the rest is static.  This could be extended to suit and pull additional information about the item due for review - but there doesn't seem to one size fits all approach when I have no idea what sort of list it will be used on
  3. At this point I have only set it up for either a date before or a date after.  In reality most people want to remind before the date, remind on the date, and remind after the date!  This can be easily overcome.
  4. (enter yours in the comments)


The solution will be posted on Nintex Xchange™ shortly.

In this blog post I'd like to provide a step-by-step guide to build a dynamic repeating section with Nintex Forms that can be used in order forms for example. Furthermore this guide will include a solution to check the total price of an order against a predefined budget. The focus of the whole solution will be on the Calculated Value control, the Lookup function, Runtime functions and Rules. I've created this guide by using Nintex Forms 2016 (On-Premises), but it should also work for Nintex Forms 2013 (On-Premises).


In the repeating section the user will be able to choose from a specified list of products, whereby the price of the product, the overall price based on the desired amount and a picture of the product will be shown. At the end of the form the user will see the overall price of all products and furthermore will get an information whether she or he is still in the defined budget or not.


At the end the form will look like this (Display mode):


Creation and configuration of the needed lists

First create a list to store the single products, this list should be called "Products" and it should look like this:



Name = Single line of text

Price =  Currency

Picture = Multiples lines or text (Plain text)


Add another list called "Product orders", in this list the orders will be created and saved. The list looks like this:



Title = Single line of text

Total price of order =  Currency

Order = Multiples lines or text (Plain text)


In a real world scenario there would probably be more columns to store additional information, like information regarding the customer/user.


General settings and configuration of budget definition

Start to edit the form in the "Product orders" list with Nintex Forms. Remove all controls that are not needed, change the background color to white (#FFFFFF) and change the grid cell height and weight to 20 pixel.


Add a "Label control" at the top of the form and insert "How much money do you want to spend?". Furthermore add a "Single Line Textbox" control right next to it. Name it "Budget", change the default value to "0.00" and set the data type to "Currency".




Configuration of the repeating section

This is how the repeating section should look like at the end:



First add a "Repeating section" control. Name it "Order", connect it to the "Order" column in the list and change the "Text for add row icon" to "Add additional product".



Add a "Label control" and insert "Position". Furthermore add a "Calculated Value" control below. Name it "Position", in the "Formula" section add the following runtime function currentRowNumber().




Add a "Label control" and insert "Product". Furthermore add a "List Lookup" control below. Name it "Product" and configure it in the way that it displays all items that are stored in the "Products" list.




Add a "Label control" and insert "Amount". Add a "Single Line Textbox" control below. Name it "Amount", change the default value to "0" and set the data type to "Integer".




Add a "Label control" and insert "Product Price". Furthermore add a "Calculated Value" control below. Name it "ProductPrice", in the "Formula" section add the following runtime function lookup("Products","ID",Product,"Price"). This function will display the price (List "Products" --> Column "Price") of the chosen product in the "Product" control. Set the "Save as data type" to "Currency" and the "Value prefix" to "$".


If you want some more information regarding the Lookup function take a look at this blog post by Eric RhodesTechRhodes | Blogging about SharePoint, Nintex and life in general 





Add a "Label control" and insert "Total Price". Furthermore add a "Calculated Value" control below. Name it "PriceTotal", in the "Formula" section add the following formula ProductPrice*Amount. Set the "Save as data type" to "Currency" and the "Value prefix" to "$".




Add a "Calculated Value" control and name it "Picture". In the "Formula" section add the following runtime function lookup("Products","ID",Product,"Picture"). This function will display the picture (List "Products" --> Column "Picture") of the chosen product in the "Product" control.



At this point many thanks to Steffen Hennig for the picture solution! You can find it here: Populate a Calculated Value Field with HTML/Picture 


Configuration of budget check

Add a "Label control" and insert "Total price of your order". Furthermore add a "Calculated Value" control right next to it. Name it "OverallPrice", in the "Formula" section add the runtime function sum(PriceTotal). The "sum" runtime function returns the result of all the values in a set being added together. Set the "Save as data type" to "Currency" and the "Value prefix" to "$".




Add another "Calculated Value" control right next to the "OverallPrice" control, name it "BudgetCheck", in the "Formula" section add the following runtime function If(OverallPrice>Budget,"You spend too much", "You do not spend too much").



If the defined overall price of the order in the "OverallPrice" control is greater then the budget in the "Budget" control, the calculated value will be "You spend too much", if this is not the case it will be "You do not spend too much".


To highlight the result add two rules on the "OverallPrice" control and configure them like that:



After a little bit of formating the whole form should look like this at the end:



Of course there are many more things that could or must be done to get a perfect order form, like adding validation rules (i.e. if the overall price is greater then the budget) but I hope this gives you a good starting point and has provided you some tips on how to implement your requirements regarding such a form. Maybe I'll add some more features in the future ;-)


If you have any questions, found an error or have a better way to accomplish this, feel free to contact me! :-)


nintex lookup control lookup function calculated value repeating section runtime functions order rules forms

Nintex form - Incorrect validation rule making Attachments disappear (or overwritten).

I had an interesting issue raised today by one of the customers I deal with regularly and thought I would share here.


Why is the attachments added to the list via the nintex form being removed or over written?

After wracking my brain (and google) I did not find an answer.

Taking a step I went through the form validation rules I found two of them had been incorrectly configured (using the isNullOrEmpty Runtime Function).

INcorrect configuration of isNullOrEmpty runtime

Once correcting the validation rule, the attachments stayed in the form / list.



I hope this helps others out there who are struggling with this.

E-Signature technology has been around for years, allowing people to get documents filled out and signed in no time. When organizations consider e-signatures, they’re looking for a solution that offers authentication, security, and even workflow customization.


Our latest  eSignLive for Nintex SharePoint connector to automate your workflows. Pairing electronic signatures with Nintex removes paper from your existing workflows by adding e-signatures for a fully end-to-end digital approval process. Whether you need an NDA or an HR business contract signed, eSignLive for Nintex SharePoint lets you obtain secure and compliant and 100% legal e-signatures for all of your documents.


The eSignLive for Nintex SharePoint connector is currently available for download.


Check out how easy it is to add e-signatures to your workflows:


In this example, I’ll walk you through how you can add e-signatures to an existing HR on-boarding workflow.


  • Create a document template you would like to use to send out for e-signature in your eSignLive Sandbox account.
  • Access the Nintex Workflow Designer in SharePoint, then drag-and-drop the e-signature actions directly into the workflow



  • When your workflow gets to the point where signatures are required, Nintex Workflow triggers the document to be sent to your signers.


  • Once the document is sent, each signer receives an email asking them to e-sign. eSignLive works across all devices. The software’s responsive design adapts to any screen, so signers enjoy a seamless experience on their preferred device.

  • After each person has signed, eSignLive embeds the digitized signatures and audit trail directly in the document. This ensures a vendor-independent record that can be verified and stored anywhere. eSignLive then automatically archives the completed document in your SharePoint library.



Interested in adding e-signatures to Nintex Workflow for SharePoint? Download eSignLive for Nintex SharePoint today to fully automate your business processes. Check out the video below to see how easy it is to use eSignLive with your Nintex SharePoint workflows.


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 benefit is that I am just using an individual account, and can only deploy the app to a select few devices before the app goes out to the rest of the user base using the Enterprise profile. NOTE: you must use an enterprise profile to deploy for production purposes.


In using the steps outlined in the linked articles, you get the certificate the same way but in the provisioning steps you get to step 10 and instead of selecting In House under Distribution you select Ad Hoc.


Then continue the steps 11-14 (14. On the Select certificates page, select the certificate you want to include with your provisioning profile.) and before you finish you are asked to select a device.

Select all the devices you want to deploy the app to and select Continue then it will be generated. Then download and use this provisioning profile.


Adding Devices

So in order to get this to work you have to first add the devices to the account to test with. To do this,

  1. Under Devices select All
  2. On the upper-right, click Add ( + ).
  3. Provide a name for the device and paste the UDID of the device
    1. To get the UDID of your device: 
      1. Launch iTunes and connect your iPhone.
      2. In the right pane, locate the information about your iPhone, including its name, capacity, software version, serial number, and phone number.
      3. Reveal the Identifier by clicking on Serial Number:.
      4. Copy the Identifier to your clipboard by choosing Edit → Copy.



After finishing the steps as normal by uploading the provisioning profile into App Studio, I deployed the app, got the email of the finished deployment, and downloaded the app as normal.

I have been creating several forms in Nintex Mobile in my O365 tenant for some time now and wanted to add some flare by adding icons the forms. My initial attempts prove somewhat difficult so I wanted to post my results and steps taken to add icons more quickly the next time I need to. 


As of this writing, (So yes, I expect this behavior to change in future updates to Nintex Mobile App), the issue I ran into was not being able to upload images to my Site Assets library on my SharePoint site and use those icons within the app. What I found was the app does not use the account that is used to log into the tenant to access the image. So this required me to upload my images to public facing locations so the app could essentially anonymously download. 


So this was the next hurdle, I don't have a public facing website I can randomly upload images to. But I thought, I do have OneDrive, DropBox, and a Google account, can't I use those? What I found out was Yes, and No.



First off, make sure your image is a 150x150 PNG file. After you upload it to a web facing location, you can reference it in your Nintex Form settings, under the section Nintex Mobile App Settings, and provide the URL for the icon and publish.


Using Google

If you upload a file to your google drive you can share it in many ways. If you upload a file, then click Share, you can set it to Anyone with the link can view.

This gives you a url similar to

This is a public image now, but it doesn't work. Why? Because it isn't a static image. If you go to that URL, you get an in app view within google docs like this,

So in order to make the image a static file, that can also be used on public sites, you can use the Google drive API. Which is using the following setup

Now the image shows up in my mobile app next to my forms! Also, when I navigate to this url, the browser only shows the image, not within a website like before.


Using Dropbox

Using dropbox is exactly like using Google Drive. You upload your image, share it so that anyone can view, and you copy the provided URL. - in App, doesn't work - Works!!

But the provided URL is seen in line 1 above and displays exactly like Google Drive and is not a static image. But using the Dropbox API and in the format in line 2, the image will appear in the browser and my Nintex Mobile App!


Using OneDrive

To use OneDrive, go to the OneDrive website. You might need to sign in with your Microsoft account.

Pick the file you want to embed by selecting the check box in the upper-right corner of the file.

Tap or click Embed on the top of the page, and then choose Generate.

Copy and paste the URL into the form settings.

The URL you will get using Embed will format like the following:

When I didn't use the embed method but simply shared the image to anonymous, I could get to the image but the in app behavior is the same as the previous two. 


Images within Forms

Just one final note, I was able to use some of the "in app" URLs to show images within my forms, but not as icons for my forms. Below is a screenshot of one of the games we will see at InspireX2017.


Free Text Search of SQL

Posted by greenawayr Champion Feb 6, 2017

A slight variation on Retrieve cities from a database post by Pamela Denchfield where Pamela uses a dropdown to create a cascading dropdown filter on a SQL Request control.


We have a lonnnnnnnngggggggg list of suppliers who our users can select from when they want to request a new product.

We've cleansed this list as best we can but it still numbers thousands and it's not fun for our users to have to scroll through the dropdown to try and find the needle in the haystack. Because there's no set choice of parent values that would allow us to do a cascading dropdown, we want to let our users search for the suppliers.


First add a text box to the form and give it a name, in our case I'm it "SupplierSearch".


Then we simply add our SQL Request Control to our form

and fill in the db details

The important part for us is the Query.

select name from vw_sp_CleansedSuppliers WHERE name LIKE '%SupplierSearch%'

We're just using the LIKE operator and wildcards either side of the reference to our text box to give our users the best chance of returning results.


So now the user can type a value in the text box and then select the dropdown box and get a much more succinct list of values.

The ability to define our SQL query with this control and insert references from our control gives us very valuable and flexible tool for presenting users with SQL data.


I'd be interested to hear of any other techniques people are using on this control to make their users life easier.


Anonymous Form Submission

Posted by rbachmann Champion Feb 6, 2017

SharePoint is a great tool to collaborate and track document changes. 

But, have you ever had the requirement, that a form should be submitted "anonymously"?
Some customers know the princip of inboxes, where you can place a complaint anonymously.

Since this is a bit "not featured by design" in SharePoint, I would like to share my solution approach.
(There are others, as you can read here: Anonymous Form Submission but in my case, I don't want to delete submitted items.)


First, I create a new Site-Workflow.
For this scenario, I need two variables. One is for the complaint-message and one is an optional textfield, where you could enter your name, if you like.

(Please note: "Show on start form")


Secondly, I edit the start form with Nintex Forms. The fields are connected to the corresponding variable.


Thirdly, I insert two Workflow Actions. The Action Set is needed to run all child actions using the credentials of the user who published the workflow.


And that's it. In my case, I use the Nintex "Start Site Workflow"-Webpart to embed the form. All submitted items will be created by the account who published the workflow. So be careful not to use your personal account.



As there is some mystery to where Nintex Forms are stored in O365 I have written a short document explaining how to find the elements that are created when you publish a Nintex Form to your list. In the unfortunate event where your Nintex Form has somehow become orphaned you can use this guide to either delete the form from the list manually or recover the form saved at the content type level.


What we store when a form is published


When a Nintex Form is published three things are created on your list/site:


1) The content type form link

When a form is published links are added to the content type at the list level. This is used to launch the form when you attempt to create a new item or edit/view an item of the same content type. These can be found using SharePoint Designer by navigating to the content type on the list:


2) The run time form

When a Nintex Form is called, the NFForm.xml file is used to render the form. This can be found inside the content type at the list level using SharePoint Designer:


3) The design time form

When you open a form in the Nintex Forms designer the form is rendered based on the file stored in the Nintex Forms hidden library named "NintexFormXML". You can also find this file using SharePoint Designer:


Finding your saved form in the NintexFormXML folder:


Unfortunately the names of the files stored in the NintexFormXML are not particularly user friendly. In the event you need to find an orphaned form in the NintexFormXML hidden repository, how do you determine what form is the form you published? To start, each file in the NintexFormXML hidden library is created using the following format: ContentTypeGUID_listGUID


You can find the content type GUID and the list GUID which may be difficult for some or you can simply review the below methods to find the form file that is being stored in the repository for the list in question.


Method #1 Use the Content type URL


Navigate to the content type the form is published to in the list using SharePoint designer:

You will see there are links under the "Forms" section for the Content type that are used open your Nintex Form:

The link above contains the following URL:

The highlighted text is the important piece to note here as it reflects the filename for the form that will be loaded when opening a form in the Nintex Forms designer.


Method #2 Use fiddler to track the request


If for whatever reason you are unable to find the links on the content type you can also find this using fiddler.

While fiddler is open, open the Nintex Form at the list by clicking ‘new item’ and look for the NFLaunch.aspx request. You can see the structure for the call for in the NFlaunch.aspx request below.


Here is the GET request for that call:

Again we find the same string of text in the content type URL as we do in the above call:


That string is in the format we are looking for in side the NintexFormXML hidden library.


To find this file all that we have to do is navigate to "All files > NintexFormXML" in SharePoint designer:


Unfortunately, you cannot export this file, however you can delete it. This file is useful in cases where we have a “stuck” form on a list that cannot be edited and we need to delete the design time form so we can load the Nintex Forms designer and republish the form. 


Final Notes


You can recover a form xml file by navigating to where the form stored (same as above) using SharePoint designer:


You can download this NFForm.xml file and import it to “rescue” a form that is not recoverable by normal means.


Please let me know if you have any questions in the comments below.



Andrew Beals


Panels never change.


But what DOES change is who can see them, and when. This is what initiated my most recent client request: "Make sure that when the Manager goes into the form, that they can only see the Manager panel, and the Software panel - and not the other two." 


"Simple!" I replied. Our panels are JavaScript controlled beauties; a sight to behold. Easy to hide using Nintex rules.


I spoke too soon.


"Also," they began, "Ensure that the Manager is taken directly to the Manager panel when they open their notification link."


My endless Googling and Nintexoogling of "target panel" was fruitless; if nothing else, I hope this blog will cement the words "target panel" forever in the search terms so that I can help future Rhias of the world come to this solution:


Step 1) Determine your code word. For me, it was "managers" and "software". We will focus on "managers" for this example.


Step 2) Ye olde JavaScript. Plop this into your Custom JavaScript settings:


NWF$( document ).ready(function() {
  if("manager") > -1) {


Explanation: This JS looks at the URL, and checks to see if the word "manager" is in it. If it is, it runs the JS function "showPanelManager()" which is what controls our Manager panel.


Step 3) In your workflow, wherever the URL is going to be doled out to a manager, append either:

               a) If after .aspx, add a ?manager (.aspx?manager)

               b) If after other data (such as ID=360), add an &manager (ID=360&manager)


And, simple as that, you can now send your user directly to whichever panel is appropriate to them.


AND ... even if you don't need this ... think of all the cool things you could do by using a URL in this way! Append a word, and magically run ANY function! NEAT.


Any questions? Comments? Let me know! I'd also like to hear of the better ways to accomplish this - I am sure they exist - as well as your ideas for how else this could be used.  


Want a Rota?

Posted by greenawayr Champion Feb 2, 2017

The client had an extensive form that needed to go online to improve the process. It's a variation to contract form that feeds into many external systems. Currently the form is owned by HR and due to poor process management, the data from this form rarely reaches other departments for updating their information, for example IT require the form for updates to Active Directory.


Anyway, a small but fiddly part of this form was to create a Working Pattern control where the user could submit the standard weekly working hours of the employee. The employee might also have fortnightly or even monthly working patterns so they needed to be able to submit more than just a weeks pattern.


The only output required for this in terms of data, was the total hours for the week, as this, combined with other data in the form could be used to calculate the employees annual salary.


It's a fairly simple control, but because there is no such thing as a "time" field, I took the approach of creating dropdowns to allow the user to select Hours and Minutes (in quarter-hour increments) and Lunch break (in quarter-hour increments).

Then calculated values do the requisite formulas to calculate the daily hours and then the weekly total.

The entire table is encapsulated in a repeating section that is limited to a maximum of 4 rows.


It's a simple little control, but I thought I'd make it available to others as it was a little fiddly and time consuming to put together.


Split-screen multitasking

Posted by kimarsde Employee Feb 1, 2017

Nintex Mobile now supports split-screen multitasking for iOS users! 

With the new supported capability, you don't have to choose between having the Nintex app or another app open. Instead, you can have two apps side by side. 


How can split-screen multitasking improve your Nintex Mobile experience? 

Let's say you get an email with information scattered throughout. You need to input information from the email into a form in the Nintex Mobile app. Rather than constantly switching between the email app and the Nintex Mobile app, you can use split-screen multitasking to easily fill in the form.  As the example image shows, you can quickly identify the needed information and enter it in the form all at the same time. 



Example image showing both apps on one screen. The Nintex Mobile app is on the left and the email app is on the right.



For more information on split-screen multitasking, see the Apple article About Multitasking on your iPhone, iPad, and iPod touch and the detailed YouTube video Split Screen Multi-Tasking on the iPad Pro.

Filter Blog

By date: By tag: