Skip navigation
All Places > Nintex Product Blog
1 2 3 Previous Next

Nintex Product Blog

70 posts

In my recent post "Change the default landing page in Nintex App Studio," I used an html page as the landing page of my app (which is quite cool, by the way). Not sure if anyone noticed, but in that example, the title bar showed the file name with the html extension. Dang! That doesn’t look very professional!



No worries, it's easy to change right in App Studio.  We just need to edit the menu item for our home page file and change the title. Just open the app, navigate to the "content" link in the left hand side menu and then select title bar in the list of menu items.  Here you can remove the file extension '.html', so it looks like this:


Now, the title bar just displays 'Home'.


Small detail but believe me, everyone in my demos asked about it. Hope it helps!


And by the way, I wrote about this and a few related points in another recent post, "

Customizing Menu Items in your Mobile App." I think you'll find that post helpful too.

Did you know that Nintex Mobile supports more than a dozen powerful ways -- which we call "controls" -- to enhance your forms? In this post I'd like to focus on just one, the attachment control. 


This is powerful because if you attach an image to a form and annotate the image, the annotation helps tell a better story by providing user-defined context. For example, in the insurance industry, an inspector could take a photo of a machine that has failed and annotate it with a arrow showing the part that has failed.  This helps anyone reviewing the image to better understand what the information is being conveyed.  


To start using this feature, just publish a form for your mobile device using the control called “Attachments” in the “List Columns” section.


Now that you know about this feature, you have the ability to enhance processes that involve uploading images to be analyzed by other people in your company or external actors such as an insurance auditor.


In this sample we have two controls with this functionality.




   Once you tap on the control to upload a new file, you will see the options to select.



  • For Camera and Video, you can get a photo or video right at this point in the process.
  • For Gallery and File, you can select a saved file/photo/video from your device gallery including Google Drive, Google Photos, or any other storing tool on your device.

Once you get a photo, you have a variety of tools for editing it. For example here below I added “Text” and “Draw.”




   Here is the complete toolbar that you can use to edit your photo:


For more information you can read the help files about the control! 

In my last post Did you know: Change the Default Landing Page in Nintex App Studio I showed you how to customize and organize the content of your mobile app. In this one I'll focus on the app's look and feel and show you a couple of tips to make it look more professional.


1. Change the name and icon of the menu items: In every menu item in the Content Section, you can select the pencil icon to change name, icon, or both. Following my example in the previous post, you can use this to name the html item "Home" and get a proper icon for a home. For another example, you can make forms and tasks more user-friendly by giving them customs name like "My requests" or "My tasks."


2. Change the Form and Task Listings: From the Forms and Tasks menu items, click Add Filter to tell App Studio to include (or exclude) specific forms and workflow tasks from among all the forms and tasks we have in our Nintex environments connected to this app.

From the same pop-up menu we can change the attributes displayed for every form and task. Again, clicking in the pencil button, you'll find the option of changing Icon, Name, Category and Description. This will override the previous attributes of the form/task.

As you can see, with just a couple of changes, your mobile App looks less generic and more purpose-built. Have a look at the below!

One of the key features of Nintex Forms is the Rules builder experience. It helps business owners and IT professionals create and apply rules and advanced logic to transform a simple, static form into a dynamic one that changes based on business rules and user inputs. Dynamic forms improve the user experience and increases engagement by reducing the time for data entry while improving accuracy.

Nintex Forms for Nintex Workflow Cloud was introduced in September 2017 with significant fanfare and we are now happy to announce new enhancements to the Rules builder design experience.

For one thing, we’ve replaced the inter-modal window with a full-modal interface. This provides more area to manage multiple rules and delivers an improved look and feel.

In addition, we’ve added a new “When form load” rule and updated the existing “On form input” rule. Now, when you select Rules builder, you see those two options:


Nintex Forms for Nintex Workflow Cloud Rules builder


What’s new: “When Form Load” Rule - This rule type executes when the form loads, meaning the only run once. As an example, you could set default values for controls.

Additional to the Form Load rules, you can now read a query string parameter from the form URL and initiate additional conditions. So, if you have a COUNTRY as a query string parameter, and the value was AU, you could show additional fields, set values and hide other fields specific to Australian form participants.


Nintex Forms for Nintex Workflow Cloud "when form loads" rule


