community
cancel
Showing results for 
Search instead for 
Did you mean: 

alteryx server Ideas

Share your Server product ideas - we're listening!
Community v19.6

Looks aren't everything... But the latest Community refresh looks darn good!

Learn More

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the star in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

I have three team members all in the same private studio. We can see each others' workflows. However, when looking at a workflow that another team member has published to the gallery, it looks like:

  1. The workflow has never been run
  2. The workflow is not scheduled to run

This is a massive impediment to collaboration because my team handles ETL for most of the company. If a user complains that their data isn't up to date, whoever receives that support ticket needs to be able to see if the workflow is actually running and whether it was successful or had an error during the last run.

Preventing a team from seeing this for each others' workflow schedules and results means that the only person who can deal with an issue is the person who originally made the workflow. Which makes the idea of a shared private studio wholly pointless as we may as well be operating in different universes.

 

Please create a studio-level setting where all members of a studio can see all schedules and results of all workflows in that studio.

When an artisan moves positions (within or external) away from their current responsibilities, their collections and workflows should be able to be transferred via an administrator to another user.

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.

As a server administrator, I would like to have more control over collections.  I have a user who is in charge of a collection out of office, and we have some users who need to get to be added to the collection to run workflows.  As admin of the server, I would like to be able to add users to this collection, modify permissions, modify workflows, etc.  This would be necessary both for when users are temporarily out of the office as well as if someone were to leave the company.

It would be useful if the Admin of a Private Gallery (in house server) could delete studios and/or members.  Also, it's confusing that a member who's added also gets a Studio automatically set up.  Members (for my purposes) are only supposed to be able to run apps in collections that I grant them access to.  They should not get their own studio.  Even if they can't use the studio (or even know that they have a studio), it's not very efficient to have all these studios show up on the subscriptions screen.

I'm really enjoying the new Save As functionality to push to the gallery, but had a request that would make it even more useful for me. 

 

I saw that you can open workflows directly from the Gallery and edit them with version control, but it would be nice if it was possible to do a Save As on a local workflow and point it at an existing copy on the server.  I need to maintain a local copy of my workflow for dev/prod separation, but currently my way to push to prod is to do a Save As to my Private Gallery, remove the existing copy from the company gallery, and then share my newly created workflow into the company gallery.  This causes some headaches like no version control, switching out icons everytime, and overall just a messy way to push to prod.  

 

It would be helpful if there was a way to overwrite an existing workflow in the gallery rather than editing it directly.  

So - one of the biggest challenges that we have with the MongoDB used by Alteryx Server is that we continually have issues with locking (where our admins have to go in and undo locks)

Additionally - the current implementation of MongoDB connectivity does not support full Kerberos authentication which means that we're on a non-compliant install (which in a large enterprise is an uncomfortable place).

 

Given that a very large amount of what the server does is transactional - it would make sense to have an option to use a large-scale SQL server instead of using Mongo.   For large enterprise customers, there must be flexibility to allow the databases that they have large supported instances of (my strong preference would be MS SQL 2016).

 

MS SQL natively supports XML so all the canvasses can be stored in native format.   Additionally, MS SQL allows very fast query across XML, and given the clustering and reporting capabilities in MS SQL, this would dramatically increase our ability to self-manage our infra.

 

Given that Alteryx is looking more and more at large Enterprise customers - a move to a large-scale clustered SQL env as the back-end would be a very positive move.

 

NOTE: as we consider DB options for a SQL backend - please consider your large-scale enterprise customers.   For example - MS SQL or Oracle or DB2 are all much more prevalent in enterprises than databases like Postgres - so it's important to focus on the enterprise support for the DB that you choose.

 

@Deeksha @avinashbonu @revathi @BenBu

 

Many people maintain valuable information in Excel files, and many organizations, like ours, also use SharePoint to store and share structured and unstructured information. We see most user-generated and maintained data in Excel files in SharePoint document libraries, and one of the great benefits of Alteryx is the ability to join that Excel data with other data sources.  Unfortunately, the v11.0 Scheduler cannot resolve the UNC-style ( \\server@SSL\DavWWWRoot\site-name\document-library\filename ) addresses, so workflows that access this valuable SharePoint Excel data must be run manually. The SharePoint List Input tool can read the list-style metadata for Document Library files, but does not access the file content.

