đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
We require a simple unique identifier for each workflow instance to use in a subsequent "Set Instance Name" action, and other communications as a short way of referring to a particular instance.
At the moment the workflow sends data to a sharepoint list and creates an item. It then uses the Sharepoint item ID to create the unique ID, however this is cumbersome.
It would be great if I could use something within NAC that would number off each instance of the workflow.
Screenshot below shows an example - the highlighted number has been created using Sharepoint. Ideal solution would not rely on Sharepoint.
For example, we will have a workflow for people to log an issue with the IT helpdesk. I would use the unique identifier to create a job number that would be used in subsequent communications. It is a short way for people to refer to and look up the issue, and find out current status.
Most of our workflows are like this, eg. Audit, Idea (where it might subsequently turn into a project, so it is useful to refer to eg. "IDEA00999" to check the original business justification etc.
It feels like this functionality should already be there, let me know if I am missing something!
Thank you.
@GuestThanks for sharing your idea! Could you provide an example use case where you need to use unique identifiers for instances?