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

alteryx server Ideas

Share your Server product ideas - we're listening!

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 like 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

Situation:

As your analytics work grows - you find yourself using the power of Alteryx to create shared macros.    These act as an accelerator for a team because one team member can us a reusable solution created by another team member.   For example - many teams need to get data out of JIRA (or some other system) so you create a connector that everyone can use.

 

That's going well - and now you have 20 teams all publishing canvasses to your server (possibly 100s of canvasses running in production) which make use of your JIRA connector - all good so-far!

 

Problem:

BUT THEN - you discover an issue with the JIRA connector and you need to fix it and publish a new version!

 

It's at this point that you realise that the canvasses on your server which use your JIRA connector are NOT pointing to it, but they have made a copy and included this inside their canvas.   So when you fix the problem with the JIRA connector - no-one gets the fix!

 

This is because every application uploaded to the server is a yxzp file, which zips up a COPY of all the shared macros and uses this in an isolated way.

So - in order to get the new JIRA connector (with the defect repaired) used instead of the old one you now need to:

- Download EVERY canvas on your server

- Unpack them all to expose the sub-macros being used

- Inspect them to see if they are actually an instance of the JIRA Macro

- Make a list of the owner and application IDs

- reach out by e-mail or phone to every one of these folk to ask them to republish their Alteryx workflow with your new version of the JIRA connector.

 

 

Proposal:

Please can we revisit this - we really do need the power of shared macros - and we also need the ability to fix and manage these like a product over time.   This will have an impact on the engine (hence copying @AdamR ) 

 

Desired end-state:

- When you build a canvas using a shared macro - it doesn't store the macro itself, but rather a reference to the version on the server - unless you explicitly decide to break the connection and take a copy.

- When you check this canvas into the server - your application / yxzp does NOT include a copy of the shared macro - instead it has a reference link

- this means that Alteryx Server can now track which canvasses use this shared macro very simply

- When I fix this shared macro - I can then do an in-place update; or if the interface is not the same (i.e. different inputs or outputs) then this has to be a new version and the users will stay pointing to version 1.

 

This is how shared assets are managed in a micro-service world, which is the way that all of our architecture is going - and it seems important that we build this thinking into the Alteryx infrastructure too.

 

 

 

 

 

 

 

@AdamR ; @Treyson ; @SteveA @DerekK ; @BlytheE 

2019.4+ Server now prompts users to select an Encoding Type when downloading a csv on the gallery. Unfortunately there is no way to disable the prompt of which encoding option to utilize or an ability to select a system default. Please provide these server options as this is causing confusion across departments. 

 

wildflower_0-1579024516244.png.csv output

yxdb_csv.jpg.yxdb output, csv format

(many users like the preview provided by yxdb but want excel download)

 

During development in Designer, when the workflow is configured to output to csv it already has the encoding configured, please provide the option to at least default this at output on the gallery:

csvoutput.png.csv config

 

The only alternative at this time is to republish all workbooks configured to output .csv or .yxdb to be .xlsx. This is not ideal.

 

Note: Scheduled jobs are not affected - I tested a scheduled run and csv files were successfully written out to a file share on the server. Content format appears to not be impacted. 

 

Thanks!

 

It would be good to have these table headers sizable, so that it can be expanded to display complete Name (and other fields).

 

nanda419_1-1578508155151.png

It would be very useful to have a standardized method to set up notifications to the server admins and to the job owner themselves if an alteryx canvas fails (error).

 

My understanding is that currently the only way to do notifications on failure for every canvas is for every canvas to individually set up events.   On a large implementation, this becomes very difficult to manage.

 

Standard notification for job failures.png

Currently the e-mail settings for the server are set up using a wizard and are not available within the admin UI.

 

Please could you add an explicit section to the Admin UI to allow the admin team to set up approved SMTP settings, allowing this all to be managed in one admin console.

 

Further: Can you allow the admins to push these settings down to the desktop users.   This would allow the admin team to control the SMTP usage and prevent data leakage.   It would also reduce complexity for the user since the SMTP settings are all pre-set making eMail tools; and Events easier to set up.

 

CentralEMailSetup.png

We use the Server API to manage our server environment - and we recently noticed that the Workflows API (/admin/v1/workflows) ignores any canvasses after the 10 000'th submission.

 

For example:

  • If we don't use any offsets or limits - then we get 10 000 applications
  • If we use an offset of 5000 with a limit of 10000 - we get 5000 applications (i.e. anything after canvas 10 000 is being ignored)
  • if we use an offset of 9990 with a limit of 100 - we get 10 rows returned (i.e. anything after canvas 10 000 being ignored)

By querying Mongo directly (appinfos collection) we know that we have 18 800 or so unique applications in our environment.

 

Please can you remove this cap from the API so that it can be used to query any number of canvasses on a larger environment?

 

cc: 

