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 would like to set a retry count when scheduling a job, and also to specify to duration in between retries, e.g. job fails, but then will retry to run 3 times with a 5 minute wait in between each retry.
Also would like a radio button next to all workflow results, so when you get a list of failed jobs you can click all the jobs and then hit rerun. This should be complimented with select all functionality. This will prevent me from having to go into each job and rerunning, i.e. save me loadsa clicks!
Currently, to allow a user to schedule jobs, prioritize jobs, assign jobs, create collections, or have API access, toggles must be set at the user level.
As a server administrator, I want to configure these toggles at the group level, so that a) I don't have to modify a large number of users individually to grant them such permissions, b) I ensure consistency across groups of users that doesn't rely on humans clicking all the right things for each of the relevant people, and c) I can easily change these settings for multiple people, if needed.
Hello, I would like improved user management features and/or training
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.
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.
Allow admins to configure an outage window(s) of a specified amount of time (say 5-6pm every sunday) for conducting admin activities. Specifically this outage window would block any scheduled jobs, drive any manual started jobs to queue, and also issue a popup on the gallery to notify users that it's during an outage window.
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.
*This is an idea from @cneivam from the Portuguese Community*
Currently the server diagnostics (http://localhost/gallery/admin/#!diagnostics) covers a narrow time window (from what I can see - only the last few hours)
.... and if you attempt to zoom out or pan to see a broader time window - the graph gets smaller, but the data does not grow to fill the remaining space
Please could we request 2 changes:
a) add a time axis on the bottom of this chart so that the user can understand the time dimension
b) Increase the time available for analytics to an arbitrarily broad set of data (which the admin can configure as a server setup parameter - retention period). For us - we'd want to keep at least 3 months of data, and be able to view this analytically.
Our Organization uses a Password Manager to automate the update of service account credentials used in Windows Services.
Would like to request the ability to leverage that functionality with the Run As user inside of Alteryx Server Settings used with Workflows.
This would increase application security, while ensuring the process is automated, thereby limiting issues from human interaction.
Examples of these types of application are ERPM(Enterprise Random Password Manager), Thycotic Secret Server, and I am sure there are others.
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.
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.
I work at a large organization where Security and Privacy are of utmost importance. The ideology that we need to follow is Least Privilege and Need to Know.
We (Curators) do not want all the Artisans to publish workflows to Home Page, either knowingly or unknowingly. We however do want to allow a few power users to publish their work in Home Page, but currently the Gallery does not provide the ability to pick and choose who can share workflows publicly. We are educating users to not share any contents publicly, but as we scale up, it will be difficult to manage and govern this.
I'm suggesting to implement a global Yes/No feature that will Enable/Disable Artisans to publish contents in Home Page (just like the way we have for Jobs/Scheduling feature). Further, in Users section, Edit User setting needs to have a Yes/No button that will allow Curators to let certain Artisans place workflows in My Company's Gallery.
Organizations that never want any workflow to be shared publicly can disable this feature using global Yes/No button. Organizations (like the one I work at) that want to enable this only for certain Artisans, can set the Global Yes/No to No, and then in Users tab, they can pick and choose the Users that need this functionality (which will override the global default). Finally Organizations that do not really care about this functionality can just set the global setting to Yes.
Hoping other organizations find value in this functionality as well. Thanks.
Would like to see a Notification hierarchy implemented to Gallery. Currently, the settings that control notifications are at the Gallery-level....where only the admin can control, for example, notifying users if a new workflow was added to a collection they belong too. Could this setting be inherited, but then, for example, a Collection owner can implement their own notification settings that overrides the Gallery default? Using the same example as before, perhaps the Collection owner could disable notifying their Users if a new workflow is loaded to the collection.
If a job fails it would be perfect if we could set something in the workflow settings so that the job would retry again in X number of minutes for the next Y number of times. We have jobs that connect to external resources and sometimes the network will reset and will cause the connections to all drop. An example would be I want a workflow to try again in 10 minutes for a maximum of 5 times so over the next 50 mins it will retry every 10 mins if it fails
With 2020.3, the new Groups feature came into light, which is great, but seems like it was only half-thought.
It would have been nicely complemented with some API endpoints that would allow managing the groups' members - add, remove, list members, etc.
Seems like the API on Alteryx is like 100 steps behind and seems like the new developments are not considering adding APIs for the new released features. I feel this is a product roadmap issue.
As an admin, I would like far more ways to automate managing the Server/Gallery than the ones currently provided by Alteryx.
Integration with AD would be nice as well, we use SAML, and would like to have the option to import AD groups that would sync automatically in Alteryx - same way Tableau has those groups that are imported directly from AD.
Below you can see few of my suggestion to improve Alteryx Server.
Idea for Alteryx Server monitoring:
Give server more functionality with:
Hopefully you will find these suggestions interesting and useful.
When saving a workflow to the gallery, none of the options I could choose from Set workflow credentials validates a workflow successfully when using database connections due to missing permission on the server (No specific Run As is configured on the Server). Apparently the server validates the workflow as following:
User is not required to specify credentials:No possibility to add credentials when running the workflow on the server. In that case, the workflow validates database connections with errors due to missing permission on the server. This error was expected.
User must specify their own credentials: This option is the most appropriate in case of working with database connections with regard to our use cases and security policies. Unfortunately this option is only enabled when the workflow is saved on the server already and run from the gallery. In case of the validation step when saving the workflow to the gallery, the server evaluates with the system user of the server. As a result, the validation fails. In that case, I expected the server to run the validation with the user from the Alteryx Designer.
Always run this workflow with these credentials: This option is not appropriate in terms of our security policy, since the workflow is permanently set with the users credentials.
So my suggestion would be to:
Otherwise is see no benefit of the validation feature (with respect to our use cases and security policies)
I'm not sure if this is too similar to this server idea
but I'd love to see the ability to add webhooks to Alteryx Server to launch a workflow. I believe that is how Flow (now PowerAutomate) can run an event. I had to spend hours figuring out how to build a "Flow" workflow which would have taken me minutes in Designer. For example, when I receive a new MS Forms Survey submission, I can shape the data and build a sharepoint list, rather than waiting for whatever interval I set in the scheduler.
Please keep in mind that this is a suggestion from a container novice! 🙂
However, our situation is such that our release upgrade deployments are taking significant time to install, test and sign-off from DEV through PROD for the four main life-cycles involved in our server environment. Even if we script the deployment to save time, there's still manual configuration needed to confirm the new version works in the next server environment.
Similar to how Promote can deploy from DEV through PROD using images/containers, my suggestion is to package the Server components into images/containers that can be similarly deployed through the life-cycles. While the container with mongoDB doesn't need to move to the next life-cycle, the containers with the web server, load balancer, and engine nodes could move with the click of a button. And if needed, reverted to prior version with similar ease.
I forgot to ask about this idea at the UX lab during Inspire, but would be very happy to hear if it's already in the pipeline!
Thank you for your consideration!