This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Now, find all your Server and Gallery questions and answers in one place! The new Gallery Admin Help Page has your Server Installation Guide, Configuration instructions, and the much-requested Administer Gallery management features - Subscriptions and Studios defined! Manage your user permissions! Edit user accounts! \n
This is Part 2 of the Alteryx Gallery Series - The Gallery Series only refers to the Alteryx Server where you can host your Private Alteryx Gallery. This Article with refer to 'Alteryx Gallery' as a privately hosted Gallery on the Alteryx Server.
Part 1 Alteryx Gallery Series - The Lay of the Land 101: Gallery Admin Edition
Part 3 Alteryx Gallery Series: App Publishing & Version Control 101 - Alteryx Community
Part 4 Alteryx Gallery Series: How to make the most of your Alteryx Gallery – Use Cases
Each section of the user interface is outlined and described below:
Often utilizing and navigating the Private Alteryx Gallery for the first time (or even for veterans) can be difficult. This article aims to make this process simpler by giving a step-by-step guide on where to find the main areas of the Alteryx Gallery, as well as those hidden features.
Finding the Alteryx Gallery
The URL is typically the ServerMachineName(or IP)/Gallery unless another domain has been defined.
**** Speak to your IT or Alteryx Server Contact to find URL address.
If it is an internal server, the user will need to be logged into your organization’s VPN before accessing the Gallery.
Accessing the Gallery
User visits the Gallery on their own:
Depending on your pre-defined user authentication setting, the user may be granted access to the Gallery the first time he or she visits the URL.
If your Gallery utilizes Windows Authentication, a Gallery Account is automatically created when a new user visits the site.
If your Gallery utilizes Built-In Authentication, the new user may create their own Account profile by “Joining” the Gallery from the Gallery home page.
Gallery Admin invites user to the Gallery:
The Gallery Administrator may invite users to join the Gallery. This allows the Administrator to set up all of the users specific privileges before that user views the site.
If your Gallery utilizes Windows Authentication, the admin would enable “No Access”. You will receive no notification from Gallery once you have registered.
If your Gallery utilizes Built-In Authentication, the admin would disable the “Sign-Up Form” (Link to gallery admin page). The user will receive an invitation email and be asked to validate their account.
Lay of the Land: Everyday Gallery User
“HOME is where the heart is”
When you create a workflow, macro or app in the Alteryx Designer and upload in to the Alteryx Gallery you can CHOOSE to share your workflow to the Public Gallery (Home). You will need to be a Data Artisan to publish to the Alteryx Gallery (Link Permissions page).
Users with access to your Gallery URL may access the Public Gallery section. External users cannot view and run workflows in the Public Gallery unless they have been invited by an Admin and have network rights to access the Gallery website.
Users often upload proof of concepts or demo applications to the Alteryx Gallery which other users can use for reference.
Public Gallery section that have been tagged (after publishing) with a specific keyword set by the Gallery Administrator.
“The last of the thirteen DISTRICTS of Panem”
Districts are Alteryx workflows shared in the Public Gallery section that have been tagged (after publishing) with a specific keyword set by the Gallery Administrator.
Districts are used for housing macros which are used within different internal departments.
“Welcome to my Private Studio”
A user will ONLY receive their own Private Studio if their user permission level (set by the Alteryx Gallery Admin at sign up or before) are designated an Data Artisan User. This will allow them to publish Alteryx workflows from their Desktop Designer.
By default, a Data Artisan will only see the workflows they have published themselves in the Private Studio section. To see content created by other Data Artisans, a workflow may be shared in the Public Gallery or via a Collection or Studio.
"Brand new Insights"
New feature added in the Alteryx Server 2018.2 allowing you publish interactive charting directly into a web browser
This dashboarding features offers users the ability to filter and drill down into Analytical Insights
“You’re the chosen one, welcome to my Collection”
Collections are a means for ensuring only specific users may access workflows to which they are assigned.
Collections are managed by users NOT by the Gallery Administrator.
Collections are tied to one Private Studio only.
A user must have their own (paid) Private Studio OR be a member of another Private Studio in order to run workflows shared via a Collection.
Data Artisans can invite Users to a collection through the users tab inside of the collection. These Users will have to sign up to the Alteryx Gallery or be users in the same domain as the Alteryx Gallery is hosted on.
You can have Multiple Admins for collections
“Let’s see these Workflow Results”
Gallery Users may view the results/output of their own previous workflow executions.
You can never see the results of other user’s executions via the Gallery.
'Let's automate that for you' - Scheduler
In Alteryx 11.0 the gallery Admin can allow users to schedule directly from the Alteryx Gallery.
You can click on the scheduler tab and schedule your workflow by choosing the workflow and frequency you wish to run the schedule on.
You then get visibility to your schedules only, and have the ability to edit the schedule and remove the schedule from being run.
Assets are an important part of your workflows in Alteryx. Assets will need to be included if you want to share, schedule, and publish your workflows to your Gallery. We run into many cases where users are able to run workflows on their Designer but they fail on Scheduler and Gallery. In a lot of cases it is due to the pieces of the workflow are not all there in the Scheduler and Server database. In this article, we will talk about when you need assets, how to package the assets, and what assets you want to make sure are a part of your workflow.
When You Need Assets:
When building and using workflows in the Alteryx Designer you don’t need to do anything with your assets as they are a part of your workflow locally, but if you want to move the workflow somewhere or to someone, you will need to package the workflow.
When sharing your workflow with another user, the workflow will need to be packaged with those assets so that the user can run the workflow without error. This would include input files as well as macros. If the workflow is connected to a database or using Alteryx Data, the user will not be able to run the workflow successfully unless they have access to those data sources on their own machine.
If you have Server or Desktop Automation, the Scheduler will be using a database separate from your Designer. If you have Server you will be using a MongoDB and if you have automation you will be using a SQLite database. This would mean that any macros that are not on the server or SQLite database would need to be added. By packaging the workflow and scheduling the package, the Scheduler will be able to access any custom macros or macros not included with Alteryx. This would include Predictive as well unless you have installed the predictive tools to your Server. If you have version 11.0 Server or later, you can send your workflows to your private gallery and schedule them on your server. When you do that, Alteryx will package the workflow the same as if you were sending an app or workflow to the Gallery as below.
The Gallery works a little different than packaging a workflow or Scheduled workflow. The difference is that the Assets will need to be on the Alteryx Server along with the workflow for the app, macro, or workflow to be used on the Gallery. Basically, the Save As option to the Gallery of your choice will start the packaging process of your workflow and Assets. The Save As a workflow window will appear with information about your workflow that you are sending to the Server Gallery. Select Workflow Option. Below the Workflow Options you will select Manage workflow Assets. This is where you can include and exclude information being sent to the Gallery.
Packaging the Assets:
Select in the tool bar Options ->Export Workflow. This will then launch a window that will show the name of your workflow, the location where the package will be stored, and the list of workflow assets.
When sending your workflow to the Gallery, you will do a Save As to and the Company’s Gallery. A window will open and you will see Workflow Options at the bottom of the page.
Select Workflow Options
You will then reach the Assets window which is similar to the packaged Assets window above.
You also have a second option when sending workflow to the gallery. In the Workflow Configuration window, select the Events tab, Select Add, Run Command. You will see a tab called Assets where you can add assets to the workflow. This is especially helpful when you are adding a chained app to the gallery. Check out Jordan’s article for the step by step: Adding-Files-to-the-Gallery.
What Assets Do I Need:
Great! I found the assets, but why are some missing, some checked, some not checked and which ones do I really need and what don’t I need?
You may see that you have Input and Output assets. When you are packaging a workflow to send to a user, you can include those assets if the user does not have those files to run the workflow. If the user does have the files or they are going to update the Input files or Output files, then you would not include them. The Input and Output assets will never include database connections only files.
The .yxmc files can be an important part of your workflow. Many of the Alteryx tools are .yxmc files and if these macros are a part of the Designer package, you won’t need to include them in the package as Alteryx knows that these tools will be in the workflow (example Report Header Tool is a macro). If macros are downloaded from the Alteryx Gallery, custom created, or sent from another user, these macros will need to be included as Assets.