Tag Archives: Nintex Workflow 2013

Get a Parameter within a URL Using a Regular Expression in Nintex Workflow

Recently had a need to extract a parameter from within a URL string using Nintex Workflow.  Specifically, I needed to get the ID parameter from a URL.  In the example URL below, I needed to extract the number 987:

//mysite/mypage.aspx?ID=987&User=654

Follow these steps to get the ID number:

  1. Open the Nintex Workflow designer and add a Regular Expression action.
  2. Configure the Regular Expression action with the following settings:
    • Pattern =  (?<=ID=)[^&]+
    • Operation = Extract
    • Input Text = String, Inserted Reference or Workflow Variable
    • Store Result In = Collection workflow variable
    • Note: Your can use the “Run Now” option in the ribbon to test out the action.
  3. Next add a Collection Operation Action with the following settings:
    • Target Collection = Collection workflow variable
    • Operation = Get
    • Index = Integer workflow variable (with “Default value” = 0)
    • Store Result In = Text workflow variable
  4. The value (987 in the example) is stored in the Text workflow variable and can be used else where within your workflow.

Nintex Workflow Regular Expression - Extract Parameter from URL

Nintex Workflow Collection Operation - Extract Parameter from URL

Remove Line Breaks in Text Using a Regular Expression in Nintex Workflow

You can remove line breaks in a text string using the Regular Expression action in 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 = [\r\n]
    2. Replacement text = Keep this empty (or use a replacement character)
    3. Input text = Insert your text string (you can insert a reference to data in a list column or workflow variable)
    4. Store result in = Text workflow variable
  3. You can then use the workflow variable as you need it.

RegExRemoveLineBreaks

Nintex Workflow Stalling on Document Generation Action

I encountered an issue recently where a few Nintex Workflow 2013 workflows that had been running successfully for some time suddenly started stalling.  The workflows still showed a status of “In Progress” but were not moving forward.  Checking the Workflow Progress and Workflow Details pages showed no error messages or issues.  I finally noticed that these workflows were freezing when trying to execute a Document Generation workflow action.

After investigating, I determined that the issue was related to a Nintex Workflow service not running in my SharePoint 2013 environment.  Specifically, the Nintex Workflow Start Service was not actively running on any of my SharePoint 2013 servers.  Once I restarted that service on one of my servers, the stalled workflows continued running, completed the Document Generation action, and progressed to the next workflow steps.

Get Digits Before a Decimal Point Using a Regular Expression in Nintex Workflow

Using the Regular Expression action in Nintex Workflow, you can get the digits before a decimal point.

Here are the steps to follow:

  1. Insert a Regular Expression action into your Nintex Workflow.
  2. Configure it with the following settings:
    1. String = Your number from a column or workflow variable.
    2. String Operation = Replace
    3. Pattern = \.[0-9]+
    4. Replacement String = Keep this empty
    5. Output = Text workflow vatiable
  3. You can then use the workflow variable as you need it.

Here are some examples from using this Regular Expression:

String Regular Expresssion Result
6.5 \.[0-9]+ 6
1234.5678 \.[0-9]+ 1234
1234567.89 \.[0-9]+ 1234567

 

Regular Expression to Get All Characters After a Specific Character in Nintex Workflow

You can get all the characters after a specific character in a 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 = (^.*?(?=-)-)  where the “-” is the character (replace both “-” with your desired character)
    2. Replacement text = Keep this empty
    3. Input text = Insert your text string (you can insert a reference to data in a list column or workflow variable)
    4. Store result in = Text workflow variable
  3. You can then use the workflow variable as you need it.

Here are some examples from using this Regular Expression:

String Regular Expresssion Result
abc123-xyz456 (^.*?(?=-)-) xyz456
abc123;xyz456 (^.*?(?=;);) xyz456
abc123?xyz456 (^.*?(?=[?])[?]) xyz456

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.

Completed Nintex Workflow Pro Certificate and Nintex Workflow Admin Certificate

I recently completed both the Nintex Workflow Pro Certificate and the Nintex Workflow Admin Certificate.

The Workflow Pro Certificate is for skilled Nintex platform users and covers designing, creating, and debugging Nintex workflows and forms.

The Nintex Workflow Admin Certificate is for skilled Nintex platform administrators and covers various abilities and knowledge including the installation and maintenance of the Nintex Platform.

Nintex Workflow Webinar Posted

I recently presented a webinar titled “Automating Business Processes with SharePoint & Nintex Workflow“. Here a quick summary of the webinar presentation:

“Organizations of all sizes are constantly searching for ways to improve efficiencies, increase productivity and add value to their SharePoint implementations. Automating business processes with SharePoint workflows addresses these goals perfectly. Building these processes is not always a simple task, but it can be easier!

This session will provide an overview of building workflow solutions with Nintex Workflow, explore several features of the product and walk through real business workflow solutions. You will leave this session with a clear understanding of how your organization can successfully implement workflow-enabled business solutions.”

You can view the recording here: Automating Business Processes with SharePoint & Nintex Workflow

Nintex Workflow Call Web Service Issue “Cannot Resolve Server Name”

I recently ran into the following message when trying to configure the Call Web Service action in Nintex Workflow 2013: “Cannot resolve server name” (see image below). No matter what I tried, I received that error message every time we hit the Refresh button beside the Web method setting.

Nintex Workflow - Cannot resolve server name

This issue was due to the Web Front End server not being able to resolve the URL of the web application from the server itself. As many of our sites are public facing, the majority of DNS is handled by external DNS servers, and all URLs are not by default added to internal DNS. This is fine the majority of the time, but there are instances, and this was one, where the server itself needed to resolve the name.

I solved this issue by adding the URL to the Web Front End’s hosts file (we’ll call that “manual DNS”) and verified that we could access the site afterwards from the server itself (which we could). This caused the problem to be fixed within the Nintex UI.