News

I recently had a client ask me if there was a way to automatically update the Role annual costs in Promapp and keep them in sync with their HR/Financial system.  As the roles and their annual costs are manually maintained in Promapp, I thought it would be a good use case for Nintex RPA.   I am going to walk you through the botflow that I built to accomplish this. The botflow I am walking through in this blog is available to download from our Nintex Gallery at this link. The first thing you would need is an export from the HR/Financial system with that lists the roles and costs you wish to update in Promapp. This spreadsheet will be used to search for the roles in Promapp and then update the costs.  The roles listed on the spreadsheet will need to match the roles in Promapp exactly in order for the bot to search for and update them.  Now let’s take a look at the RPA bot, the first thing that the bot is going to do is open the exported workbook and select the data in the worksheet to cre

#RPA #RPASolutions #Robotics #ProcessAutomation #ProcessDiscovery #DigitalTransformation  When you think of RPA, there are several tech-related questions that might come to mind. Will RPA replace my job? Should I be worried about RPA adoption in the workplace? Can RPA even help my department? Check out our answers to the most commonly asked RPA questions below:  1) Is RPA only applicable for IT services?  Automation may have been conceived in the back office but RPA can help the entire business. As RPA gains more maturity we can expect to see RPA not only in transactional or back office environments, but also in middle and front office settings – anywhere there is a large amount of data sets and inefficient processes.  2) Is RPA only about cost reduction?  RPA offers the solution to many of the challenges that organizations and BPOs currently face. However, it's not only about cost reduction, but also about driving predictability, providing higher process quality, speeding up time to c

List item attachments are not available from a task form – even one customized with Nintex Forms. Providing all pertinent information (including related documents) to complete an approval task from a single form, can go a long way toward making the user experience as seamless as possible for approvers. This post walks through meeting this requirement by leveraging a custom action created by Nintex Technical Evangelist, Vadim Tabakman. But, what if you don’t have access to deploy a custom action to your SharePoint environment? The following solution produces a similar outcome, without the need for any custom actions. The WorkflowGet AttachmentsFirst, use the Call web service action to get all attachments from the current item and store the URLs to a multi line of text variable.Next, use the Query XML action to parse through the web service result and get a collection of attachment URLs.Start an HTML TableThe collection of URLs needs to be formatted in a user friendly way for the task fo

The Nintex Product team continues to innovate our Nintex Analytics ­capabilities, and we are excited to share some of the latest enhancements. The needs of our users have always dictated how we prioritize our Nintex Platform roadmap. To gain actionable feedback and direction for this product update, we conducted in-depth research to understand our users’ most pressing pain points using our older analytics tool, Nintex Analytics. In the latest version of Nintex Analytics, we strived to provide better insights into how our customers utilized their Nintex investments. The new dashboard presents data in a more digestible and visual way so you can easily understand how the Nintex Platform is performing in your organization. We focused on building a strong foundation to rapidly expand beyond just workflow, so you can easily integrate other parts of the Nintex Platform. What changes were made to Nintex Analytics?In the latest version of Nintex Analytics, we focused on four main points to impr

We've improved the underlying technology for the Process Edit page to improve performance when editing and saving. The overall functionality is much the same but we've made a few changes: Improved functionalitySystem and Lean tags now show icons to distinguish between them: Improved dialog for selecting an additional group: RACI section now shows the same content as the Procedure page: Removed functionality Map replaced with image - this functionality will be discontinued. Any processes that use this display option will remain unaffected. However the option to change to this display type will be removed. If you use this display type on a process and change to another type, you will not be able to change back. 

Today we will see how we can leverage on simple HTML tags to create a very intuitive log table on Nintex forms.Nintex provides a very easy to view Track History, something like below, with the detailed description of the flow of events and an option to view the changes by clicking on Show completed task.  Many a time you would have come across users who would say “I can’t be clicking at multiple places, can I have a single view of the details. I also want to see the comments on each flow, is it possible out of the box”. They answer is Yes, out of the box using HTML tags.Quite easily you can build a very simple, yet informative table as shown below in every approval page. Here’s how you do it. It’s a quick and easy way. Before approval begins initiate a variable as below. After everywhere approval / outcome modify the variable as below. We can create the table based on the information as needed by the business.  For every approval page just add a label in a group where needed and this v

Hi, Everyone, I wanted to let you know that our latest releases are available now for RPA Central and Bot. Please checkout the Release Notes for what is fixed in these releases, but know that we could not fit the ShadowDOM work in this time around -- that'll come in the next release. Thanks,Mike

IntroductionIn the 15.5 release of Nintex Drawloop DocGen for Salesforce, we introduced new components for DocGen and Salesforce Admins to configure automatic docgen runs using Process Builder (PB) or Flow. In order to use the components for either PB or Flow, you will need to need to have the "Automated DocGen" addon for your subscription.  Creating a Process Builder work to generate documentsA button-click is the most common way Drawloop is used to generate document outputs. This method requires a Salesforce user to login to Salesforce, navigate to a record where a majority of the data is held and select a URL button if you’re using the Classic SFDC interface or through a run component if you’re users are in Lightning. But this process is not the only way Drawloop can generate outputs. Drawloop has always offered its customers the ability to have event-driven outputs through Salesforce workflow rules and apex triggers. This requires a custom field formula field, an outbound message a

IntroductionWith the Nintex Workflow Cloud Release 135 update there is an update to date formats for the document tagger in the document generation action, I wanted create this quick blog post to demonstrate how we can now format a date variable without time without having to format the date to string. How we previously had to format the date to remove the time. Before the Release 135 update to Nintex Workflow Cloud we had no options from within the document tagger in the document generation action to format a date to remove the time from it.   In order to do that we had to use the Format date to string action to format the date to remove the time and save it to a variable that we could use in the document tagger.  How we can now format the date to remove the time.With Release 135 we now have the capability to choose from multiple date formats from within the document tagger.  Thus making the workflow a little more efficient and saving time because we don’t have to format the dates out

Hi everybody,as I did not found out how to add images in comments to community-blog posts, I decided to write an own article. The original post can be found here. The intention to extend the existing solution was to hold the Nintex form small. Imagine how many rich text boxes you need for a larger form with a lot necessary helptexts. And the effort to update them if another person is writing them plus somebody who needs to update the Nintex form if any changes appear.So this a preview of the final version where every dialog-text comes from the externally maintainable list where every text gets loaded and cached on demand without any hidden richtextfield inside the form: To achive this, I created a new list named "Helptexts" where I renamed the displayname of the Title-column to "Key", added a richtext-column named "Helptext" and created the two demo-entries:Then I created a javascript-file, uploaded it to the SiteAssets-library and set a link to it in the Form settings: The configurati

PLEASE NOTE: This advice is for those of you who are using On-Prem SharePoint 2013 prior to release 3.2.4.0. It's way easier in 3.2.4.0 as you have the image URL variable! ~~~ Only recently have I started using the "Document Generation" action instead of "Update Word Document" action.    I didn't realize what I had been missing out on. Suddenly, we can insert tables and images easily, as long as we have our populated variables and templates set-up correctly. And the photos can be auto-resized! AND CAPTIONED! Craziness. This is going to save coworkers a LOT of time! I've taken care of the latter part (the template) for you, and it's attached to this post. The rest of this blog will teach you how to put it into use! Let's focus on the idea of having an inspector out in the field, taking photos, and writing captions using a repeating section, all via Nintex Mobile - maybe on an iPad. I'll walk you through how we bring those pieces together, and if you need more detail on anything, there's

"Stop doing the things you know are wrong, that you could stop doing!" ~ Jordan B. Peterson Are there things that you do (or tolerate) that you know - on some level - are wrong (or just not optimal)? Meaning: Things that are not moving you towards your goal(s), but instead moving you further away? Perhaps in your professional career? Specific processes? In your projects? Your hobbies? Or even your relationships? What might those areas of your life look like - in 1 week/month/year - if you stopped doing those things? It's an important question worth contemplating. At least on an RPA-level, we can provide some guidance on how to to do the right things while minimizing the wrong ones. The following resources will help: Automation: The Way is NOT the Goal! The "Ten Commandments" of Kryon RPA Attended Automation Kryon RPA // UI Automation Method Decision Helper

