News

Very often we have a scenario where it is difficult to upfront decide on the number of level of approvals or eye checks needed in a workflow. Have got the same request twice this week so thought of putting it down in a blog. Today I will show you on how we can achieve dynamic level of approvals straight out of the box from NWC itself without having to do any major customization. Do note, though the screenshot and references are of NWC, the same can be achieved in Nintex for SharePoint on-premise as well as Nintex for office 365. To achieve this, I have used the best friend of a workflow designer, Branch by Stage Action.In my example I have 3 parties who will evaluate the requestLegal Procurement ManagementIn the screenshot above you will see an extra stage, Decision stage. Let me explain why we need that in a while.Now while in legal stage my customer wants N-number of approvals. It can go back and forth to multiple people with different expertise. The user may also send to the request

To date in Nintex Workflow Cloud (NWC), designers and developers have had the capability to publish changes to any type of workflow. If this works for you, you can leave this setting in place...however, if your organisation insists on additional governance or demands greater visibility of when changes are being made, NWC now offers configuration options to specify who should have the ability to publish changes to workflow. Let's find out more! Your admins will find new options available on the Workflow settings page under Settings. The Workflow publishing section is where to look to begin configuring the new feature.  When you first visit this page, the Designer and Developer option will be selected under Workflow publishing. This is the status quo...how NWC has worked up until now. If you are happy with this model for publishing, you need do no more! Now let's look at the second option...Groups. Toggling the main setting to Groups allows us to add one or more groups of users who will

Update - August 20th (17.4.1 now available)Hello, RPA Community,Thanks again for your patience while we got the Google Chrome issues fixed in the latest release. Nintex Bot 17.4.1 is now available -- I strongly encourage you to install this version as soon as possible, and not only if you're targeting Chrome in your botflows.  You do NOT need to update RPA Central as long as you updated it last week. Note that we released a new Chrome Extension today as well -- 1.2.0.0. The combination of 17.4.1 and the new Chrome extension should greatly improve the speed and reliability when designing or running botflows that target Chrome. Thanks again,MikeProduct Manager - RPA Update - August 16thHi again, Everyone, We are planning on releasing 17.4.1 mid-week. Thanks again for your patience as we work through the targeting issues with Chrome and Edge. For a little more detail, some of these changes that caused the instability in our web table targeting were to support what we internally call Shado

Periodically users will generate a document inside of Nintex Workflow Cloud or SharePoint Online Nintex and place a signature in that document.  When you tag the document, that signature will be very large.  Here is how you resize that signature image.  The key is in the Word document under "Picture Format" to select "Selection Pane" and put your tag in that pane.   Video below to see it in action.

Great news Nintex K2 five users !  You no longer need to keep visiting Error management page just to keep checking on any K2 workflow errors. Old timers with K2 platform wanted a feature where notifications are sent to IT or Business team for any erroring instances on K2 Five platform. Now you can do exactly that by configuring a new workflow to start on any error, see the start pane below   A simple example scenario would be to send your IT Administrator notifications so they can action the error. You can also setup an advanced scenario where K2 automatically retries ay any error instance automatically so you don't have to. More details are available at below Nintex link-https://help.nintex.com/en-US/k2five/userguide/5.5/default.htm#K2-Workflow-Designer/Start/ErrorEvent/Start-Error-Event.htm Now, what if you want to setup the same scenario if you are on earlier versions of K2 Five. Stay tuned for my next post as I will be covering how I have been using a custom K2 workflow to do exact

Automate your first K2 process"Request/Renewal of Company ID" #Nintex MVP#K2 Five https://www.youtube.com/watch?v=Me0zdvn8RSU 

 Why can’t I see my AssureSign template in Nintex Workflow Cloud?Currently only “non-partial” templates are available within the integration with Nintex Workflow Cloud. If you have a template configured in AssureSign and do not see it in the Nintex Workflow Cloud ‘Get a signature’ action, it is most likely because the template in AssureSign is in a partial state.  What is a partial template?A partial template is any template in AssureSign that is missing a component that could put it into an “incompletable” state. For example, if you have Signer 1 and the sender input of [Signer 1 Email], no SMS support, and then make the [Signer 1 Email] input optional, the template will become partial as there could end up being a signer that doesn't have an email for delivery. There are several basic requirements for a “non-partial” template that are outlined below. A template must have:One signer At least one required Sender Input for Email or Phone One document One non-fixed JotBlock (input JotBl

