Alteryx Server Ideas

Today, when you trigger a job using the Server API, it is considered as a manual run type. In fact there are only 2 type of jobs : "Scheduled" and "Alteryx_Run"

I think "Alteryx_Run" should be segregated into "API_Run" and "Manual_Run". This way in future version we could treat those type of job differently. 

We could also have more stats around the type of jobs.

As the title says: please make the date modified data more granular e.g. yyyy-mm-dd HH:MM:SS and not 6 months ago

The current behaviour is the same in designer & browser, but is more important in browser (first screenshot) as there isn't an indicator or method or sorting the order.

Hello,


There are some tools that helps to monitor what happens on a website. Some are even open source (like matomo and open web analytics). Why not including one of those tools on Alteryx Server ?

There are of course a lot of feature but I like this one, an heatmap to show where a user click

Best regards,

Simon

User who share Apps/Workflows with other users in a collection are not able to see the results of the other users executions directly in the gallery.

Could you please add the possibility to share workflow results in the Alteryx Gallery?

currently, there isn't any way to fully delete (safely) a user from the gallery. So if there is a previous client or previous employee in gallery, we cannot clean up the gallery settings - only "disable". It would be great to have a "trash can" symbol next to the users where we can remove them from the server and keep all of the users clean. 

Situation:

As your analytics work grows - you find yourself using the power of Alteryx to create shared macros.    These act as an accelerator for a team because one team member can us a reusable solution created by another team member.   For example - many teams need to get data out of JIRA (or some other system) so you create a connector that everyone can use.

That's going well - and now you have 20 teams all publishing canvasses to your server (possibly 100s of canvasses running in production) which make use of your JIRA connector - all good so-far!

Problem:

BUT THEN - you discover an issue with the JIRA connector and you need to fix it and publish a new version!

It's at this point that you realise that the canvasses on your server which use your JIRA connector are NOT pointing to it, but they have made a copy and included this inside their canvas.   So when you fix the problem with the JIRA connector - no-one gets the fix!

This is because every application uploaded to the server is a yxzp file, which zips up a COPY of all the shared macros and uses this in an isolated way.

So - in order to get the new JIRA connector (with the defect repaired) used instead of the old one you now need to:

- Download EVERY canvas on your server

- Unpack them all to expose the sub-macros being used

- Inspect them to see if they are actually an instance of the JIRA Macro

- Make a list of the owner and application IDs

- reach out by e-mail or phone to every one of these folk to ask them to republish their Alteryx workflow with your new version of the JIRA connector.

Proposal:

Please can we revisit this - we really do need the power of shared macros - and we also need the ability to fix and manage these like a product over time.   This will have an impact on the engine (hence copying @AdamR_AYX ) 

Desired end-state:

- When you build a canvas using a shared macro - it doesn't store the macro itself, but rather a reference to the version on the server - unless you explicitly decide to break the connection and take a copy.

- When you check this canvas into the server - your application / yxzp does NOT include a copy of the shared macro - instead it has a reference link

- this means that Alteryx Server can now track which canvasses use this shared macro very simply

- When I fix this shared macro - I can then do an in-place update; or if the interface is not the same (i.e. different inputs or outputs) then this has to be a new version and the users will stay pointing to version 1.

This is how shared assets are managed in a micro-service world, which is the way that all of our architecture is going - and it seems important that we build this thinking into the Alteryx infrastructure too.

@AdamR_AYX ; @Treyson ; @SteveA @DerekK ; @BlytheE 

Hi all,

Having all the schedules/results centralized in the same place would be neat!

Option 1: Have all on the same page and have an additional column to describe the shared source.

Option 2: Have a separation between my own schedules and the ones shared with me.

Best,

Fernando Vizcaino

When adding jobs to the queue via API call, you currently cannot specify the name of the job.

Running the job directly from gallery allows this as in the picture below, but there is no setting to do so in the API.

When a workflow is used in many different situations, being able to specify a name for the individual run will make tracking and troubleshooting easier.

We leverage Active Directory groups to manage user permissions to most of our company's resources like databases, file shares, applications, etc.  This idea is for the ability to manage a Gallery Data Connection via an Active Directory group.  In many cases, our AD group membership actually dictates what permissions a gallery connection should have, but we must manually add/remove users to the Alteryx connection to keep it synched with AD.