Hi Nintex Community!As community managers, it is always fantastic to receive feedback from the community and to know where we can improve.We’ve created this quick online survey to collect your feedback and suggestions. Please click here to complete it and thank you for participating!

As some of you might know, we've recently deprecated the Nintex Workflow for Salesforce app, and that took away the ability to embed an NWC form directly into your Salesforce Lightning page layouts. To address this, we put together a new tool that will allow you to embed your forms as before, and submit them with the context (in this case, Record Id), of the record the form was submitted on.  Here's how to use it:First, download the package from gallery.nintex.com, under the "Tools" section.Once you have the zip file, unzip, and you'll discover 2 different files. One is a component, and one is a design file. Next, you'll want to open up the developer console in your Salesforce Organization. Hit "New", and select "Lightning Component". You're going to then get a prompt that asks you to name the component. Give the component a name that you and your teammates will understand, and hit "Submit"It should automatically open a file that has an extension of ".cmp". This is the component piece

I was working on a Nintex Form for a client recently where there were several disabled fields. Actually, based on the type of request they were submitting, anywhere from 2 to 20ish fields could be disabled. The problem was that the default styling of disabled fields is not much different than enabled fields and our client wanted to make it more obvious which fields the user should be focusing on for certain scenarios. Allow me to explain... The Default StylingThe following screenshots show the default Nintex Forms styling. Initially, when the form for this scenario loads, all fields are disabled until a Type of Request is selected. You'll also notice that the Person or Group controls do not have the same white background as all other controls. So, we will address that with this solution as well. There are basically two main scenarios for this form:If the Type of Request equals "New Requirement", then only the Course Code and Justification controls are enabled. If the Type of Request do

#RPA #RPASolutions #Robotics #ProcessAutomation #ProcessDiscovery #DigitalTransformation  If you're worried about RPA and what the future holds, you're not alone! While no one can predict the future with 100 percent accuracy, we're here to debunk some of the most common RPA-related myths:  1) Will RPA replace humans?  People will always have an invaluable role in the workplace, especially when it comes to performing creative, collaborative, and interactive work. You can have people spend their valuable time executing mundane, repetitive tasks, or you can offload these processes to your virtual workforce so your teams can focus on the value-added work that only they can perform at a top-notch level.  2) Will RPA replace 100% of my processes?  Typically, 70-80% of rules-based processes can be automated as long as some human resources will always be necessary to resolve issues, develop and maintain the technology. The best RPA deployments will occur in stages - allowing for the process of

#RPA #Automation #DigitalTransformation #RPASolution #Robotics  The fear of robots taking our jobs is thankfully becoming old hat. Instead, the real question is: how can I utilize technology to get better (and more accurate) outcomes?  That's why we commissioned the Kryon Automation and the Future of Work survey, a global study of employees spanning a range of industries and job titles, to find out.  Check out our key takeaways below:  Takeaway 1: Employees are Eager for Automation  Employees no longer fear automation. In fact, they embrace it. 100% of our respondents shared that they understood the value of automation, with 46% weighing in that it can help save time on repetitive administrative tasks and allow them to tackle the more challenging aspects of their positions. While many companies have only scratched the surface when it comes to implementing automation, the desire for RPA solutions opens up a vast array of opportunities.  Takeaway 2: Repetitive Tasks Detract from Employee

Managing Training Seats for Nintex UniversityBodyTopicManaging Nintex University Seats for https://learn.nintex.com Instructions Training Seats are no longer a requirement for https://learn.nintex.com  If you have any questions regarding this topic please reach out to your Account Management TeamRelated Linkshttps://learn.nintex.com 

#RPA #Automation #DigitalTransformation #ProcessDiscovery #ProcessAutomation  To stay competitive in today's new world of work, organizations need a strategy in place to select, implement, and successfully scale various automation technologies. But how can they make it less daunting?  Join Hyperscience's VP of Corporate Development and Kryon CMO, Julie Shafiki, to learn how leading organizations across banking & financial services, insurance, healthcare, and public sectors are leveraging AI/ML to unlock efficiencies, elevate the customer experience, and fuel business growth.  We'll break down how state-of-the-art Machine Learning and human-in-the-loop functionality are redefining human and machine collaboration as well as shaping workplace and business models now and into the future.  Save your seat here: https://bit.ly/3E1dT9l  

