alteryx server Ideas

Share your Server product ideas - we're listening!
Register for the upcoming Live Community Q&A Session - and don't forget to submit your questions for @DeanS regarding the future role of analytics here.

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the like in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

2019.4+ Server now prompts users to select an Encoding Type when downloading a csv on the gallery. Unfortunately there is no way to disable the prompt of which encoding option to utilize or an ability to select a system default. Please provide these server options as this is causing confusion across departments. 

 

.csv output.csv output

.yxdb output, csv format.yxdb output, csv format

(many users like the preview provided by yxdb but want excel download)

 

During development in Designer, when the workflow is configured to output to csv it already has the encoding configured, please provide the option to at least default this at output on the gallery:

.csv config.csv config

 

The only alternative at this time is to republish all workbooks configured to output .csv or .yxdb to be .xlsx. This is not ideal.

 

Note: Scheduled jobs are not affected - I tested a scheduled run and csv files were successfully written out to a file share on the server. Content format appears to not be impacted. 

 

Thanks!

See following article for background reference: https://community.alteryx.com/t5/Alteryx-Server-Discussions/workflow-exceeded-maximum-runtime-of-30-...

 

I have a support case (#00278355) advising unsupported changes to the alteryx.config file, involving an undocumented setting for chainedTimeout, as in:

 

<engine enableAutoLicensing="true" useServiceLayerComposer="true" chainedTimeout="10800"

 

This setting should be documented, supported, and made user-configurable through the System Settings GUI. 

 

 

When an artisan moves positions (within or external) away from their current responsibilities, their collections and workflows should be able to be transferred via an administrator to another user.

As the Server Admin I'd like to have the ability to view ALL "Workflow Results" for all Subscriptions.This will give the highest level admin the ability to monitor all schedules (on the entire server instance) and monitor if they are unable to complete successfully (example- unable to allocate memory) and any other errors are occurring. 

 

Knowing this information will help the server administrator understand if there are issues with the server itself (e.g. if we need more workers or to simply adjust actual server system settings..etc..)

 

 

 

 

For whatever reason a schedule is disabled, whether a Studio expires, or for any other legitimate reason, a notification email should be sent to the Admin and the one that created the schedule in advance of it being disabled. When a scheduled workflow is not executed, it leaves us scrambling for answers. A sudden disablement of the schedule is disappointing to discover after all other stones have been turned. Notify us in advance of a schedule being disabled. 

The Save to Gallery window does not resize. When I try to Save my Workflow to my Gallery and Manage Workflow assets, I can not widen that window to see the full path to my assets.

This makes it very hard when you have many assets to know if they need to be included or not with the promotion. It may take two or three attempts guessing what asset is what to get the correct combination to make my App run correctly.

 

Assets.png

 

It would be nice to be able to widen this window much like we can with the Workflow dependencies window.

Allow to create custom user security groups server .

Sales
User1
User2
Studio1


Supply chain
User3
User 4
Studio3
Studio1
......

As a server administrator, I would like to have more control over collections.  I have a user who is in charge of a collection out of office, and we have some users who need to get to be added to the collection to run workflows.  As admin of the server, I would like to be able to add users to this collection, modify permissions, modify workflows, etc.  This would be necessary both for when users are temporarily out of the office as well as if someone were to leave the company.

One of the issues that we have with Alteryx jobs in prod (and also Tableau, coincidentally) is that often a canvas is built to serve a need at the time, but after a while it's no-longer needed but it continues to run and consume server resources.

 

Can we add the option to our server environment to request recertification that a particular job is still needed every X months.

This will achieve 2 useful purposes:

- if the job is no-longer needed then the user hits "No thank you" and it's then taken off the scheduler which reduces server loads

- Alternatively - the user may realize that this should have been handed over to a new team or owner, and they can then make this change based on the recertification prompt.

 

I'm pretty certain that this would help to manage the inevitable build-up that happens on server environments where jobs build up until the server starts thrashing and the admin team then need to go out to all the users to do this recert process manually.

 

 

CC:  @rijuthav@jithinmony@HengHe@RajK@ydmuley@revathi@Deeksha@MPistone@Ari_Fuller@Arianna_Fuller@JoshKushner@samN@avinashbonu@Sunder_Sriram@Rahul_Thakur@Rahul_Singh

It would be useful if the Admin of a Private Gallery (in house server) could delete studios and/or members.  Also, it's confusing that a member who's added also gets a Studio automatically set up.  Members (for my purposes) are only supposed to be able to run apps in collections that I grant them access to.  They should not get their own studio.  Even if they can't use the studio (or even know that they have a studio), it's not very efficient to have all these studios show up on the subscriptions screen.

In regulated environments, like banks, there is a requirement to fully segment Alteryx Jobs so that people on either side of a Regulatory Wall cannot access each other's canvasses or results.

 

As an example:

- Public vs. private side in Broker/Dealer banks

- Compliance or HR or Finance need to be segmented from all other areas in most banks

 

What is needed here is for any canvasses belonging to each of these walled-off areas to be controlled so that they cannot be shared across the wall, and results cannot be viewed across these areas.   This also means that the Gallery Environment needs to be capable of being segmented fully within 1 installed environment.

 

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

 

 

Along with setting a schedule for an app in the gallery, the user should also be able to set the different interface values for each schedule he/she makes.

 

My main use case is regarding having generic templates for ETL processes, that have multiple different types of runs based on configuration values, but I'm sure there are plenty others.

 

Best,

dK

Use Cases:

 

  1. As a server admin, planned PM outages should be scheduled.  These outages should prevent jobs from beginning execution (window of time) prior to the outage.  Jobs running at the time of the cut-off should be system-cancelled.  
  2. As a server admin, unplanned outages should cause running jobs to stop.  At the conclusion of an outage, jobs that are system cancelled should be restarted.

Currently, we use Task Manager to control Alteryx Service (or command line).  An administrative function within Alteryx should support graceful stopping and starting of the service as user jobs are interrupted (or can be) by our activities.  While I currently post messages to users alerting them to admin activities, I am asked why Tableau can restart jobs (admin) and we can't.  Other admins have asked what is "hanging" alteryx service up for a STOP command.  I have explained that all jobs must be stopped in order for a quick restart of the service.  

 

We're using a single server today (this client) and plan to add workers to the configuration.   It would be helpful to know where work is running and be able to use admin functions across the servers.

 

Cheers,

Mark

My company, a very large organization, is in the early implementation phase of Alteryx right now. My company requires frequent password changes and we plan on making heavy use of Shared Connections since there are also many shared data sources. Unfortunately, this would mean that every time a credential has changed that affects a workflow, the credential holder would have to contact Server Administration (me), and I would have to update any Shared Connections or other assets that use those credentials. This problem is exacerbated by also having to manage user permissions and which users belong in each Subscription Right now, that is not much of a big deal, but as the number of users begins to scale, this could become a very daunting task.

 

My current solution is to create Subscriptions for each Department, Group, or Team and give one person from that Subscription Curator permissions. This enables each Department to work more autonomously and reduces the load for Server Admin. The issue is that there is no permission level between the publishing rights of an Artisan and the ubiquitous acces of a Curator. So, with my solution, any one of the Subsription Curators can start using connections they're not supposed to have access to or deleting/stopping scheduled flows, intentionally or otherwise.

 

I propose that we find a middle ground between Curator and Artisan, a (Studio) Moderator. This person can be assigned one or more subscriptions by a full Curator and will have Curator-like permission, but only to the assigned Subscriptions. This means that they will be able to add/modify Credentials, Connections, and/or Scheduled under the envelope of their Subscriptions, but they won't have access to any others. I believe that this solution will mitigate the possible overflow of tedium to the true Curators while allowing the powerful communal features of Alteryx be used to their full potential.

When saving a workflow to the Gallery, I would like an option on the Save window to save directly to a collection. This can be an existing collection, or would have the ability to create a new collection. The current process requires you to log into the Gallery after saving the workflow and move it to the appropriate collection.

Please provide the ability to bulk add/delete users to a gallery. This would be useful for on-boarding/off-boarding large companies, departments, and external customers. For public-facing galleries, this would provide us the ability to on-board/off-board entire customers of ours. 

Not sure if this has already been suggested but I couldn't find it in the ideas...

 

It would be awesome if in the Gallery some better documentation could be created for the naming of the different private studios, collections, and districts. The naming causes some confusion because it is so different than most other products which causes confusion in our company.

We have the need to bulk-add users, and to bring in their information (full name; location; etc) from Active directory.

 

Right now, adding users is a 1:1 process which is highly painful.

Desire is to be able to take a list of Kerberos IDs, and bulk add them as users - and then select a group of them and permission either for the gallery; or for designer licenses.

 

cc: @revathi @avinashbonu @Deeksha

Hi,

 

I have an existing app in my company's gallery. I updated the app in the gallery to not allow others to download. I just made changes to the desktop version of the app and saved it to the gallery, then went thru the steps of replacing my existing gallery app with the new version (this part I like). BUT, after updating the app, when I went back into the app settings, the option for others to download was checked again. To me, the app should inherit anything that was manually done to it in the gallery, like making it not downloadable. Is it possible to have this changed in a future release?

 

Thanks!

Aliases are a really powerful tool, particularly when you have multiple environments (EG Test, Prod) and need a published workflow to work without any code changes (In particular in an IT or Release/Change Control model).  By configuring a system alias on your Test and Prod servers, code will dynamically point to the correct server.

However, aliases can be somewhat cumbersome if you have a lot of databases on a server, and those database names change by environment.  Effectively, you end up needing an alias for each Database, which runs into naming convention and standardization issues.


Having the ability to configure a "database value" or a "database alias" would do a lot to help this.  This could either be a file that would be attached (allowing for easy config changes without risk of modifying the underlying code structure) or a secondary tier of aliases, so that a connection string might go from:

aka:SQLSERVER (contains sqlserver and database information)

 

 

to:

aka:SQLSERVER||aka:database - so that at runtime Alteryx would evaluate the SQLSERVER alias and the database alias to create the correct connection string for that environment.