Alteryx Server Ideas

*This is an idea from @cneivam from the Portuguese Community*

• Can’t use CReW macros in Server

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.

I've created a few apps for our company's private gallery for users. These take a couple of minutes to process. Also, some of them have very long lists to choose from. If the user doesn't make all of the selections because they don't realize there are more questions at the bottom, the app fails--but, only after running through the long process time. It would be nice to have:

1) a pop up message that lets them know they haven't answered all the questions ("STOP! You've a few more questions at the bottom to answer before this app can run.")

2) a customizable pop up message once the app is ready to run. These users don't actually use Alteryx, and aren't necessarily tech savvy or patient. Something along the lines of "OK. Now, stand up, stretch, grab a cup of something warm and come back in a minute or two while your app is processing." would be very nice.

The idea is that we could grab a workflow that had been placed in the scheduler db and then if the workflow is lost as a file then it could be reclaimed from the scheduler db

When scheduling in Gallery and creating a recurring daily schedule, if you a start time of 7AM @ any time after 7am you also have to click the date on a day, for the schedule start date, else the you will receive an error message.  Please click the date on automatically, after all if the time is after 7am you can't schedule a job to run at 7am today. 

The workflow execution log file is locked while execution is in progress. Can we look at making the log file available in read only mode while execution is in progress. This will to triage any performance issues on run time and track the progress on run time, rather than waiting for completion of entire process.

regression

Judging by the Community, it seems like the Alteryx business model is to crowdsource documentation. Do the same for a QA checklist. The 2019.4 release of Server shipped with some major regressions, notably:

DE21143 Workflow events no sending Email

DE22751 32-bit OCI connections not working in 2019.4 release

The QA team should publish the QA checklist and allow feedback from the community. The entire point of the community is to make the users and the product better. Let the users see which scenarios are tested and add ideas here for the QA team to utilize.

I have a chained app that is running on the gallery/server. When I run it, I see status changing from Processing to Running, but the window doesn't show a meaningful message as to which app is running. Is it possible to show that in the Browser window which reflects what stage is currently running in the Chained App? 

See snapshot of window below.

This would be super useful to monitor the progress of the chained app currently executing on the server. 

Please provide support for sharing a (gallery/Stored) Workflow Credential with a Group.  

Current capability appears only to support Users/Studios.