This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesI'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.
CC: @BlytheE
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!
We have the Local License Server installed. Right now, if a Designer user changes roles, or leaves the company, they have to release their license from their client-side machine. If they don't release it properly, and IT can't get us into their machines, then we have to wait 7 days for that license to roll off the server. There should be a way for a system admin to forcefully revoke someone's license.
Password is required to execute any command on LLS. Last time we forgot the password, only way to retrieve it was to reinstall the LLS !
A command to reset password in LLS should do.
@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone
Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted.
Product should be capable of using the newly installed configuration and not require manual Config change and service restart.
so every time there is a java version upgrade, users have to be notified of the downtime (even though they could move into 7 day grace period) and then the flexnetls.settings file should be updated with Java home path.
Password entered during installation is changed to LLS default password after the following sequence of events.
LLS Service start -> Settings update -> Service restart (to let the settings change take effect).
Avoiding this behavior will save server admin's time in changing password every time setting is changed.
@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone
Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted.
so every time there is a java version upgrade, users have to be notified of the downtime (even though they could move into 7 day grace period) and then the flexnetls.settings file has to be updated with Java home path.
Local License Server settings has to pick up the latest Java installation and not require manual Config change and service restart.
Installation/upgrade of java in all servers are usually firmwide Tech team activity - which are outside of Server admins control.
Java support by Alteryx - is version 8.0.212 - while the latest version available in our premise is 8.0.241. support for latest version of java - which is required for functioning of Local License Server should be prioritized.
@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone
Right now, with LSS, the only thing you can query who has taken seats on licenses (you get user's email and host name). This is OK, but it would be great if we could get more information than that. Primarily
As you know, there is no way to forcefully remove a license from the LLS (you either have to have user deactivate from Designer, or wait 7 days). Knowing this information would help admin's know who is actually using the licenses and if someone leaves the company, you can get a countdown until that license is released.
For historical tracking and auditing, I would also like to setup an Alteryx Workflow that puts licensed user information into a table or DB so we have a log of who is using the licenses.
I know the Alteryx server supports auto-scaling up and out as of now. Alteryx Servers should also support auto-scaling down and in.
User | Likes Count |
---|---|
19 | |
17 | |
5 | |
4 | |
2 |