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)
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
Using current version of the server - you can see that there is no OAuth managed or published API endpoint for canvas delete (screenshot 1). However this API does CLEARLY exist as you can see if you inspect what happens when you hit the delete button (screenshot 2 clearly shows the API being called - but it requires user login security token)
Please can you enable this API for OAuth - the API already exists, it just needs to be exposed with the others.
I have three team members all in the same private studio. We can see each others' workflows. However, when looking at a workflow that another team member has published to the gallery, it looks like:
This is a massive impediment to collaboration because my team handles ETL for most of the company. If a user complains that their data isn't up to date, whoever receives that support ticket needs to be able to see if the workflow is actually running and whether it was successful or had an error during the last run.
Preventing a team from seeing this for each others' workflow schedules and results means that the only person who can deal with an issue is the person who originally made the workflow. Which makes the idea of a shared private studio wholly pointless as we may as well be operating in different universes.
Please create a studio-level setting where all members of a studio can see all schedules and results of all workflows in that studio.
We use the Server API to manage our server environment - and we recently noticed that the Workflows API (/admin/v1/workflows) ignores any canvasses after the 10 000'th submission.
By querying Mongo directly (appinfos collection) we know that we have 18 800 or so unique applications in our environment.
Please can you remove this cap from the API so that it can be used to query any number of canvasses on a larger environment?
Could the community receive a comprehensive data dictionary of all the collections in Mongo with:
- Description of each collection
- Description of each attribute (or field) within each collection
- Documentation of joins between the collections
A great example can be seen in how Tableau documents their postgresSQL tables: https://help.tableau.com/current/server/en-us/data_dictionary.htm
This would be extremely helpful as we are determining which collections we need to store, how to construct queries and how to build analytics on our assets.
Now, gallery does not support AD group , need to setup user one by one.
If gallery support AD group synchronization, it is more convenient for gallery admin to manage large number of users.
By assigning AD users to AD group, it will reduce the maintenance task of gallery admin, since gallery admin don't need to grant rights in the gallery directly.
It would be nice to be able to change the Gallery URL from:
The reason being to make it easier for end users to find the server/content.
Original forum post here: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Changing-the-Gallery-URL-on-Alteryx-S...
Currently on Alteryx it is possible to add visibility of a subscriptions scheduled workflows to all members of that subscription.
What we would quite like is for the ability to turn on or off the ability to edit workflows within that subscription for all members.
As in if a member goes on leave, or leaves the company, or is ill, other members can edit, update and cancel the scheduled workflow as needed without needing to go through an admin for it.
Please support GZIP files in input tool in Server. This is related to https://community.alteryx.com/t5/Alteryx-Product-Ideas/Support-for-GZIP-gz-compressed-files-in-input..., but logged in a separate Idea because the staff indicated in the thread that they are planning support for GZIP in Designer only in 2018.2. We need it in Server as well.
When posting an app to the Gallery, if the app has, say, one PCXML output for the user to see, and one Excel file for the user to download, it would be helpful for to be able to specify which shows first to the user. For example, I have a PCXML that gives the user summary tables, and instructions on how to go to the drop down above and select the second report, click on the Excel icon, and download it. But if the Excel report shows up first, then there is no ability to give them instructions and many simply won't be savy enough to go find the PCXML in the drop down.
When opening a canvas - it is possible to open from the gallery, which is important in a team environment.
However - as you work on this canvas - if you hit save, it does not save a new version to the server and increment the original (as would happen on sharepoint) - instead it asks you to create a new file.
Please can you change this behaviour as follows:
- If I open from the gallery then when I save I'm updating the same Gallery asset and incrementing the version ID by 1.
- The only time I would save in a new file is if I use Save As; and explicitly pick a new file.
Currently, this is completely manual with whoever is assuming the schedule creating it under their profile and then the old schedule being deleted.
This can happen often in organization where a user leaves the company or assumes a new role requiring some else to maintain those schedules. It would be convenient if there was an option to reassign the owner of a schedule to simply this process.
I'm really enjoying the new Save As functionality to push to the gallery, but had a request that would make it even more useful for me.
I saw that you can open workflows directly from the Gallery and edit them with version control, but it would be nice if it was possible to do a Save As on a local workflow and point it at an existing copy on the server. I need to maintain a local copy of my workflow for dev/prod separation, but currently my way to push to prod is to do a Save As to my Private Gallery, remove the existing copy from the company gallery, and then share my newly created workflow into the company gallery. This causes some headaches like no version control, switching out icons everytime, and overall just a messy way to push to prod.
It would be helpful if there was a way to overwrite an existing workflow in the gallery rather than editing it directly.
Currently the Gallery does not support Chained Apps or workflows triggered by events or Run Command Tool.
Please enable Chained Apps and flow triggering from Events and Command Tools.
I started building Apps a lot this last year and I have been using events and Run Command Tool for 3 or 4 years regularly. In both cases I can't migrate most of them to the Gallery because the Apps chain and many flows trigger other flows in before and after events or Run Command Tool.
This should also enable the CReW macros that trigger flows.
Hi all, Per this thread, it would be helpful if we could have finer control of scheduled jobs in Alteryx Server: https://community.alteryx.com/t5/Publishing-Gallery/Resource-control-on-scheduled-jobs/m-p/61016/hig...
- Dependancies (one job should run after another in a chain)
- lower priority (some jobs should go down the priority queue to allow for others so that high priority jobs are not blocked by other less important ones)
Thank you Sean
In the Alteryx Gallery UI, it's possible to set up workflow credentials so that a workflow published to the gallery runs as a specific user.
Unfortunately when that workflow is run from the Alteryx Gallery API, it appears to only ever run as the Alteryx Server Run-As account.
Our developers in working with this figured out that if they called the (undocumented) API that runs the actual Alteryx Gallery directly, they can achieve what they want, but it seems a risky strategy.
The idea would be:
-Either unify the APIs so that the Gallery itself uses the same API to run workflows as what you present as the "Gallery API" (the eat your own dogfood way)
-Alter the Gallery API to enable us to run as a different workflow credential
Without this, we're forced to permission the run-as account to access anything that uses this method, which in turn then becomes a bit of a security hole (any workflow run will have access to everything that the run-as account uses)
Suggested information to be included in audit logs.
A secure audit record of all activities on the system:
At minimum the logs should include the following:
I believe many customers could benefit from this type of audit logging, especially those who are required to obtain specific security certifications for their alteryx deployments. From what I can see online there does not seem to be out of the box functionality for this. If anyone has implemented any type of audit logging like this please feel free to comment.
We have more clients that would like to prioritize their scheduled jobs based on run time and importance.
It could be a simple priority number, that decides which job that need to run next. Further it could be nice to be able to allocate certain workers to certain jobs.
I am looking forward to your feedback.
Organizations using Alteryx Server with an embedded MongoDB can benefit from an option to change the MongoDB User and Admin User passwords.
Current deployments of Alteryx Server allow regeneration of the Controller Token, and for many of the same reasons, the ability to change the MongoDB passwords would be beneficial to customers.
Many organizations rely on a centralized team for daily administration of the Alteryx Server and MongoDB. With the current functionality, when members of this team change positions, they continue to know the MongoDB authentication information indefinitely. Providing organizations with this capability allows them to make the determination of how/when a change is required to mitigate any risk of misuse.