Hello.The learning team at Nintex is pleased to announce that we have released brand new On-demand courses for Nintex Workflow Cloud Expert Series. We now have a full array of courses for Nintex Workflow Cloud on demand if you need. Please take full advantage of these courses to learn all about this powerful platform. The expert courses are now available on learn site as below: Please note:We have released 3 new expert courses and we recommend, that the users should navigate these courses in sequence as shown in the picture. However, if not sequentially, we strongly recommend that you start your learning journey by first visiting the Advanced Form Features course. This is the first recommended course since it is based on several foundational courses form the Practitioner course series. Do not forget to check the about your course section to know what the courses contain and know the learning objectives for each of them. How are these courses designed? Each course is carefully designed

[Update: 14 April 2023]Nintex for O365 does not support the changing of the domain name for SharePoint Online. Note the list (not exhaustive) of issues that will be encountered: The Nintex Workflow app will not be accessible Runtime issues with workflows that contain Copy an item action Workflows with conditional start can’t be republished Runtime issues with child workflows Issues with Nintex list forms that will require republishing Existing Nintex task forms are brokenAbove are some of the issues discovered and is not an exhaustive list. Note that the changing of domain name feature was released recently after SharePoint Online has been in market for a while, there has been no provision built into the Nintex for O365 products to support this change. Therefore, extensive product updates will need to be made to fully support the changing of domain name for SharePoint Online which Nintex will not be doing.[Update: 25 July 2022]Assessment has been completed. Renaming the SharePoint doma

Nintex has evaluated both its on-premises products and cloud-based capabilities with respect to the Zero Day Remote Code Execution (RCE) Vulnerability in Java Logging Package Log4j and Log4Shell. NVD - CVE-2021-44228 (nist.gov).   Nintex can confirm that we have found no areas of concern and can state that Nintex on-premises products are not affected. Nintex can also confirm that we have found no areas of concern and can state that Nintex cloud-based capabilities are not directly affected. We continue to work with our supply chain vendors to establish any potential issues.1. Has Nintex organization investigated the Zero Day Remote Code Execution (RCE) Vulnerability in Java Logging Package Log4j and Log4Shell? NVD - CVE-2021-44228 (nist.gov) Yes   2. Does Nintex products provided to customers directly use affected version of Java Logging Package Log4j and Log4Shell? No   3. Was any of the Nintex partner or third-party providers impacted by Zero Day Remote Code Execution (RCE) Vulnerabil

Please refer to: https://help.nintex.com/en-US/platform/AllowlistIPAddresses.htm

 Using Dynamic Data Dynamically Populating Documents eSignatures customers can often encounter times where they want to dynamically position signing fields inside their documents, but either do not want to, or are not able to, manage their document templates directly within the eSignature tool itself. One example of this is when combining the capabilities of Nintex Document Generation and eSignature to dynamically pull information from a given system of record and populate it into a document (DocGen) before sending it out for approval and signature. Historically, customers that leveraged Adobe Sign as part of their Nintex Workflows or Drawloop Delivery Options could use Adobe Sign Tags to indicate where signature fields should be populated in the document when it was sent to the Adobe eSign service. For customers that wish to move from Adobe Sign to Nintex AssureSign, this same use case can be facilitated through the use of ‘Dynamic JotBlocks’, and the table below provides a comparison

Those with workflow enterprise subscriptions also have access to Nintex Analytics. With Nintex Analytics, you’re provided with a robust data infrastructure to support reporting on workflows across your entire Nintex deployment. Nintex Analytics gives you visibility into vital data like the total number of published workflows, most commonly used workflows, top workflow developers, and more. Built using state- of-the-art data technology Azure Data Bricks and Data Lake technology ensures the highest possible performance allowing you to gain key insights into how your workflows are being used. Data accuracy Make critical decisions based on detailed data to drive optimization and return on your Nintex investment. Simple and easy to use Pre-built dashboards (see examples below) allow you to visualize data across your organization efficiently.    For more information about Nintex Analytics, check out this video from the Nintex Analytics product Manager, Cheyanne Ong.

 Nintex AssureSign + Nintex Workflow Cloud Integration with Nintex AssureSign is now available within Nintex Workflow Cloud and to help make sure that users are able to start using as quickly as possible here are the answers to some frequently asked questions related to working with the two products. As we continue to enhance the integration between Nintex AssureSign and Nintex Workflow Cloud, it will become easier and easier for Nintex users to take advantage of the native eSignature capabilities directly within their automated workflows. Directing a workflow based on signing outcome Setup Nintex AssureSign API Key/User Controlling Sender Input Values from Nintex Workflow Cloud Configuring webhooks for use with Nintex Workflow Cloud Configuring signing notifications with Nintex Workflow Cloud  Photo by Adeolu Eletu on Unsplash

