The Workflow configuration window currently has "Canvas" as the default tab when clicking on whitespace in a workflow.
Since workflow orientation, annotation settings, and progress settings tend to be consistent for a user, I think it makes more sense to have the default tab on something that might be more relevant to the user.
Workflow provides information that is useful...location of the workflow and constants related to the workflow.
Runtime has settings that can change often as the user is developing out the workflow.
So either of these would provide better access to more important info that that found on the Canvas tab.
I love the gallery data connection feature - we're going through some big systems architecture changes, resulting in new locations for many datasets. Having a single place in the Gallery Admin area to update connection information works beautifully.
We're running into issues with the gallery-hosted data connections when trying to run some apps on our private gallery though. The trouble comes up when the gallery-hosted data connection appears inside a macro that's part of an app. We get an "Unable to translate alias" error when trying to run these types of apps.
If we have an app using gallery-hosted data connections that are outside of a macro, the gallery is able to resolve the connection alias fine and work properly. The issue only appears when the gallery data connection is part of a macro used inside an app.
We use macros a lot in our app development because it allows us to use standard methods for accomplishing common tasks. Using macros also enables us to set up automated testing workflows to make sure our processes produce expected results. As it is, we're unable to take full advantage of the gallery-hosted data connections because they don't work within macros, and instead have to continue using hardcoded connection strings. These are a bigger maintenance burden as our underlying systems evolve and are updated.
Currently, if you want to change from Built-in to Windows Authentication, you have to:
To switch authentication types, you'll need to start from scratch.
1. Stop the AlteryxService 2. Open a Windows Folder Explorer and go to the directory you have MongoDB loaded (System Settings->Controller->Persistence->Data Folder 3. Rename or delete that folder (a simple backup would be to rename the folder, you can move it to another directory as well) 4. Open the Alteryx Server System Settings and click next to Gallery->General. 5. Select the new Authentication process you would like to use. 6. Finish the System Settings and the new database will be created.
The Gallery and Scheduler databases are closely tied. Workflows that are uploaded, results created, and schedules created from the Gallery are stored in the Scheduler database. So you will need to start from scratch on both the Gallery and in the Scheduler.
This is a non-starter for any company that has any amount of time invested in establishing the use of the Gallery. Starting over is not an option, but improving security, streamlining access protocols as a part of overall data governance is a must. Please consider fixing the authentication protocol to make it so we don't have to start over.
When I first started using Alteryx I did not use macros or the Runtime Tab much at all and now I use both a lot but...I can't use them together.
When working in a macro there is no Runtime Tab. While working on a macro and testing it you can't take advantage of any of the handy features in the Runtime Tab. I am assuming a macro will inherit any settings from the Flow that calls it, can't find anything in the community or "help" to confirm that though, but this is not helpful while developing and testing.
Currently the Gallery's Admin API is a bit light on functionality. It only works with data connections & workflows and not regular server admin functions. Endpoints I'd love to see, but not limited to, are:
Create/modify/delete subscriptions (including assigning users to subscriptions)
When using the Alteryx email tool to send a text to a mobile device via carrier URL (i.e. firstname.lastname@example.org) bad characters appear. This is due to the fact that the Alteryx email tool is sending in XML format and the carriers only accept HTML.
This was determined after working with the Alteryx support team to determine the root cause of that bad characters appearing on the mobile phone.
We are using an Alteryx workflow as an early warning system for technical issues to upper management. These advisories or alerts are being sent to mobile devices via email tool.
@PaulT put this list of keyboard shortcuts for the Alteryx Designer together in 2013, and it seems to not have been updated since then, and I cannot find a well-structured version of this elsewhere in Alteryx documentation.
As each version of Alteryx is rolled out, it would be much easier for our users and admin team to validate the new version, if Alteryx allowed parallel installs of many different versions of the software.
So - our team is currently on 11.3 - if we could roll out 11.5 in parallel then we could very easily allow users to revert to 11.3 if there are issues, or else remove 11.3 after 2-3 weeks if no issues.
When saving a workflow to the gallery, the manage assets box is a fixed size. Due to the length of our file paths, the full path name is cut off. This makes it difficult when trying to package macros to select the correct box. I understand you can group assets by tool, however with the more complicated workflows this can still present it's challenges. I'd like to see this box to be re-sizeable.
This idea arose recently when working specifically with the Association Analysis tool, but I have a feeling that other predictive tools could benefit as well. I was trying to run an association analysis for a large number of variables, but when I was investigating the output using the new interactive tools, I was presented with something similar to this:
While the correlation plot draws your high to high associations, the user is unable to read the field names, and the tooltip only provides the correlation value rather than the fields with the value. As such, I shifted my attention to the report output, which looked like this:
While I could now read everything, it made pulling out the insights much more difficult. Wanting the best of both worlds, I decided to extract the correlation table from the R output and drop it into Tableau for a filterable, interactive version of the correlation matrix. This turned out to be much easier said than done. Because the R output comes in report form, I tried to use the report extract macros mentioned in this thread to pull out the actual values. This was an issue due to the report formatting, so instead I cracked open the macro to extract the data directly from the R output. To make a long story shorter, this ended up being problematic due to report formats, batch macro pathing, and an unidentifiable bug.
In the end, it would be great if there was a “Data” output for reports from certain predictive tools that would benefit from further analysis. While the reports and interactive outputs are great for ingesting small model outputs, at times there is a need to extract the data itself for further analysis/visualization. This is one example, as is the model coefficients from regression analyses that I have used in the past. I know Dr. Dan created a model coefficients macro for the case of regression, but I have to imagine that there are other cases where the data is desired along with the report/interactive output.
When looking at the Results window, I often find it a headache to read the numeric results because of the lack of commas. I understand that incorporating commas into the data itself could make for some weird errors; however, would it be possible to toggle an option that displays all numeric fields with proper commas and right-aligned in the Results window? I am referring to using a display mask to make numeric fields look like they have the thousands separator while retaining numeric functionality (as opposed to converting the fields to strings).
Currently if one wants to compare different alteryx files or different versions of the same file - one needs to compare the XML files. If you are not very familiar with navigating XML, this poses a risk as one may not be able to identify all changes.
It would be a great addition to Alteryx to integrate Alteryx with Git, Subversion, CVS, Mercurial, and GitHub as this tool is becoming the go-to tool for data processing for data analysts and even programmers.
This additional functionality to compare previous versions (diff) and also to merge alteryx workflows if two people are working on the same workflow, and also to easily see what changes have been committed/ made by other developers and when would make Alteryx a much more powerful tool and would open doors to other types of users, as essentially you can run anything through Alteryx.
I think Alteryx uses the Tableau SDK to create tableau data extracts, TDE's. Since Tableau 10.3, there is functionality to connect to spatial files in Tableau (.shp). These shapefiles can be converted to an tableau data extract within Tableau. The tableau SDK has this functionality as well, but Alteryx does not support it yet. The suggestion is to add this functionality. See https://onlinehelp.tableau.com/current/api/sdk/en-us/SDK/tableau_sdk_samples.htm for the SDK link.
Spatial TDE's are way smaller (3gb .shp went to 140mb TDE) and way faster.
Although the connectivity to the eMail infrastructure is set up on the controller and worker nodes - there is no ability to set up automated alerting for errors on workflows from the server.
We would like to be able to set up the gallery as follows:
- Every job is owned by a user or a distribution list
- If that workflow throws an error or warning (this should be configurable on the server, whether warnings are included), then the author should be e-mailed with a link to the specific workflow and the error log.
This can be done in a round-about way, by running an error-reporting alteryx job after the fact - but this kind of alert needs to go out almost immediately given our dependance on Alteryx for specific SLAs.