Alteryx Server Ideas

I did not find a better category, but this issue relates to Data Connection Manager and credential setup with key files in a Server and Desktop environment.

Issue: When using key file credentials in DCM a Key File Path needs to be specified. This path cannot be a UNC or Mapped drive, has to be a local drive for Google BigQuery with the latest Simba ODBC driver at least. This prevents centralized credentials management and defeats the purpose of DCM. I understand this might be a driver limitation, however it's still an issue that I think Alteryx could handle.

Suggestion: Since the key file is simple text (JSON) file, it could be embedded (i.e. uploaded via the DCM interface) into the connection itself. That way it can be centrally distributed to the local computers when the DCM connections are synchronized from the server (or vica versa). I would also store them encoded for Information security reasons.

Bonus: Tying into this it would be really good if Alteryx Desktop would automatically sync Server DCM connections when a connection is made to Alteryx server the first time after the software was launched (i.e. opening a Server workflow) to keep it automatically updated.

For admins to be able to prioritize workflows, because by default, users are not allowed to prioritize jobs.

In combination with Quality of Service (3 - Critical Priority and above) and worker tagging, for example we have all workflows belonging to a project tagged to a specific worker, but since "Member" (default) users cannot prioritize jobs, these workflows would never run on this specific worker

As the Alteryx Server administrator, I would like to see this functionally restored.

See attachment

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.

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

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

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

Hi folks

There are quite a few very useful Alteryx items I have been using recently that I have found on the help pages / public gallery. However, when I searched for them, I didn't quite use the correct search terms so this took longer than I had hoped and I was on a tight deadline. An example is the "Server Pre-Upgrade Checks" workflow used during Server upgrades.

My idea is to put these utilities in the Download portal in the same way that the Server Usage Report is. 

Of course, there should be a limit as to what goes in there but, like the Server Usage Report  can be done on a case-by-case basis. 

Cheer, jonna

I have inherited admin duties, and have been running to many problems. Some of which will escalate when the subscriptions go away. 

The pages desperately need to be updated for a more streamlined admin experience.

Couple examples I came up with below. 

Naming Convention

• Allow workflow renaming without the replace function.
• Force a unique plan name across all private studios. instead of being unique on just ID.

API Access

• Allow any user who can access the module from Collections to be able to trigger it from the API using their own API key.
• Store results of "API" triggered workflows on the page.
• Groups:

• Identify Users without a group
• Identify users in more than one group
• Add multiple users at one time (Muticheck box) with filters.

User Page

• Add/remove Users to Groups
• View, add, and remove Collections from Their User Page

Collection Page

• Add Collection from the Admin collection Page

Designer "save" window.

• Give the ability on Save As & Save for the user to automatically share the plan with their collection(s).
• Default all "Workflow" assets to be unchecked by default, rather than relying on users to click "workflow options"," manage workflow assets", and then uncheck everything.

Workflow Page

• Change Owner (Can be limited to admin only)
• Add directly to collection from this page.
• Do not reset the "private data exemption" to default every time an updated version is updated.
• Allow admin users to see logs of all users who run the plan (Also add this to the admin page while you are at it)

Hello,

In our environment, we decided to do not use the Data Connexion from the Gallery for internal security reason.

Then we use the internal Designer in the Server to create (IT Teams) all the BDD Connexions for our workflows (In Memory and In DB).

Our Curators (not in IT Teams) has only access to the Gallery and not directly to a Server but it's responsible of these conenxions.

I checked all the API and we cannot retrieve the list of our "In DB" Connexions.

Is possible to have a new API to list all these connexions or to have an update of the existing API /admin/v1/systemdataconnections ?

Thanks !

In the User record you can get the subscription ID, but it doesn't show the Subscription Name and doesn't provide a link to the subscription which would be helpful (and seems pretty simple to implement).

I know subscriptions are going away, but until they do please make working with what we have easier.    Thanks!