Early bird tickets for Inspire 2023 are now available! Discounted pricing closes on January 31st. Save your spot!

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

Allow all users in a studio to see workflow status in gallery , like wise in old scheduler we can see all scheduled workflows with a controller key .

Hi,

 

Currently on Alteryx it is possible to add visibility of a subscriptions scheduled workflows to all members of that subscription.

 

What we would quite like is for the ability to turn on or off the ability to edit workflows within that subscription for all members.

 

As in if a member goes on leave, or leaves the company, or is ill, other members can edit, update and cancel the scheduled workflow as needed without needing to go through an admin for it.

 

Many Thanks,

 

Oli

Suggested information to be included in audit logs.

 

A secure audit record of all activities on the system:

 

  1. General user access
  2. User creates / modifies / archives / deletes data (ie: history on what the user did)
  3. Administrator actions

At minimum the logs should include the following:

 

  1. Unique user identifier
  2. Unique data subject identifier
  3. Function performed by the users
  4. Date/time stamp of what was performed by user

I believe many customers could benefit from this type of audit logging, especially those who are required to obtain specific security certifications for their alteryx deployments.  From what I can see online there does not seem to be out of the box functionality for this. If anyone has implemented any type of audit logging like this please feel free to comment.

 

Thanks

 

-Vincent

Organizations using Alteryx Server with an embedded MongoDB can benefit from an option to change the MongoDB User and Admin User passwords.

 

Current deployments of Alteryx Server allow regeneration of the Controller Token, and for many of the same reasons, the ability to change the MongoDB passwords would be beneficial to customers.

 

Many organizations rely on a centralized team for daily administration of the Alteryx Server and MongoDB. With the current functionality, when members of this team change positions, they continue to know the MongoDB authentication information indefinitely. Providing organizations with this capability allows them to make the determination of how/when a change is required to mitigate any risk of misuse.

 

 

It would be great if i as a developer could create a DB alias connection and for it then to be available to other developers and distributed via the server.

 

Collaborative working like the above does seem rather limited at the moment.

 

 

Alteryx , Currently only supports AD , but looking for LDAP Support for the server to Mange users and Groups. It would be great if it supports SAML too.

In Gallery, I'd like to see the execution log in the workflow results, i.e. what you get if you run the workflow from Designer.  I'd like to see this whatever the status of the workflow completion.  Would be useful to assess warnings and the performance of components within the workflow.  Also would give me useful stats about records loaded etc.

In larger organizations or organizations with global coverage, it is possible for users to be in different time zones from each other and the Alteryx server. 

 

WIth our implementation of Alteryx server, we have the server time zone set to that of our data warehouse, but this time zone is different than my own by -2 hours. In the case of scheduling a workflow in the future, I normally correct for this by setting the scheule in the time zone of the server and things work alright. 

 

 

Problem 1:

It falls apart is when I want to schedule something in the future, but it is within the timespan between my time zone and the server time zone. For example: It is 6PM my time, and 4PM server time. I want to schedule a workflow to run at 5PM server time (7PM my time). When I try to set this up with the Version 10 scheduler built into Alteryx desktop, it overides the date field upon saving to run the following day instead of today as it thinks im trying to schedule the run at a time that has already passed (which it has in my timezone, but not in the server time zone). Upon trying to edit this schedule to reset the date to today, it again reverts upon saving.  

 

The only way I have found to get around this is to reset the time zone of my computer to match the server time zone, then set the schedule, then reset the time zone of my machine back to local time again. This is not the best experience, and will likely be required more frequently for users as their time zone difference increases. 

 

Problem 2:

When wanting to run something server side immediately (I do this in cases where the runtime will be long, or im mobile and on a machine with a lower amount of processing resources) the "Once" option can be used in scheduler to push something to server and run it. In my case, due to the timezone difference, the default time set when trying to do this is the current time in my time zone, but 2 hours ahead of the current server time.

 

 

I have two proposed resolutions:

1) Transmit Server time zone information to the local scheduler to have everything involving scheduling in Server time. Also for any timestamp fields, include the time zone designation so its clear to the user.

2) Use information from the user's machine and information from the server to do timezone conversions behind the scenes so whenever scheduling or viewing schedules, all timestamps are in local time to the user. I feel this is the prefered solution for the best user experience, but would also be the more complex to implement. 

 

 

Thanks,

Ryan

Hi,

 

We have more clients that would like to prioritize their scheduled jobs based on run time and importance. 

 

It could be a simple priority number, that decides which job that need to run next. Further it could be nice to be able to allocate certain workers to certain jobs. 

 

I am looking forward to your feedback.

 

Daniel

I like to be able to access and run my apps from my iPhone.

Currently the Gallery does not support Chained Apps or workflows triggered by events or Run Command Tool.

 

Please enable Chained Apps and flow triggering from Events and Command Tools.

 

I started building Apps a lot this last year and I have been using events and Run Command Tool for 3 or 4 years regularly.  In both cases I can't migrate most of them to the Gallery because the Apps chain and many flows trigger other flows in before and after events or Run Command Tool.

 

This should also enable the CReW macros that trigger flows.

 

Hi All,

 

Is there any plan to create an automated way of publishing apps/workflows to the gallery. This has been a common painpoint for me on several different projects when I explain how manual of a process this is.

 

I'd imagine this could easily be solved by adding an additional API call to their library. Ideally, you'd be able to point the gallery to a shared folder with workflows you want to push (git repo functionality would even be better), and have it just move the .xml scripts to the server/mongoDB.

 

Best,

dK

I wish Alteryx would allow more control over user access to scheduling workflows. Currently there is only a radio button that globally allows users to access the scheduler. I wish we had another layer where we could limit access by Permissions. For example, we would like all Artisans and Curators to have access to the scheduler, but not viewers.

 

 

It might be helpful to be able to use an API to call and pass parameters to/from an Alteryx App or Workflow on an Alteryx Server.  Then a user could use a  browser or another application to call an Alteryx app/workflow.

Would it be possible to specify whether a worker handles scheduled jobs, ad-hoc jobs or both?  Right now it seems that the workers treat both types of jobs the same, meaning that a slew of ad-hoc jobs initiated from the Gallery could slow down jobs that are scheduled to run on a regular cadence.  It'd be great if those scheduled jobs could have a dedicated worker (or workers) and have any ad-hoc jobs handled by a separate worker (or workers) so that the scheduled jobs (which might be more important) are not held up by one-off jobs.

Hi there,

 

Please can we extend the support for MongoDB to include MongoDB Enterprise latest versions, and certify at latest version within 3 months of release (both with the connector components, and the server infra)?

 

Given the deep dependence that Alteryx server has on MongoDB, being current with the latest version is critical (since many enterprises have a policy of moving to the latest version within 6 months, and shutting off old after 12.

 

https://docs.mongodb.com/manual/release-notes/3.4/

https://docs.mongodb.com/manual/release-notes/3.2/

 

Mongo 3.2 has been out since Sept 2015, and my understanding is that Alteryx Server is not yet certified for 3.2 - so it may be worth skipping to 3.4 (released 11 Sept 2017).

 

Many thanks

Sean

 

Hi All,

 

The limit of data connections in Alteryx Gallery is 100 only.

Is it possible to increase the limit ? 

 

Best Regards,

Samuel

We've purchased a server license and several designer licenses to publish analytics apps to customers via our internal/company gallery. Whether a user signs in or not, users should not be subjected to corporate Alteryx ads. This is a terrible user experience and detracts from our ability to deploy self-serve solutions.

It would be GREAT if we could have an optional notes field in the gallery. When many tools are uploaded to a collection, the titles alone are not descriptive enough for end users. I have to publish a separate "menu" for reports that are available in the gallery. In some cases I have to number them. I wish users could just browse for themselves to find the application that is suitable for their use case. 

 

Capture.PNG

 

Capture.PNG

 

 

Hi

 

My idea is to facilitate scheduling through Gallery vs the separate scheduler built into Designer. The reasons for this:

 

  1. The current scheduler authentication with Alteryx server via token is a big security concern. This allows all users to see all schedules, workflows, output logs, etc. for the entire server.  
  2. It will better interact with the Alteryx 10 version contol. Current scheduler shows all prior versions in the workflow list.
  3. Allow the server/gallery admin to setup scheduling rules. Ex: No scheduling during certain windows (for maintance downtimes), max frequency of scheduling, prevent users from scheduling too many jobs at the same time, user level rules.
  4. Allow scheduled workflow output to be retrieved from the "Workflow Results" section by the user who scheduled the workflow. Ex: I schedule a workflow that takes 2 hours to run at 6AM each day, then by the time I arrive at the office at 8AM, I can login to the gallery and download the output. 

 

Thanks,

Ryan

 

 

Top Liked Authors