Author Archive: BamaEric

Nintex Mobile and Nintex App Studio Webinar Posted

I recently presented a webinar titled “Empower Your Mobile Workflow with Nintex Mobile & Nintex App Studio“. Here’s a quick summary of the webinar presentation:

“Employees today are increasingly on the move and expect to have access to the tools they need to get their work done. Nintex, the world’s leading workflow and forms automation solution, provides tools necessary to enable your mobile workforce to be more efficient and productive.

In this webinar, we will cover features of Nintex Mobile and Nintex App Studio that you can utilize to build dynamic mobile forms and apps with little or no code. You will learn how to leverage Nintex Mobile and Nintex App Studio to create powerful, easy-to-customize mobile forms and apps to empower your organization.”

You can view the recording here: Empower Your Mobile Workflow with Nintex Mobile & Nintex App Studio

Remove a Forward Slash at the End of a URL String in Nintex Workflow

I recently had a need to remove a forward slash (“/”) from the end of a URL text string using Nintex Workflow.  Here are the steps to follow:

  1. Insert a Regular Expression action into your Nintex Workflow.
  2. Configure it with the following settings:
    1. Pattern = /[^/]*$
    2. Replacement text = Keep this empty
    3. Input text = Insert your URL text string
    4. Store result in = Text workflow variable
  3. You can then use the workflow variable as you need it.

Coercion Failed: Input cannot be null for this coercion.

I created workflow in Nintex Workflow 2013 that contains a “For each” action that loops through a collection and performs several actions.  The workflow ran to a certain point and began throwing the error below and then stopped progressing.

Coercion Failed: Input cannot be null for this coercion.

After lots of trial and error, I finally figured out how to resolve the issue.  It turned out that immediately after the last successful action in the workflow that completed, the workflow had several “Set variable” actions that were disabled.  These “Set variable” actions were configured to perform a list lookup on another list.

I deleted these immediate “Set variable” actions (four in total) and republished the workflow.  The next time I triggered the workflow, the workflow successfully completed without encountering the error.

Proud to be a Nintex virtual Technical Evangelist (vTE)

I am honored and excited to be named a Nintex virtual Technical Evangelist (vTE) for 2017.

nintex-vte-signature-100px-pngNintex selected 60 workflow pros from the global network of Nintex partners for this program because of our technical aptitude about Nintex and deep understanding of the workflow and content automation (WCA) market.  Nintex vTEs possess in-depth understanding of the entire Nintex Workflow Platform including business process automation and analytics, document generation, forms, and mobile apps.

Nintex vTEs are an elite group and gather annually with Nintex employees, technical evangelists, and other vTEs, as well as receive training courses and early access to Nintex certifications and beta programs.

