Many people maintain valuable information in Excel files, and many organizations, like ours, also use SharePoint to store and share structured and unstructured information. We see most user-generated and maintained data in Excel files in SharePoint document libraries, and one of the great benefits of Alteryx is the ability to join that Excel data with other data sources. Unfortunately, the v11.0 Scheduler cannot resolve the UNC-style ( \\server@SSL\DavWWWRoot\site-name\document-library\filename ) addresses, so workflows that access this valuable SharePoint Excel data must be run manually. The SharePoint List Input tool can read the list-style metadata for Document Library files, but does not access the file content.
The Scheduler should be enhanced so that scheduled workflows can read Excel data stored in SharePoint Document Libraries.
On the workflow results window, I'd like to see a column for "Start Time". If I have a workflow that is running, I'd like to know what time it started running so I have an idea on when it might finish.
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.
Along with setting a schedule for an app in the gallery, the user should also be able to set the different interface values for each schedule he/she makes.
My main use case is regarding having generic templates for ETL processes, that have multiple different types of runs based on configuration values, but I'm sure there are plenty others.
The admin (aka curator) needs to be given more control. The admin should have greater control than the users of the system.
My organization is in the Healthcare industry and we have HIPAA laws to abide by when it comes to data. Not all users should be able to see all data. Developers should not have complete control over the data they publish.
Get tips from Tableau as they have admin controls down with their permissions process.
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!
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
The Alteryx Server Usage Monitoring & Reporting reports are very useful. In order to automate the distribution and leverage our Tableau Server we have modified one of the macros within to publish the TDE to the Server and reworked the workbook to point to it. This is a fairly time consuming process to do, so the idea is to introduce a version of the workflow which pushes the datasource, producing a version of the workbook pointing to it.
In the interest of information and system security, would it be possible to provide a means to remove social media and email sharing options (Facebook, Twitter, etc.) from the SHARING drop down menus, such as through a configurable setting in the RuntimeSettings.xml file?
Currently there is no means (confirmed by Alteryx tech support) to remove these options from the sharing menu. Sharing within the system can be controlled somewhat by controlling access to the system or specific output locations.Once the info leaves the system, there is no longer any means of control.
Providing a configurable option will allow locations to tailor to their specific needs.
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.
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.
24/7 access to the server is desirable, but not always feasible. If scheduled downtime is needed, it would be nice to have the ability to have scheduled blocks of time where jobs are prevented from being executed or scheduled. If we are planning a downtime, these windows would cease accepting new workflows and would possibly even kill jobs if they moved from a grey block of time to a black block of time.
Just a thought,
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)
I have described my issue in the Community post here:
Is there a way to retrieve an exact date when new version of a workflow was uploaded to Gallery? I know it works when it is today, yesterday or couple days ago but after that you can only see "2 months ago" etc. in Creation Date, which is not sufficient for any version management.
Alteryx Server does a pretty good job of tracking all the information you need in order to find out who ran a workflow at a given time, even if that workflow has been deleted from the Gallery.
However, if I need to identify what that workflow actually did on a specific date, and that version is no longer available on the Gallery, it gets really hard to track down.
There are some posts throughout the community on leveraging the MongoDB to try and reconstruct this, but in some cases the workflow is "Chunked" and becomes impossible for an end user to reconstruct.
I spoke to support about this recently and they suggested that by using the Scheduler, I could schedule the historical instance of the workflow and then "Really quickly" grab it when it was reconstructed from the temporary staging folder used by our Alteryx Server. This has a few concerns, among them, finding a way to run this workflow so that the files can be created but it has no impact on tables, for instance if the given workflow drops a table as part of its execution. Additionally, the only way to schedule with a different set of permissions in a 1-Worker environment is to change the default "Run Workflows As" to a different user, who also needs permission to access all files on the Alteryx Server. This can also impact any other Scheduled or Gallery job that is executed while this recovery is underway, effectively causing downtime to do file recovery.
These restrictions are specific enough as to be impractical for most organizations using Alteryx Gallery/Server.
I think this could be solved by adding to the Scheduler an option along the lines of "Download a copy of the workflow", available to administrators. Ideally this copy could include some important metadata, like when that version of the workflow was uploaded, who uploaded it, and its ID/Version Number from the Gallery.
This would go a long way towards making it easier to Audit and respond to requests for historical information about Alteryx Workflows on the Server, and since the Alteryx Engine can already recreate these workflows, I think that a basic version of this feature could simply save out that temporary file, rather than executing it.
For a given DB connection - there's a need to be able to specify the owner for this specific connection.
Reason for this is that the credentials for a given DB are not all managed by the central admin team - so we'd want to say that a given DB connection is owned by a particular person so that this can be updated frequently as passwords change.
For resilience - our particular policy would be to have 2 owners so that if one person resigns or changes roles, it invalidates the primary and reverts to the secondary - and then asks the new Primary to create a backup owner.
We spent almost a full day on Friday internally, and also about 3 or 4 hours of time for 3 Alteryx Server engineers (thank you all - MattH; ZachH; WayeW) and Ben Burkholder trying to get our gallery server to start.
Error message was "
Failed to construct Gallery daemon process, process exited code <9002>
This was all that was provided in the server log files; the gallery log files; and the Windows Event Viewer.
In the end, it turned out that the issue was very simple - the MongoDB had open locks in place that needed to be deleted; and then the service came up immediately.
Several man-days of our effort; as well as the precious time of the Alteryx Engineers who gave up their Friday afternoon to help could have all been avoided if the error-message on the server failure said "Login failure on server due to open locks - please clean out locks on db.locks collection" with a link to the solution or a lookup code that be researched on the Alteryx support site.
Please could we go through the server service and eliminate all the exit codes and replace with human-friendly error messages - that way we could allow this kind of issue to be self-diagnosed, and allow the Alteryx Engineers to spend their time building the next generation of Alteryx Server rather than diagnosing a table lock.
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.
We are hoping to move to Mongo Enterprise as the backend for our Alteryx server, however we may not be able to given that Alteryx does not currently support Kerberos & Keytab authentication.
Please could you add this to the server so that larger clients with Enterprise Mongo can scale upwards?