Alteryx Server Ideas

Hello

Alteryx Server with SSO configuration not able to sign request. Could you remind ? We need this feature to go into production (see attached image). 

best regards,

Nissar

Hello, 

We have been building a solution for a client that involved chaining apps. When we uploaded the workflow to the server, we got the below error: Workflow exceeded maximum runtime of 30 seconds and was cancelled. We were able to rectify this by having the client implement the change here. While I understand the need for the limit, is there any plan to have this fix be more obvious to the average user to implement or avoid needing to reimplement following a server upgrade?

Thanks, 

Option to update ownership to any other valid license holder as needed.

Use Case: Currently the canvas owner is marked by default as the user publishing the canvas to production.

However, we have seen instances where the person moves teams and would like to hand it over to another person.

Hello,

Looks like the user inputs (check boxes, free text fields, drop downs, file uploads etc., ) to the app are "temporarily" stored during the course of the app "Run" time. These - especially the "uploaded files" get deleted from  the temporary folder after the successful run of the workflow.

Ex: user uploads 2 files to the app as inputs. see attached interface.

It is important that the user selections are persisted on the alteryx server for debugging, investigation, audit trail purposes.

Of-course - there are workarounds by some extra code/logic within the app. But - in-order for the "server" tool to be considered as robust/industrialized - it is critical to "log" the user interactions on the server side.

Is it something already looked into?

Regards,

Sandeep.

The search for replacing a workflow is poor (and I get that it is probably challenging to write on the back end) but as a result even if I type in the exact title of the workflow (aka copy and paste) Alteryx replace can't find it. Not only does this mean I have multiple workflows with the same name running around (loads of fun with lack of version control) but it also makes this entire thing more frustrating every time I update a workflow (as normally this also means the scheduling of said workflow breaks).

It would be awesome if instead of having to search by title for your workflow that you wish to replace with if you could instead use the URL where Alteryx Gallery put the workflow and then there wouldn't be any confusions about which workflow and you wouldn't have to type.

We're looking to use the worker setting that cancels jobs that run over a certain amount of time. However, In testing we noticed when the server kills the job it does not trigger the workflow event for 'after run with errors'. That said, it does trigger the 'after run without errors' event, but there is no detail in the email as to what happened. This behavior seems counter-intuitive. We primarily use 'after run with errors', so our users could potentially have their workflows cancelled and never hear about it. 

is it possible to do one of the following:

• Trigger the 'after run with errors' workflow event if the server cancels a job
• Have a server notification that emails users when a job is cancelled due to run length

We're currently running server 2019.1, so please ignore this idea if this issue has been resolved in later releases. 

Here is the server setting I am referring to

Have the Alteryx Server send a notification when the license is within a configurable amount of days to being expired via SMTP

The admin (aka curator) needs to be given more control. The admin should have greater control than the users of the system.

My organization is in the Healthcare industry and we have HIPAA laws to abide by when it comes to data. Not all users should be able to see all data. Developers should not have complete control over the data they publish.

Private studio

• admin should be able to control if users can publish to Alteryx gallery (compliant issues occur when our organization's data is shared to outside users)
• admin should be able to control if user can publish to public gallery (compliant issues occur when all users can all see and run workflows)
• admin should be able to delete subscriptions and users

Collections

• admin should be able to create collections so they can manage the collections and what users have access to (devs should not be able to give any user access to their workflows)
• admin should be able to control if users can create new collections (again, compliance issues)
• admin should be able to grant and remove download of workflow rights
• admin should be able to delete connections

Get tips from Tableau as they have admin controls down with their permissions process.

Hello,

Currently we are working on an issue where we are seeing an "inbound pipe" error during a scheduled workflow, terminating at the error.

However, the workflow doesn't officially complete; it simply terminates.

For the majority of workflows, when a workflow runs with errors, completing with errors, even if the workflow was unsuccessful, you can send an email via the events for that workflow, if the workflow completes with errors, to use as an alert or trigger, etc...

However this doesn't work when a workflow suddenly terminates with errors.

I'd like to see functionality added to all ow for an email event when a workflow terminates unexpectedly, without completing.

This way, I could set up a job to re-trigger the workflow if this happens.

This can occur when memory is swamped during the initial workflow.

This functionality would be a huge positive.

Thanks

When installing and configuring Alteryx, the wizard allows the administrator to select the Gallery authentication to be used among:

Built-in

Integrated Windows authentication

Integrated Windows authentication with Kerberos

SAML authentication

The note states:

Once an authentication type has been selected, it should not be changed. Changing it may cause technical problems.

The gallery manual states "Once an authentication type has been selected it should not be changed or Gallery functionality may be compromised." 

https://help.alteryx.com/server/current/admin/Configuration/SystemSettings/Gallery.htm?Highlight=%22...

If you are reading this idea suggestion, I hope it is not too late for you. Why allow the user to change the authentication method once the install is completed? What are the options to solve this?

One option would be to grey-out the "Authentication Type" section in the  "Gallery Authentication" screen, so the user is not able to change authentication methods once after the first configuration is set. This would still allow the user to change SAML settings.

Another option, if somehow there is a reason why a user would want to change authentication types even though it is not supported, what about changing the layout to make it more difficult to change the authentication type.

What are your other suggested changes?

This is not relevant if this idea is implemented https://community.alteryx.com/t5/Alteryx-Server-Ideas/Allow-changing-of-Gallery-Authentication-witho...

However, I would imagine that a UI change would be a lot easier to implement that supporting overhauling the user management in the MongoDB.

Enhance the USER tab in Gallery for showing the active user status, last login time

Easy to filter out the active user

Allow Admin to kill user session 

Please could all log file paths on Server have the option to change their location, including 

C:\ProgramData\Alteryx\ErrorLogs\AlteryxE2

To enable all log files to be written to an alternative drive than the installation.

The benefit it to prevent excessive space usage on the C: drive

Support have advised there is no way to alter the path or limit these log files by number or size.

Many thanks.

Hello! We just upgraded to 23.2, and I see in v3 an endpoint to start a job (v3/workflows/{id}/jobs) and then another to get that job's status (v3/jobs/{jobID}). Compared to v1, I think the outputs endpoint is missing (v1/jobs/{jobID}/output/{outputID}). I'd love for this to be added so we can upgrade from v1 to v3. 

The dcm admin apis look promising. I would love if they could add put endpoints for sharing/execution and sharing/collaboration for admins. There is already a delete command for those two endpoints

I want to let my artisans choose the collaboration option when sharing dcm sources. Currently they'd have to be promoted to curators to do this.

On the Job page, in addition to seeing the worker tag that a job is running on, it would be great to see which server the job is running on to ensure the work is being spread out and look for bottle necks.  We have a group on servers broken down into Small , Medium and large with several servers in each group.  Looking at the current screen, you can not tell what server a job is running on within the group.  Example, 'Large' has 3 servers with 4 jobs running on it.  But you can not identify which server the job is running on.

I develop workflows or analytical apps in the Designer and save them in a Gallery. If I need the setting "Always run this workflow with these credentials", I have to type in my username and password every single time I want to save it, even in the same Designer session. This is very annoying and results in saving the workflows much more seldom than I would do if I did not have to type in the credentials every single time.

My idea is to cache the credentials (login name and password) for one Designer session. It would be perfect if it was for the entire Designer session for multiple files. But even if it was specific to the opened file it would help.

Result would be:

• After loading the file, the user has to type in credentials only for first saving.
• Every subsequent save would be done without further interaction.
• After closing and re-opening the file, credentials have to be typed in again.

Admin ability to put restrictions specifically on the Designer email tool.

Enhancement request to add the ability to restrict the ability to make workflows public