In our latest release of Nintex K2 Cloud, we’ve added a new feature to make styling your Nintex K2 SmartForms easier than before and made further enhancements to unify the powerful low-code process automation capabilities of Nintex K2 Software with the Nintex Process Platform.  New Style ProfilesBrand new to the design experience, we are excited to release the Style Profile Designer. In the familiar Nintex K2 Software designer experience, you can now create a new artifact type called the Style Profile. Treated as a first-class citizen, a Style Profile can be created once and used across one or more forms. By studying and evaluating how our customers style Nintex K2 SmartForms, we discovered several trends: Styling each control is painful and takes too much time to make each form look consistent. Creating custom themes, while possible, required a lot of CSS code and wasn’t consistent with modern CSS approaches. Branding SmartForms is critical for using automation applications widely at

Nintex has released Version 2 of the Nintex Workflow Cloud workflow engine. As of December 1, 2021, new instances of workflows published to the v1 workflow engine will no longer be operational. If your current Nintex Workflow Cloud tenant has workflows published to our v1 workflow engine, you will need to migrate those to the v2 workflow engine by November 30, 2021.  Benefits of upgradingIn addition to improved scalability and runtime performance, the new v2 workflow engine includes:Higher workflow throughput – workflow start rates from 100s in engine v1 to up to 2,500 in engine v2 Increased loop iterations – workflow loop iteration rates from 250 in engine v1 to up to 1,000 in engine v2 New and improved actions – such as Query and Update XML, Loop N times, modify string and much more The new workflow engine is available in your tenant today, but to take advantage of the new capabilities you will need to republish your current v1 Nintex Workflow Cloud workflows by November 30, 2021. Up

2022 is just around the corner, and as we continue through uncertain times, we’ve learnt to adapt quicker than ever in changing times. As a leader of change ask yourself these top 5 questions and ensure you’re set up for success next year. Did I support my people and ensure they were heard?Digital transformation is more effective when we consider how it impacts our people, whether it is your internal staff or customers. What is your feedback process?  Is it managed effectively?  Understanding where the pain points are will have the best impact on your customers and outcomes. While ensuring you put your efforts into the right areas investing where it is needed most. Do I have a core understanding of how my business runs today?Automation and digital change is exciting!  There are so many opportunities and ways to improve your business to gather and analyse information in more effective ways.  I'm a BIG believer in understanding current flows of work to pinpoint and make impactful change.

With the latest Nintex Promapp release v.6.0.11 we’ve introduced an exciting new feature that allows you to identify and nominate processes you think is good for automating which connects both Promapp functionality with Nintex Workflow Cloud (NWC) functionality in a smooth process.  Watch the video below to view how to use this new feature. Creating a workflow framework with just a few clicksAs a Promapp Automation Specialist, you can review the process from the process overview page and confirm whether or not you want to see a workflow framework designed for it. If so you can click on the ‘Request Automation’ button. Promapp uses natural language processing to review the process and suggest workflow steps that could be handled by a workflow. As the automation specialist, you can confirm or change the workflow steps so that they map correctly to the activities and tasks you have in your process. Once you're comfortable with the process to workflow mapping, simply click the submit butto

Ease and Advantage of NintexNintex makes it easy to automate processes to keep everything moving while staying focused on your core business deliverables..Nintex is an easy, point and click workflow and content automation application that makes collaboration easier by connecting every person, department and system inside or outside your business. Nintex takes business efficiency to the next level, no matter where you are or what device you are using.What is Nintex Connector in NWC?Nintex Connectors integrate your business apps within your automated workflows. Integration is as simple as dragging a built-in connector into the Nintex designer canvas. Nintex Connectors cover the popular apps you use every day.Few Examples of connectors that can be easily added and utilized  in your workflows.Google Drive Salesforce ServiceNow Trello Slack Azure componentsSteps To Add Nintex Connectors1.Select the connector from the list of default connectors available.2.Select the action required and drag

