Alteryx Server Ideas

The Swagger page looks completely different to Alteryx Server, and essentially looks like a suspicious webpage to users clicking on. It would be preferable if this was uplifted to be Alteryx branded.

With 2023 release of server you now have two tabs Home & Admin, which is nice for Admins, but unless there are plans to add additional tabs for standard users showing the Home tab button is pointless. This is exacerbated but the fact that you cannot change the selection colour of dark blue, which doesn't work well with darker backgrounds, reducing the usefulness of theme settings.

It would be a better user experience if for standard users the Home tab button was hidden.

Currently pages you add to server when opened via the link icon open in a new window. If you are using SSO authentication, such as SAML this essentially logs the user out in that window. This is not a good user experience.

Ideally there should be an configurable option to open pages within the current window, thereby maintaining login and provided a better navigation experience.

If two users sit in the same studio and have multiple scheduled workflows in that studio, both users can see the results of those schedules under "Workflow Results" -> "My Jobs"/"Jobs Shared with Me" 

It gives both users in the studio good visibility of all the workflow results they have access to.

Now if we move to a 1 studio-1 user environment and share workflows and schedules via collections, this "Workflow Results" -> "Jobs Shared with Me" functionality is empty. Instead users have to go to each schedule individually to see the results from them there. 

So if you're in a 1 studio-many users environment, there is a single place to go to see all workflow results. But if you're in a 1 studio-1 user environment and sharing via collections, you have to go to infinitely many places to see the results of all the schedules shared with you.

So my idea is to have results from schedules shared via collections appear in Workflow Results.

Hello

Alteryx Server with SSO configuration not able to sign request. Could you remind ? We need this feature to go into production (see attached image). 

best regards,

Nissar

It would be good to have a new field with the owner of the data connection, when users asks to be part of a data connection, we should know who is the identified owner to contact and ask for approval.

Thanks.

Regards

Joana Santos

regression

Judging by the Community, it seems like the Alteryx business model is to crowdsource documentation. Do the same for a QA checklist. The 2019.4 release of Server shipped with some major regressions, notably:

DE21143 Workflow events no sending Email

DE22751 32-bit OCI connections not working in 2019.4 release

The QA team should publish the QA checklist and allow feedback from the community. The entire point of the community is to make the users and the product better. Let the users see which scenarios are tested and add ideas here for the QA team to utilize.

Hi

It will be great to make visibility of workflow execution results to other users in same subscription.

As of now, only schedules are visible to all users in a subscription, but not the workflow execution results executed by a user to other users in same subscription. 

This will avoid duplicate execution of same workflow by multiple user in a team as it will provide option to cross check the execution results by other users, if executed already, before execution of same workflow.

Regards

Haribabu Muppaneni

Currently the server diagnostics (http://localhost/gallery/admin/#!diagnostics) covers a narrow time window (from what I can see - only the last few hours)

.... and if you attempt to zoom out or pan to see a broader time window - the graph gets smaller, but the data does not grow to fill the remaining space

Please could we request 2 changes:

a) add a time axis on the bottom of this chart so that the user can understand the time dimension 

b) Increase the time available for analytics to an arbitrarily broad set of data (which the admin can configure as a server setup parameter - retention period).   For us - we'd want to keep at least 3 months of data, and be able to view this analytically.

Thank you 

Sean

Hello,

I need to monitor which applications are shared with who on regular basis. We follow the 19.2 subscription model to share applications. 

Can you extend server usage reports to include such data?

Best,

Piotr Zawistowski

Hi,

We have more than 100 workflows scheduled in different intervals for a day. Inorder to monitor this we have to manually check in the workflow results if the workflow ran successfully or not. 

Say a workflow is scheduled every 30mins then we have to check this 48times in a day manually in the Gallery results if it ran successfully or not.

Similarly we will have N number of workflows scheduled with different intervals.

We feel its too time consuming to manually verify this.

It will be good if there is a notification when there is a failure in the run, so we can check it only then rather than checking it every 30mins.

Hey Alteryx Dev Gurus - 

I've got a situation wherein the user runs something in Gallery, and complains.  I have to log in as that user to view the output files that came back out.  As a super user, I should be able to have all seeing ability!  Thanks!

brian

As a Server 2018.4 admin, I need granular control of Server/Gallery defaults including:

1.) Pre-allocate AD users and groups (under Permissions) to specific Studios

2.) Control defaults for scheduling/priority/worker settings on Users

3.) Control defaults for workflow download/no-download at Gallery or Studio level

