community
cancel
Showing results for 
Search instead for 
Did you mean: 

alteryx server Ideas

Share your Server product ideas - we're listening!

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the star in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

I work at a large organization where Security and Privacy are of utmost importance. The ideology that we need to follow is Least Privilege and Need to Know.

 

We (Curators) do not want all the Artisans to publish workflows to Home Page, either knowingly or unknowingly. We however do want to allow a few power users to publish their work in Home Page, but currently the Gallery does not provide the ability to pick and choose who can share workflows publicly. We are educating users to not share any contents publicly, but as we scale up, it will be difficult to manage and govern this.

 

I'm suggesting to implement a global Yes/No feature that will Enable/Disable Artisans to publish contents in Home Page (just like the way we have for Jobs/Scheduling feature). Further, in Users section, Edit User setting needs to have a Yes/No button that will allow Curators to let certain Artisans place workflows in My Company's Gallery.

 

Organizations that never want any workflow to be shared publicly can disable this feature using global Yes/No button. Organizations (like the one I work at) that want to enable this only for certain Artisans, can set the Global Yes/No to No, and then in Users tab, they can pick and choose the Users that need this functionality (which will override the global default). Finally Organizations that do not really care about this functionality can just set the global setting to Yes.

 

Hoping other organizations find value in this functionality as well. Thanks.

With Version 2018.3, you removed the Autodetect SMTP button, and with it, have rendered the Email Tool virtually useless for many people, which is a shame because it is a critical tool for some of us to share reports produced in Alteryx.

 

In requiring an SMTP path, there are a host of authentication issues that need to be addressed, and we can't seem to figure out how to configure the path and From emails properly to allow the tool to work without errors. 

 

My only solution at this point is to rollback to 2018.2 so I can continue to use the Email tool. 

 

Please address this so we can use the tool as before, or provide the necessary configuration options to allow for proper authentication with popular email services (Gmail, etc.)

 

We currently have the ability to store connections on the server which protects the credentials - however this capability does not exist for APIs for Sharepoint sites etc.

 

Please could you extend this to cover authentication for ALL connectors?

 

Many thanks

Sean

 

cc: @revathi

For a given DB connection - there's a need to be able to specify the owner for this specific connection.

Reason for this is that the credentials for a given DB are not all managed by the central admin team - so we'd want to say that a given DB connection is owned by a particular person so that this can be updated frequently as passwords change.

 

For resilience - our particular policy would be to have 2 owners so that if one person resigns or changes roles, it invalidates the primary and reverts to the secondary - and then asks the new Primary to create a backup owner.

In order for us to manage the large number of canvasses on our server - we need to add the ability for Admin teams to require additional attributes on every canvas:

For us, these mandatory attributes would be:

- Which team do you belong to (dropdown)

- What business process does this serve (dropdown - multiselect)

- Primary & secondary canvas owner (validated kerberos)

 

For the ones that have dropdown lists - we can provide the master data into a drop location or into a manually configured list on the server.

0 Stars

Insights should work like Apps. We should be able to publish insights then grant permission to other people/studios to access the visualizations. I have many clients / users that can benefit from having access to the Insights i'm gathering from Alteryx. 

Top Starred Authors