The Scheduler should be enhanced so that scheduled workflows can read Excel data stored in SharePoint Document Libraries. 

Allow to create custom user security groups server .

Sales
User1
User2
Studio1


Supply chain
User3
User 4
Studio3
Studio1
......

As the Server Admin I'd like to have the ability to view ALL "Workflow Results" for all Subscriptions.This will give the highest level admin the ability to monitor all schedules (on the entire server instance) and monitor if they are unable to complete successfully (example- unable to allocate memory) and any other errors are occurring. 

 

Knowing this information will help the server administrator understand if there are issues with the server itself (e.g. if we need more workers or to simply adjust actual server system settings..etc..)

 

 

 

 

This post illustrates the current state of how the Gallery and Scheduler interact with time zones as of V11.7. The behavior it showed in that test is unintuitive and may lead to issues with setting schedules correctly. One possible correction would be to unify all times on the server to server time, but I think we can do better.

 

What I suggest instead is to add time zone as an option on the scheduler. This way users that set schedules don't ever have to wonder at what time the workflow is actually going to run. That information can also be passed through to results such that users that want to make sure a schedule is working as planned don't have to back track and figure out if 5pm means 5pm their time or server time. Finally, it would allow a more intuitive way for an employee in Denver, CO schedule a workflow such that his or her boss in Irvine, CA receives the resulting report exactly when needed/expected.

I was reading a post on the Community (http://community.alteryx.com/t5/Publishing-Gallery/Macro-sharing-Best-practice/m-p/38330) which reminded me of an idea that I had.

 

It would be really nice if a Gallery location could be used as a "Macro Search Path" so that macros don't need to be downloaded from the Gallery and saved locally to be used in a workflow.

 

So in addition to going to Options>User Settings>Edit User Settings>Macros and adding a local/network path, you could add your internal gallery information...

I would like to collaborate with my team, but also maintain my own personal private studio.

 

Is that on the road map?

 

-Dan

 

 

The Save to Gallery window does not resize. When I try to Save my Workflow to my Gallery and Manage Workflow assets, I can not widen that window to see the full path to my assets.

This makes it very hard when you have many assets to know if they need to be included or not with the promotion. It may take two or three attempts guessing what asset is what to get the correct combination to make my App run correctly.

 

Assets.png

 

It would be nice to be able to widen this window much like we can with the Workflow dependencies window.

Currently the InDB tools require to select a DSN that is defined on your computer.

 

This makes any workflow which uses a DSN incredibly painful to deploy to the server, since the DSN needs to be created on every worker node and for a large server environment this can  mean creating DSN entries on 6+ worker nodes in prod plus prod server plus dev/UAT environment plus dev/UAT worker nodes.

 

Could we please change the InDB tools to default to DSN-less connections, where the connection persists the connection details in-line so that it can deploy to the server without a DSN setup (since all connection details are contained within the connection string)?

 

Thank you

Sean

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

Now, gallery does not support AD group , need to setup user one by one.

If gallery support AD group synchronization, it is more convenient for gallery admin to manage large number of users.

By assigning AD users to AD group, it will reduce the maintenance task of gallery admin, since gallery admin don't need to grant rights in the gallery directly. 

When posting an app to the Gallery, if the app has, say, one PCXML output for the user to see, and one Excel file for the user to download, it would be helpful for to be able to specify which shows first to the user.  For example, I have a PCXML that gives the user summary tables, and instructions on how to go to the drop down above and select the second report, click on the Excel icon, and download it.  But if the Excel report shows up first, then there is no ability to give them instructions and many simply won't be savy enough to go find the PCXML in the drop down.

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. 

 

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

 

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

 

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

 

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

Today, if I want to save a job onto the Alteryx Gallery, I need full permissions to do so and it is a manual process.  For some organizations, this level of access is deemed excessive, which can make properly leveraging the Alteryx Gallery difficult.  Having the ability to write a "deployment" script that could publish a workflow to the Gallery, and potentially add a new workflow to a Collection would be incredibly helpful in these cases.

Please support SAML 2.0 for gallery

Top Starred Authors