4.) Control defaults for notifications. Currently I have to check each notification template individually to disable it. Change template tile colors (or whatever) to provide visual queue as to which are enabled or disabled.

Above all, the tiled approach to displaying users, groups, studios simply isn't scalable. A simple data grid type display will allow higher information density allowing settings like: sharing, download ability, scheduling, credential type settings (studio default, artisan specified, runtime entered etc) to be easily reviewed. Basic server governance relies on easy visibility (reporting) of settings to ensure consistency...

Hi there,

we are in a dynamic team where people move from 1 project to the other that implies moving series of workflows from private studio to collections prior to sharing. I have not found other ways but to do that 1 by 1 with very limited ways to filter the flows.

Could there be, from the collection, a way to 

 - increase number of possibilities to filters to find the proper flows (or maybe just simply allow folders in the Private studio)

 - be able to multi select the one to add / delete from / to the collection

thanks,

Currently there are certain locations on server that are paginating content results:

• /gallery/#!apps/studio
• /gallery/admin/#!apps
• /gallery/admin/#!subscriptions
• /gallery/admin/#!users

Each of these pages require users to either know exactly what they want to find by using keyword filtering or know exactly what page they want to go to and use the bottom arrows/page numbers to navigate to that page. Ditching pagination for something more intuitive helps users that may not be as acclimated with the depth of content when there are a lot of results, and also saves users multiple click interactions to find what they want.

There are tons of solutions for this, but infinite scroll is the most user-friendly & least taxing server & client side.

https://infinite-scroll.com/ has code & examples, and jquery seems to be the most widely used implementation.

It is currently (Alteryx Server 2018) not possible to delete Districts one created - we can only disable them. See also: https://community.alteryx.com/t5/Alteryx-Connect-Gallery/Deleting-Gallery-Districts/m-p/32684

Frankly, this is rather inconvenient if one wants to restructure a Gallery. Renaming them is an option, but there might still be a number of districts we want to delete. Would appreciate if this could be considered for a future update.

Alteryx Designer is an amazing data tool but it’s partner, "the Scheduler" needs some much needed upgrades. The Scheduler interface that pops up from Alteryx Designer does need a complete make over. I’m not going to address this but rather focus on the functionality that if delivered makes the Scheduler much more useful. 

Today I’m reading our Mongo db scheduler data using an Alteryx workflow and Tableau to show what’s happening on the Scheduler. This dashboard is what we refer to frequently to see the health of our companies data pipeline.  I’ll share both files soon. 

Here are the top 5 features for the Scheduler.

1. Workflow priority ranking. When two or more workflows are scheduled to run at the same time, ‘priority’ sets the order of execution. Priority is set at the time of scheduling the workflow. Values range from 1 to 100. If a priority is not set the default is 50. The ‘priority’ field can be read from Mongo db. 

Why: At midnight we set off several workflows. We want to centrally manage which runs first based on a common ‘priority’ field. 

2. Restrict which controller and workers a specific workflow can run on. Default is to run on all servers. At the time of scheduling a workflow can designated to restrict which server to execute on. This creates a field called ‘restrict’ which server it cannot execute on. 

Why: Some workflows only run on the main controller due to file system references. Also a worker can be tuned for CPU or Disk I/O and workflows that can benefit from this tuning.  Selecting a disk I/O intensive workflow to run on a server tuned for Disk I/O would speed up our workflows. 

3. Set sequence of successfully completed workflows. 

FYI: We used the Runner tool for a short time to resolve this issue but learned quickly that the Runner tool is like a bull in a china shop and brought our server down. The runner tool as it is today is not an option for production work.

Why: This would allow you to run several workflows one after another. For example the first would read from a data source, the second would do calculations on the data and the third workflow would publish the data. All workflows are given a ‘workflow-number’ which can be seen in the scheduler list and read from Mongo db. 

4. If a workflow fails you can set the number of attempts to run successfully. Report attempts greater than 1 in a new field called ‘attempts’ that can be read from the Mongo db. 

Why: Some workflows fail and if attempted to run again may work. This includes issues with locked files and workflows dependent on processes outside of Alteryx. 

5. If a workflow runs more than X minutes the scheduler kills the workflow and reports a workflow error with a unique code called ‘execution-limit’.  This code can be read in the mongo db. The defaut is 90 minutes and can be set to any number of minutes. Each workflow can have it’s own limit. 

Why: Some workflows start to hog resources and need to be killed. If a new workflow is added this is a good way to protect the overall scheduled workflows.