News and Guidelines

What is Nintex Workflow Cloud (NWC)?It’s a state-of-the-art cloud workflow capability that lets you easily extend and connect your forms, applications, content, and systems of record, with the people who make the decisions your business relies upon to succeedNintex Workflow Cloud empowers anyone in your organization to unlock the transformational business benefits of humancentric workflow automation. Why Nintex Workflow Cloud?Four main key factors that determine why should be used NWC:EASY Hit the ground running fast with a cloud-based solution that removes upfront setup and costs. Drag-and-drop to design and build workflows the way you think – in a fewclicks, not code.       Connect structured and unstructured content sources, from legacy systems to modern SaaS apps. HUMAN-CENTRIC Empower the people closest to lines of business to automate the processesthat are your business.         Bring the right content, at the right time, to the right people. Share the workflow innovations your p

It was a busy conference for Nintex in Chicago. Technical Evangelist, Terry Simpson had to juggle a lot of things.  He started off with a 2 hour workshop that focused on Process Mapping with the Nintex Promapp tool.  If you haven't seen it, it's definitely time to take a look.   Wednesday, Terry had a session named Art of the Possible: Automation Demystified.  This was a technical deep dive into the tools that businesses can use to help their automation needs, with specific focus on time saving and increasing productivity. Thursday, a session on Clicks not Code.  Here, Terry focused on the ease of use of automation tools like Nintex Forms, Workflow and Promapp and the lack of need for coding.  Essentially, empowering the business users. The booth was also really busy.  Since the event was a mix of regulars and first timers, conversations varied quite a lot.  Between the current hot topic of Teams, Forms, Workflow automation, Robotic Process automation and understanding your processes,

See post on SimplifyingProcesses.com Execute your BPM plan and establish continuous improvementAs a quick recap – in Part One of this blog series, I suggested that digital transformation efforts can often be derailed by an organization’s lack of process knowledge. I followed by positioning business process management (BPM) to better understand, capture, and manage process knowledge. Then, in Part Two, I identified the three-phase approach organizations can follow to implement BPM (1. Planning – 2. Execution – 3. Continuous Improvement) and went on to exposit the Planning phase. Now, in my final post in this series, I’ll detail the key steps for successful BPM Execution and Continuous Improvement. ExecutionThe Execution phase can be broken up into five subsections. First, we must have a clear understanding of the scope of the project. Second, the scope of work must be prioritized based on objective factors understandable to the stakeholders involved in the project. Thirdly, we must recr

I recently attended the Dreamforce event in San Francisco. While there and speaking with new/current customers... something became clear. There is an AMAZING feature that is not commonly used by our current customers. I was completely shocked when folks were so excited to hear about a feature they already have (not an add-on) they are not using that could completely remove manual tasks for their users while also keeping your Salesforce data live and accurate. This feature is called INSERT-UPDATE. I have added a link to the setup of this feature at the bottom of this article. "What is this feature? Why do I care?" Great Question! Insert-Update will allow a Document Generation Package (at the beginning of creation or the end) to update your Salesforce data model. Why you care is really a creative answer. You can update ANYTHING. You can create Tasks. So, if you have a use-case where you create proposals you can have the insert update assign a task to the current user that ran it for exam

The initial release of the online version of the Nintex RPA and Nintex RPA Central documentation is now available. This release represents the beginning of 100% online documentation availability and the ability to continuously update the documentation with the latest information. This release of the Nintex RPA online help documentation features:Information for using Nintex RPA Quick start information for the new Nintex RPA Central  Installation information for Nintex RPA Additionally, the following efforts are taking place to modernize the Nintex online help documentation across all platforms: Customer interviews to collect feedback about what you believe is important and useful in product documentation. Peer reviews to help create a consistent user experience across the Nintex platform help documentation. Internal expert reviews to ensure the accuracy of the content of the documentation. So take a moment and become familiar with the documentation home for all of your Nintex platform p

