Alteryx Server 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

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

I am in the process of migrating apps from the old gallery to the new. I have screen captures of the results from the same app in both. In the older gallery version, if there is only a single file type available, it defaults to that file type and you click the icon for the type. In the new gallery version, you must select a file type before you can download the file, even if there is only a single type available. The dropdown makes sense for one that you have multiple types (like pcxml), but it makes no sense to require the user to go through an extra step to select a type before downloading when that's the only type they can download. Please see all the screen captures. The blue-ish background is from the new gallery.

I’m facing issues with scheduling workflow in Europe/London timing. I’m trying to schedule jobs to run at 10pm UK hours everyday (except Fri and Sat) starting from today i.e. 26th Jan (as per UK timing)
However since I’m in India and my local desktop is showing India time (which is 00:15hrs on 27th Jan), the Alteryx Gallery scheduler is picking India hours but not as per the region we selected. The 26th Jan date is greyed out and unable to select.
The workaround for this to change local time on desktop which is not in our control in our case.
Could you please bring a change in this behavior. If I am am scheduling on x date a workflow for a timezone which is x-1 the scheduler should allow me to set up the schedule.

In prior versions, Gallery Admins could easily and quickly reactivate users that were deactivated (e.g., and employee leaves the company so we inactivate their Gallery account, but then they come back to the company in a few months with the same name and email).  

Now, the only way to do this is to edit the Mongo page.

We need a way via the UI to reactivate users, like we did in the old UI.

I suggest adding an option in the current User List/Grid to be able to filter for Inactive users.

Ability to change the default workflow settings when to also include [Others may view this workflow's history] in a similar way to the other attributes in workflow settings that are set by default.  This would prove beneficial for workflows which are shared across a large team and need to be run on a consistent frequency and are not run headless.  The inability to set this by default leaves a risk that the setting remains unchecked and more than one user triggers that workflow in a given month which could result in a material impact if the output of that workflow is posting to another system in the firm.

Hello, 

We have been building a solution for a client that involved chaining apps. When we uploaded the workflow to the server, we got the below error: Workflow exceeded maximum runtime of 30 seconds and was cancelled. We were able to rectify this by having the client implement the change here. While I understand the need for the limit, is there any plan to have this fix be more obvious to the average user to implement or avoid needing to reimplement following a server upgrade?

Thanks, 

We have situations where some workflows that are scheduled end up having intermittent connection issues to other databases that result in the workflow running to timeout. The timeout settings are set in the server, but it would be nice if you could set an override value for a lesser timeout in the runtime settings for individual workflows and basically use the server setting as a not to exceed value. We have a multi-node environment with multiple worker nodes and about 250 artisans. We have some regularly scheduled workflows taking the full amount of time in the timeout setting and obviously if a couple of normally quick running workflows ran to timeout that causes issues with the queue.

I Would Like a new Email added under [ Admin -> Notifications -> Emails ] where it would send an Email when a Schedule reaches the status "Complete" 

This can serve a couple of use cases;

1. You have many things going on and this email can let you know "This schedule has now been completed"  
   1. From my experience we usually schedule things indefinitely, however if an end was put in place this can be a reminder of whether or not to continue scheduling the workflow
2. It can also notify when a schedule inadvertently reaches "Complete" status, in the backend this could be because it has status "Corrupt: AlteryxService_RetrieveSecureData Failed."
   1. This has caused issues multiple times of schedules that are supposed to be indefinite reach "Complete" Status without our knowing. With many workflows and schedules this is not something we can babysit.
   2. brief research suggests this error could be due to restarting the Alteryx Service during a schedule, which we do weekly for our backup. And trying to coordinate a time when no schedules are running is difficult when something runs every 10 minutes.

Issue: When Workflow names have similar beginnings on server a user cannot distinguish between them because the columns on this GUI are not expandable as would be expected. A user has to make their browser larger and all columns open proportionately.

Solution: Change column settings so users can drag column widths to make changes. A bonus would be to allow a user to set a default along with an option to always auto expand all.

It would be good to have a new field with the owner of the data connection, when users asks to be part of a data connection, we should know who is the identified owner to contact and ask for approval.

Thanks.

Regards

Joana Santos

I am an Artisan but not the Owner of the studio - I uploaded the workflow and would like to see all the jobs (including manually triggered) that run for my workflow so I can track any issues i.e. when workflow fails. I checked with the Owner of the studio and he also can see only the runs he triggered. 

I understand from the Support team in my company that option to see all the jobs that run is currently available only for the Curator role but would be extremely helpful if you would make it available to all the users that have access to the Private Studio.

When we download from the gallery, please return both the altered gallery code and the original unaltered code so user can choose the base to build next version on.

Most everyone learns the hard way that saving to the gallery alters their code in ways that it may no longer work as it did before when running on desktop. After figuring out what has happened and laboriously un-doing the alterations that happen when saving to the gallery, we develop schemes to keep separate desktop versions of gallery apps in sync. These schemes should not be necessary. 

The publishing endpoint, a POST to api/admin/v1/workflows/, is useless whenever workflows, apps, or macros contain Gallery Data Connections.  The workflow will get published but valid Gallery Data Connections are ignored and the apps will not run.

Please add the same dependency checks against Gallery Data Connections as is performed when a workflow or app is manually published from Designer.

This might be considered a subset of the Idea Server API to extract / submit workflows.

Thank you for your consideration.
Sincerely,

David

When saving to our company's gallery, we must deselect dozens of assets for our numerous workflows every time they need to be resaved, which is very frequent.

I would like to suggest a select/deselect all button under manage workflow assets. This would save a considerable amount of time.

Thank you,
Daniel

The Schedules tab of the Gallery currently lists all schedules, 20 to a page, with no option to filter.  I am currently managing 183 active schedules.  In order to find a single schedule, I have to sort by Workflow name, then page through 10 pages of schedules to find the schedule I'm looking for.

Please add an option to filter this list. 

Ideally, I would like to be able to filter on multiple fields at once (example:  Priority = High, Status = Active, Owner = Bob Smith, Times Run > 20).  Barring that, a simple search option on workflow name, similar to the search option on the Collections tab, would be enough.

We leverage Active Directory groups to manage user permissions to most of our company's resources like databases, file shares, applications, etc.  This idea is for the ability to manage a Gallery Data Connection via an Active Directory group.  In many cases, our AD group membership actually dictates what permissions a gallery connection should have, but we must manually add/remove users to the Alteryx connection to keep it synched with AD.

I think there are several ways Alteryx could be enhanced to support this; i.e. the AD group could be specified on the connection itself or it could be inherited from a Studio where the subscription is enhanced to support assigning AD groups to it (which could benefit other areas of Alteryx).

I'm told by Alteryx support that this functionality is unsupported but to post the idea here.  If anyone knows of workarounds to this limitation I'd certainly be interested!

When using In-DB with iSeries over Generic ODBC everything works fine in Designer however when executing via Gallery process fails because a semi-colon ";" is added to the SQL statement as a terminator character and iSeries rejects this SQL0104 - Token ; was not valid. Valid Values < END OF STATEMENT > 

We have a MongoDB connection string that we plug in to RuntimeSettings.xml during install.  Upon startup, the Mongo connection fails because RuntimeSettings.xml expects the connecting string to be encrypted.  The fix for this, is for someone to manually update the MongoDB connection via the Alteryx UI.  We would like a way to encrypt the MongoDB connection string for RuntimeSettings.xml before we start Alteryx for the first time.