What’s improved: “On form input” rule. Introduced in September, “On form input” is a category of rule that can be applied to influence interaction of the user with the form. Although the look and feel of this rule hasn’t changed, the “On form input” rules, now exist in their own section of the Rule Builder.


Nintex Forms for Nintex Workflow Cloud "on form input" rule


This recent release also provides additional rule parameters supporting email control (adding: contains, does not contain, does not end with, ends with) and short text control (adding: contains, does not contain, does not equal, equals).

Like other Nintex offerings, the Rules builder in Nintex Forms for Workflow Cloud is straight-forward and intuitive. If you haven’t had a chance yet to build a form in Nintex Workflow Cloud and experience the Rule builder for yourself I’d like to show you how easy and powerful it is.

  1. First, let’s create a form as a “Start event” in a Nintex Workflow Cloud workflow. You do that with these steps:
    Click on the "Create workflow" button to open the drag-and-drop designer
  2. Click on the "Start event" and select the following options:
    1. Connector: Nintex
    2. Event: Form
  3. Click "Design form" and you're off! 


You’ve now created a Nintex form as a workflow start event.  Now you can configure the form by dragging controls on to your design canvas.


Select the link at the top for "a>b Rules".  Configuring a rule takes 3 steps:

1. Name - describe your rule
2. When - select a field on the form and choose a condition to set it
3. Then - this is what will happen when the chosen condition is met


Nintex Forms for Nintex Workflow Cloud Rules builder


Now that you have your rule configured, you can test it to make sure it works. In Nintex Workflow Cloud, it’s easy to do so. On the form designer, select "Preview" to see the form and confirm your rule is working as expected.


Nintex Forms for Nintex Workflow Cloud Rules builder preview


We encourage you to experience the enhanced Rules builder in Nintex Forms for Nintex Workflow Cloud for yourself.


We continue to introduce new features to Nintex Forms for Nintex Workflow Cloud. There is a great blog post on Nintex Community that describes the new Forms “submit” options in Nintex Workflow Cloud as well as a blog post for the new form File Upload control.


You can stay current and learn more about what’s new by frequenting the Nintex Community Public Roadmap.

The Nintex product managers want to talk with you!


You can schedule a one-on-one chat with a Product Manager so they can understand what you  are using the Nintex Platform to do, how you're using it, and how we can make improvements.


Just CLICK HERE to pick a day and time!


We still have the Customer Feedback for Nintex site, where you can make suggestions and vote up those you like.  


But we hope you'll take this opportunity to connect directly with us. We look forward to speaking with you!

In the recent release of the Nintex Workflow for Box app, we provided support for getting and setting Enterprise Metadata for a file in Box. To understand more about Box Metadata and how to set it up, you can read this excellent how to guide from Box.


We've added two new actions to the Box Connector that provide the ability to "Get file metadata" and "Set file metadata." These new actions allow you to build workflows that can manipulate the file's Enterprise Metadata as the workflow progresses.


These new actions build on the review process I wrote about in the initial post involving a workflow we built to enable collaboration on the marketing brochure for Nintex Workflow for Box. Imagine we need to manage multiple marketing campaigns across the organization. This could involve multiple pieces of marketing collateral that require review and approval but may not reside in a single folder as they might for a single campaign.


Using Nintex Workflow for Box together with the Enterprise Metadata provided by Box, we could create an Enterprise Template to capture the workflow and its progress. Now, within the workflow design, we can decorate the workflow design with the "Set file metadata" action at various points to help bubble up workflow progress via the Enterprise Metadata panel within the Box user interface.


Box Set File Metadata


In addition, within Box, someone can use the Metadata Template to search across the organization for the status of a specific file.

Search using Box Enterprise Metadata Template


Through the search, users now can view files based on their workflow across the Enterprise, regardless of how folders are structured.


In the near future, we plan to add support for starting a workflow when someone updates an Enterprise Metadata field in a file.

Document Set Forms


We are pleased to announce the release of a new feature for Nintex Forms 2013 with the latest On-Premises Nintex release – read the latest release notes here: Nintex Forms 2013 - Release Notes.


Nintex Forms for SharePoint 2013  now supports the Document Set Content Type.


Note: We will be releasing the update for SharePoint 2016 in the following weeks.



Nintex Forms now allows for the management of the ‘Document Set’ Form (New/Edit/Display) for interaction with the ‘Document Set’ properties.


This will allow you to have more control over your document sets and provide a more consistent end-user experience across document libraries and lists.


