Alteryx Server Ideas

Right now, with LSS, the only thing you can query who has taken seats on licenses (you get user's email and host name).  This is OK, but it would be great if we could get more information than that.  Primarily

• What was the date/time that the user first grabbed that license
• When was the last date/time the user connected to the license

As you know, there is no way to forcefully remove a license from the LLS (you either have to have user deactivate from Designer, or wait 7 days).  Knowing this information would help admin's know who is actually using the licenses and if someone leaves the company, you can get a countdown until that license is released.

For historical tracking and auditing, I would also like to setup an Alteryx Workflow that puts licensed user information into a table or DB so we have a log of who is using the licenses.

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

For our large organization a requirement is that the Server connect to MongoDB cluster requiring keytab kerberos authentication. Can we please upgrade to needed MongoDB version that would support this as well as enable it within Alteryx Server.

(https://docs.mongodb.com/v3.2/tutorial/control-access-to-mongodb-with-kerberos-authentication/)

Alteryx Server seems to natively support MicrosoftSQL and Oracle connections on Alteryx Server. It would be helpful to natively support (i.e., a non-ODBC connection) for Cloudera Hadoop as well.

When we upgrade a server - we often want to do this progressively so that we can move a few canvasses to the new version over time.
However - in order to do this we need to create an entirely new server URL and then users have to deal with the irritation and complexity of storing multiple addresses and knowing which one is where.

This would be substantially easier if we could put a load balancer / a consolidator in front of the alteryx server - so the user can go to the same gallery - but under the covers some of their stuff has been upgraded to the new version (on a new server) and some is still on the older server.    

Hi Team,

We have new idea which we dint find on Alteryx community, also Alteryx expert confirmed for now this is not possible.

Please find the below details:

Use Case: Automating Onboarding Process for collection creation.

Idea: Currently we are doing this onboarding manually, such as user fills up the form in Sharepoint with all relevant details for Collection Creation.

We as an Alteryx Support team, check the form and create the collection Manually.

We want to create a Workflow, such that it will read the form from SP and create the Collection Automatically without any Manual user intervention.

Benefits: If we Automate this then we can save manual user efforts and also avoid any manual mistakes.

Note: If this can be possible with any other feature of Alteryx like API, then also we are good.

Regards,

Niharika

Currently, Alteryx Server has a setting for how many days to keep Results from scheduled workflows, which prevents your Results log from getting too large.

Unfortunately, this setting is universal to all workflows, regardless of schedule.  If you have monthly jobs sharing a server with jobs that run every 5 minutes (which we currently do), and you set your limit to 30 days, you get at most 1 result from monthly jobs, but 8,640 results from your 5-minute jobs!

A better option would be to keep the most recent X results from any schedule (where X is user-configurable).

*This is an idea from @riverotoledo_21 from the Portuguese Community*

• How to bring user’s variables/information that we want to use within the workflow that will be published in the Analytic App in the Gallery (For example, I believe that all “non-sensitive” information from MongoDB related to the Gallery actual session should become variables)

I'd love the ability to have one schedule for a workflow at specific times. 

Currently you have to create 4 different schedules if you'd like a workflow to run at 10 am, 3 pm, 5:30 pm and 11:30 pm and doing this makes the "Scheduled Workflow" section of the server not only cluttered, but a lot more difficult to manage.  (like spotting accidentally duplicated schedules- which also happens more often than i'd like :)

Thanks!

I manage a server with 200 + Artisans. Some of them tend to abuse the Scheduler by having workflows running every hour or every x hours. This can penalize other users creating big queues thought the day. Currently I monitor the queue and schedule often and then contact these individuals to better accommodate their needs.

Having the possibility to disable hourly workflows, or enable to only specific users, would help a lot to deter the abusers.

Thanks,

Mauricio Estevez

It should be possible to trigger the same workflow in different ways from Alteryx Gallery: 

- Workflow chaining: 

      -  Workflow B runs after the successful execution of Workflow A

      -  Workflow B runs after the failure of Workflow A

 - Schedule: Workflow B runs on multiple schedules

- API call (even when it is not an analytical app) 

For example (considering the same workflow): 

- Audit workflow runs every day

- Audit workflow runs every hour during the last day of the month

- Audit workflow runs if triggered by financial close on 3rd party tool 

- Audit workflow runs after the execution of the financial workflow

We are looking for the ability to use Alteryx as PaaS in the Azure cloud similar to how Databricks is working on Azure. So servers spin up when demand shows up and then they spin down.  Where we are not on the hook for server patching etc., but instead, we lease processing power/time from Alteryx in the cloud on an as needed basis. The licensing model will also need to be a scalable to support this type of usage.

It seems from my own experiences and other community posts (e.g. https://community.alteryx.com/t5/Alteryx-Server-Discussions/Scheduled-worklfow-not-picking-up-the-qu...) that when scheduling a workflow in the gallery, the gallery will run whatever version was most recently uploaded, regardless of which one has been labeled as "Published". Since naturally the intent is for the Published workflow to be the only version running, it would be nice (adnd would me much more logical and intuitive) for the scheduler to run that version.

Having the option to disable schedules within the Designer application would be advantageous for we support staff.  Especially when multiple service restarts or server reboots are required.  When we perform migrations or restores or even upgrades or when conducting server maintenance actions.   As we know starting of the Alteryx service immediately queues up workflows to be run based against there schedule times.   When maintenance is being performed we do not want workflows to run, and/or having to wait for completions or have the user to rerun the workflow.   The option to temporarily disable schedules globally with a click of a button is far better then changing the parameters of the schedule or even deleting it.   To go a step further = an internal mongodb administration command to disable/enable schedules would also be helpful at the database level 

Please consider adding this feature to the Alteryx PRIVATE Galleries.  This is a feature of the Alteryx Gallery and would be useful for our clients too.

Thanks,

Mark

Hi!

It would be very useful if Alteryx would allow users to create folders under their Private Gallery. My private gallery is now 3+ pages long & it would be super helpful to be able to organize the workflows into different folders (Archive/Retail/Linear/Fin/etc), allowing for easier housekeeping & tracking. I realize their is collections but I'm not trying to share anything here, just organize my content for easier viewing.

Thank you!

We've noticed on our Server Gallery that users must click 'Run' two separate times when running an app.  The first time they see 'Run', its really taking them to a configuration screen, rather than actually executing the tool.  What if that first 'Run' button was changed to 'Configure'?  We've seen that users hesitate to run apps because they aren't sure what they're getting when they click 'Run' the first time.

 Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted. 

Product should be capable of using the newly installed configuration and not require manual Config change and service restart. 

so every time there is a java version upgrade,  users have to be notified of the downtime  (even though they could move into 7 day grace period) and then the flexnetls.settings file should be updated with Java home path.  

@Kosi @SeanAdams 

Password entered during installation is changed to LLS default password after the following sequence of events.

LLS Service start -> Settings update -> Service restart (to let the settings change take effect). 

Avoiding this behavior will save server admin's time in changing password every time setting is changed. 

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone