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
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.
When there is an app that has multiple tabs across the top but can extend down below the page, the user will scroll down to complete the boxes and click the 'Next' button at the bottom.
This takes the user to the next tab but remains at the bottom of the page.
It would be very useful for this 'Next' button to jump back to the top of the page.
You cannot currently upload a new workflow and specify your own workflow_id GUID. This would be useful for systematic workflows that need to be referenced in code. Currently, you either to search for a workflow by name, but you are not guaranteed it a workflow instance you uploaded. This would be helpful for server and workflow administration.
Given there are multiple api versions. I need a way to call the api and get the server version so I can make the correct API call or construct code logic which provides the user code requirement based on the versions features or limitations.
I propose a api call ../getserverinfo/ that returns server metadata like version, default worker thread count, and default memory allocation.
There is currently not a way to call the API and find out the calling user. For instance, if I have a user API key and secret, I to return the rest of the user info for the calling user or who is calling the api. I propose a api call like ../user/whoami
Commas save lives! With large numbers, it's difficult to see what number was actually entered without commas present, and the wrong number can easily be entered as a result:
Is this number
It's hard to say without taking a really close look!
As the single user who upload workflow MYWorkspace ends up being very crowded. I move them to collections to be able to share but on My workspace, I can not see which collection they are associated to. It would be nice if there was a column displayed that showed associated collections. As well as being able to have some different types of category classification. I would want something like a development stage: (In-progress, UAT level, deployed, retired) If they are retired a way to remove them off my general workspace area.
Hello all,
Right now, we can choose either MongoDb or Microsoft SQL Server as a backend. I would suggest to add Postgresql. Why ?
-it's open-source
-it's reliable
-it's free
-it works well on many environments
-it's popular
-it's already used as backend for Tableau or Qlik and many others
-it respects SQL norm and doesn't have a lot of specificity
Best regards,
Simon
After a job is run on Alteryx Server, Gallery lists Job Results with a Status column containing with one of 2 values:
If any WARNING messages are generated by the workflow, the operator/user is unaware unless they take the time to expand the message log details, then scroll through the long list of messages that typically appear in the log.
Because the Success Icon appears whether there are Warnings or not, the user must dutifully spend extra time scrolling through the list looking for Warnings even if there are none to be found.
My Idea: provide additional information under the Status column in one or more of these ways:
I think that the user would benefit from a filter where they could focus on errors, warnings, or other types of messages in the same spirit as the Designer interface, but I recognize that would be a lot of work and I am not asking for that now.
Workflows which are scheduled and continuously failing in a row 5 times need to stop/disable the schedule. Sent a mail to the workflow owner stopped schedule due to continuous error.
For Administrating the schedule workflows this feature helps a lot. Many users create workflows and dump into server and schedule it and forgot it if we implement this strategy, it will be helpful to both users and Admin team.
Currently the default 'Rows Per Page' is set to 10 when within various pages on the Gallery.
As we add more and more Apps to our Gallery it would help to be able to increase the default so it is higher than 10.
This will help ensure users do not forget about or miss tools that are available to them which are hidden on other pages. Additionally, they will not need to remember what page to jump to if the App does not pull through to the first 10 rows, or prevent the need for them having to increase the number of 'Rows Per Page' themselves.
Hello,
Maybe it's time to have a better licensing model. In addition of the current and restricted core-base model, why not having a user-based model?
Best regards,
Simon
At my organization, we have many workflows on our server that take data from one database and store it on another. We would love the ability for an alert system that warns us when a job fails so that we can solve it immediately and not risk the chance of not noticing until a few weeks or months later.
Please could all log file paths on Server have the option to change their location, including
C:\ProgramData\Alteryx\ErrorLogs\AlteryxE2
To enable all log files to be written to an alternative drive than the installation.
The benefit it to prevent excessive space usage on the C: drive
Support have advised there is no way to alter the path or limit these log files by number or size.
Many thanks.
in version 2019.3, with artisan role, I able to add workflow to collection in the workflow page.
I not sure for later version, but in version 2021.4, only curator can do so.
If I uploaded a workflow, designer already give me a link to the workflow, hence if I can add the workflow to the collection.
it goes through 2 pages within 2mins (max). it is very fast for me.
but now, I have to go back to the homepage > collection > add workflow > wait eternal time for server to get the list of workflow > select it > click add.
it extra 5~ steps. with min 10mins extra time. and if the number of workflows larger and larger,
it has chance that it fails to load the list and have to wait another 10mins, and another and another endless 10mins.
so 2mins > endless 10mins? please add back this feature.
Alteryx DCM has been an incredibly useful addition that supports key security concerns from companies. Currently, only three external key vaults are supported:
Hashicorp Vault (KV secrets engine) - supported for Designer 22.3 and later.
CyberArk Conjur - supported for Designer 22.3 and later.
AWS Secrets Manager
https://help.alteryx.com/current/en/designer/tools/dcm---designer/dcm-external-vaults.html##
I propose that we also include Delinea Secret Server.
Thank you and hopefully we can start to add more to make this feature widely useable and support security compliance.
Maintaining multiple workers (five currently, soon, six) with identical setups is challenging when dealing with In-Database (InDb) connections. I must log in to each worker, start Alteryx Designer, go to In-Db settings, and create the connection. This also becomes tedious when trying to update passwords, which occurs every 90 days in my company.
The suggestion is to set up an In-Db connection on one worker and have it propagate to the other workers.
Propagates to other workers → |
This would save time maintaining workers in the gallery and help prevent errors during setup on each worker (e.g., typing in the wrong password).
As an "extra credit" mission, expose In-Db connections through an API that can list, create, update, or delete an In-Db connection.
When scheduling workflows in the gallery that are recurring, it would be beneficial to have start and end times also. For example, when setting the frequency to hourly, if there is an option to run between 9 AM and 5 PM that would be great. This would prevent us to schedule workflows for all 24 hours and take up systemic resources when other important workflows could run instead
Hello! We just upgraded to 23.2, and I see in v3 an endpoint to start a job (v3/workflows/{id}/jobs) and then another to get that job's status (v3/jobs/{jobID}). Compared to v1, I think the outputs endpoint is missing (v1/jobs/{jobID}/output/{outputID}). I'd love for this to be added so we can upgrade from v1 to v3.
User | Likes Count |
---|---|
2 | |
2 | |
2 | |
2 | |
1 |