Alteryx Server Ideas

The current Enterprise Utility Workflow does not have a match/look-up in place between the two environments for user ID's.  Thus, the migration workflow doesn't work without adding in a couple extra API calls.  When we upgrade to a new version of the utility, I have to add this back in. 

It would be nice if the workflow would come with this already configured.

Hello! We just upgraded to 23.2, and I see in v3 an endpoint to start a job (v3/workflows/{id}/jobs) and then another to get that job's status (v3/jobs/{jobID}). Compared to v1, I think the outputs endpoint is missing (v1/jobs/{jobID}/output/{outputID}). I'd love for this to be added so we can upgrade from v1 to v3. 

I want to let my artisans choose the collaboration option when sharing dcm sources. Currently they'd have to be promoted to curators to do this.

On the Job page, in addition to seeing the worker tag that a job is running on, it would be great to see which server the job is running on to ensure the work is being spread out and look for bottle necks.  We have a group on servers broken down into Small , Medium and large with several servers in each group.  Looking at the current screen, you can not tell what server a job is running on within the group.  Example, 'Large' has 3 servers with 4 jobs running on it.  But you can not identify which server the job is running on.

I develop workflows or analytical apps in the Designer and save them in a Gallery. If I need the setting "Always run this workflow with these credentials", I have to type in my username and password every single time I want to save it, even in the same Designer session. This is very annoying and results in saving the workflows much more seldom than I would do if I did not have to type in the credentials every single time.

My idea is to cache the credentials (login name and password) for one Designer session. It would be perfect if it was for the entire Designer session for multiple files. But even if it was specific to the opened file it would help.

Result would be:

• After loading the file, the user has to type in credentials only for first saving.
• Every subsequent save would be done without further interaction.
• After closing and re-opening the file, credentials have to be typed in again.

Admin option to restrict certain tools to not be used on the Gallery - Run, Python, Email, and R - without Safe or Semi-safe mode

Enhancement request to add the ability to restrict the ability to make workflows public

Admin ability to put restrictions specifically on the Designer email tool.

The Users, Workflows, Collections & Schedules tabs all have hyperlinks to the relevant sections of administration. However, this only shows the current 'as-is' active state. What would be useful is for each number show to have its own drillthrough to that subset of data, i.e. clicking on Inactive under users takes you to a list of inactive users, similarly clicking on Active Jobs under Schedules takes you to the list of actively running jobs etc.

This would provide a more intuitive navigation for admins.

Currently SAML configuration can only pass First Name, Last Name & Email Address. It would be useful if additional attributes could be configured, such as group information. This would link to another enhancement that is automatically linking new users to a given collection based on this additional attribute.

Currently pages you add to server when opened via the link icon open in a new window. If you are using SSO authentication, such as SAML this essentially logs the user out in that window. This is not a good user experience.

Ideally there should be an configurable option to open pages within the current window, thereby maintaining login and provided a better navigation experience.

When a user saves an APP and that APP contains macros with embedded macros (2 to N layers deep).  Make package with ALL subroutine/macros included an option.  This is a PAIN for users to try to manage otherwise.

cheers,

Mark