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.
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.
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.
In Gallery, I'd like to see the execution log in the workflow results, i.e. what you get if you run the workflow from Designer. I'd like to see this whatever the status of the workflow completion. Would be useful to assess warnings and the performance of components within the workflow. Also would give me useful stats about records loaded etc.
I wish Alteryx would allow more control over user access to scheduling workflows. Currently there is only a radio button that globally allows users to access the scheduler. I wish we had another layer where we could limit access by Permissions. For example, we would like all Artisans and Curators to have access to the scheduler, but not viewers.
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.
It would be great if i as a developer could create a DB alias connection and for it then to be available to other developers and distributed via the server.
Collaborative working like the above does seem rather limited at the moment.
In larger organizations or organizations with global coverage, it is possible for users to be in different time zones from each other and the Alteryx server.
WIth our implementation of Alteryx server, we have the server time zone set to that of our data warehouse, but this time zone is different than my own by -2 hours. In the case of scheduling a workflow in the future, I normally correct for this by setting the scheule in the time zone of the server and things work alright.
It falls apart is when I want to schedule something in the future, but it is within the timespan between my time zone and the server time zone. For example: It is 6PM my time, and 4PM server time. I want to schedule a workflow to run at 5PM server time (7PM my time). When I try to set this up with the Version 10 scheduler built into Alteryx desktop, it overides the date field upon saving to run the following day instead of today as it thinks im trying to schedule the run at a time that has already passed (which it has in my timezone, but not in the server time zone). Upon trying to edit this schedule to reset the date to today, it again reverts upon saving.
The only way I have found to get around this is to reset the time zone of my computer to match the server time zone, then set the schedule, then reset the time zone of my machine back to local time again. This is not the best experience, and will likely be required more frequently for users as their time zone difference increases.
When wanting to run something server side immediately (I do this in cases where the runtime will be long, or im mobile and on a machine with a lower amount of processing resources) the "Once" option can be used in scheduler to push something to server and run it. In my case, due to the timezone difference, the default time set when trying to do this is the current time in my time zone, but 2 hours ahead of the current server time.
I have two proposed resolutions:
1) Transmit Server time zone information to the local scheduler to have everything involving scheduling in Server time. Also for any timestamp fields, include the time zone designation so its clear to the user.
2) Use information from the user's machine and information from the server to do timezone conversions behind the scenes so whenever scheduling or viewing schedules, all timestamps are in local time to the user. I feel this is the prefered solution for the best user experience, but would also be the more complex to implement.
Please can we extend the support for MongoDB to include MongoDB Enterprise latest versions, and certify at latest version within 3 months of release (both with the connector components, and the server infra)?
Given the deep dependence that Alteryx server has on MongoDB, being current with the latest version is critical (since many enterprises have a policy of moving to the latest version within 6 months, and shutting off old after 12.
Mongo 3.2 has been out since Sept 2015, and my understanding is that Alteryx Server is not yet certified for 3.2 - so it may be worth skipping to 3.4 (released 11 Sept 2017).
It might be helpful to be able to use an API to call and pass parameters to/from an Alteryx App or Workflow on an Alteryx Server. Then a user could use a browser or another application to call an Alteryx app/workflow.
It would be GREAT if we could have an optional notes field in the gallery. When many tools are uploaded to a collection, the titles alone are not descriptive enough for end users. I have to publish a separate "menu" for reports that are available in the gallery. In some cases I have to number them. I wish users could just browse for themselves to find the application that is suitable for their use case.
My idea is to facilitate scheduling through Gallery vs the separate scheduler built into Designer. The reasons for this:
Currently any workflows/apps published to the gallery can be found via the search function - even when the particular user has no permission to this workflow/app. While this only allows for the non-permisssioned user to see the title, this could still leak information as it allows anyone to find apps published in someone's private gallery.
Both the Alteryx Public Gallery and the Private Gallery product are impacted by this. Additionally this is not just limited to logged in users, but also public viewers of the gallery.
My proposed idea:
The SDKs are great and allow the community to expand Alteryx in many ways. I think it would be great to have some way to package these so we could easily share them and provide updates and fixes.
Not sure how many people use the SDKs but being able to easily share and install the output would help up take I think.
It is more convenience that allowing gallery admin to download any workflow from the gallery for trobleshooting.
For example, if the workflow is long running , the gallery admin can download the workflow and then drill down to it to find out the root cause. Sometimes, it maybe workflow design related issue.
I'm really loving the new data connections for 11.0. We have deployed them in a private gallery for our users and it's great. The only drawback is that the server itself cannot easily be configured to use these same credentials. I would like some way for the service account running our jobs on our server to use the data connections from the gallery. I can assign the credentials to that service account just fine, but it never picks them up since it never open up the Alteryx GUI when it's running jobs. This would allow us to have one spot with all of the credentials. Currently, we're going to have 2 locations with all of our credentials that we'll have to make sure stays in sync: 1 in the gallery for the users, and 1 on the sever box for the server.