We are celebrating the 10-year anniversary of the Alteryx Community! Learn more and join in on the fun here.
Start Free Trial

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

0 Likes

I have inherited admin duties, and have been running to many problems. Some of which will escalate when the subscriptions go away. 

The pages desperately need to be updated for a more streamlined admin experience.

Couple examples I came up with below. 

 

Naming Convention

  • Allow workflow renaming without the replace function.
  • Force a unique plan name across all private studios. instead of being unique on just ID.

API Access

  • Allow any user who can access the module from Collections to be able to trigger it from the API using their own API key.
  • Store results of "API" triggered workflows on the page.
  • Groups:
  • Identify Users without a group
  • Identify users in more than one group
  • Add multiple users at one time (Muticheck box) with filters.

User Page

  • Add/remove Users to Groups
  • View, add, and remove Collections from Their User Page

Collection Page

  • Add Collection from the Admin collection Page

Designer "save" window.

  • Give the ability on Save As & Save for the user to automatically share the plan with their collection(s).
  • Default all "Workflow" assets to be unchecked by default, rather than relying on users to click "workflow options"," manage workflow assets", and then uncheck everything.

Workflow Page

  • Change Owner (Can be limited to admin only)
  • Add directly to collection from this page.
  • Do not reset the "private data exemption" to default every time an updated version is updated.
  • Allow admin users to see logs of all users who run the plan (Also add this to the admin page while you are at it)

 

0 Likes

When I publish a workflow, I want it to have different behaviour based on the collection from which it was executed or scheduled. Let us suppose that I create a DEV collection and a PROD collection. The workflow is shared in both. If the workflow is executed from DEV, then I will have some logic to do X (output to specific folders, etc). If from PROD, the logic will do Y. The logic will be up to me. If the collection information is captured in the MongoDB layer, then I can pull it out on the fly by joining the collections, appInfos, and AS_Queue or AS_schedules collections. Querying the DB on the fly during execution and pulling that value is trivial. Once I have it, I can use it for any sort of logic as an environment sensing variable. Can you please store the info in MongoDB?

Top Liked Authors