The existing action to externally start a NWC workflow from O365 requires the full start URL with token - the main issue with this is that the url has to be hardcoded, so the only way to replace an expired token is to open the workflow and update it manually.

Even with one workflow this would be annoying to keep track of and you'd have to schedule a day annually where you refresh the token and replace the url (else the 365 workflow will start failing to call NWC), however many of our workflows call NWC more than once, then there's the issue of keeping track of these token epiries across all projects. This maintenance is tedious and time consuming.

Solution 1

Allow dynamic input (variables, list lookup) in the start url field. I understand the existing action is set up so the entered url can be looked up and the startdata schema returned to show the available input fields (which frustratingly don't support array data types, but that's a different issue), however I feel like as long as the user has entered a url first, the schema should generate then stay fixed (ever after url changes) unless they explicitly click a button in the action config to fetch the latest schema.

This would allow users to update the token from a separate list (or variable) without having to re-enter all their startdata fields in the wf action config again. While this eases the process it doesn't solve the issue of needing to manually remember to regenerate and update the token.

Solution 2

Completely rework the 'start NWC workflow' action to use a connection and a workflow dropdown. Connection dropdown should allow for NWC connections to be created in the connection manager - selecting a connection then populates a workflow dropdown with all the external start workflows the authenticating account has access to. When a workflow is selected from the dropdown, it can pull back all the startdata fields. Ideally the connection could store tokens, and manually call the NWC API to regenerate (and replace) any expired tokens making the process completely automated.

This would be a far simpler user experience and also completely remove the need to manually regenerate and update the url/token when calling NWC workflows from 365.

How about supporting the ability to do new lines in multi-line plain text textboxes?

An example would be a comments field, where multiple comments are entered. You should be able to use the Regular Expression action to replace a temporary character (eg ~) where you want the line break to be, with \r\n. The Regular Expression action even tells you to use .NET syntax, which is \r\n but it doesn't work.

I've googled and googled for a solution but can't find a solution for Nintex 365. Seems like such a simple thing but it can't be done, at least not to my knowledge.

Can we get a central place within nintex online to terminate or retry suspended workflows?
Use case: we have a list, managed by users, that syncs specific info from one list to another. The source list had a choice column change and thus has started suspending wf's because users did not make sure destination choice column contained the same values. Now we have 200+ suspended workflows in the source list. Due to the nature of a suspended wf, we cannot just kick off a new on those items, even after the issue with the choice values are fixed between the lists, because nintex will auto terminate a new workflow running when an existing instance is suspended. Requiring us to either manually terminate all 200+ wf's, write some powershell to terminate, create a workflow to terminate or manually delete all the items that have a suspended wf and add them back using excel import. All of those options are too much for end users to handle.
If we could have a central place where users can view wf statuses of list or site workflows and can action upon suspended workflows by either terminating them on the spot or retrying them in this central view. This would be an extremely useful feature.

When using the "set variable" action I can populate any list-field into a variable.

However: if the field is of type "choice" or "lookup" and the field allows multiple values, I would assume that I could populate a collection, containing all values of my "multi-choice" or "multi-lookup" field.

However, this is not the case. Instead a choice column with multiple values creates a JSON-string suggesting collection-of-strings. But this is just a string. Similar for lookups.

Instead I have to query the list and return the result into a collection. This way I get a collection of values - why can't I get this behaviour when using the "set-variable" action?

We will like to use Nintex Workflow DocuSign actions and to be able to make use of the automatic template matching.
It looks like this is not possible with Nintex Workflow for Office 365, Version: 1.0.4.3 as this feature is not implemented.

Automatic template matching compares the files that you upload with all previously saved templates. Based on the sensitivity setting you select, if the match is close enough, you can choose to apply the matching template to your document, either automatically or with a notification. When you apply a matched template, all aspects of the template are applied to your new document: the recipients, messages, and the recipient signing fields.

How do I enable and manage automatic template matching in my account?
https://support.docusign.com/en/articles/How-do-I-enable-and-manage-automatic-template-matching-in-my-account

Set Template Matching Account Preferences
https://support.docusign.com/en/guides/ndse-user-guide-manage-automatic-template-matching