+  @Hemanth @marydest24 @Shreyasi @Sotoll @Kosi @revathi @Bethanyturner012  @TanyaS 

Wanted to grab some attention here regarding the Alteryx gallery search engine (which also bleeds over into searching for schedules and jobs when troubleshooting). 

 

Since a picture is worth a thousand words, I'm pasting two pictures (one attachment) of searching our gallery for the word "Contour" and the word "Signal". Both of these words are in the title of a single workflow - when I search for the word "Contour", the workflow pops up. When I use the first word in the workflow, which is "Signal", it doesn't pop up. 

 

I appreciate all that Alteryx does, but I wouldn't think this should be a difficult issue to fix, and I would imagine there are other frustrations with the functionality here. 

Could the community receive a comprehensive data dictionary of all the collections in Mongo with:

- Description of each collection

- Description of each attribute (or field) within each collection

- Documentation of joins between the collections

 

A great example can be seen in how Tableau documents their postgresSQL tables: https://help.tableau.com/current/server/en-us/data_dictionary.htm

 

This would be extremely helpful as we are determining which collections we need to store, how to construct queries and how to build analytics on our assets. 

 

Thank you!

Currently the server diagnostics (http://localhost/gallery/admin/#!diagnosticscovers a narrow time window (from what I can see - only the last few hours)

 

Current Server Window.jpg

 

.... and if you attempt to zoom out or pan to see a broader time window - the graph gets smaller, but the data does not grow to fill the remaining space

 

zoomAndPan.jpg

 

Please could we request 2 changes:

a) add a time axis on the bottom of this chart so that the user can understand the time dimension 

b) Increase the time available for analytics to an arbitrarily broad set of data (which the admin can configure as a server setup parameter - retention period).   For us - we'd want to keep at least 3 months of data, and be able to view this analytically.

 

Thank you 

Sean

 

 

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 using the server API to list the workflows on the server (/admin/v1/users) - only the first 10 000 canvasses are returned.

 

  • If you ask for all canvasses - only 10 000 returned
  • If you ask for an offset of 9000; limit of 2000 - only 1000 are returned (taking you up to row 10 000)
  • If you ask for an offset of 9950; limit of 1000 - only 50 rows are returned (taking you up to row 10 000)

It seems as if there is an internal constraint built into this API call that only considers the first 10 000 rows irrespective of how the query is structured.

 

Please could you eliminate this constraint so that we can query all the canvasses in our environment?    Right now the only alternative is to query MongoDB directly which is not a preferred option.

 

Many thanks

Sean

 

cc: @TanyaS 

 

 

See following article for background reference: https://community.alteryx.com/t5/Alteryx-Server-Discussions/workflow-exceeded-maximum-runtime-of-30-...

 

I have a support case (#00278355) advising unsupported changes to the alteryx.config file, involving an undocumented setting for chainedTimeout, as in:

 

<engine enableAutoLicensing="true" useServiceLayerComposer="true" chainedTimeout="10800"

 

This setting should be documented, supported, and made user-configurable through the System Settings GUI. 

 

 

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

 

 

 

 

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.

For whatever reason a schedule is disabled, whether a Studio expires, or for any other legitimate reason, a notification email should be sent to the Admin and the one that created the schedule in advance of it being disabled. When a scheduled workflow is not executed, it leaves us scrambling for answers. A sudden disablement of the schedule is disappointing to discover after all other stones have been turned. Notify us in advance of a schedule being disabled. 

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.

A nice to have is a connector for Microsoft Flow to trigger workflows.  With Microsoft Flow, users can automate processes, or set conditions that can trigger services across many different providers.  

 

Having the ability to use a Microsoft Flow can enable alteryx users to run workflows and feed in data that could be used by Microsoft Flow to feed into other processes. 

 

This would be a game changer for many users.

 

 

Currently when scheduling workflows, there is an option to schedule based on the calendar day but not on business day. For example, if I want to run a workflow on Business Day 1 of every month, it is not necessarily the first day of every Month. For the month of June 2019, Business Day 1 is June 3rd, since the 1st and 2nd fall on the weekend. Many departments run their processes on Business Days rather than Calendar days. Also factoring Holidays into consideration would be a plus since January 1st for example is a Holiday, Business Day 1 would fall on the 2nd.

Given the need for administrators to be able to perform analysis and monitoring on server performance; user usage etc - it is necessary to provide full documentation for both the API and the database underlying the server so that admins can use this to good effect.

 

Ref: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Server-API-Download-packages-for-surveil...

 

Although very limited documentation is available on the server API (https://gallery.alteryx.com/api-docs) what we're looking for is a much more fully formed and navigable experience like some of the examples below.

 

This will make building helper processes substantially easier; as well as allow admins to fully manage their environment.

 

Many thanks

S

cc: @HeatherHarris @revathi @AshwiniChezhiyan @LizaNemchynova

 

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.