Alteryx Server Ideas

It would be nice to be able to toggle between the Admin screens and the Gallery screens.  

In the Private Server settings, you can "Run As", but it is all or nothing -- anything on Scheduler will "Run As" the user coded (or you can leave it as the default which is the machine).  It would be helpful if functionality existed like the Gallery - where you can dictate "Run As" for each individual module.

Please keep in mind that this is a suggestion from a container novice! 🙂

However, our situation is such that our release upgrade deployments are taking significant time to install, test and sign-off from DEV through PROD for the four main life-cycles involved in our server environment. Even if we script the deployment to save time, there's still manual configuration needed to confirm the new version works in the next server environment.

Similar to how Promote can deploy from DEV through PROD using images/containers, my suggestion is to package the Server components into images/containers that can be similarly deployed through the life-cycles. While the container with mongoDB doesn't need to move to the next life-cycle, the containers with the web server, load balancer, and engine nodes could move with the click of a button. And if needed, reverted to prior version with similar ease.

I forgot to ask about this idea at the UX lab during Inspire, but would be very happy to hear if it's already in the pipeline!

Thank you for your consideration!

We have at the moment our server configured to work with SAML credentials. Whenever a user sets the credentials option to be "User must specify own credentials" the validation is performed using the servers own local user, giving out an error whenever some workflows with SSO data access are uploaded.

It would be great if a window would pop up or credentials could be configured for the validation to aviod seeing the error to show up.

The idea here is that it would be very beneficial to allow general users to publish .YXZP packages to their server gallery (and/or the pubic gallery!!!).  Currently, this can only be accomplished by a server administrator through the 'Admin' page on the server.  It is also a completely different process than that of publishing Apps, Workflows, Macros etc., which can be done easily from the desktop designer.

For instance,  I have developed an Adobe Analytics - Connector Toolkit, which is a .yxzp package, and is located HERE (check it out!).  However, I do not have the ability to upload it to gallery.alteryx.com because I am obviously not an admin on the public gallery.

The neat thing about publishing packages to the server is that they appear just like Applications in the gallery.  Descriptions can be added and you can even disable the default 'Run' button and provide a 'Download' or 'Save' button instead.

Hopefully, this is a feature that may be available in a future server release!

Regards.

Taylor Cox

P.S. - the Adobe Analytics - Connector Toolkit is also attached below.

Enhancement request that there is an ability to limit collection naming rights to the collection owner and/or collection admins. Currently anyone with access to a collection can rename it.

Enhancement for the ability to trap errors at the tool level, take actions, and direct workflows based on error messages. If a tool presents an error, check for additional handling instruction in the configuration panel.

Sometimes when using someone else's Gallery App which has a long list of options to select from, I will hit Run before realizing that I haven't set all of the options.  Then, the App fails (obviously).

Rather than just getting a message that my app run failed on the Gallery, it would be nice to have a link then that automatically re-loads the previous options I had set so I would be able to see which option I didn't fill out properly.

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.

As we have more and more users onboarded to the Server, and many users share similar names, it is getting more and more complicated to manage. 

It will be great if we have a management console that allows us to create User Groups, Tags, set User Departments, and more controls alongside their curator, designer, etc status on Server.

Groups like User Groups gives a group of people access into certain workflows, districts, collections, etc. It will also be helpful as it can also be an audit trail of who ran what - with a feature that allows users or groups of users to run certain tasks or schedules. 

Hi,

As part of enterprise alteryx server deployments, would it be possible to remove alteryx server controller tokens and use asymmetric certificates (X509) instead?

Adrian

When a user publishes and schedules a workflow on the gallery, they have the option to specify their time zone to ensure that the execution of the workflow occurs at the appropriate time. However, if the workflow invokes the DateTimeNow() function, the captured time is in UTC. If it is important for the end-user to have that time that is captured be in their local time zone, they will need to manually (either within the workflow or as a user input for an Analytic App) specify the offset from UTC.

Instead, there should be an Engine variable that captures the offset (or the time zone) that the workflow was executed from (or scheduled in), which can dynamically adjust the DateTimeNow() output appropriately.

Wondering if there are any plans to change the RC4 encryption on alteryx server to something stronger (eg: AES, Blowfish etc)

Would be curious to see if anyone else in financial services has this challenge from a security perspective.

Adrian

The current Gallery API executes a job until it reaches a completion state with either success or failure.  Once reaching that state, the callout to /v1/jobs/{jobId}/ will return an array of messages that can then be parsed to gather information about the execution of the job, similar to the output you see in designer or via the CLI when running a job directly.

It would be nice if the callout to the jobs endpoint would constantly update and return the messages array with each callout.  With jobs that take longer to execute, our Gallery API wrapper could then report back to us and let us know what messages have come out as the jobs runs.  For example, if a process takes 2 hours to execute, we might want to know how far along the job is or if it has met a special condition that will cause it to run longer, etc.  To do that, we could add in message tools that report info messages to us.  Unfortunately, these messages are ineffective if we are running via the API because we won't see them until the job has fully completed.

Many organizations have IT applications (Splunk, OSIsoft PI, etc.) that can consume, historize, and monitor Windows Performance Monitor items.  If would be great if Alteryx wrote application-specific information to PerfMon.  Things like: number of engines running, number of workflows in the queue, number of people logged into gallery, time it takes for data to pass between DB/Controller/Gallery, etc. This would go a long way in helping admins to properly size systems and monitor them for upsets.

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

If you run an Alteryx app on your desktop or hard drive, a help button will appear in the bottom right. This button defaults to sending you to help.Alteryx.com, but you can adjust it to send you to any location by adjusting the app in the interface designer. This means that you could use the help button to send users to a location detailing how to actually use the app built. The issue comes that when you upload an Alteryx app to the Alteryx Gallery, the "help" button disappears. I propose that the help button be made available in the Alteryx gallery for apps so that designers can use it to direct users to locations detailing how to use the apps.

As per design Alteryx Server retains all FAILED jobs in the Queue and Results collections even when we set the server to keep run history and results for x days

Purging records from Designer involves manual activity

Proposing the idea of purging these error records through automation script:

Step 1: Stop Alteryx Server

Step 2: Backup Mongo DB

Step 3: Replace big size files: AS_ResultsFiles.Files.bson, AS_Results.bson, AS_ResultsFiles.bson, AS_Queue.bson with Empty .bson files of same name in the backup/AlteryxService

Step 4: restore MongoDB from the backup (with the replaced files

Step 5: restart Alteryx service.

When a user adds a canvas to the gallery - we need to be able to ask for a set of mandatory attributes on every canvas which are tied to meta-data.

So - in our world, these would be:

- Which business line does this belong to (pick from a list)

- What business process does this belong to (multi-select from a tree)

- Which part of the organization does this belong to (multi-select from an org tree).

- Who is the canvas owner as a developer; and as a Line-of-business owner (there are two different versions of the word "Owner" to us)

Every canvas that's booked into the gallery needs to have these fields added to the canvas so that we can inform the right person if a canvas fails, understand which part of our business is impacted, look at velocity & density analytics; etc.

This then requires a few pieces to be set up on the server up-front:

- Define your meta-data elements (tree; drop-down list; etc).   Admin will need to set this up in the beginning

- Define which meta-data elements are mandatory; and which are optional for every canvas.

- When these meta-data structures change - there needs to be a process that forces the owners to update them again.   For example if we change our org structure, that will invalidate some of the meta-data tagging on assets.

- If a user leaves the firm, owner information needs to be forced to be updated

Happy to talk this one through - for any large corporate env, tagging assets like this is super-critical, and this would need to be flexible because every org has a different set of tagging needs.

cc: @Deeksha @avinashbonu @revathi