Alteryx Server Ideas

I have tried so many python packages to Refresh excel Pivot table automatically through Alteryx and save the refreshed data, most of the packages are working perfectly on designer but none of them are working on server.

If we find out anyway that will refresh pivot tables of Excel through Alteryx then it will be great for us. 

I have inherited admin duties, and have been running to many problems. Some of which will escalate when the subscriptions go away. 

The pages desperately need to be updated for a more streamlined admin experience.

Couple examples I came up with below. 

Naming Convention

• Allow workflow renaming without the replace function.
• Force a unique plan name across all private studios. instead of being unique on just ID.

API Access

• Allow any user who can access the module from Collections to be able to trigger it from the API using their own API key.
• Store results of "API" triggered workflows on the page.
• Groups:

• Identify Users without a group
• Identify users in more than one group
• Add multiple users at one time (Muticheck box) with filters.

User Page

• Add/remove Users to Groups
• View, add, and remove Collections from Their User Page

Collection Page

• Add Collection from the Admin collection Page

Designer "save" window.

• Give the ability on Save As & Save for the user to automatically share the plan with their collection(s).
• Default all "Workflow" assets to be unchecked by default, rather than relying on users to click "workflow options"," manage workflow assets", and then uncheck everything.

Workflow Page

• Change Owner (Can be limited to admin only)
• Add directly to collection from this page.
• Do not reset the "private data exemption" to default every time an updated version is updated.
• Allow admin users to see logs of all users who run the plan (Also add this to the admin page while you are at it)

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.

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

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).