Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello all,
This may be a little controversial. As of today, when you buy an Alteryx Server, the basic package covers up to 4 cores :
https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/How-Alteryx-defines-cores-for-licensing-our-products/ta-p/158030
I have always known that. But these last years, the technology, the world has evolved. Especially the number of cores in a server. As an example, AMD Epyc CPU for server begin at 8 cores :
https://www.amd.com/en/processors/epyc-7002-series
So the idea is to update the number of cores in initial package for 8 or even 16 cores. It would :
-make Alteryx more competitive
-cost only very few money
-end some user frustration
Moreover, Alteryx Server Additional Capacity license should be 4 cores.
Best regards,
Simon
In Alteryx Gallery admin, please add a confirmation before applying a change to the default user roles. Since it can be changed so easily and isn't very clear to what happens when new admins make a change to that drop down. For example: They do not realize they changed all the default users to curators! But they do learn quickly.
Regards,
John Colgan
Please add a TAGS filter for workflows filter
Hello,
We have been building a solution for a client that involved chaining apps. When we uploaded the workflow to the server, we got the below error: Workflow exceeded maximum runtime of 30 seconds and was cancelled. We were able to rectify this by having the client implement the change here. While I understand the need for the limit, is there any plan to have this fix be more obvious to the average user to implement or avoid needing to reimplement following a server upgrade?
Thanks,
Data Connections and Workflow Credentials are key part of migration process for workflows to Gallery.
They are provisioned for each user upon request.
When a developer leaves the organization, there is no easy way to identify all the Data Connections and Workflow Credentials assigned to that user.
Current options in the Gallery is for the Admin to browse through each Data Connection and Workflow Credential, navigate the Users tab and identify the list users.
For a large organization with many Data Connections and Workflow Credentials it will hard to manage this since.
1. If the workflows change ownership, the new owner has to be given access to the Data Connections and Workflow Credentials.
2. Remove user access to the Data Connections and Workflow Credentials.
A Gallery page in Admin should include all Assets a user owns/has access to which includes the following. By selecting a user, the list should populate.
We have implemented a solution to capture this information by getting the details from MongoDB. Also an automated process where the list goes to the manager when a developer leaves the organization so that he can manage the assets by identifying a new owner for the assets.
In the new version, we have an easy way to change ownership of a workflow in Gallery. In the same manner other Assets also should be taken care.
Special characters cannot be accommodated when searching usernames or workflows in the Gallery and Admin UI pages.
When it comes to cancelling a running/queued job though the Gallery admin portal it never fails to add some new jobs to the list right as I am about to click to cancel a job,
thus instead of removing the unnecessary queued job I actually cancel the job that has been running for the past hour creating the report I need for the meeting in 30 minutes
I think that adding check boxes (similar to the "Users" page) would be a nice UI enhancement to this page
There is a typo under the Help area for the Default Gallery Administrator (System Settings). It should be a backslash, not forward slash there. Correct is: domain\username
I thought that in our previous version of Gallery (2018.3) the list of available data connections in the Admin page of the same name used to fill the entire depth of my browser window?
In 2020.4 in uses only about half the depth and presents a scroll bar to view the additional records whilst there is additional white space unused at the bottom of the window.
I suggest that this changed to make full use of the available browser window space.
I note that the data connections page uses a scrolling list as opposed to the paged list which is used in most other pages in the UI. However I would be resistant to changing this as a solution since with the scroll bar view any sorting applies to the entire list as opposed to the current displayed page (c.f. Users)
Currently, only Gallery administrators can create credentials on the Gallery. But this doesn't seem to make sense because publishing users may need to embed their credentials in workflows. And they would benefit from managing these on server so that password changes don't require re-publishing large numbers of workflows. Please allow any user to create and manage credentials on the Gallery.
It used to be possible to create a robust user profile within the gallery, with many additional user details fields available. However all have been taken away leaving only a name and email address as a user profile.
Please bring back those user details as having additional information about the user always beneficial. If internal to the company, sometimes I need to know what department they are from or what office. And if external to the company, I need to know what organization they are from.
Having no additional user information can cause a lot of confusion, especially if any two users share a name since I don't know if it's the same user with a new email, or a different user completely.
Thanks.
The gallery needs to implement basic auditing in the data connections.Currently, there is no way to determine who or when a data connection was created or updated.
The dataConnections Collection contains data connections with these keys
_id: (ObjectId) Document primary key.
ConectionString: (String) Hashed database connection string.
PasswordSecured: (String) Encrypted password for the database connection.
ConnectionName: (String) Data connection display name.
Subscriptions: (Array) Array of subscription IDs the data connection has been shared with.
Users: (Array) Array of user IDs the data connection has been shared with.
UserGroups: (Array) Array of group IDs the data connection has been shared with.
Add these keys to provide a basic audit trail
Modify the gallery to allow the values of the new keys to be displayed. Modify the API endpoint to retrieve this information.
Log changes to Gallery settings made by Admins in the UI
We would like the ability to configure SMTP settings in the Gallery for the Email Tool separate from the SMTP settings for Gallery notifications. We do not currently support the Email Tool being used on our Gallery, and the only way for us to prevent this is to not allow any email out from our Gallery server. This also prevents us from utilizing any Gallery notification functionality
Enhancement request for the ability to search within workflow files for tools, data connections, key words.
Hi Alteryx Team,
in one of my current projects we would like to set up a Alteryx Gallery Collection using the API, which already works fine using the current API implementation.
In addition we want users of this collection enable to use DataConnection to DBs they are allowed to access. This can already be done manually. I can create a Data Connection manually and then I assign the same users I already assigned to the Collection also to the Data Connection. Adding these users to the Data Connection can also be done using API. The only part that is missing is the CREATION OF DATA CONNECTION USING API.
The other option is to make it possible to assign Data Connections to Collections, which is unfortunately also not possible at the moment.
Our challenge is that we want to create those kind of workspaces a lot of times for a lot of colleagues without additional manual effort.
That's why I ask for enhancing the DataConnection API in order to create Data Connection using Gallery API.
Regards
Robert
User | Likes Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |