Alteryx Server Ideas

Hi Alteryx experts!

There were some ideas similar to this one but none like it and really really old ones, so I`m revamping the idea due to recent struggles and the many questions we got on the server discussion board!

Workflow events are nice and helpful but they require the user to add it to every single workflow.

The Gallery admin also struggles to know when a schedule fails. 

There was the Server Usage Report before, but now most server admins have no idea when a schedule fails.

There are many ways of managing schedules and failed jobs (MongoDB, logs, events), but it would be nice to add a simple option to notify a user on each schedule. It would be even better if we added another option to enable this option in all schedules globally!

This idea could be combined with this one from @fjablo 

https://community.alteryx.com/t5/Alteryx-Server-Ideas/Notification-from-the-Alteryx-Server-when-a-sc...

Let me know what you all think!

Best,

Fernando Vizcaino

Data Connections and Workflow Credentials are key part of migration process for workflows to Gallery.

They are provisioned for each user upon request.

When a developer leaves the organization, there is no easy way to identify all the Data Connections and Workflow Credentials assigned to that user.

Current options in the Gallery is for the Admin to browse through each Data Connection and Workflow Credential, navigate the Users tab and identify the list users. 

For a large organization with many Data Connections and Workflow Credentials it will hard to manage this since.

1. If the workflows change ownership, the new owner has to be given access to the Data Connections and Workflow Credentials.

2. Remove user access to the Data Connections and Workflow Credentials.

A Gallery page in Admin should include all Assets a user owns/has access to which includes the following. By selecting a user, the list should populate.

1. Workflows
2. Schedules
3. Collections
4. Data Connections
5. Workflow Credentials

We have implemented a solution to capture this information by getting the details from MongoDB. Also an automated process where the list goes to the manager when a developer leaves the organization so that he can manage the assets by identifying a new owner for the assets.

In the new version, we have an easy way to change ownership of a workflow in Gallery. In the same manner other Assets also should be taken care.

The current Enterprise Utility Workflow does not have a match/look-up in place between the two environments for user ID's.  Thus, the migration workflow doesn't work without adding in a couple extra API calls.  When we upgrade to a new version of the utility, I have to add this back in. 

It would be nice if the workflow would come with this already configured.

Add entered parameter into the result panel. It helps to debug process and audit.
sometime users save file in different way, and it not directly related to the interactive question
(e.g. Question: "SAP FBL5N Data" Input: "EXPORT (2).XLSX")
when error happen, I need the source file and the parameter.
if this idea is implemented, i just need the screenshot, which faster, without user to re-run the workflow to screenshot and share the parameter setup.

Hello,

Could you make it possible for curators to administer DCM connections created by other users?

Currently if one of the curators creates a connection, then only that person can modify it and give other people access to it.

Therefore if the person who created the connection isn't available then nobody can be given access to the connection.

Any curator can manage legacy gallery connections so to be able to move away from legacy connections and use DCM connections instead we need the same administration capabilities for DCM connections.

Thanks.

There are some products in the Market whic allows to install multiple services as Windows service on a single server. 

In large organizations it is found that when we are running ALteryx Server in multi node setup at that time 1 worker server has only one Alteryx service installed and runs as single windows service. If we have configured FID with log on as a service FID in that case if one FID reached to its shared path mapping capacity 1018k then it stops authentication and windows service is not able to start.

If we have multiple services installed on the same server then we can configure like :

AlteryxService.exe : FID1

AlteryxService2.exe : FID2

AlteryxService3.exe : FID3

In this case we can utilize the server compute and enhance the multi tenancy instead of adding more additional server.

The V3 jobs API endpoint woefully lacks any usefulness. The current endpoint only has a get jobs/{jobid} method that is not useful because a database admin must query the database to get a list of all job IDs. To add insult to injury, this method is only limited to the user whose job is running or queued.

These are new features that I am proposing

1. GET jobs/list—This method must be callable by all users. Parameters such as none (default—full list), running, or queued will display jobs with the appropriate status. The job ID of the running or queued job and the worker it is running on must be included in the resultset.

2. GET jobs/{ownerid} — This method must be callable by all users. Like the GET jobs/list above, the resultset must include the job ID of the running or queued job and the worker it is running on.

3. DELETE jobs/{jobid} — This method must be callable by the person who scheduled the job, the owner of the workflow, or the curator. This method is the equivalent of cancelling a job on the Server Admin page - #!/admin/jobs by a curator. All three mentioned people have a vested interest in the running or queued jobs on the server and must be able to cancel those jobs.

4. POST jobs/reassign/{jobid}/{new_job_tag} — This method is restricted to the curator and applies to any job in a queued state. It allows a curator to reassign a job to another job tag or the first available worker for reasons determined by the curator.

This is an enhancement that I am proposing
1. GET jobs/{jobid} — This method must be callable by all users. This will allow any user to get the details of any running or queued job.

Logging requirements

All DELETE or POST methods must be logged and purged based on the Persistence Option > Delete queue and results after (days).

I would like the ability to "favorite" Public flows that are on the server and then have a separate "Favorites" section.  As the volume of Public flows on the server increases, It would allow for users to be able to navigate to frequently used flows much faster.

The gallery needs to implement basic auditing in the data connections.Currently, there is no way to determine who or when a data connection was created or updated.

The dataConnections Collection contains data connections with these keys

When there is an app that has multiple tabs across the top but can extend down below the page, the user will scroll down to complete the boxes and click the 'Next' button at the bottom. 

This takes the user to the next tab but remains at the bottom of the page.

It would be very useful for this 'Next' button to jump back to the top of the page.

You cannot currently upload a new workflow and specify your own workflow_id GUID.  This would be useful for systematic workflows that need to be referenced in code.  Currently, you either to search for a workflow by name, but you are not guaranteed it a workflow instance you uploaded.  This would be helpful for server and workflow administration.

Given there are multiple api versions.  I need a way to call the api and get the server version so I can make the correct API call or construct code logic which provides the user code requirement based on the versions features or limitations.

I propose a api call ../getserverinfo/ that returns server metadata like version, default worker thread count, and default memory allocation.

There is currently not a way to call the API and find out the calling user.  For instance, if I have a user API key and secret, I  to return the rest of the user info for the calling user or who is calling the api.  I propose a api call like ../user/whoami

Commas save lives! With large numbers, it's difficult to see what number was actually entered without commas present, and the wrong number can easily be entered as a result:

Is this number

• 100,000
• 1,000,000
• 10,000,000

It's hard to say without taking a really close look!

As the single user who upload workflow MYWorkspace ends up being very crowded.  I move them to collections to be able to share but on My workspace, I can not see which collection they are associated to. It would be nice if there was a column displayed that showed associated collections.   As well as being able to have some different types of category classification.  I would want something like a development stage: (In-progress, UAT level, deployed, retired) If they are retired a way to remove them off my general workspace area.

Hello all,

Right now, we can choose either MongoDb or Microsoft SQL Server as a backend. I would suggest to add Postgresql. Why ?

-it's open-source
-it's reliable
-it's free
-it works well on many environments
-it's popular
-it's already used as backend for Tableau or Qlik and many others
-it respects SQL norm and doesn't have a lot of specificity

Best regards,

Simon

After a job is run on Alteryx Server, Gallery lists Job Results with a Status column containing with one of 2 values:

• Error (represented by a red exclamation point icon); and
• Success (represented by a green checkmark icon).
  See attached screenshot for illustration.

If any WARNING messages are generated by the workflow, the operator/user is unaware unless they take the time to expand the message log details, then scroll through the long list of messages that typically appear in the log.

Because the Success Icon appears whether there are Warnings or not, the user must dutifully spend extra time scrolling through the list looking for Warnings even if there are none to be found.

My Idea: provide additional information under the Status column in one or more of these ways:

1. add a 3rd status option with a yellow/orange icon that indicates if/when 1 or more warnings are present
   • This should be a quick/easy enhancement that would provide immediate value
     
     
2. append one or more numbers after the Icon to indicate counts (see mock-up example)
   • There seems to be ample space for this type of info
   • This could be done at a later date as a subsequent enhancement

I think that the user would benefit from a filter where they could focus on errors, warnings, or other types of messages in the same spirit as the Designer interface, but I recognize that would be a lot of work and I am not asking for that now.

Workflows which are scheduled and continuously failing in a row 5 times need to stop/disable the schedule. Sent a mail to the workflow owner stopped schedule due to continuous error.

For Administrating the schedule workflows this feature helps a lot. Many users create workflows and dump into server and schedule it and forgot it if we implement this strategy, it will be helpful to both users and Admin team.

Currently the default 'Rows Per Page' is set to 10 when within various pages on the Gallery. 

As we add more and more Apps to our Gallery it would help to be able to increase the default so it is higher than 10.

This will help ensure users do not forget about or miss tools that are available to them which are hidden on other pages. Additionally, they will not need to remember what page to jump to if the App does not pull through to the first 10 rows, or prevent the need for them having to increase the number of 'Rows Per Page' themselves.