Alteryx Server Ideas

Open Custom Group management internal API's for Curators (or those with Admin Secret/Keys)

• GET .../gallery/api/usergroups/   --> Get all Groups
• POST .../gallery/api/usergroups/   --> Add new custom group
• POST .../gallery/api/usergroups/<GroupID>/members/    --> Add a group member
• Get .../gallery/api//usergroups/<GroupID>/ --> Get Group Details

If your server is on SAML, you can't leverage any AD group for granting access to resources. The new custom group feature is a help, but still requires you to manually add groups and member users, so it doesn't scale for large organizations (too much management overhead).

Having the internal APIs exposed would allow me to do my own group sync tool, synching members between Custom and AD groups of the same name. 

As a server Admin, I'd like to be able to do via APIs all that I can do via the Server Admin UI. This other idea was recently accepted for opening the collections APIs for Admin, it would be great if both Collections and Groups management were opened on the same upcoming release.

Currently, to allow a user to schedule jobs, prioritize jobs, assign jobs, create collections, or have API access, toggles must be set at the user level.  

As a server administrator, I want to configure these toggles at the group level, so that a) I don't have to modify a large number of users individually to grant them such permissions, b) I ensure consistency across groups of users that doesn't rely on humans clicking all the right things for each of the relevant people, and c) I can easily change these settings for multiple people, if needed.

It would be a very pleasing user experience if we could enjoy the Server usage with a true dark mode. The customization in the Theme-Panel isn't advanced enough to do it ourselves - unless we deep dive into the css-files. The CSS already has a good structure and the dark mode could be enable with just a few changes. 

Here is a comparison of my server in light and dark mode.

It's probably noticeable that I haven't studied Design, but it should give a rough suggestion how it could look.

Obviously not everyone wants a dark mode, therefore every user should have toggle in the user settings to switch between light and dark mode.

We have several workflows that call other workflows (i.e. via the Conditional Runner macro) but are running into some versioning challenges since we moved to storing all of our workflows in our gallery.  When I publish a workflow that references another workflow, I can bundle it up with the workflow when I save it, but then Alteryx places that workflow into the /externals directory, which is obvioulsy not the same as the workflow that we've saved to our gallery.  An example:

I have two workflows in our gallery...one that generates a TDE and one that calls that one if certain file availability and time conditions are met.  The "master" version of each is in the gallery, which is what we want...

...but when I load or save the Sales Analytics workflow in Designer, I have to bundle the TDE workflow with the main workflow in order for it to run from Gallery.  But now I've created a disconnected version of the TDE workflow and if I forget to update it when I update the version in the Gallery, I'll be running the wrong version.  I know I could store these workflows in a network directory, but that seems to defeat the purpose of the Gallery.

If I'm not missing something insanely obvious, I think this would be a very important feature enhancement, namely the ability to pull in a Gallery workflow into another workflow.

When I create a DCM Entry in Gallery, it would be great if the users I share it with would also be able to reference the credentials in their desktop designer when they sync their connections to the Gallery. 

Hello

Imagine the dream : Alteryx Designer Cloud with in database tools.

Well, that would be so great I won't write more....

Best regards,

Simon

Today, when you trigger a job using the Server API, it is considered as a manual run type. In fact there are only 2 type of jobs : "Scheduled" and "Alteryx_Run"

I think "Alteryx_Run" should be segregated into "API_Run" and "Manual_Run". This way in future version we could treat those type of job differently. 

We could also have more stats around the type of jobs.

Currently, Alteryx Server lacks rich job scheduling functionality to other products like Control-M and Informatica's Scheduler

Feature Requests:

1) Ability to configure job retries on failure without having to rerun the workflow based on a  event trigger: https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/How-to-run-a-workflow-from-an-event...

There are common occurrences where a workflow may fail to connect to Input sources and a retry would normally resolve the issue. 

2) More user friendly way to setup dependencies between scheduled workflows.  For example, if workflow A fails it triggers workflow B to run.  If workflow B runs without errors, it triggers workflow C to run.  Currently, we would need to configure this based upon events.  A complex chain of scheduled workflows becomes difficult to manage and scale.

In the interest of information and system security, would it be possible to provide a means to remove social media and email sharing options (Facebook, Twitter, etc.) from the SHARING drop down menus, such as through a configurable setting in the RuntimeSettings.xml file?

Currently there is no means (confirmed by Alteryx tech support) to remove these options from the sharing menu.  Sharing within the system can be controlled somewhat by controlling access to the system or specific output locations.Once the info leaves the system, there is no longer any means of control.

Providing a configurable option will allow locations to tailor to their specific needs.

If two users sit in the same studio and have multiple scheduled workflows in that studio, both users can see the results of those schedules under "Workflow Results" -> "My Jobs"/"Jobs Shared with Me" 

It gives both users in the studio good visibility of all the workflow results they have access to.

Now if we move to a 1 studio-1 user environment and share workflows and schedules via collections, this "Workflow Results" -> "Jobs Shared with Me" functionality is empty. Instead users have to go to each schedule individually to see the results from them there. 

So if you're in a 1 studio-many users environment, there is a single place to go to see all workflow results. But if you're in a 1 studio-1 user environment and sharing via collections, you have to go to infinitely many places to see the results of all the schedules shared with you.

So my idea is to have results from schedules shared via collections appear in Workflow Results.

Hi all, Per this thread, it would be helpful if we could have finer control of scheduled jobs in Alteryx Server: https://community.alteryx.com/t5/Publishing-Gallery/Resource-control-on-scheduled-jobs/m-p/61016/hig...

Specifically:

- Dependancies (one job should run after another in a chain)

- lower priority (some jobs should go down the priority queue to allow for others so that high priority jobs are not blocked by other less important ones)

Thank you Sean

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

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.

I have been trying to scan all of the workflows that are stored in the gallery and wrote this community post about it. Some Alteryx employees reached out to me directly to see if they could help solve my problem. We ended up with a somewhat wonky roundabout solution (that I haven't implemented yet) by downloading yxzp files through the Gallery API, unzipping them, then scanning the workflows as xml. I think the process could be greatly simplified if Alteryx had a set of Introspective tools.

The introspective tools would use similar, if not the same, processes that Alteryx already has in place to pull data from the gallery/server itself. The set of tools would be most useful for Server admins or people that are trying to build meta-workflows for Alteryx to make things easier for their users. Similar to the solution to my problem above, most of this functionality can be worked around by querying the Mongo and/or scanning engine logs. The Introspective tools would simplify this process greatly, especially when it comes to joining records from the Mongo and collecting workflow-internal data.

Since the tools will have direct access to the gallery/server it would make sense that they would only be available to machines with server licensing or could be made available if the user has a high enough permission level in the gallery they are trying to obtain data from.

One of the issues that we have with Alteryx jobs in prod (and also Tableau, coincidentally) is that often a canvas is built to serve a need at the time, but after a while it's no-longer needed but it continues to run and consume server resources.

Can we add the option to our server environment to request recertification that a particular job is still needed every X months.

This will achieve 2 useful purposes:

- if the job is no-longer needed then the user hits "No thank you" and it's then taken off the scheduler which reduces server loads

- Alternatively - the user may realize that this should have been handed over to a new team or owner, and they can then make this change based on the recertification prompt.

I'm pretty certain that this would help to manage the inevitable build-up that happens on server environments where jobs build up until the server starts thrashing and the admin team then need to go out to all the users to do this recert process manually.

CC:  @rijuthav; @jithinmony; @HengHe; @RajK; @ydmuley; @revathi; @Deeksha; @MPistone; @Ari_Fuller; @Arianna_Fuller; @JoshKushner; @samN; @avinashbonu; @Sunder_Sriram; @Rahul_Thakur; @Rahul_Singh

In an enterprise multi-node Alteryx Server deployment that has existed for many years and many upgrades, there are artifacts within the MongoDB that are unknown to Gallery Administrators. I envision a workflow or app that is developed by Alteryx that queries the MongoDB and looks for orphaned documents in the MongoDB across all collections. With 2022.3 there is a pre-upgrade check, however, it does not find all unexpected items within the MongoDB. Regular ongoing MongoDB health helps with overall management of the environment and could prompt for support cases before it becomes a problem during pre-upgrade activities.

Hello Alteryx Server Admins,

It would be fantastic to manage users' permissions with user groups. This would help manage all users with permission to create collections and schedules from a centralized page.

Something like this:

Best,

Fernando Vizcaino

Currently, in order to run an app via the API, you have to have uploaded the app to your private studio. Frankly, I don't find this function useful because you have to download then re-upload an app in order to gain access to the API. The API would be more useful if when an app is shared with you (or a collection is shared with you), then it would also allow for that app to be run via API by the user it was shared with. Right now, the only person who can run the app via API is the user who originally uploaded said app.