cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!

Enterprise-ready download for Alteryx tooling

As an admin - we currently need to download a large number of different binaries for every release; then package them for internal deployment; then send them out.

This creates unnecessary work for our admin teams, our packaging teams, our deployment teams etc.

 

This problem is becoming more acute now that Alteryx is shipping add-on tools via the public gallery - so our standard desktop designer can now require 10 or more separately packaged installs.

 

Can we please change the download experience to allow enterprise admins to:

- Select the components that they want in a standard download

     - This would allow for a menu selection across all the starter kits (e.g. Tableau; microsoft; qlik); the standard designer; the predictive

     - it would also allow for a menu selection across public gallery assets so that we can include things like the model comparison tool and other new predictive capabilities

     - the addins for Microsoft R Server

     - database drivers

     - Connect data loaders

     - Server components

- Given this set a name (like "Standard designer install") since in a large enterprise we will have several different configurations (some for super-users; some for standard users).    In our world we'd have "Standard Designer"; "Admin"; "Connect Controller"; "SuperUser" as our starting list.

- Then download one installer which is the aggregated set of these in one place 

- ... and finally allow the Admin to be notified when any component in the install set changes so that they can download the new version.

 

 

cc: @jason_m_mack @AshwiniChezhiyan @LizaNemchynova @revathi

3 Comments
Alteryx Certified Partner
Alteryx Certified Partner

@SeanAdams,

 

Don't forget to add the "Save Usage Data" configuration setting so that the enterprise can get the telemetry data (Phone Home) information for internal usage.  This requires modification of everyone's config xml.

 

https://help.alteryx.com/server/current/admin/Configuration/SaveDesignerUsageData.htm

 

Cheers,

 

Mark

Aurora
Aurora

That's a great point - so before we generate the package on the Alteryx site - add any custom config items like:

- Common Macro Paths

- Phone Home telemetry settings etc.

 

Good shout!

I feel this pain as well every time I get a new version packaged (going through that now for 2018.1) I really like the idea of a 'shopping cart' type experience from the licensing and downloads portal where we can pick the desired components, customized settings, etc., and generate a single set of binaries I can hand off to my packaging team.