News and Guidelines

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'

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 fo

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. Ch

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 

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

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 regardin

 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!!

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.      

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

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

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

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

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

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 F

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

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

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)

So the idea behind this was to create a master booking, I.E a photographer or doctor is coming in for a day, and we need people to signup for one of the available 10 minutes slots throughout the day for their photo flu jab.There are two lists. One to capture the main booking and the other to hold the available slots. The master booking form needs to capture the following information... Once saved we can then run the generate slots workflow. It works by simply taking the start time of the first session adding it to a collection, then until the end of the 1st session, looping through and adding the slot duration and adding that to the collection. Repeated for each session.  The workflow then creates those slots in the other list. On my home page, it shows the current open booking with a link to a

IntroductionNot a lot of people know about Nintex RPA’s great interaction with SAP, so I thought I would create a blog about it and explain exactly how easy it is to get started. If you’re familiar with Nintex RPA (formerly Foxtrot RPA), then you should know by now that our goal  has always been to make things as easy as possible for anyone to get in and start automating their tasks. This is no different when working with SAP, and as usual the main tool is the drag-and-drop selector to build all of your SAP actions. Setup within SAPBefore getting started, it is important to enable scripting access within your SAP client. Without changing these settings, Nintex RPA will not be able to interact in the best way possible.After logging in, find the Options menu. From there, choo

Coming Soon: Nintex Customer Central We have some exciting news to share with you all about the forthcoming launch of our Nintex Customer Central portal. Nintex is proud to announce the upcoming release, in March 2018, of the next generation of customer self-help web portal. In conjunction with our customers we have developed an innovative and intuitive self-help web portal.   Tell me more!These are some of the features that will be available in the portal:Gain instant visibility to your usage summary of Nintex products Ability to manage your Nintex licenses, renewing, upgrading or adding. Ability to create and fully manage support cases Omni-channel user experience between Nintex products Access to Learning Central, enabling you to manage your consumption of Nintex training modules Dynamic Knowledge Central tool enabling you to search for content across all Nin

NTX PowerShell Action - Stable Release FeaturesRobust security features based on Windows Remote Management. Ability to execute PowerShell scripts from any machine allowing Remote Management from your SharePoint servers. PowerShell exceptions are handled so workflows are unaffected. OpenSource Actively Developed Automated Installation RoutinePlanned FeaturesAsync PowerShell script execution Script Repository Run worker as a centralized SharePoint service instead of in Workflow Infrastructure Pass SPServer object to PowerShell session for determining executing server. Current roadmap/planned features can be found here. Downloads

The other day I was presented a questions about a date not being presented the way the customer wanted. In Spanish typically months are not capitalized but this customer wanted to have the month capitzalied for all of their Spanish documents. At first I gave them the idea to create a formula field in Salesforce to see if they can reformat the date the way they wanted. This option was not possible as it would take weeks of approval and testing.  We were now stuck with option 2 and that was to create an excel file that would get the date from Salesforce and we will have to translate the date as needed.  I like to create two tabs in the Excel a Sheet for Input and the other Sheet for Output. The Input sheet is used for the values that coming from Salesforce. In this example it will be the date value that they are trying to translate.  

In receiving hundreds of Insurance Claims per day, we going to look into how RPA solution can help insurance companies save efforts and money hiring tens of people to do the capturing of claims, from scanned documents to claim processes. In this blog post, I am going to share how I convert a PDF file to an image for the OCR purpose. Converting PDF to image is not a mandatory step, but in the RPA Claim Processing exercise, it is a step I will need to overcome challenges that we going to discuss later. We will need some basic setup for the PDF to Image Conversion purpose, this is shared in the following paragraphs. Environment and Steps Setup:1. Python 3.7.4 2. ImageMagick 6.9.10 Q8 (64-bit) 3. Project speicific Python Virtual Environment 4. Python Wand library package install to the virtual environment5. creating a Python action in Foxtrot RPA 1. Install Python