As a Nintex vTE, I regularly promote Nintex in the marketplace and assist with sales readiness activities.  I frequently participate in community engagements and I am available for pre-sales demos and discussions, industry conferences, and other event support. I also actively participate in the more than 10,000 member Nintex Connect technical community (https://community.nintex.com).

Find out more about the Nintex virtual Technical Evangelist (vTE) program

Introducing the 2017 Class of Nintex Virtual Technical Evangelists (vTEs) – Experts in Workflow Automation

proud-to-be-a-vte-social-image

Using the Lookup Function in Nintex Forms

Nintex Forms offers many great features for designing and customizing your SharePoint forms. There are times when you need to pull in data to your forms from other sources, including other SharePoint lists.  One way to accomplish this is to use the Lookup function, which allows you to retrieve data from a column within a SharePoint list and display that data on a form or use it in a formula. The Lookup function can be utilized within a Calculated Value control, Form Variable, or Rule.

Here’s the syntax for configuring the Lookup function:

lookup(List Title, Column to filter on, Value to filter on, Output column)

  • List Title – The title of the list that contains the data you are retrieving.  The list can be in the current site or another site.  To configure with a list on another site, start by prepending the List Title with the server relative URL path of the site and then delimit the list title with a pipe (|) symbol.  For example, “/sites/siteCollection/siteName|ListTitle”.
  • Column to filter on – The name of the column in the list that you want to filter on.  This column is used to filter which list items are returned as matches occur against the third parameter.
  • Value to filter on – The specified value that is compared against each item in the list.  Be sure to use a Named Control instead of an item in the Item Properties tab for this value.
  • Output column – The column name in the list from which the data is retrieved.

Lookup Function Configuration Example

For our example, we created an Order form using Nintex Forms that is used to create a customer order.  When a user enters a value into the Product Number field, the Orders form pulls back data from the Product Information list using the Lookup function.  The following two lists were created and configured for this example:

  • Orders – This list houses the order form and stores the order information upon submission.  List columns include Order Number, Product ID, Product Name, Production Description, and Product Cost.
  • Product Information – This list is used to provide information about the products offered.  List columns include Product ID, Product Name, Product Description, and Product Cost.

Now that we have the required lists and columns in place, here are the steps used to configure the Product Information lookups in the Orders form.

  1. Open the Orders form in the Nintex Forms designer.
  2. Add a Calculated Value column to the form to display the Product Name and configure the Control Settings with the following values:
    • Formula = lookup(“Product Information”, “Product ID”, ProductID, “Product Name”) where ProductID is the Name of the form control.
    • Name = ProductName
    • Connected to = Product Name
    • Save as data type = String
    • Recalculate formula on view mode = Yesnintexforms_lookup1
  3. Add a Calculated Value column to the form to display the Product Description and configure the Control Settings with the following values:
    • Formula = lookup(“Product Information”, “Product ID”, ProductID, “Product Description”) where ProductID is the Name of the form control.
    • Name = ProductDescription
    • Connected to = Product Description
    • Save as data type = String
    • Recalculate formula on view mode = Yesnintexforms_lookup2
  4. Add a Calculated Value column to the form to display the Product Cost and configure the Control Settings with the following values:
    • Formula = lookup(“Product Information”, “Product ID”, ProductID, “Product Cost”) where ProductID is the Name of the form control.
    • Name = ProductCost
    • Connected to = Product Cost
    • Save as data type = Currency
    • Use thousand separator = Yes
    • Value prefix = $
    • Recalculate formula on view mode = Yesnintexforms_lookup3
  5. Publish the form and open it in the Orders list.
  6. Enter a valid value into the Product ID field on the form and go to another field.  The form will automatically pull and display the data from the Product Information list into the Product Name, Product Description, and Product Cost fields.

nintexforms_lookup4

Speaking at SharePoint Saturday Charlotte 2016

I am speaking at SharePoint Saturday Charlotte 2016 on September 17, 2016. This year I will be speaking on “Create High Impact Forms with Nintex Forms”. Find out more and register for this free SharePoint conference at the SharePoint Saturday Charlotte site.

Be sure to attend my session and say hello at the conference!

Create High Impact Forms with Nintex Forms Workflow

Want to build sophisticated forms that solve business scenarios? Learn how to leverage Nintex Forms to create powerful, easy-to-customize forms for your organization. This interactive session explores design techniques and advanced features utilized to enhance your browser and mobile forms. You can build dynamic forms with corporate branding, rules, validation, mobile layouts, and more with little or no code. We will showcase real world examples and construct a live form application that attendees can interact with on their mobile device.

Speaking at SharePoint Satuday Atlanta 2016

I am speaking at SharePoint Saturday Atlanta 2016 on June 11, 2016. This year I will be speaking on “Create High Impact Forms with Nintex Forms”. Find out more and register for this free SharePoint conference at the SharePoint Saturday Atlanta site.

Be sure to attend my session and say hello at the conference!

Create High Impact Forms with Nintex Forms Workflow

Want to build sophisticated forms that solve business scenarios? Learn how to leverage Nintex Forms to create powerful, easy-to-customize forms for your organization. This interactive session explores design techniques and advanced features utilized to enhance your browser and mobile forms. You can build dynamic forms with corporate branding, rules, validation, mobile layouts, and more with little or no code. We will showcase real world examples and construct a live form application that attendees can interact with on their mobile device.

Error publishing workflow. Invalid JWT token. The token is expired.

I periodically run into an issue when working with Nintex Workflow for Office 365.  When I go to Save or Publish a workflow, I get the following error message:

Error publishing workflow. Invalid JWT token. The token is expired.

Invalid_JWT_token

I found a solution that has been working for me.  Keep the workflow you are trying to save or publish open.  Open up another browser tab or window, then open up a new workflow on the same site in designer mode.  Once you’ve done that, go back to the original workflow and try to save or publish it again, which you should now be able to do.

“Transitioning from InfoPath to Nintex” Whitepaper Published

I can now add “Whitepaper Author” to my resume.  Nintex recently published the “Transitioning from InfoPath to Nintex” whitepaper that I authored with their team.

If you’re currently using InfoPath and are considering a move to Nintex Forms, this whitepaper will be a great resource for you.  You’ll find information about Nintex Forms features and functionality, transitioning best practices, which forms make sense to convert, a real-world forms migration scenario, and what other organizations have to say about their transitioning experiences.

Here’s a summary of the “Transitioning from InfoPath to Nintex” whitepaper:

Microsoft has retired InfoPath but transitioning to a new forms solution doesn’t have to be daunting. And whether you use InfoPath or don’t use any forms solution, implementing Nintex Forms can result in increased productivity and other benefits for your organization.

We built Nintex Forms to be easy to use, customizable, mobile-friendly, dynamic and powerful. Customers like BGC Engineering rely on Nintex Forms to capture valuable information. “Having all of my forms available on my device has really helped accelerate the process of gathering information when I’m in the field,” says Annie Ruksys, Geological Engineer at BGC. “It makes my job easier knowing that I can just enter the data, and it is sent automatically once a connection is available.”

In our “Transitioning from InfoPath to Nintex” whitepaper, you’ll find answers to the following questions:

  • What features and functionality make Nintex Forms unique – and help customers like BGC Engineering successfully complete projects faster?
  • What are best practices for transitioning to Nintex Forms?
  • How do you identify which forms make the most sense to convert to Nintex Forms?
  • What’s a real-world forms migration scenario?
  • What do employees at organizations that have transitioned from InfoPath to Nintex Forms say about their experiences?

Download the “Transitioning from InfoPath to Nintex” whitepaper.

Congratulations! You’re a Nintex Connect Champion!

“Congratulations! You’re a Nintex Connect Champion!” was the headline on the new email in my inbox.

I’m honored to be named a Nintex Connect Champion for 2015.

Each year, Nintex recognizes the top point earners on Nintex Connect.  They describe it as a symbol of your experience, knowledge, performance, and contributions to the Nintex Connect community.  Only 20 out of nearly 9,000 active accounts have earned this recognition each year.

Nintex Connect is a great site for Nintex users to connect with other Nintex users, learn valuable skills, ask questions, create discussions, and help other users out.  I’ve been able to gain and share a lot of Nintex knowledge through the community.  I’m proud to be a part of it.

Visit Nintex Connect at https://community.nintex.com.