Alteryx Server Ideas

Please could all log file paths on Server have the option to change their location, including 

C:\ProgramData\Alteryx\ErrorLogs\AlteryxE2

To enable all log files to be written to an alternative drive than the installation.

The benefit it to prevent excessive space usage on the C: drive

Support have advised there is no way to alter the path or limit these log files by number or size.

Many thanks.

Alteryx DCM has been an incredibly useful addition that supports key security concerns from companies. Currently, only three external key vaults are supported:

• Hashicorp Vault (KV secrets engine) - supported for Designer 22.3 and later.

• CyberArk Conjur - supported for Designer 22.3 and later.

• AWS Secrets Manager

https://help.alteryx.com/current/en/designer/tools/dcm---designer/dcm-external-vaults.html## 

I propose that we also include Delinea Secret Server.

Thank you and hopefully we can start to add more to make this feature widely useable and support security compliance.

Maintaining multiple workers (five currently, soon, six) with identical setups is challenging when dealing with In-Database (InDb) connections. I must log in to each worker, start Alteryx Designer, go to In-Db settings, and create the connection. This also becomes tedious when trying to update passwords, which occurs every 90 days in my company.

The suggestion is to set up an In-Db connection on one worker and have it propagate to the other workers. 

Propagates to other workers →

This would save time maintaining workers in the gallery and help prevent errors during setup on each worker (e.g., typing in the wrong password).

As an "extra credit" mission, expose In-Db connections through an API that can list, create, update, or delete an In-Db connection.

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. 

The dcm admin apis look promising. I would love if they could add put endpoints for sharing/execution and sharing/collaboration for admins. There is already a delete command for those two endpoints

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 just underwent an exercise of recovering my controller in the event of a catastrophic failure. One of the steps is to recover the DCME keys (DCM Encryption keys) - which is documented here: https://help.alteryx.com/20221/en/server/install/server-host-recovery-guide/dcme-keys-to-backup.html...

This DCME recovery needs to be revisited. This document assumes that the previous controller is running. In a disaster recovery situation, this is not possible. What, if any, can be done to recover the DCME keys if the host has is completely irrecoverable?

For context, having an irrecoverable host has happened. Complete hard drive failure (showing my age), nuked virtual machine and its backups (no one paid attention to the notices that the data center was shutting down), and fire.

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.

Currently, we see the Districts and Collections now compressed into a list view. 

Previously, the Server had the widgets feature which really showcased the self-service nature of the Sever. Losing that just made decreased the emphasis on user experience. 

It would be great to allow Server Admins to decide whether they want lists or widgets to be available toggles as a design feature for both districts and collections will be of great help.

In addition, regardless of the option, the image size and wording size should be much larger - easier for people to see. Right now, we have to zoom to 150% to make it easier for ourselves to see. Having the ability to control font size, font control with bolds, italtics, etc. will be very helpful as well.

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.

As we have more and more users onboarded to the Server, and many users share similar names, it is getting more and more complicated to manage. 

It will be great if we have a management console that allows us to create User Groups, Tags, set User Departments, and more controls alongside their curator, designer, etc status on Server.

Groups like User Groups gives a group of people access into certain workflows, districts, collections, etc. It will also be helpful as it can also be an audit trail of who ran what - with a feature that allows users or groups of users to run certain tasks or schedules. 

Sometimes, a workflow posted to the Server is calling from a source data that has dimensions which are specific to certain users based on departments, divisions, countries, regions, states, or etc. depending on the level of granularity. 

Although Alteryx developers can create Analytical Apps that have the option for end users to select these dimensions, a more seamless experience for end users (and better for security as well) is to have the ability to configure such filters for existing users on the Alteryx Server itself.

So, if Person A belongs to State 1 and Person B belongs to State 2, by default when both Person A & B enter the Server to that specific workflow in a collection or district, they will automatically be filtered for State 1 and 2 respectively. 

This is similar to Section Access configuration - whereby users have already been pre-filtered the moment they enter.

The current workaround is to create multiple workflows and store them in different collections or districts specific to end users, and to make any changes will require a change to the workflow itself. 

It will be great to have a dashboard that allows for Alteryx Server admins to configure on their own without hassle.

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.

In an enterprise multi-node Alteryx Server deployment that has existed for many years and many upgrades, there are artifacts within the MongoDB that are unknown to Gallery Administrators. I envision a workflow or app that is developed by Alteryx that queries the MongoDB and looks for orphaned documents in the MongoDB across all collections. With 2022.3 there is a pre-upgrade check, however, it does not find all unexpected items within the MongoDB. Regular ongoing MongoDB health helps with overall management of the environment and could prompt for support cases before it becomes a problem during pre-upgrade activities.