To access this feature, once you have updated to the latest version of Nintex, simply locate the document set content type that would like to associate a Nintex Form with. You will then find the option to edit the content type with Nintex Forms as below:


Edit Content Type with Nintex Forms



You can utilise both Classic Forms and Responsive Forms with this new feature:




Classic or Responsive


You can manage the form via your own custom ‘Document Set’ based content types. Once deployed to a list or library you can make further modifications at the specific list level or manage the form at the content type level to push out updates to wherever the content type is already deployed.



Edit List Level Document Set Form





Document Set Form Sample


This has been a highly requested feature on our User Voice site and we would like to thank our community for all their valued feedback.

To submit your ideas for further Nintex Features please check out our User Voice: Nintex User Voice


To check out the rest of our roadmap check it our here: Nintex Roadmap







At Nintex we’re always looking for ways to make it easier for you to work just the way that you work.


Nintex Hawkeye leverages some powerful technologies to give you deep visibility into your workflows and how your business is operating. We harness Microsoft’s Power BI for complex data modelling and to generate dynamic visuals to help you understand what’s happening in your environment.


From within Nintex Hawkeye, you can view pre-built dashboards or download them as Power BI templates. Opening these in Power BI lets you dive deep into your data to explore questions beyond those answered by the pre-built dashboards. For example, how an approval process performs across different departments, or which teams have recently started publishing more workflows.


While many people have skilled up in Power BI, those of us new to such analytical tools often like to fall back on tried and trusted tools to do some quick processing and analysis. Enter our old friend Microsoft Excel.


Nintex Hawkeye supports the industry standard OData feed, so you can connect to your organization tenant in the Hawkeye Cloud from any analysis tool that supports OData v4.


For details, see this blog post for how to connect using an OData feed in Power BI.


Additionally, this step-by-step guide shows you how to connect an OData feed into Microsoft Excel.


Once you’ve followed the steps in that guide, you can quickly do your own quick analyses, or follow a similar approach to use the OData feed in another analytics tool of your choice.


We'd love to hear how you use your OData!


Have a question? Visit the Nintex Hawkeye space and ask it. Or see the Hawkeye how-to page to see how to get started.

Have you ever felt like there was a File upload shaped hole in your Forms design experience? You can now fill it with Forms' new File upload control.

Workflow designers need only edit their existing forms or create a new form, and the File upload control will be ready and waiting.


Take advantage of the powerful configurations unique to File upload:

  • Accepted file types - Guide your form submitters to upload only the files types of your choosing
  • Maximum number of files - To limit how many files can be uploaded
  • Maximum file size (MB) - So files are always a reasonable size


I need to create a workflow for employees to submit their Leave requests. If they're ill, they have the option to attach an image of their medical certificate. If an extended sick leave period is required, HR policy dictates that a medical certificate is essential.




Because a user will likely take a photo of, or scan their medical certificate, the file types should to be limited to .jpg, .png and .pdf.

Chances are only 1 file is needed, but in case they have multiple certificates, the limit has been set to 3 files.

You probably wouldn’t want picture-perfect photos of their medical certificates, so a maximum file size of 5MB is enforced.


To improve the experience of submitting their leave request, some Rules are also in play:

1.  Only show the Medical certificate File upload control when the "Type of leave" is "Sick leave"


2.  Make Medical certificate File upload control mandatory when "Duration of leave" is 4 or more days.



And here is how the form submission experience will look:


For more information, go to our Form controls help page, or check out our Nintex Workflow Cloud templates to get started with your first workflow.

Nintex workflow cloud just keeps getting better. With this latest release you can really create some powerful forms to enhance your end user experience when they submit data via forms built in Nintex Workflow Cloud.

We now have more control over our textbox, single and multiple choice controls. Let’s get into what these updates look like. First, we are going to cover two controls, the single and multiple choice because the concepts are the same for both.


For this example, we will use the single choice control. After you drag-and-drop a single choice field on to your designer you have new configuration options. You can now set the control as read only, and set a custom name for your variable or have it auto generated in the configuration panel. This will be helpful because you might only want certain fields to be filled out, but if a user selects a certain answer you can unlock the control with a rule.


I have the control set to read only, and when a user selects Yes, they will need to select an option from the single choice control. I create two rules. First to turn read only to NO and second to make the field required. I am also renaming my choice field to a variable to something that make more since. Before this latest release your title was your workflow variable making for very long names to use within your workflow.


