Nintex Upgraded Workflows Configuration 101

Nintex Upgraded Workflows Configuration 101 provides a step by step guide on how to configure upgraded workflows in the Nintex Autoamtion Cloud

1. Check the start event:

   1. Starting from Component workflow

   2. SharePoint-New List Item

   3. SharePoint update List Item and SharePoint-New or update list Item:

1. Configure the start conditions to prevent the infinite loop guardrail by setting the display name to not be equal to the service account. Read more about infinite loop guardrail here: https://community.nintex.com/upgrade-to-nintex-workflow-72/infinite-loop-guardrail-72732

2. How to find the service account:

   1. In ADO, On work item, select the Parent Item link. The service account will be displayed in the Connection/Service account display name Field

1. Set the instance name of the workflow right after the start event

As seen below:

1. Click the Actions in use button to displayed all the unconfigured actions

1. SharePoint Actions/Connections

   1. Query SharePoint list

Ensure all SharePoint actions are using the correct SP Connection, Web/Site URL. Querying the correct lists and the conditions is set as per the original workflow in SharePoint. Ensure the number of items returned matches that of the SharePoint Original workflow. Store the results of the query in an object that references the list i.e objQUERY(LISTName)

1. Call a SharePoint Webservice

If in the original workflow there is an action calling a web service, you can utilize the Call SharePoint Web Service Action. Select the correct connection, insert the Web/Site URL, The Request type. Store the Results in an object and reference it correctly i.e. objResponseContent

If the request type was a Get, which is obtaining information from a website then you need to query the JSON to extract information stored in the Response content. Insert the JSON to be response content from the web service query, use the correct JSON Path expression to extract the information required store the first result, in an appropriate variable i.e. text, integer, decimal etc.

If there's more than one result then store in a collection using the correct naming convention for reference purposes i.e. col

1. Variables

Variables need to be resolved in a manner that matches the variables in the original workflow

1. WebURL Constant Variable:

You can store the WebURL in a variable named WebURL as seen below:

This variable can be utilised when Querying or connecting to sharepoint or when calling api's

However if the workflow has start event variables that may contain the URL it is not necessary to create the WebURL Variable as you can use the Site URL Variable from the start event

You can see the

1. Check the logic and flow of the workflow as per the original workflow and resolved inavlid workflow actions with matching actions in the cloud i.e

Commit pending changes is an action that is not in use in the cloud and may be deleted

Error reporting and logging is no longer supported in Nintex Automation cloud and the error logic and variables may need to be disabled or deleted in the workflow.

1. String Operations

Nintex automation cloud does not support inline functions that may have been utilitised in the original workflows to concatenate strings. Using string operations helps to resolve or concatenate strings in the upgraded workflows as seen below in the example: