Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello 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-licensing-our-products/ta-p/158030
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
Add Admin ability to place the Alteryx Service (Engine) into Maintenance mode allowing current workflows to complete, but all new workflow processing moved into Queue to allow for server configuration and/or maintenance.
Currently, if I want to make a small configuration change (like a memory setting in the Runtime settings) I have to hunt for a quiet window or the lowest level of activity to kill the service (and the running jobs).
It would be helpful to flip a 'switch' and have all new jobs go into 'Queue' allowing for the change and service stop/restart ... then pick right back up with the queue in configured order. (execution time, priority level, etc...)
Submitting this idea based on the Case #00361430.
We are trying to do alteryx workflow chaining based on workflows available in alteryx gallery, but this option is not currently available in alteryx right now and we are raising this idea to enable this feature in upcoming release or existing version patches.
Currently couple of methods available; saving the workflow in network share drive and chain the alteryx workflow based on events or run another analytical app on success.
The disadvantage of these methods are,
1. We cannot have version history maintained for the workflows in network share drive.
2. We cannot able to run a specific workflow in chaining as the workflows are packaged together.
Good Day
We need a way to read a workflow log file while the workflow is running .. we want to peek inside the log file to see what is happening in the workflow, especially for the case when the workflow seems to be "hung". This would be an invaluable troubleshooting tool.
Currently these worklfow log files are locked by Windows and are inaccessible by all but unapproved 3rd part utilities .. if at all.
Often these logs disappear if the workflow needs to be deleted in order to save the environment
It is noted that the service logs do not exhibit this behavior, so the request is to
1) allow the running workflow logs to have the same behavior as the service logs
2) provide a work around to allow reading of the running workflow logs
3) ?????
Thank you for thinking about this
Tom D
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
Schedules on Alteryx Gallery/Server
Admin settings for the Alteryx server are currently split between the Admin GUI in the gallery (screenshot 1 below) and a tool called "Alteryx System Settings" (screenshot 2 below).
Please could you move all of the system settings into the Admin section of the GUI. Not only will this allow an admin to administer the settings remotely (rather than having to be logged into the actual server with an interactive login which is needed now) - it will also consolidate them into one place which makes things easier for admins to ensure that all settings are set up correctly.
This could be done progressively - a little bit in every release - over the next couple of releases, it does not need to be done in a big reengineering or a massive big-bang release (in fact - progressive release is much more favourable since you learn along the way and big-bang releases are well known to be failure prone).
cc: @TanyaS
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
Currently the e-mail settings for the server are set up using a wizard and are not available within the admin UI.
Please could you add an explicit section to the Admin UI to allow the admin team to set up approved SMTP settings, allowing this all to be managed in one admin console.
Further: Can you allow the admins to push these settings down to the desktop users. This would allow the admin team to control the SMTP usage and prevent data leakage. It would also reduce complexity for the user since the SMTP settings are all pre-set making eMail tools; and Events easier to set up.
It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).
My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events. On a large implementation, this becomes very difficult to manage.
Hello,
Now it is possible to share a collection which a user who is not granted to access Alteryx server.
We use AD to grant users access to Alteryx Gallery. However, when a user is not in this group, it is still possible to choose him as a person to share.
In my opinion, such user should be indicated as someone who won't be able to use a shared collection, or he should be presented at all.
Best,
Piotr
A nice to have is a connector for Microsoft Flow to trigger workflows. With Microsoft Flow, users can automate processes, or set conditions that can trigger services across many different providers.
Having the ability to use a Microsoft Flow can enable alteryx users to run workflows and feed in data that could be used by Microsoft Flow to feed into other processes.
This would be a game changer for many users.
Hello,
I've used a standard configuration to set up an Alteyx server. The gallery is available at https://alteryx.samplecompany.com/gallery
I'd would be really helpful if you enable to create a landing page at https://alteryx.samplecompany.com/ and add a possibility to host add extra pages. The easiest way to do this is to add an option to the Alteryx Server configuration wizard and read the pages from Alteryx workspace location.
Additionally, such landing page should have redirection from HTTP to HTTPs.
Best,
Piotr
Hello,
The Analytics team for our company services 9 different lines of business, and it would be helpful to create sub folders within each line of business. It would be helpful to be able to restrict the access for each individual sub folder also. Our team deals with different teams within each line of business, and they may need to have different access due to sensitive content.
Thanks,
Erik M
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.
As Alteryx leans more into the Data Science space - it becomes more important to be able to keep rich documentation of the project along with the Alteryx Asset. This does also require the concept of a "project" on the alteryx server, which would allow for meta-tags; and various different documents to be added with the project.
This would include things like Requirement documents; test evidence; test data sets etc.
This would extend Alteryx from a data prep engine to more of a data-science workbench as different user groups can participate in a specific project.
Currently when scheduling workflows, there is an option to schedule based on the calendar day but not on business day. For example, if I want to run a workflow on Business Day 1 of every month, it is not necessarily the first day of every Month. For the month of June 2019, Business Day 1 is June 3rd, since the 1st and 2nd fall on the weekend. Many departments run their processes on Business Days rather than Calendar days. Also factoring Holidays into consideration would be a plus since January 1st for example is a Holiday, Business Day 1 would fall on the 2nd.
I really want to see this feature in new versions. Its frustrating the lack of options we have with scheduling workflows on the server. I need to have my process run every 10 mins but only on certain days and in certain time windows. Creating a schedule for this is impossible unless I manually create hundreds of schedules.
I have a few workflows that I have hosted on out Gallery Server and I have them scheduled.
Ex: Process A is scheduled to run every 10 mins Mon – Sunday.
Problem: I only need Process A to run Every 10 Mins on Mon – Sat from 2 AM to 6 PM
Currently there is not a scheduling configurations that allow this type of schedule. How can I get my workflow to run every 10 mins but only during certain times and on certain dates?
Right now, if you are using Windows Authentication, you can map AD group and users on the Permissions and Collections tab. But for some reason, you can't use AD groups on the Data Connections tab. Most of our databases are already secured by in-house AD groups in which you have to be a member in order to access that database. Instead of managing a 2nd, most likely duplicate, list of users in the Data Connections tab I would like to be able to map the pre-existing AD group to that data connection. That also means I don't have to service access requests. If someone wants access to a database, they talk to the database owners, get added to the group and then they automatically can pull that data into Alteryx.
We have several clients that operate in a Multi-Forest environment due to mergers and acquisitions. Currently with Alteryx Server the only option we can offer them is to use Built-In authentication. A lot of corporate and particularly finance institutions prefer a single sign on approach and utilise Windows authentication to do this.
Would it be possible to add support for Multi-Forest organisations into Server to support organisations going through mergers and acquisitions?
This would really benefit us in selling Server in to organisations with complex structures and reduce friction in publishing or preparing workflows.
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.
It would be nice to be able to widen this window much like we can with the Workflow dependencies window.
So, .YXI files are great, they allow a much simpler installation process of macros from the Gallery to your local machine and server.
However one problem; they are not supported to be hosted on the Alteryx Gallery. This means that in order to share .yxi files they have to be hosted on some other drive and then you have to have a workflow in the alteryx gallery which provides users with the download link.
This makes that clean process a bit less clean, and it also causes problems with big customers who cannot whitelist these share drives for which the .yxi files are hosted. I myself have had about 20 emails from one global consulting firm in the US requesting access to a macro, I can't link them to the content as they are blocked, and therefor I have to email them individually.
It's a tad tedious and ruins the 'install experience'.
If you don't know what I'm talking about you can follow my colleagues (Peter Gamble-Beresfords) blog here:
https://www.theinformationlab.co.uk/2017/10/05/create-share-alteryx-tool-installer-yxi-file/
What I'm asking for is simple, support for .yxi files in the Alteryx gallery, in the same way you do with macros.
Ben