Featured Ideas
Hello 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
Would like to see more flexible options for workflow run-as credential settings, both for when publishing the workflow and kicking off the job.
Here is a thread where we discuss the limitations we are seeing when trying to publish the workflow to Gallery via an API. We would also like to see more flexibility when our users want to kick off their workflows via an API where they could pass in different run-as credentials they would like the job to run as.
- API
- Enhancement
Currently we can only configure questions and flow priority when using the POST API to queue workflows.
Would be good to be able be able send some of the Runtime configurations as well.
This would allow for much more flexibility.
Example
{
"questions":
[
{"name":"Test_dt","value":"1/1/2020"}
,{"name":"Test_Num","value":"53"}
,{"name":"Test_txt","value":"schedule test"}
]
, "priority": ""
"disable browse":"True" // When running flows in production this would reduce resource usage as data will no longer be cached. Having it as a parameters would mean that we can ensure that it is disabled
,"disable output":"False"
}
Current Fields
Possible other fields
- API
- Enhancement
Hi Team,
Just like the workflow upload API, could you please provide an API end-point for deleting the workflow,Job results and it's related information. In a scenario we might use gallery for one time execution of workflow, once the output was generated there is no point to have some workflows in the Gallery hence in this scenario the Delete API helps as a clean up activity on the Gallery to avoid the Junk/Unused information (Workflow/Job/Outputs).
Are there any plans to add support for the Spatial Object, File Browse and Tree questions for the Gallery REST API?
I see via the Interface Viewer in Designer that the "answers"/values to these questions are just (messy) XML I realize the File Browse could be difficult because it would involve accommodating some type of BLOB data but the Spatial Object (one or more lat/lngs describing a point or shape) and the Tree questions seems to be fairly straightforward.
We currently get around the Spatial Object limitation by specifying a latitude and longitude (for a Point) in text boxes. For shapes (polygons) we just stuff the WKT (Well Known Text) representation of the polygon in a text box. This works fine but requires special handling on the workflow side.