Alteryx Server Ideas

In order to migrate workflows from our UAT environment to a Production server environment, we are looking for an API capability to work with the server:

- Query canvasses by name or ID (to get a list of canvasses)

- Extract Canvas to a particular location (by ID)

- Upload canvas including dependancies (with parameters for team; collection; etc)

This would assist with automating the UAT to Prod process until Alteryx Promote can step into this gap.

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh 

There is a strong need for more APIs to be introduced in Alteryx Server so that our Admin teams can provide automated solutions to our users. My understanding is that a lot of these will be introduced into Alteryx Analytics Hub however, it is also needed in Alteryx Server.

I would propose that the internal APIs for Collections and Scheduler be exposed to the Admin Key/Secrets so that we can use these APIs to move our Users workflows directly to their collection or automatically schedule for them, if needed. It seems that all this would take would be to release the Authorization from internal to the Admin on the API.

APIs I am requesting be released:

• PUT .../gallery/api/collections/{collectionID}/apps/{appID}/
• POST .../gallery/api/scheduler/

I like to be able to access and run my apps from my iPhone.

Please support SAML 2.0 for gallery

As users change roles; or possibly even leave the firm - we need to automatically manage the ownership of their and their permission.

- We need to be able to export all permissions and ownership of assets by user using an API

- We then need to be able to revoke permissions using an API (we have a central entitlement management process that this can be tied into)

- we also need to trigger a revoke on all licenses via API.

If done within Alteryx server:

- When a dept code on a user changes; or user leaves - trigger an invalidate on all assets.

- Workflow to both the primary and secondary owner to ask for a new owner

- Also automatically trigger a revoke on all licenses

I’ve had a query from a Team here at my organisation regarding OAuth2. They are trying to investigate whether a Robotic Process Automation Tool can be integrated with the Alteryx Gallery API.

It uses OAuth2 but my understanding is Alteryx Gallery uses OAuth1. 

Can Alteryx Gallery API be enhanced to use OAuth2? A plan to support OAuth2 authentication for a REST API in a future release?   

Hi all, Per this thread, it would be helpful if we could have finer control of scheduled jobs in Alteryx Server: https://community.alteryx.com/t5/Publishing-Gallery/Resource-control-on-scheduled-jobs/m-p/61016/hig...

Specifically:

- Dependancies (one job should run after another in a chain)

- lower priority (some jobs should go down the priority queue to allow for others so that high priority jobs are not blocked by other less important ones)

Thank you Sean

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 the Alteryx Gallery UI, it's possible to set up workflow credentials so that a workflow published to the gallery runs as a specific user.  

Unfortunately when that workflow is run from the Alteryx Gallery API, it appears to only ever run as the Alteryx Server Run-As account. 

Our developers in working with this figured out that if they called the (undocumented) API that runs the actual Alteryx Gallery directly, they can achieve what they want, but it seems a risky strategy.

The idea would be:

-Either unify the APIs so that the Gallery itself uses the same API to run workflows as what you present as the "Gallery API" (the eat your own dogfood way)

-Alter the Gallery API to enable us to run as a different workflow credential

Without this, we're forced to permission the run-as account to access anything that uses this method, which in turn then becomes a bit of a security hole (any workflow run will have access to everything that the run-as account uses) 

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. 

Problem 1:

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. 

Problem 2:

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. 

Thanks,

Ryan

Please support GZIP files in input tool in Server. This is related to https://community.alteryx.com/t5/Alteryx-Product-Ideas/Support-for-GZIP-gz-compressed-files-in-input..., but logged in a separate Idea because the staff indicated in the thread that they are planning support for GZIP in Designer only in 2018.2. We need it in Server as well.

Hello, I would like improved user management features and/or training

• Display 100 does not seem to work consistently
• Click /navigate from user to user – once I select a user would like to go to next user
• Changes I make with filters refresh every time I go back – which means I have to constantly reset my view in between each user
• Modify user settings in collections – would like to modify user settings instead of delete and re add user

Using current version of the server - you can see that there is no OAuth managed or published API endpoint for canvas delete (screenshot 1).   However this API does CLEARLY exist as you can see if you inspect what happens when you hit the delete button (screenshot 2 clearly shows the API being called - but it requires user login security token)

Please can you enable this API for OAuth - the API already exists, it just needs to be exposed with the others.

CC: @BlytheE 

We use the Server API to manage our server environment - and we recently noticed that the Workflows API (/admin/v1/workflows) ignores any canvasses after the 10 000'th submission.

For example:

• If we don't use any offsets or limits - then we get 10 000 applications
• If we use an offset of 5000 with a limit of 10000 - we get 5000 applications (i.e. anything after canvas 10 000 is being ignored)
• if we use an offset of 9990 with a limit of 100 - we get 10 rows returned (i.e. anything after canvas 10 000 being ignored)

By querying Mongo directly (appinfos collection) we know that we have 18 800 or so unique applications in our environment.

Please can you remove this cap from the API so that it can be used to query any number of canvasses on a larger environment?

cc: 

+  @Hemanth @marydest24 @Shreyasi @Sotoll @Kosi @revathi @Bethanyturner012  @TanyaS 

Could the community receive a comprehensive data dictionary of all the collections in Mongo with:

- Description of each collection

- Description of each attribute (or field) within each collection

- Documentation of joins between the collections

A great example can be seen in how Tableau documents their postgresSQL tables: https://help.tableau.com/current/server/en-us/data_dictionary.htm

This would be extremely helpful as we are determining which collections we need to store, how to construct queries and how to build analytics on our assets. 

Thank you!

It would be nice to be able to change the Gallery URL from:

• http://localhost/gallery/
• http://alteryx.mycompany.ca/gallery/

to:

• http://localhost/
• http://alteryx.mycompany.ca/

The reason being to make it easier for end users to find the server/content.

Original forum post here: https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Changing-the-Gallery-URL-on-Alteryx-S...

Currently, this is completely manual with whoever is assuming the schedule creating it under their profile and then the old schedule being deleted.

This can happen often in organization where a user leaves the company or assumes a new role requiring some else to maintain those schedules. It would be convenient if there was an option to reassign the owner of a schedule to simply this process.

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.