*Auto generate variables or rename them to fit your organization naming convention.

Variable Auto Generate



Another great enhancement in the forms is within your single line (short field) textbox. You can now specify an input that you are looking for called a Text Mask. An example might be a phone number, credit card, or maybe you just want an input of number or letters. This will help ensure quality data being entered into your form.


We're excited to announce these much-requested new features. And we'd love to know how they improve your experience in Nintex Forms for Nintex Workflow Cloud. Please leave a comment or provide examples below!


We encourage you to formally submit additional product feature ideas on the Nintex Product User Voice Site. And we invite you to visit our NEW Nintex Public Product Roadmap often to see what we’ll be delivering in the near term. You can read more about this exciting release here.

One of my favourite features of Nintex App Studio is the ability to control and organize all the content within the App. It's like a folder structure, and every folder or menu item can contain one or more items. By default we have the same folders we can see in Nintex Mobile:

  • Forms
  • Tasks
  • Outbox
  • Sent
  • Drafts

From this section it’s also possible to add custom content and enrich our forms and workflow tasks with documents, images, videos or html pages. If you didn’t know about this, I strongly recommend you to have a look at Dan’s article Nintex App Studio for the win and explore the options for adding custom content.



Nintex App Studio also allows us to organize all these folders. We can:

  • Delete any folder. For example, we might want to delete the Drafts folder. Or maybe the App we’re building is for a specific purpose; we might need to display just one form and hide the Tasks.
  • Edit any folder. For instance, if we edit the forms and tasks folder, we can create a filter to tell App Studio what forms and workflow tasks we want to bring into the App.
  • Change the order of folders. If you want to show your forms first, or put the "sent" folder at the bottom of the list, you just drag and drop the folder to where you want it.

Changing the order is more important than you might think because the first menu item on this list of folders is going to be the landing page of our App. When you open the App, the viewing behaviour will be the same as if you selected that menu item. This way, if the folder contain a single item (for example a form), the app will open that the form. If the folder contains a list of items (for example our list of forms), you will see the list of forms.

Essentially what it means is that we can make any menu item the landing page of our App, which opens a whole bunch of scenarios. Here are some examples:

  • Your App is very simple and specific: You just want to create a request, a safety inspection, or a survey. The first item could be the forms menu with only that particular form, and the landing page will be that form.
  • You want to create a short welcome/intro video so every time the app is opened, the user will see that video. In that case, the first item of your list would be a custom content folder containing only that video.
  • You only need to scan QR codes and collect the data behind each one. Then your first item could be a QR scanner and your app will directly open your camera, ready to scan the code.
  • You create a nice home page where you include links to the rest of the content in your app. Have a look at my example, in which every item of the navigation menu points to a menu item that I created in my app: documents, videos, an image, a form, another html page, and so on.


Powerful, isn’t it? Now, what about your app? What would be the landing page? Could it be the Outbox folder? Would that be crazy? Let me know, I’d love to hear your use case!


I've had the opportunity during my career to work across a vast array of industries, environments and situations. During this time I've seen the same problems with slightly different flavors, but none the less a problem. Whether it is someone always eating the snacks in the morning tea room through to a business processes hindering innovation. Another thing I've come to see during this time, is that when organisations start to think about business processes. The defaults are something to do with HR, IT or Finance. Now don't get me wrong! There are a lot of business processes among those business departments. But often the department that gets either forgotten about or are simply too busy to sit down with the business to work through some of the issues they may be having, is the Service or Field arm of the organisation. This tide is changing however, and you'd have to be living under rock to not see the vast amount of Field / Mobile applications that service these very scenarios. 


So let me set the scene: The fictitious company I work for "Safalo Realty" provides building management services, which includes everything from landscaping, plumbing, administration, leasing services and general maintenance. To keep my customers happy I have to be able to provide fast, efficient and excellent service. So the first thing I need to do other than have the right people in place, is to ensure that the experience for my customers interfacing with us is easy, and keeps them informed. I also need to engage with my field staff who are almost always remote or are engaged on a sub-contractual basis.


Safalo Realty use multiple systems of record, and all the customer data is stored in Salesforce. This also includes equipment assets, case management and service requests. I'm also using Nintex Workflow for Salesforce which you can read more about here - What's New: Nintex Workflow for Salesforce.



