Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.
Free Trial

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

Hello all,

This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensi...

I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
https://www.amd.com/en/processors/epyc-7002-series

image.png

 

So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration

Moreover, Alteryx Server Additional Capacity license should be 4 cores.

Best regards,

Simon

Hello,

We would like to have the option to configure the timeout of the manual running jobs, as already exists for the schedule jobs.

 

Regards

When I create a DCM Entry in Gallery, it would be great if the users I share it with would also be able to reference the credentials in their desktop designer when they sync their connections to the Gallery. 

When scheduling an analytical app on Gallery, there is no UI for submitting app values. This significantly limits the value of scheduling workflows and using analytical apps. With this feature, it would allow our users to have more flexible scheduling while also simply maintaining one workflow. Because this feature doesn't exist, we have had to build workarounds by either creating multiple workflows or utilizing APIs. 

 

Since this feature is already available for manual runs and APIS (shown below), it shouldn't be a reach to also have this feature when scheduling a run.

 

Manual Method:

elsastark_0-1665672271718.png

 

API Method: GET /workflows/{appId}/questions

 

Scheduling Method (no app questions): 

elsastark_1-1665672495023.png

 

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.

I've seen various solutions/workarounds but this seems to be a table-stakes ask?  When scheduling a workflow I should be able to specify which parameter values to run with.  Just two of many use case examples - 

Use case #1 - a single analytic app could be scheduled multiple times, each schedule specifying a different line of business

Use case #2 - credentials, allow the user to schedule a workflow with their saved credentials.  When their credentials change all they would have to do is update the schedule parameters

 

(If you know a better way I'm all ears, not the API thought that isn't a bad way to do it, just not super Easy)

6-25-2020 5-39-35 PM.png

We want to share direct links to analytics apps with our users.  However this does not work with our current SAML login.   This the use case.  

1. User clicks on direct link URL for the app  

2. User  is required to click log-in button

3. After login user is taking to the gallery home page not to the app

 

The end effect is that we cannot share links to apps with our casual users, instead we have to instruct them to go to the gallery log in and then search all public workflows for the specific app they are looking for.   Not a great user experience, especially because we did not have this issue before single sign on support. 

 

personally I think this is bug more than a feature request, but was asked to create it as a request by support 

I would like to see the enhancement of being able to schedule a start and stop time for specific jobs that need to run multiple times per day, so they don't run during the nightly backup periods of the Alteryx server. This can cause the daily backups of the Alteryx Gallery to fail. Currently SQL Server Management Studio/SQL Server has the function to able to schedule start and stop times for specific job. Currently Scheduler page on Alteryx Gallery/Server lacks this feature.

 

SQL Server Management Studio

mackedet_0-1590532280855.png

Schedules on Alteryx Gallery/Server

mackedet_1-1590532639645.png

 

 

Hello all,


Alteryx Designer Cloud is quite young, somehow incomplete, not compatible with Alteryx Desktop etc... but I'm very optimistic than in a few years it will become a killing app !

That said, I'm more skeptical on this race to the cloud : from my experience, Cloud should just be one way of selling a product, not the only one. It has a lot of cons and a lot of pros and customers should have the possibility to choose between "on-premise" and "cloud"  product, and change from one to the other very easily.

My main customer on Alteryx is a government agency that deals with highly confidential, personal data. They won't go to cloud. Not in the next ten years. But they would love to have the Alteryx Designer Cloud on their own server.

Best regards,

Simon

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. 

indb.jpg Propagates to other workers → indb2.jpg

 

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.

 

Currently, failed job results stay in the Mongo DB forever.  Please either make it adhere to the same coding in the Server Settings for "Delete queue and results after (days)" setting, or make it a separate option for failed jobs. 

It would be beneficial to be able to add a description to collections to explain the purpose of the collection, i.e. the types of content contained within or even a waiver stating "use of the contents in this collection is at your own risk, please ensure you validate the results are accurate" sort of thing.

I would like to be able to view all schedule results from all users in my Gallery.  Currently, I can see the "Workflow Results" for any schedules I create.  But I cannot see them for users unless they share them.  As admin, I want an option on the Gallery Admin screen just like there is on the Gallery user screen to see "Workflow Results" for every schedule that is in the Scheduler Database, regardless of who the user shared it with.

 

Currently, the only way to accomplish this is to go to Designer, View Schedules, connect to the Controller, and go to the Results tab.  This should be built into the Admin screen in the Gallery.

Hi all,

 