I was trying to find a simple way to get an Employee's Manager in a People field on a form.  You can use a Calculated Field to display the Manager but I couldn't connect that directly to a People column.  Also, in some cases, the Manager a person reports to is not always the Manager in their User Profile, so I wanted to give users the ability to select the appropriate manager as an alternative option. I found a few posts that used JavaScript to do this, but they seemed needlessly complicated.  I used People Picker Extensions and JavaScript events in Nintex Forms as references and came up with a simpler solution (also, I'm using Nintex Forms Enterprise version 1.12.2.20).  First, I added a People Field for the Employee:Formula: Current User Store Client ID in JavaScript variable: Yes Client ID JavaScript variable name: EmployeeSecond, I added a People Field for the Manager:Default Value Source: Use connected field's default value Store Client ID in JavaScript variable: Yes Client ID Jav

Have You ever had the situation in Forms Designer that the minimal width of a list lookup control is too big for your form? In this example I wanted to insert a list lookup for 'unit of measure' to the right of the 'quantity' field.But the width of the inserted control is too big and I could not shrink it in Forms Designer. What to do?CSS is your friend. Assign a class name to the control, e.g. 'measure' and enter a little piece of CSS in the form settings:Now the form looks as exspected:You have to play with the number of pixels for width und position. For the width its important to use '!important' in CSS!I think you can use this also for other controls. Hope that helps someone Manfred

Mistakes happen, change is needed, so you need to make sure you’re supported when it is. We hope the Nintex Workflow Generator reduces these incidents of change by adding better compliance pre build but when you need to rollback or simply track the history, introducing Nintex Workflow Cloud Version History.For the most part, version history is fairly self-explanatory. It’s a history of all your workflow version events, Saved (minor) or Published (major). What it does give you is control over storing, tracking and restoring your Nintex workflow cloud workflows, as well as enforce auditing of changes using comments.Workflow SettingsBut first let’s tackle the small configuration setting required. Under Settings – Workflow Settings there are two simple on/off options regarding whether to make comments compulsory for both a workflow save event and a workflow publish event.Save EventClicking Save on a workflow will display a prompt to enter Version Comments. Note, this popup will only displa

This is a brief blog to overview the migration tools that work for Nintex. For more information about migrations, please visit the Nintex Migration Center. How to Approach a Migration with Nintex?Before a migration, perform an inventory of what processes you have that should be migrated. Run the Know Your Workflow script to gather as much information as possible to help make smart transition decisions. Once you’ve decided which workflows to move, prepare them by either replacing actions that are more compatible for Office 365 or assessing the benefits of rebuilding the process from scratch in order to take maximum advantage of Office 365’s platform functions. Remember, there’s no wrong way to build a workflow, but there are more efficient ways for that workflow to run depending on the platform and functionality available. Choosing a Nintex Migration PartnerNot every process – including those requiring high security – should be migrated. The more security required for a process, the les

SummaryNintex Form Rule will not execute as expected when using the List Lookup Control output for the value used in Nintex Rule due to ID-prefix. ResolutionWhile in the Nintex Form Designer, do the following:Alter the Rule to remove the ID-Prefix by using the replace() runtime function and adding the following RegEx:"^[0-9]+;#" For Example:If 'test' is the first value in the list, the value would appear as: "1;#test". A formatting rule will be created to hide a different control, if the List Lookup Control, "LLUP" has a value of 'test'. The following Rule will be used: replace(LLUP, "^[0-9]+;#", "" ) == "test"

As you would recall in our last blog post - A day in the life of the Automation Jedi (Part 1) we were able to design a process map for Mr Happy's automation feedback requirements, if you haven't had a look at it, never fear its located here ...I assume you're all caught up now, and well across our little ballad between Mr Happy and Mr Grumpy. To start automating Mr Happy's automation requirements, we're going to use Nintex Workflow Cloud (NWC) - What is Nintex Workflow Cloud you ask? NWC allows Mr Grumpy to automate his business and transform any business process, no matter how sophisticated– using clicks, not code.To do this he'll need an NWC account, for those tuning in at home, if you don't have one you can sign up for one here. Now, that we all have an account – let’s login to NWC! This is Mr Grumpy’s story;Once Mr Grumpy has logged into NWC using his credentials, he selects the Create workflow button (the red box in the left-hand top corner.) Item 1 - NWC Entry screen After the pa

If you have occasion to hide the Save button along the top of a Nintex Form in Office 365, below you will find some simple CSS that you can copy and paste into your Form Settings -> Custom CSS section to do so. Before:   The below CSS will remove the button labels and the Save icon:#RibbonSaveButton{display: none;}‍‍‍‍‍‍‍‍ After:

OverviewPromapp presently has two ways to publish a process.  The first is a basic toggle of the process state available in the editor; this is commonly referred to as Normal mode.  The second requires the editor to specifically click a ‘Publish’ button when saving changes; this is referred to as Publish Only mode as it was previously coupled with the process approvals functionality.NOTE: The publish only mode mechanisms are used when approvals have been enabled. Key DifferencesThe follow describes the key differences between the different mechanisms for publishing are as follows: How to publish a processNormal Mode Edit the process Change the state in the summary section Save the change Publish only mode Edit the process Select “Save with a comment” and click “Save and Publish” Or, after saving changes click ‘Publish’ from the toolbar at the bottom of the Editor. Version numbersNormal ModeVersion numbers update after saving changes to a process. The major version is updated after

Click HERE to see the recorded webinar from November 7th, 2019, hosted by Ayelet Gazit, Training Manager, and Marlon Gobitz, Product Trainer. This webinar covered the following:Release Highlights AI Booster The Enhancements in Advanced Commands HTML Engine- Kryon Now Supports Firefox Web Browser HTML Engine- Support Cross-Domain Frame Localization Support OCR Improvements Improved Authentication Changes in Architecture Improved Security and Compliance Q & A Session:Data security azure Q: when OCR’ing documents through the cloud, e.g., handwriting, how is the security guaranteed? A: “Microsoft is governed by strict standards regarding the privacy and protection of customer data. We take strong measures to protect your data from unauthorized persons or improper access.” See here for more information regarding compliance offerings and privacy details.  File format for Azure receipts Q: What format is supported? A: Hovering on the ‘i’ tooltip near the file path will provide the fil

 Demonstrations and LearningDay 3 was full of demonstrations and sharing of knowledge.  The traffic at the Nintex booth had a busy tempo all day.  I did notice a lot more in-depth conversations and repeat visitors who wanted to learn more.  It is a lot of fun when 3 or 4 different attendees who are all passionate about the same technology get together.  Several times today this happened where they all started to socialize ideas and visions about how to implement solutions.  Once they get on a role, the idea sharing and learning truly begins.  To me, this is what the Ignite conference is all about.     Microsoft Teams Connector!!One of the most exciting moments of the day was the launch of the Teams Connector in Nintex Workflow Cloud (NWC).  I heard some feedback this week from current clients around governance in Teams.  The timing couldn't have been better seeing these connectors going live in NWC.  Stay tuned to the community site for specific posts on the new connectors.  Chris Elli

Settled InDay 2 of Microsoft Ignite seemed to have a bit of focus and organized chaos to it.  Today was the day everyone started to settle in.  By now everyone has quickly adapted to the environment and knows where the sessions, food, exhibits, bathroom and most importantly the wifi is located.  I personally experienced great wifi service on Monday and you could tell today everyone figured out the password and was diligently downloading all the new stuff they were learning about. Knowledge SharingAs attendees settled in, the knowledge sharing seemed to pick up steam.  I personally spent the majority of my time at the Nintex Booth.  We had a ton of conversations ranging from what does Nintex do, to best practices, how to's and much more.       Theatre SessionI had the privileged to present a small session at one of the theaters in the Hub today.  "Automate your business with Nintex, Teams, and Dynamics" was the topic.  I really enjoyed showing how you could bring Nintex, Teams, Dynamics

KeynoteDay 1 of the Microsoft Ignite Conference was a very busy day.  The morning started out first thing with the Keynote.  I chose to view it from The Hub and see it broadcast on one of the theatre areas.  Tons of great content and several announcements.  Below are a few that I took note of.Project Cortex - Classifying content in Office 365 Updated Microsoft Edge Power Automate - re-branded Flow + RPA capabilities Azure Arc - Azure management on other clouds Azure Synapse AnalyticsI'll be interested to learn more throughout the week. The HUBFollowing the keynote, I am always interested in the pace and tempo that carries over into the day.  Today did not disappoint.  I spent the majority of the day at the Nintex Booth, #2449.  One of the my favorite parts of the week at Ignite is spending time with partners, customers and random folks who love technology.  I was fortunate enough to demonstrate the Nintex Suite of tools a good bit over the course of the day.  One minute we might be tal

As it has been asked and instead of sharing the slides of my session "Managing permissions when a workflow is executing" from Nintex InspireX 2017, I think that it's more useful to create a blog post  Minimum permissions to design a workflow (save and publish)Site workflows (On Premises) Site workflows (Office 365) Minimum permissions on the SharePoint site: Design (Workflow Gallery not accessible ; shortcut to create a site workflow not displayed) Full Control (Workflow Gallery accessible ; shortcut to create a site workflow displayed) Minimum permissions on the SharePoint site: Design List workflows (On Premises) List workflows (Office 365) Minimum permissions on the SharePoint site containing the list: Design Minimum permissions on the SharePoint list: Edit Minimum permissions on the SharePoint site containing the list: Design Minimum permissions on the SharePoint list: Design (Nintex Workflow icon is not displayed) Full control

Effective 13 September 2019 (the “End of Support Date”), Nintex will officially stop supporting Nintex Mobile deployed on Windows Tablet and Windows Phone. Nintex functionality that relies solely on a specific underlying operating system operated by a third party reflects the lifecycle of that underlying OS. Accordingly, as this Nintex Mobile functionality targets the Windows 8 platform that is currently in the end of its Microsoft lifecycle. Between the date of this notice and the End of Support Date, only applicable critical patches will be implemented. What will happen effective 13 September 2019?Nintex Mobile installed as of the End of Support Date will continue to work normally for SharePoint environments. However, Nintex Mobile will no longer be able to connect to Office365. Nintex Mobile for Windows Tablet and Windows Phone will be removed from the Windows App Store. New Nintex Mobile and Nintex App Studio customers will no longer be able to create apps for Windows Tablet and Ph

This question seems to come up pretty frequently, so I wanted to provide a quick walk through on how to use a SQL Request control as a cascading lookup to your backend databases.  In this scenario, the Safalo corporation requires a Nintex Form for their agents that interfaces with their larger Property Management database.  In this form, they need a few pieces of information to be exposed on the form including their Property State, City, and Address along with their Agent contact information.  In this scenario I have three SQL Request controls configured as dropdowns (pulling in my property information) and two controls configured as labels (displaying my Agent Information).  Below, I'll walk through the configuration of each of the controls along with a quick video of the form in action. First, I setup my control to pull in the state in which my property is located. I have named the control 'Property State', I have configured my server / database settings, setup my query and configure

What are local Nintex User Groups (NUG)?Local, in-person groups that meet to connect with each other, share knowledge, deep dive into technical solutions and understand where Nintex is heading in the industry. This is your chance to work with others like yourself and learn more about Nintex. Why you should join a local NUG?User groups can benefit you by helping expose and increase your knowledge about the platform overall. This isn’t a sales play, so you don't have to worry about someone pitching you to buy anything. This is about connecting with others just as yourself who are using the same technology as you so learn how to do more the platform.  At Nintex Connect, we see the local user group as a physical representation of the online, digital Nintex community where an external representative of Nintex helps promote best practices, tips and tricks and other solutions locally to users. We currently have NUGs sponsored by Nintex partners as well as some of our larger enterprise custome

Hola guys    .Author Palesa Sikwane‌ Long Description This is a little workaround that can assist you providing a user friendly way of keeping track of an items version history while keeping your Workflow History list data to a minimum on your site. Dependencies SharePoint ® On Premise or SharePoint ® Online Versioning Enabled on the List/Document Library Compatibility Nintex Workflow ® Office 365 ® Nintex Forms ® for Office 365 ® Nintex Workflow ® On Premise Nintex Forms ® On Premise Platform SharePoint® On Premise (2010, 2013 or 2016) Office 365 ® Useful Reads You can read my previous posts to get more information about my Timesheet scenario:   Part 1 Part 2 Part 3 (the Nintex® Form) Part 4 (Office 365®)   VideoCheck out the video below(Enjoy ):  Summary/Requirement OverviewEver wondered how you can present a forms version history in a user friendly format without having to rely on the Nintex Workflow® History Lis

A tricky & alternative solution to split string at specified delimiter.Thanks to KuanChiang Lui to provide this Trick.  Scenario: There have a string value (Delimiter strings) that returned from a data source or response value from a web request (SOAP or REST) and would like to split it and store into a dictionary.   Example Input Text = “1,2,3,4,5,6,7,8,9,10‌”   Expected Output Dictionary = ["1","2","3","4","5","6","7","8","9","10"]  Solutions: Check out the step by step below.Pre-requisites: Create a Text Variable and set value with "1,2,3,4,5,6,7,8,9,10".{Variable: String to Split} = 1,2,3,4,5,6,7,8,9,10‌ Step 1: Apply “Set Workflow Variables” action and configure to add XML node in between “String to Split”. Step 2: Apply “Replace Substring in String” action and configure to replace the delimiter “,” with XML node.The Output “String to Split” is becomes a valid XML as below. <values>                 <value>1</value>                 <va

Hello! I wanted a solution to remind my users that they had outstanding and overdue items. My current solution is to query a list for users with outstanding items and send them an email with a link to a page showing the items to do. While this works to a point I wanted to spoon feed them a little more. I wanted the email to include information about each item and to have a link to each item. Something like...  The list for this example is a Diary list. A simple list that sends reminders on a due date for the Event Owner to do a job and then Close or Rollover the item. Of course many don't bother closing the item so we have lot's of events that look overdue. Hence the reason for this reminder. We need to use a site workflow for this to work. First couple of Actions. Query List to capture the EventOwners and then a Collection Operation to Remove Duplicates  Query List. Filter to just overdue Items in progress and gather the EventOwner field into a collection.     Collection Operation. Re

In my previous blog post (i.e. RPA Claim Processing - Part 2: Simple OCR), we have learn how to use the built-in Simple OCR to read printed text from a PDF form. This helps us to process all inbox pdf and categorize the documents to different claim categories. Let us take a step further, instead of OCR the printed form title, if we use the same technique to OCR a PDF that is filled with handwritting, we will come to realize the Simple OCR is having difficulty to get the right recognition of handwritting for us.  The results of the Simple OCR i have tested are shown in the below captures (i.e. using PDF, Image, and Cropped Image). Take note of the Preview results, the result is somehow unpredictable and unexpected. Figure 1: Simple OCR with PDF Figure 2: Simple OCR with JPG Image Figure 3: Simple OCR with Cropped JPG Image Google Vision APIGoogle Vision API can detect and transcribe text from PDF and TIFF files stored in Google Cloud Storage (i.e. Google Cloud Vision API ). Unfortunatel