Sally works at the fictitious 'Mur Blancs,' who lease 3 floors from us in Downtown Seattle. They are currently having some HVAC issues on one of the floors. So Sally reports this via the Safalo Realty Website. 

Click to enlarge



Sally has submitted the form to request maintenance from the Safalo Realty website, this will trigger a workflow. 

Click to enlarge

The workflow is going to do a number of things before it serves up any information to the Field worker however. First of all it needs to go and get the account information to validate whether the information is correct. At this point you could also do validation checking to see if the account is on Credit hold or have any other outstanding cases that haven't' been rectified. If this was the case you could gather this information and change the priority based on this knowledge and inform the Field worker that there are other jobs outstanding, and that someone may mention this when they are on site. Because Sally selected HVAC in the form, the field engineering manager's picture will be displayed, we can also take this information from the form and use it to create a case in Salesforce and assign it to this person. 

Once the Case has been created in Salesforce, the workflow will send a SMS or Email to the customer who lodged the job. The primary purpose of this is to keep the customer informed and to let them know that we have received their request and that we can created a case and it has been assigned. 

The workflow progresses on now to create a work order document. This work order document is a requirement of the Safalo Realty and Sub-contractor legal requirements, and it is how they (sub-contractors) bill Safalo. 

The document is created by the document generation action within the workflow and stored in Box so the Sub-contractor can access it. 

A task is then sent out to the assigned field worker. They will receive this as an email and as task in their Safalo Realty App, which was built using Nintex App Studio. 

From the task / email they can open the work order document to find out what they need to do, and with all the information about the account they need, such as point of contact, address, Case Number etc. 

Right now we are leaving it to the specialist hands of the person in the field to fix what they need to, and the first workflow ends. 


Once the issue has been solved by the field worker, they need to report this back. In the same way we are trying to lower the complexity for our customers when they submit requests, we also want to lower the complexity for our field workers. They are often remote, offline, only on mobile and have limited time to. We also want to maximize their productivity in terms of; we want them in the field fixing and solving issues for our customers. Not filling paper work. 


Using the Safalo Realty app the field worker can simply type in the case number, which they know because it was on the work order they were given, and simply fill in the resolution / fix that was applied. 

This form starts a new workflow that uses the case number to pull forward the information about the case and to write the new information tot he case, post it to chatter on the account, inform Sally that work has been completed and to update the work order form with the resolution and the date. This completed work order document is then sent to field worker and Sally via Adobe eSign to complete. The Signed document is then placed back into for sub-contractor to be able to process for billing and the Case in Saleforce is updated with the resolution and closed.


Through out this entire process we have also been gathering the data via the Nintex Hawkeye Beacons that allow Safalo to produce dashboards to effectively monitor and track any cases that are on going and to identify any trends in particular buildings or with particular customers.


This particular scenario is very specific in what it is trying to achieve, but the same principles can be applied to just about any field type operation. Whether it is equipment maintenance spot checks at the end of a shift, to in-home care visits for stay-at-home elderly patients. Moving data between the field and your central office and involving the field in the daily processes of the business has never been easier. 

Data entry can be challenging in almost any system of record. Whether on a mobile device or a desktop, you often have to navigate screen after screen, and do click after click, to enter data that is often repetitive and predictable.


Take sales, for instance. If I own a lead with a company name and address, all I should need to know is which product(s) my lead is interested in so I can create the appropriate quote document. But lead management systems often require you to convert the lead to the next stage, add a quote, add SKUs, etc. There are more screens and clicks after conversion. You face even more complexity if your organization uses third-party configure-price-quote software.


Many of the fields you’ll have to fill in during this process are predictable (such as currency codes) or redundant. Most of the rest are things you know before you convert the lead. Wouldn’t it be great if your “convert” process allowed you to enter all the necessary data in one form, on a single screen?


Enter Nintex Workflow for Salesforce, a platform that allows anyone in the organization to create sophisticated workflows with clicks, not code, and without relying on IT. You can use it to embed smart forms into Salesforce Lightning and Salesforce1 that in turn enter data in Salesforce the instant the user clicks “Submit.”


Does your sales process require you to completely fill in account, contact, opportunity, quote, line items, and other objects in order to create a document at the end? Forms you create with Nintex Workflow for Salesforce let you do all of that on one screen. Want to text message the sales manager whenever an opportunity over $10,000 is created? Nintex Workflow for Salesforce can help with that too!

 forms in salesforce

