Alteryx Server Ideas

Given some jobs are scheduled / can take a while to run it would be useful if Server provided the option to notify the submitting user when it has been completed, which a link to the results.

If you look at post: Re: How do I extract Server Job Run ID at runtime - Alteryx Community amongs others you can see there have been various attempts to create workarounds for this using a combination of API's & Mongo DB calls to build up the information to provide a URL in an email at the end of the flow. However, it feels like this should be an out of the box notification that can be enabled/disabled at the flow level with Alteryx Server.

Hello,

We would like to have the option to configure the timeout of the manual running jobs, as already exists for the schedule jobs.

Regards

Hi all,

In an enterprise environment - DB connections need to be set up from the server and pushed down to your users; and they need to be managed across the various servers in your software lifecycle.

In other words - you may have a sandpit / dev server env; a UAT env; a pre-prod; and a prod env - and each of these need to have the same DCM credential IDs so that users can access these.     

(before you say "you can do this from the desktop) - that is true, however that's not a workable solution in an enterprise env because that means that users can change the password from their desktop into a prod env which is a breach of IT General Controls)

The solution here is to break DCM out in to a separate service - where

- all your servers (dev; UAT; Pre-Prod; Prod) can all point to one instance of DCM

- users can maintain their own connections and credentials

        - Each needs to have up to 2 owners so that you can deal with people moving jobs / leaving the firm

- users can also entitle these connections and credentials to their team members so that when the team member logs in, it shows a popup saying "you've just been given access to new credentials / connections"

- A particular connection may have multiple different variants - depending on the environment.

        - HR Data may point to a UAT version of HR data if you're on the UAT server; and to Prod if you're on the Prod server

        - if a connection is environment specific - then it also needs to have segregated credentials (since the login to your UAT HR Data may not be the same as prod).

Thank you all

sean

cc: @wesley-siu @_PavelP 

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

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

Improve Gallery scheduling to allow the end user to specify company denoted Holidays when scheduling a workflow. If the workflow is scheduled on a Holiday the schedule would not run. This should be configurable per workflow schedule. Example: A daily report Monday through Friday would be able to skip Holidays based off a Holiday exclusion list. 

In an enterprise multi-node Alteryx Server deployment that has existed for many years and many upgrades, there are artifacts within the MongoDB that are unknown to Gallery Administrators. I envision a workflow or app that is developed by Alteryx that queries the MongoDB and looks for orphaned documents in the MongoDB across all collections. With 2022.3 there is a pre-upgrade check, however, it does not find all unexpected items within the MongoDB. Regular ongoing MongoDB health helps with overall management of the environment and could prompt for support cases before it becomes a problem during pre-upgrade activities.

Hello all,


Alteryx Designer Cloud is quite young, somehow incomplete, not compatible with Alteryx Desktop etc... but I'm very optimistic than in a few years it will become a killing app !

That said, I'm more skeptical on this race to the cloud : from my experience, Cloud should just be one way of selling a product, not the only one. It has a lot of cons and a lot of pros and customers should have the possibility to choose between "on-premise" and "cloud"  product, and change from one to the other very easily.

My main customer on Alteryx is a government agency that deals with highly confidential, personal data. They won't go to cloud. Not in the next ten years. But they would love to have the Alteryx Designer Cloud on their own server.

Best regards,

Simon

We want to share direct links to analytics apps with our users.  However this does not work with our current SAML login.   This the use case.  

1. User clicks on direct link URL for the app  

2. User  is required to click log-in button

3. After login user is taking to the gallery home page not to the app

The end effect is that we cannot share links to apps with our casual users, instead we have to instruct them to go to the gallery log in and then search all public workflows for the specific app they are looking for.   Not a great user experience, especially because we did not have this issue before single sign on support. 

personally I think this is bug more than a feature request, but was asked to create it as a request by support 

My team has started using an Alteryx Gallery 2022.1 instance and we have workflows that take a few minutes to run. Whenever we run a workflow, we are presented with a blank screen instead of the progress bar that we are used to in previous versions of the Gallery. I was wondering if there is a way of enabling the progress bar or at least setting up a load screen to notify the user that the workflow is in progress to avoid them wanting to re-run the application because “nothing is happening”.

This is what we are seeing:

This is what we are used to and would want to see when running our applications:

I've seen various solutions/workarounds but this seems to be a table-stakes ask?  When scheduling a workflow I should be able to specify which parameter values to run with.  Just two of many use case examples - 

Use case #1 - a single analytic app could be scheduled multiple times, each schedule specifying a different line of business

Use case #2 - credentials, allow the user to schedule a workflow with their saved credentials.  When their credentials change all they would have to do is update the schedule parameters

(If you know a better way I'm all ears, not the API thought that isn't a bad way to do it, just not super Easy)

after run workflow in server, it has to download output files one by one. it very annoying when the number is huge.

please change like other platform like SharePoint etc. enable select all options and/or download all options.

Hello

Imagine the dream : Alteryx Designer Cloud with in database tools.

Well, that would be so great I won't write more....

Best regards,

Simon

Currently, failed job results stay in the Mongo DB forever.  Please either make it adhere to the same coding in the Server Settings for "Delete queue and results after (days)" setting, or make it a separate option for failed jobs. 

I'd like to request the ability for the Curators to change the priority on Apps in the Gallery.

Today we have a system where users are not allowed to set the priority on workflows. The Curators change the priority of scheduled workflows based on workflow runtime/ business need by going to Gallery Admin> Jobs> Scheduled Workflows, and then editing the schedule priority.

The problem that that we have a numbers of Gallery Members/ Viewers that run Apps through the day that are very fast to run, but depending on how big is the queue they can several minutes/ hour until a spot is free to run.

If would be very helpful to get a better UX if the curator can choose which apps should have a higher priority to run.

Thanks,

Mauricio Estevez

I would like to see the enhancement of being able to schedule a start and stop time for specific jobs that need to run multiple times per day, so they don't run during the nightly backup periods of the Alteryx server. This can cause the daily backups of the Alteryx Gallery to fail. Currently SQL Server Management Studio/SQL Server has the function to able to schedule start and stop times for specific job. Currently Scheduler page on Alteryx Gallery/Server lacks this feature.

SQL Server Management Studio

Schedules on Alteryx Gallery/Server

Most companies work on a period level basis and that is every 4 weeks.  There is no way in Alteryx currently to schedule workflows to run only every 4 weeks, the monthly options do not match this cadence.  If the option was added to select "every X week(s) on X day" this would also encompass biweekly scheduling as well.  Outlook currently has exactly what would be needed (screenshot attached.)

I would like to be able to view all schedule results from all users in my Gallery.  Currently, I can see the "Workflow Results" for any schedules I create.  But I cannot see them for users unless they share them.  As admin, I want an option on the Gallery Admin screen just like there is on the Gallery user screen to see "Workflow Results" for every schedule that is in the Scheduler Database, regardless of who the user shared it with.

Currently, the only way to accomplish this is to go to Designer, View Schedules, connect to the Controller, and go to the Results tab.  This should be built into the Admin screen in the Gallery.

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.

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.