In an enterprise environment - DB connections need to be set up from the server and pushed down to your users; and they need to be managed across the various servers in your software lifecycle.

 

In other words - you may have a sandpit / dev server env; a UAT env; a pre-prod; and a prod env - and each of these need to have the same DCM credential IDs so that users can access these.     

(before you say "you can do this from the desktop) - that is true, however that's not a workable solution in an enterprise env because that means that users can change the password from their desktop into a prod env which is a breach of IT General Controls)

 

The solution here is to break DCM out in to a separate service - where

- all your servers (dev; UAT; Pre-Prod; Prod) can all point to one instance of DCM

- users can maintain their own connections and credentials

        - Each needs to have up to 2 owners so that you can deal with people moving jobs / leaving the firm

- users can also entitle these connections and credentials to their team members so that when the team member logs in, it shows a popup saying "you've just been given access to new credentials / connections"

- A particular connection may have multiple different variants - depending on the environment.

        - HR Data may point to a UAT version of HR data if you're on the UAT server; and to Prod if you're on the Prod server

        - if a connection is environment specific - then it also needs to have segregated credentials (since the login to your UAT HR Data may not be the same as prod).

 

Thank you all

sean

 

cc: @wesley-siu @_PavelP 

 

 

Hello,

Maybe it's time to have a better licensing model. In addition of the current and restricted core-base model, why not having a user-based model?

Best regards,

Simon

I'd like to request the ability for the Curators to change the priority on Apps in the Gallery.

 

Today we have a system where users are not allowed to set the priority on workflows. The Curators change the priority of scheduled workflows based on workflow runtime/ business need by going to Gallery Admin> Jobs> Scheduled Workflows, and then editing the schedule priority.

 

The problem that that we have a numbers of Gallery Members/ Viewers that run Apps through the day that are very fast to run, but depending on how big is the queue they can several minutes/ hour until a spot is free to run.

 

If would be very helpful to get a better UX if the curator can choose which apps should have a higher priority to run.

 

Thanks,

 

Mauricio Estevez

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.

Hello

Imagine the dream : Alteryx Designer Cloud with in database tools.

Well, that would be so great I won't write more....

Best regards,

Simon

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.

Situation:

As your analytics work grows - you find yourself using the power of Alteryx to create shared macros.    These act as an accelerator for a team because one team member can us a reusable solution created by another team member.   For example - many teams need to get data out of JIRA (or some other system) so you create a connector that everyone can use.

 

That's going well - and now you have 20 teams all publishing canvasses to your server (possibly 100s of canvasses running in production) which make use of your JIRA connector - all good so-far!

 

Problem:

BUT THEN - you discover an issue with the JIRA connector and you need to fix it and publish a new version!

 

It's at this point that you realise that the canvasses on your server which use your JIRA connector are NOT pointing to it, but they have made a copy and included this inside their canvas.   So when you fix the problem with the JIRA connector - no-one gets the fix!

 

This is because every application uploaded to the server is a yxzp file, which zips up a COPY of all the shared macros and uses this in an isolated way.

So - in order to get the new JIRA connector (with the defect repaired) used instead of the old one you now need to:

- Download EVERY canvas on your server

- Unpack them all to expose the sub-macros being used

- Inspect them to see if they are actually an instance of the JIRA Macro

- Make a list of the owner and application IDs

- reach out by e-mail or phone to every one of these folk to ask them to republish their Alteryx workflow with your new version of the JIRA connector.

 

 

Proposal:

Please can we revisit this - we really do need the power of shared macros - and we also need the ability to fix and manage these like a product over time.   This will have an impact on the engine (hence copying @AdamR_AYX ) 

 

Desired end-state:

- When you build a canvas using a shared macro - it doesn't store the macro itself, but rather a reference to the version on the server - unless you explicitly decide to break the connection and take a copy.

- When you check this canvas into the server - your application / yxzp does NOT include a copy of the shared macro - instead it has a reference link

- this means that Alteryx Server can now track which canvasses use this shared macro very simply

- When I fix this shared macro - I can then do an in-place update; or if the interface is not the same (i.e. different inputs or outputs) then this has to be a new version and the users will stay pointing to version 1.

 

This is how shared assets are managed in a micro-service world, which is the way that all of our architecture is going - and it seems important that we build this thinking into the Alteryx infrastructure too.

 

 

 

 

 

 

 

@AdamR_AYX ; @Treyson ; @SteveA @DerekK ; @BlytheE 

Top Liked Authors