Sure, you can string a few other solutions together to make this happen. But the time to market with those solutions may well depend on your internal Salesforce release cycle and the bandwidth of your coding resources. Nintex Workflow for Salesforce can be built directly into your production environment by a system admin or business analyst – again, without relying on IT.


You can get started right away by downloading Nintex Workflow for Salesforce from the Salesforce AppExchange here. Read up on the forms and workflow documentation here and start building. And keep in mind that the need for simple data entry isn’t limited to Sales; it also applies to Field Service, HR, Billing operations and many other areas of your business!

Back to Future 2 screenshot with caption: Where we are going, we don't need code

Today we are excited to bring you a glimpse into the future with Nintex Workflow for Salesforce!


Nintex Workflow for Salesforce is a new managed package on the AppExchange that is your solution for automating and optimizing your sales processes, all without having to develop custom code. Nintex Workflow for Salesforce is powered by Nintex Workflow Cloud, the industry leading solution for workflow and content automation.


With Nintex Workflow for Salesforce you have access to an intuitive and easy to use drag-and-drop designer to build and deploy intelligent state-driven workflows that act on objects or data in Salesforce. You can build and monitor workflows that interact with your organization's data in a native application without ever having to leave Salesforce. And all this is fully supported in Salesforce Lightning as well as Salesforce Classic.

Features and options such as contextual forms you can deploy in a Lightning Component, express approval via email, and mobile interaction, enable your organization to participate in the process automation, freeing up your team’s time to do what they do best: move your company forward.

Get started with the Nintex Workflow for Salesforce app today! If you already use Nintex Workflow Cloud you only need to provide your tenant info when launching the app. If you are new to Nintex Workflow Cloud, we made it really easy to sign up for a new trial right in the app.


For more help, go to how to install the Nintex Workflow for Salesforce app, or check out our Nintex Workflow Cloud templates to get started with your first workflow. A template is a pre-built workflow that offers a starting point for automating your business process.

Welcome to Dreamforce 2017! Over the last decade, Nintex Drawloop has been accelerating business results for organizations with Salesforce at the center of their sales and services operations. As we await all of the exciting product news and innovation to be unveiled at Dreamforce this week, we wanted to take a moment and recap the tremendous investments and enhancements we have made to Nintex Drawloop since Dreamforce 2016.


Nov. 2016

  • Increased support for Salesforce Files: Users can leverage Salesforce Files to store generated documents, include as additional attachments, and create document templates.
  • Email templates: Users can send emails via Salesforce or SMTP, using data-driven documents created through Word templates.

Jan. 2017

  • FedRAMP certification: Nintex Drawloop is available as a FedRAMP-compliant SaaS service through Project Hosts' Federal Private Cloud. Government agencies can digitize, automate, and standardize all of their document generation processes by adding Nintex Drawloop to their Salesforce deployment, while being fully assured that the entire solution is FedRAMP authorized.

July 2017

  • Document Packages in Lightning: Salesforce admins can create, edit, and manage document packages in the Lightning experience, eliminating the need to switch between the classic and Lightning UIs.
  • Lightning Component support for Community Builder: The Nintex Drawloop Lightning Component now works in Community Builder, enabling all users within Salesforce communities to easily get the document generation tools they need.
  • Start a workflow in Nintex Workflow Cloud: This is a new delivery option through which a generated document can trigger a workflow in Nintex Workflow Cloud, enabling enterprises to create end-to-end business process automation.


Since the acquisition of Drawloop by Nintex more than two years ago, we have worked to thoughtfully integrate the organizations across a number of teams such as engineering and support. The continued innovation in Nintex Drawloop, plus the availability of Document Generation across SharePoint, Office 365 and Nintex Workflow Cloud, speaks to our commitment in making this integration a success for our customers, partners and Nintex.


This brings us to an important announcement in our integration journey: Nintex Drawloop will now be known as Nintex Document Generation for Salesforce. The AppExchange listing has been updated to reflect this change, and is now available under the name “Nintex Document Generation.”


Tomorrow, we will share more details on the innovation and investment we are driving for enterprises that use Salesforce. If you are attending Dreamforce, be sure to visit us at the Customer Success Expo #105/107, or in the Developer Forest. Or check back here on the Nintex Product Blog, to learn how Salesforce customers can benefit from intelligent process automation, and achieve improved performance, better collaboration, and growth.