#RPA #ProcessDiscovery #ProcessAutomation #Automation #DigitalTransformation  Together, we'll explore how Process Discovery and RPA can help you exceed your automation goals and find your way to the path of digital excellence.  Save your seat now to learn how businesses around the world ar exploring the possibilities of automation, productivity, customer experience, and much more - we'll even share how you can help your organization gain a competitive edge.  Learn more here: https://bit.ly/3mTkrRm

 We're excited to be answering some of the most frequently asked RPA questions across the web! Check out what these RPA specialists had to say about making a splash in the RPA industry with a C# background:  1) "The shorter answer: 'yes'! The longer answer: Expanding your skills is something that we should always be doing. The more you can get into the habit of perpetually learning, the more you’ll survive and thrive in the exciting (and scary) years ahead. What is more important than having C# programming skills is the mindset and mentality that you have. That fits very well with any RPA platform. In reality, you’re not going to be doing too much programming - which is why we've had career changers like audit managers and tax consultants join our organization as RPA developers. However, knowing how to program is going to make you stand out and be confident that you can tackle any project.  Most importantly - if you are looking for entry-level RPA jobs when you have zero hands-on RPA e

SharePoint web services can be used to manage content, as well as site settings and some configuration. You can read more about the SharePoint REST service here. Nintex Workflow Cloud provides many out of the box actions for provisioning of objects in SharePoint Online; however sometimes we might want to apply further settings to newly provisioned sites and site collections than those actions allow.  Enter the new Call a SharePoint web service action!  In this example we'll see how site provisioning form has been created in NWC, with options to allow the requester to specify particular commonly used features they would like to have activated on their new site. Our simple form below offers the requester the ability to switch on the following features in the new site collection: Document Sets Document ID Service Open Documents in Client Application by Default (instead of the web app option) Here's the form:  Our workflow has a simple approval step - if approved it will go on to create a

#RPA #Scalability #Robotics #Robots #Automation #ProcessAutomation #ProcessDiscovery  What can you do to prepare your business for the next disaster?  Join us in our on-demand webinar, where we cover scalability as a barrier of RPA in enterprise organizations. We'll share innovative solutions that will keep you prepared for the business interruptions of the future.  Meet us online, and we'll share:  -Why only 13% of enterprise RPA solutions utilize more than 50 robots and how to get that number to 500+-How automated process discovery eliminates the cost of expensive consultants and delivers a three-year ROI rate of 352%-How to solve scalability and TCO issues by moving to the cloud with Full-Cycle Automation as-a-Service, the future of RPA.  Catch up with us here: https://bit.ly/3tobG32    

Hello RPA Community, It’s been about two weeks since we released Nintex Bot 17.4.1. Thanks again for your patience while we worked through the issues with 17.4.0. Like I mentioned in my previous posts, we introduced changes that were meant to increase the reliability and stability of Bot and its communication with RPA Central over the course of the last few releases, starting with 17.2.0, and had completed those changes with 17.4.0. We also introduced support for Shadow DOM in that release. However, we found that some new issues cropped up with some of your botflows and some old issues came back after our releases. To make sure 17.4.1 had what we had intended for in 17.4.0, we redoubled our efforts to make the communications across the RPA platform even more robust and reliable. DetailsIn 17.2.0, we made changes in Bot to make sure our communication with RPA Central was as solid as possible. This was causing some status mismatches and jobs not being assigned properly.In the same releas

IntroductionThere will be certain circumstances where one would start an NWC process, have some records written to a third-party system and then pause processing of the NWC process while waiting for the external system to process these records. Once these records have been processed, NWC should then continue the process as these processed records can then be used by the process. For example, if we have received some shipping containers, the contents will need to be inspected and the results entered into a separate system that cannot be called directly from NWC. There is a batch job that runs once every 30 minutes, which will process these items and mark them as inspected and received. Once that is completed, we need to tell the NWC process to continue down the payment process.As a side note, this particular example could be a good fit for RPA, which can be initiated from NWC as well. The SolutionA simple way to implement this is to use a task assigned to a system account. At the end of