Alteryx Server Ideas

Everyone on our team would benefit from having access to each other's workflows -- including workflow results and scheduling -- but publishing them to gallery where any user in the company can run it/ download it would present a security issue. Functionality that is not met with Collections. I found a similar idea, but not anything that encompasses the whole thing.

It would be of immense value to have a Team Gallery - something intermediate to the company gallery and the private collection. This would enable our team to have access to modify, publish, schedule workflows as a team.

It would be great to have an option to show intermediate output in gallery and allow user to modify that intermediate output before running the next step in a chained app environment.

This will come really handy in cleaning messy data which requires some manual input and user can complete their work form single gallery screen.

Currently the only way to achieve it is to build separate workflows/apps where first you have to download the messy data on your local drive and then upload it back via a separate workflow to complete the task.

The AlteryxService addtoqueue command is great, but it leaves me wanting more.  My simple use case is to run WorkflowB via the addtoqueue command in an after run event from WorkflowA, which is run daily.  The result is that i end up with a cluttered scheduler with many instances of WorkflowB that i need to manually clean up, since addtoqueue creates a new record in AS_Applications each time it runs

It would be useful if there was an AlteryxService command for each of the subroutines already built in to the scheduler front end app: schedule workflow, update workflow, add workflow, remove workflow, edit schedule, etc

MongoDB objects could be identified by oid which the user can get from querying the AlteryxService database

I don't want to rebuild what you've already built, just need a little more control over it 🙂

Currently the default 'Rows Per Page' is set to 10 when within various pages on the Gallery. 

As we add more and more Apps to our Gallery it would help to be able to increase the default so it is higher than 10.

This will help ensure users do not forget about or miss tools that are available to them which are hidden on other pages. Additionally, they will not need to remember what page to jump to if the App does not pull through to the first 10 rows, or prevent the need for them having to increase the number of 'Rows Per Page' themselves.

Alteryx DCM has been an incredibly useful addition that supports key security concerns from companies. Currently, only three external key vaults are supported:

• Hashicorp Vault (KV secrets engine) - supported for Designer 22.3 and later.

• CyberArk Conjur - supported for Designer 22.3 and later.

• AWS Secrets Manager

https://help.alteryx.com/current/en/designer/tools/dcm---designer/dcm-external-vaults.html## 

I propose that we also include Delinea Secret Server.

Thank you and hopefully we can start to add more to make this feature widely useable and support security compliance.

Maintaining multiple workers (five currently, soon, six) with identical setups is challenging when dealing with In-Database (InDb) connections. I must log in to each worker, start Alteryx Designer, go to In-Db settings, and create the connection. This also becomes tedious when trying to update passwords, which occurs every 90 days in my company.

The suggestion is to set up an In-Db connection on one worker and have it propagate to the other workers. 

Propagates to other workers →

This would save time maintaining workers in the gallery and help prevent errors during setup on each worker (e.g., typing in the wrong password).

As an "extra credit" mission, expose In-Db connections through an API that can list, create, update, or delete an In-Db connection.

Hello all,

According to https://openlineage.io/ 

An open framework for data lineage collection and analysis

Data lineage is the foundation for a new generation of powerful, context-aware data tools and best practices. OpenLineage enables consistent collection of lineage metadata, creating a deeper understanding of how data is produced and used.

 
This is typically the open standards needed for lineage analysis and I think it will become more and more a differenciator with your competitors. As of today, DBT or Apache Airflow already supports it (as producer), Egeria or Marquez already support it (as consumer) and guys from Datahub are working on it  (as consumers)https://feature-requests.datahubproject.io/p/openlineage
So I think Alteryx should implement this standard API as a producer, it's the next big thing in Data Governance and you don't want to stay behind !

Best regards,

Simon

Previously, Alteryx Gallery had a progress bar when the job is running. However, it has been removed in the newer version and the screen only appear blank when the job is running. This could lead to confusion in users as they might be wondering what is happening when the screen goes blank when it actually is running the job. Users might also attempt to click the run button repeatedly due to this.

Hence, I hope Alteryx could bring back the old UI that showed progress bar or anything similar when the job is running so users will aware of what is happening. 

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

Sometimes, a workflow posted to the Server is calling from a source data that has dimensions which are specific to certain users based on departments, divisions, countries, regions, states, or etc. depending on the level of granularity. 

Although Alteryx developers can create Analytical Apps that have the option for end users to select these dimensions, a more seamless experience for end users (and better for security as well) is to have the ability to configure such filters for existing users on the Alteryx Server itself.

So, if Person A belongs to State 1 and Person B belongs to State 2, by default when both Person A & B enter the Server to that specific workflow in a collection or district, they will automatically be filtered for State 1 and 2 respectively. 

This is similar to Section Access configuration - whereby users have already been pre-filtered the moment they enter.

The current workaround is to create multiple workflows and store them in different collections or districts specific to end users, and to make any changes will require a change to the workflow itself. 

It will be great to have a dashboard that allows for Alteryx Server admins to configure on their own without hassle.

API that allows to specify the workflow version to download.

An example would be where a user has a scheduled workflow that runs at regular intervals and they might want to look at the logs from the results from a specific date. Having the ability to filter the date column would help with this, as the only other alternative at the moment is manually working through the pages.

User setting possible for:

1. Sorting of content to be saved: Cohoseing wether to sort by name, date, type or all

2. number of entries displayed to be saved, 10 is not a good default

3. 1.+2. should be valid for all content like: Workspace, Collection overview, Collection content etc.

Hi everyone,

Since the Home page has been replaced by the My Workspace page as the main page on the Gallery, end-users are getting confused or at least uncomfortable with this transition.

It would be amazing to change the default main page to the Public tab or even remove/deactivate the My Files tab for these users. 

Removing /deactivating the My Files tab will also correct an issue generated when an Artisan is downgraded to an end-user. Currently, these users can see their workflows in the My Files tab but can't access them.

Idea based on @phottovy 's question: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Change-quot-Public-quot-to-default-view-...

Currently Alteryx has a timeout setting at a worker level which applies to all of the workflows/schedules that run on that node. 

It'd be great and very useful is that setting is made available at a granular level like at the Collection/User Group or workflow level. 

I've been told by Alteryx support that this is not a feature that is currently available. Hence proposing an Idea on the community requesting for such an ability!

It would be nice to have workflow version information on the Workflow Results page for every running status.
The reason for that is after workflow was scheduled and then the published version has been changed, there is no way to follow versions.

The job timeout function is a perinate issue on the the Alteryx server because scheduling workflows on the server that overlap with another workflow can cause bottleneck issues. Depending on the number of workers and the other workflows, the workflow in question could fail to run or not complete running at the desired date and time. I recommend a view option of the Schedule Forecast feature for all users, so as to allow all users to effectively schedule workflows on the Alteryx server that do no conflict with other workflows. 

When rerunning a failed manual job, the same Priority is used, but the Optional Job Name is not and cannot be re-entered on submit.  User has to go to Workflow results page and Edit to add the Optional Job Name for a rerun.

I suggest the Optional Job Name text box be added to the rerun submit page.

Prefill using the original job's value if one exists.

Thanks,

MJ

As we look at upgrading Alteryx Server - one of the challenges is that it's an all-or-nothing approach; and there doesn't seem to be a guided wizard approach to upgrading.

The upgrade process would be much less intimidating if we could create a Migration tool which can work across versions - similar to Microsoft SQL Server which has the.    This would allow us to:
- Migrate a subset of assets up or down versions

- Migrate across servers to do consolidation or to split loads into different servers for the purpose of segregation

- Progressively migrate over time to limit the risk.

cc: @JohnPelletier