I think there are several ways Alteryx could be enhanced to support this; i.e. the AD group could be specified on the connection itself or it could be inherited from a Studio where the subscription is enhanced to support assigning AD groups to it (which could benefit other areas of Alteryx).

I'm told by Alteryx support that this functionality is unsupported but to post the idea here.  If anyone knows of workarounds to this limitation I'd certainly be interested!

This idea has been touted in different flavours over the years (but not implemented), but I'd like to push it a little further:

1. Create the ability to collaboratively edit an Alteryx workflow - e.g. like you can edit Microsoft documents collaboratively. If the front-end is primarily an XML interface, this should in theory be possible?

2. Version control (not version tracking) - i.e. automatically state the differences in scripts between versions and allow for checking in and checking out of code

3. Power BI & Tableau Prep have the ability to see exactly what changes were made and to reverse steps to get back to a specific stage of development: it would be great to have a panel that tracks all the edits you've made since you started editing the workflow

In simple terms, a modern, interactive way for multiple developers to work together, but also to encourage the use of Server to "check in" your application and to avoid developers saving the same file over & over again locally.

I would like to propose a number of small enhancements to the Gallery:

1. Time format. The 12-hour time format (

    

   ) is confusing to everybody except Americans. Please add support for a 24-hour format. This could be done either by extending the Locale settings or by a separate check box. Please make sure that this time format is used everywhere in the Gallery (last update, last run, schedule, etc.).
2. Date format. Even though using English as GUI language, I prefer the time format according to ISO 8601-1, namely "YYYY-MM-DD". Please add support for this format, independent of selected language.
3. Number of Rows per Page in My Workspace: Each time I open My Workspace, the number of listed workflows per page is set back to 10. Please add support to set the default number of workflows in the user settings or at least preserve the chosen number within the same session.
4. Fully utilize the screen in My Workspace: Even after switching to more than 10 rows per page, nearly half of my screen stays empty. Please add function to utilize the screen completely.
   

Currently, the API V3 endpoints does not have anything for Data Connection Manager (DCM). Create an endpoint to allow users to add/delete/update and list data sources, credentials, and users of DCM data sources. Also include an "admin" endpoint that can list all of the above for the entire server.

The admin screen of Alteryx gallery does not have an admin function for DCM sources, its users, and credentials. This can cause visibility issues during audits of the gallery. An API endpoint can alleviate this issue until it is added to the UI.

It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).

My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events.   On a large implementation, this becomes very difficult to manage.

The current Alteryx user interface is displayed in a vertical orientation without the option for customization. To optimize space efficiency, it would be highly advantageous if the filters could be arranged horizontally, as depicted in the attached figure.

Additionally, there is a usability issue with the options list for interface tools like the list box. Currently, all options are displayed without utilizing a dropdown, requiring users to scroll extensively when multiple tools with numerous options are present within a single analytic app. Implementing a dropdown functionality for improved navigation would significantly enhance the overall user experience.

Hello Alteryx Server Admins,

It would be fantastic to manage users' permissions with user groups. This would help manage all users with permission to create collections and schedules from a centralized page.

Something like this:

Best,

Fernando Vizcaino

Hi all,

I would like to suggest the idea to make the ability to add a graphic to an Interface on the server as well. 

Currently, the function only seems to work on Desktop, but having it work on the Gallery as well would be very nice.

Especially if we could have the image be horizontally oriented as well as vertically, depending on our other interface tools. 

Would love to hear any other related comments or ideas!

One of our Server customers has a need to disable all schedules temporarily across all worker nodes.  I do not see an easy way to do this unless we go into each worker's settings and disable from there, but this is not ideal.

The reason is for scheduled maintenance windows during a large upgrade or migration.  Currently stopping the Alteryx Service on each worker is time consuming.

Thank you! 

The AlteryxService internal authenticated API that the nodes use to communicate with each other for status is not accessible to customers because it is using an undocumented authentication method. The data this appears to provide would be useful to server administrators to determine the true health of the individual nodes and for reporting purposes.

There is no good way to get server user credentials into a workflow without asking them for it in an App interface.  It would be great if we could have a built in Constant that could be used to silently pass user credentials into a workflow for things like API's or logging user information.