Hi @brandiwoodson,

To build this report, you could create a workflow with a couple of call web service actions.
You will need to use the Nintex API.
The first call would be to retrieve all the published workflows.
https://developer.nintex.com/docs/nc-api-docs/ref/workflows-v1/operations/get-a-design-published
Once you have this list, you must loop through and remove anything that is "publishedType": "Development."

Next, you need the List workflow owners API.
https://developer.nintex.com/docs/nc-api-docs/ref/workflows-v1/operations/list-design-permissions
You can use the workflow IDs from the first query to feed into the second call a workflow action in a loop to retrieve the owners.

If you have issues with this, I may be able to put together a workflow for you.

Hi @brandiwoodson,
I created a workflow that will report the workflow owner(s) for each published workflow.
You will need to edit the two Call a Workflow actions by adding in your personal token.
It includes development workflows, but each workflow is labeled as either dev or prod.
If there are multiple workflow owners, all of their names will be listed.
It emails the workflow initiator.
Workflow key : mf8MfiqD5TwEiXuyPnWyihcNZdHxWVDrqfN6hV7gEw5VUs2Fc
Valid until: 23 Aug 2024 - 6:49 PM

Example of the output.
 

Thanks. Running it now. But we have more than 1,000 workflows in our tenant, so this was initially why I didn’t feel the use of a workflow would help me obtain this data. :(

Hi @brandiwoodson,

The workflow surfaces the type for each published workflow. You could branch off or have a run if that skips, adding the workflow to the report if it’s Development. This will reduce the size of the report.

Regardless of how you generate the report, it will still be large due to your number of workflows, so there is no getting around this issue.

The Nintex Automation Cloud API is not just for workflows. You can use it to extract data in other apps, such as SKUID, or a programming language like Python. You can also present the data in many ways.  I have just generated a simple HTML output that puts each workflow on its own line but you could generate a CSV or populate a table or even a SharePoint list.

I’m not concerned about the length of the report, it’s the looping we end up having issues with that is limited to 1k. We have more than 1k, so as a result we wouldnt’ be able to loop through that many without the workflow failing.

SharePoint list would require looping I would think, no?

And which one doesn’t involve looping? I'm not familiar with generating a CSV in NAC. What does that consist of?

Hi @brandiwoodson,

The API to retrieve the published workflows has parameters that you can use to limit the workflows returned.
You can Limit the number of workflows returned.
The Offset allows you to skip items before the query starts returning items.

Using these parameters, you could run the workflow to return the first 500 items and then run it again to return the remainder.

PS. I didn't realize that the API call defaulted to 10 results. I have updated the workflow to return 1000 results. 

Query Parameters

limit

integer<int32>

The maximum number of items to return in the list

Default:

10

offset

integer<int32>

The number of items to skip before starting to return items from the query

A CSV is, as the name suggests, comma-separated values.
To create one in Nintex Automation Cloud, just update the create string actions in the workflow provided to include commas.
Email the result, Copy and paste it into a notepad document, and save it as .csv.

Open it in Excel, etc.