Hi, Everyone,I wanted to let you know that our latest releases are now available for RPA Central and Bot. The biggest feature to ship for Central is the support for a licensed SQL server. Fresh installations are given a choice to use SQL Express (default) or to specify a SQL username and password. Upgrade installations are given instructions and a downloadable tool to configure the connection to the RPA Central databases (RPACentralKeys and RPACentralWeb). Please see the following topics for more information:Select your SQL database setup (fresh installation) Migrate SQL Server database (upgrade installation) Edit the SQL Server connection (updating simple/advanced connections)For Bot, we’ve improved targeting and performance as well as fixed a few issues when using the Unlock action (the topic is updated with some best practices too around using it on remote desktop/VMs). HTML-formatted emails with attachments are now working as well, @cristopxer.Please see the release notes for detai

Products: Nintex Workflow 2013, Nintex Workflow 2010 We have often seen the requirement to be able to report on how many Nintex Workflows are in an environment and where they are. Using this PowerShell script you can generate a report of how many workflows are found on each site/subsite/list in a SharePoint environment. Note: This script only targets the Nintex Configuration Database. Update: Script now targets all Nintex databases. Run the below (attached as well as a *.txt file for your convenience) PowerShell script (PowerShell ISE works well) from a SharePoint Server:PowerShell Script Add-PSSnapin Microsoft.SharePoint.PowerShell   [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") [void][System.Reflection.Assembly]::LoadWithPartialName("Nintex.Workflow") #[void][System.Reflection.Assembly]::LoadWithPartialName("Nintex.Workflow.SupportConsole") [void][System.Reflection.Assembly]::LoadWithPartialName("Nintex.Workflow.Administration")

AssureSign sites will be updated to our latest tested release:Account/CA1/NA1/WWW/SB: Tuesday, November 30, 2021 at 5:00 AM EDT (November 30, 2021 10:00 AM UTC) EU1: Tuesday, November 30, 2021 at 11:00 PM EDT (December 1, 2021 4:00 AM UTC)Please monitor release notes for a list of included changes.

Repeating sections are a critical and heavily used piece of functionality in Nintex O365 forms which allow users to solve a wide range of problems. These problems involve building up lists of data for use cases ranging from inventory lists, incident reports right through to expense forms. Repeating sections are the most heavily requested feature for Nintex Workflow Cloud on UserVoice, and I'm happy to announce you can now use them in NWC. Not only that, but they come with some awesome new functionality - row calculation. It's clear from customer feedback that users need a reliable way of performing row based calculation relating to items, e.g. line total​, to help inform form participants and capture relevant data. By adding the "current row" concept to our repeating sections object - we have allowed to do this quickly, as well as still provide the existing collections of controls for other use cases. e.g. adding up the items in a column. See the example below where "Line Items" is a r

Watch a recording here for an overview of these changes. View our updated help content here. Why are we doing this?The existing user interface in the Viewing Permission page can be confusing. For some of our clients, the process group tree can be very large, and it can be difficult to identify the parent group when deciding to apply a permission.  There is additional complexity considering process groups can have multiple permission groups applied.Clients with large data sets could also have performance impacts with the current Viewing Permission page.What is changing?We will be removing the concept of Viewing Permission groups. Users’ visibility of processes can be applied directly to process groups on the Manage Groups page. We’ll also be adding role support for permissions, so Promasters can quickly apply viewing access by applying a role to a group - every user in a role will be given viewing access. Moving groups and sorting will remain the same on the Manage Groups page, with the

Hi Nintexers, I just wanted to share a simple workaround for the missing support of the "Append Changes to Existing Text" option for Multiline text fields in Nintex Forms for Office 365. Apparently on 26th September Nintex announced that this feature is planned for development, but I can't wait that long...  Support lists with versioning turned on and where "Append Changes to Existing Text" is set to "Yes." – Customer Feedback…  For my solution I was using the new responsive forms but it should work also in the classic ones. What you needRepeating section Multiline text field: Comment/Notes People field: Created by One Rule How to How toMove Note and Created by field into the Repeating Section which is connected to a SharePoint Multiline text column Set the default value of the Created by field to "Current User (Display Name)" Disable the People field Create a rule for the Multiline text field: When not(Note_Created_By==Current User (Login ID)) Then Disable  Advantages• Every comment f