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

alteryx server Knowledge Base

Definitive answers from Server experts.
This is   Part 1   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 2 Alteryx Gallery Series - The Lay of the Land 101: User 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   The Lay of the Land 101: Gallery Admin Edition   The Gallery Admin is the Godfather of a Alteryx Gallery. The Admin is less involved with the workflow content of the site and more involved with management of users and their overall experience on the Gallery. This article will help the Gallery Admin navigate the Admin settings within the Private Alteryx Gallery.    Each section of the Admin interface is outlined and described below:   Subscriptions A   Subscription is another name for a Studio. A Studio allows Alteryx Designer users to publish and share workflows privately within their organization.  Each user that creates a Gallery account is automatically given their own subscription which can become a Private Studio if the   user permission level is designated an Artisan. As a Gallery Admin you will have to make this user an Artisan, take a look at the ‘users’ section below which details how to do this. Each Studio includes a limited number of artisans and members – assigned by the Gallery Admin. Once a subscription has been created, it can be deactivated but not deleted. Gallery Admins are the only ones with permissions to create subscriptions.    Subscription Management Permission levels     Creating and adding users to Private Studios To create a studio (subscription) click on ‘subscription tab’ and click on ‘Add New Subscription’. You will now have the ability to create a studio (subscription) Subscription Screen     This will be the subscription screen below:       Gallery Admin can create studios as well as manage the users and workflows assigned to them. There are numerous options when creating a Subscription or Studio: Private Studio Name: The name for the studio, which displays at the top of the page when the user clicks “Private Studio” on the left menu of the Gallery page. Contact Name: The person who owns and manages the studio. Subscription Type Free: Artisans and Members who are part of the studio can run workflows in the Public Gallery Paid: Artisans who are part of the studio can publish and run workflows in that studio and Members can run workflows Artist Seats: The number of Artisan seats available in the studio. Artisans can publish, run, and share workflows. Member Passes: The number of Member seats available in the studio. Members can run workflows in studios for which they have been assigned. Expiration Date: The date the Paid subscription expires. When a paid subscription expires it is downgraded to a Free subscription. API Enabled: Access to the Private Server Gallery API is enabled by default. The Gallery API supports the ability to authenticate, list apps, run apps, and retrieve app results using an API Key and Secret which are accessible via Gallery Settings.  Users Disable user sign-ups: Limits who can sign up for your Gallery. Forces users to be “invited” to join the Gallery. Allow anyone to run public workflows without singing in: If this option is selected, anyone with access to your Gallery URL may run workflows that are available on the Home Page.  This is how to add a user to a studio (Subscription). You need to take the subscription key from the ‘subscription’ section (above screenshot) and add this into the studio key within the User profile below.     When a user now publishes from there Alteryx Designer to the Alteryx Gallery they will see the studio name they are associated with. This is linked by the same subscription and studio key. Users can only be part of one Studio at a time.    Gallery Users Gallery Admins can add users directly to the Gallery or they can send an email inviting user to log in and add themselves via the Join now form on the main page of the Gallery. User permissions are managed in the users profile (or in “Permissions” if using Windows Auth) as well as in their assigned studio. The new user is added to the Users page. The users name, email (for Built-In Auth), and name of their studio display in the user box as well as icons that represent their permissions. When using Built-In Authentication, the Gallery Admin can designate the permission level of users before they sign up to Alteryx Gallery on the users tab   Built-in Permissions Screen (Users permission level for the whole Alteryx Gallery)     Windows Auth Permissions screen (Users permission level for the whole Alteryx Gallery)   Gallery Admins can manage user permissions in the Permissions page when using Windows Authentication only. A default permission level (No Access, Viewer, Artisan, Curator) can be set for any new or existing user who joins the Gallery. Admin Tip:   Set the default permission to No Access or Viewer if Content Security is of chief concern. This will require users to be invited to run workflows on the Gallery Once a user has been created, it can be deactivated but not deleted.   Workflows Gallery Admins can add workflows, apps, and macros to the Gallery and manage their icon, description, Run Mode settings, and exemptions. Admins can also create “tags” and associate them to workflows so searches within the Gallery return better results.   Run Mode: Determines the level that workflows are permitted to run in the Gallery. Workflows that contain certain tools or access may need to be blocked. The default Run Mode is selected when the server is configured. Unrestricted: Any workflow can be run. Semi-Safe: Workflows using Run Command, Download, Email, “R”, or Events will be blocked. Safe: Workflows using above tools or accessing/storing data on non-local drives will be blocked. Requires Private Data: Indicates if the workflow requires licensed data to run. Private Data Exemption: An exemption can be given to a workflow with private data so that it can be run.   Districts Gallery Admins can create new districts and modify the district name, description, and icon image. Once the District has been created, it will be displayed below the “Home Page” menu option on the Gallery.   Data Connections   This tab within the Gallery Admin section is only available for Alteryx Server Version 11.0 and above This tab will give you the option to pre-define credentials that can be sent down to designer users This will help when managing access and Alias creation on both Designer & Server DSN-less connections will run straight away. DSN connections will need to be set up on the location machine and server machine   Workflow Credentials Set workflow credentials which can be use when running a workflow from the server. These will also appear in the designer when uploading/scheduling a workflow Click on 'change; and you get the following options Use Default Credentials This will use the server service account details to run workflows if nothing has been set in the 'Run As' section of the Server System Settings Require User Credentials When running the application from the Alteryx Gallery the users will have to enter in credentials    Allow users to set options for credentials option The best practice would be to ask users for their credentials so they can only access the data they have privileges for within your internal IT environment.  The interface will look like the screenshot below. When uploading an App from your Alteryx Designer (File>>Save as>>>My Company's Gallery) you can click on 'Workflow Options' & 'Set Workflow Credentials'.    This will give the user three options    'User is not required to specify credentials' - The application/workflow will run as the default Alteryx Server user account (Run As settings in system settings on server config).  'Always run this workflow with these credentials' - The user can enter the credentials at this point, however preset credentials can be added within the Alteryx Gallery Admin section ("Workflow Credentials")   Jobs This is where you can give users permission to schedule workflows they upload to the Alteryx Gallery. This will allow all artisans to schedule workflows.         Notifications The server can send email notifications for various events. The SMTP server information is entered when the server is configured. Gallery Admins can manage the types of notifications and the message text. Admin Tip: Disable notifications so your users don't get spammed by the Gallery.   Customize your Alteryx Gallery! Banner Ads can be added to be displayed below the search bar on the Home page. Uploaded Files can be added to the site to which Gallery Users can access via Links. You have the ability to change the Gallery Name, Logo and Color Scheme within the web Browser. This is often used to house FAQs, Help & Links Add link to your Page or URL in the Header or Footers.   If you have any outstanding questions please reach out to our Alteryx Support   Best,   Jordan Barker Solutions Consultant
View full article
Credentials are how we control who has access to what on a computer or a network. Credentials are a way to prevent people from touching data or folders or content they aren’t supposed to. This article goes over the different options for setting credentials on a private gallery. 
View full article
Alteryx Server provides a fully scalable architecture that allows an organization to scale Alteryx to automate data analytics, tackle bigger projects, process larger datasets and put self-service data analytics into the hands of more decision makers. From scaling Worker nodes to Gallery nodes to the MongoDB persistence layer, Alteryx Server allows organizations to efficiently manage their automated and self-service data analytics needs.
View full article
One common reason why the Alteryx Service appears stuck in the 'Stopping' state is when the service is trying to stop but the AlteryxEngineCmd.exe process is running. In other words, a workflow is running. The Alteryx Service cannot be stopped when a workflow is running due to a schedule or a Gallery run.
View full article
You will not be able to use this functionality on the Alteryx Server at this time. As of 10.6.8 and higher either the 'Allow Local Logon' or 'Logon as a Batch Job' permission is required for the Run As user and/or any Gallery Credentials.
View full article
How do I differentiate between workflows which are not uploaded to gallery and those that are present in the gallery?
View full article
If a quick/straight forward solution is not available, you may be asked to provide screenshots, files, and/or error logs that our Server/Gallery Support requires to help troubleshoot your issue.
View full article
If a quick/straight forward solution is not available, you may be asked to provide screenshots, files, and/or error logs that our Server/Gallery Support requires to help troubleshoot your issue.
View full article
If you are running into problems scheduling a workflow over VPN even though you can schedule without VPN – look no further!
View full article
As Alteryx analysts, we’re whipping up insight at blazing fast speeds. Workflow after workflow, tool after tool, we’re gleaming functional understanding from inert webs of data that empower us to make better decisions. Good insight is only as good as it is shareable, however, and to enable better sharing any Alteryx analyst can take advantage of their Workflow Dependencies to simplify input or output path dependencies in shared workflows.
View full article
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!   
View full article
One of the three database options when setting up the Alteryx Server is to connect into a User-Managed MongoDB instance.  Why would you want to set up your own implementation of MongoDB?  The main benefits are to take advantage of the features of MongoDB that are not included with our embedded instance.
View full article
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.   Alteryx Designer: 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.   Scheduler: 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.   Gallery: 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?   Input/Output Assets 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.   Macro .yxmc 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.
View full article
When you publish an application to the Alteryx Gallery it packages this workflow up into a yxzp and creates folders called 'Externals'. In these folders it might contain macros within your workflow or more commonly input and output file locations.    The Designer does this is to ensure your application has the read and write capabilities when published to the server. However, you may be confident that the server has access to a mapped drive or database. Therefore, you can do the following to keep your macros, input & output file paths absolute (C:\Users\etc.) rather than relative (.\etc):   1. Within the Alteryx Designer go to File>>Save As>>Gallery   2. Before Saving go to 'Workflow Options' >>> 'Manage workflow assets'   3. Make sure all macros, input and output files you want to keep absolute are unchecked    4. When you publish to the Alteryx Gallery now these macros, input and output file will keep the same path and not kept in external folders.    Consideration: When uploading to the Gallery the location of the macros needs to be accessible from the server. Hence, it is best practice to have these on a mapped drive or on the server itself so the workflow does not error.    Best,   Jordan Barker Solutions Consultant  
View full article
Question The below question was originally asked in the Discussion boards and comes up somewhat frequently from Server users:  Where I'm left scratching my head is how to best set up Gallery, manage permissions, and manage schedules. In an ideal world, I guess I'd see it going like this: Developers create workflows & upload to private gallery Admin (me) updates connection strings and performs cursory review before moving it into a shared area. Developers should be prevented from doing this.  QA team reviews and gives signoff. Admin (me) moves to a shared area (a collection?) and schedules the workflow as needed.  Developers sho uld be prevented from doing this.  Is this approach feasible given the functionality of Gallery? For now, it seems somewhat all-or-nothing to me. If I make somebody an Artisan, it seems like they can publish things to the gallery, schedule workflows, etc. But I may be completely missing something here.    Also, I'm using Windows authentication and I don't see any way to add users to a Subscription. There's literally no button below the Artisans & Members boxes. How do I do this? Answer The below answer was provided KoryC:   What you're wanting to do is very similar to what we see other customers looking to accomplish - essentially, better and more granular control over what users can do within given projects, and a promotion process of workflows. Today, our Gallery does indeed, as you mention, provide the artisan access as a sort of all or nothing type of deployment. So unfortunately, the level of access control you're looking for today is not yet available, but it is on our roadmap and something we are actively looking at for a future release - this is one of our top priorities.   So today, the best approach is indeed to make those developers artisans. Yes, this will enable them to make things public or share them even if they shouldn't, but there are still administrative capabilities, such as removal of workflows, that can help in case such accidents or activities occur.   And as for the user-to-studio management in Windows Auth mode - we're looking to get that button added for an upcoming release, and on top of that, taking a good look and building out some better and easier ways of managing users in Windows Auth mode in general, much in alignment with how we want to make user and gallery management easier in the future.   Let me know if this helps. I know it's not the ideal answer you'd want today, but we are looking to make some significant improvements here. I'd also greatly appreciate any time you may have to go over features like this and to get more direct feedback in the future too!   As far as your question regarding Windows Auth vs. Built-in - no, it's not required to use built-in for subscription artisans (though members don't make much sense in a Windows Auth environment). It is, however, trickier to manage, as you've discovered. The facilities for managing studios-to-users in Windows Auth are lacking at the moment, and it's an area we're looking to improve. Copying and editing the subscription key is indeed the only way. And yes, only one subscription per user - though this is another area we are looking at expanding upon in the future.   There is a button in v10.5 to add artisans to a studio, but not for members, which will likely ultimately go away, at least with Windows Authentication deployments.   For more information about Gallery Administration and setup, take a look at the following article. The link goes to the first of a four part article series: Alteryx Gallery Administration  
View full article
We receive quite a few questions on how to properly chain workflows together. We have a few options that depend on what Alteryx type you are using.   If you have Designer only, your options are to use the Crew Macros which are found on the Community. No link provided as the tools get updated. Please use the Community search for the latest Crew Macros.   In the Crew Macros set, the tools that you will be looking to use are the Runner Tools. You can find a description of the tools here Runner Tools.     Note: You will have to create another workflow using these macros to execute the workflows.   If you have Designer with Scheduler or Alteryx Server, you can use the Crew Macros on the Scheduler, but they are not able to be used on the Gallery. You have other options that will allow you not to have to build another workflow using the Runner Tools and use the workflow on the Gallery or Scheduler.   When you have Scheduler or Server you have access to the Alteryx Engine Command. This will allow Alteryx to run workflows through the command line to execute additional workflows or programs. In most cases, the AlteryxEngineCmd.exe will be located in C:\Program Files\Alteryx\bin\AlteryxEngineCmd.exe.   Great, so what do I do with it?   In your Workflow Configuration window, you have a tab called Events. In that tab you can add a Run Command event. You can choose to run the command as:       In the Command: you can either browse to your AlteryxEngineCmd.exe or type in the location like so - C:\Program Files\Alteryx\bin\AlteryxEngineCmd.exe   In the Command Arguments [Optional]: You will add the location of the 2nd workflow along with the name of the workflow and file type. example: "C:\temp\NHL2.YXMD"   VERY IMPORTANT: Notice in the example above that we have quotations around the string. The reason for this is that the command has difficulty with spaces in the directory paths. By putting quotes around the string, this tells the command to essentially ignore the spaces. However, best practice is to not have spaces in your directory paths when using this command.   Sample:     Note: This method is a great method, but can be finicky. if you are running other command process or do not have admin access to the folders it can cause issues.    You have another option as well! You can turn your workflows into apps for either Gallery or Scheduler use and have them run consecutively.   When you drag an Interface Tool onto the canvas your workflow will automatically change to an App. If you don't want to use an Interface tool you can still change the workflow to an app to use the chained app option. Once you change the workflow to an app, you can use the Interface Designer window to chain the apps together.     Note: When creating chained workflows to use in the Scheduler and Gallery, the workflows and Assets for the workflow must be placed on the Server. Also, the Server will need to have access to any database connections, file directories, and input files.    Want to know more about the Interface Designer? Interface-Designer-Part-1    Want to schedule workflows to run consecutively? Check out this article - Scheduling-Workflows-Using-Event-Run-Command
View full article
As more and more users become familiar with macros it is useful to know the potential ways of scaling and sharing these insights within your business.    Here are just a few ways to achieve this aim!   Push latest macros to users/automatically ensure that users are using the latest version   Alteryx Designer Desktop Working with colleagues and sharing macros? Within the Alteryx designer you can create your own macro ‘Parent Category’. When specifying a file path, you can choose either a local or a network/mapped drive. If you are building macros within a team and looking to share or update macros dynamically, having a mapped location will allow you to reflect any changes on everyone’s machines. As a best practice when overwriting a macro it would be best to update the Meta-data tab (Within workflow properties tab) within the macro to add initials or details of what has changed. This can help you track who edited each version. Unfortunately, if you choose to use an overwrite function, you will be unable to control the version of the macro overtime. Therefore, you may choose to add “V1” etc. to the macro when saving it to the network location. This macro parent category could then be used as a development location and then you could have another macro parent category where you publish production ready macros.     Alteryx Server The Alteryx Server can adopt a similar outline to that of the Alteryx Designer however, it has a greater flexibility in terms of version control. When building a macro you can publish it with a description.   Then when a change is made to the macro you can press the save icon and add another description.   Within the gallery this is then reflected when you click on the macro and click on the version number.  You then have the capability of running & publishing up and down versions.       Include macro pack as part of installation procedure for new users You could zip all the macros together and get a user to extract them to their own macro folder (mentioned above).   Or to the Admin (C:\Program Files\Alteryx\bin\RuntimeData\Macros) or Non-admin (C:\Users\%USER%\AppData\Local\Alteryx\bin\RuntimeData\Macros) folders.   If you use the metadata tag when building the macro workflow it can land in that parent category as well.     Best,  Jordan Barker Solutions Consultant 
View full article
Changing your private gallery URL can be very important, particularly when inviting end users to run applications, download macros and run workflows from your company's gallery.    There are few steps you will have to take to make this happen:   The URL The default URL will look like this: http://localhost/gallery/ The part of the URL which is editable is the "localhost" part and this can be changed to the IP or Machine Name of the server The reason for the /gallery is when the full Alteryx Server is loaded and configured, AlteryxService (the Scheduler) takes root / for itself.  Since both the Scheduler and Gallery can’t coexist in the same area, Gallery is moved into its own subfolder DSN Settings DSN settings will need to be altered when you set up a  fully qualified domain name  (FQDN) For example pointing a server with the computer name of ir-lt-jb-01 and an IP address of XXX.XXX.XX.XXXX to jordanbarker.alteryx.com.  You will need to get your company's IT department to make these edits as they will have access to their DNS servers Best,  Jordan Barker Solutions Consultant 
View full article
Users have noticed that a private gallery that is enabled with Kerberos sometimes will not work with Firefox.  Chrome and IE might seem to pick up the credentials and display the gallery correctly, however, Firefox will present a blank page. This is because by default Firefox blocks all SPEGNO challenges from any web server. We need to configure Firefox to whitelist these sites to allow these requests to come through.   Open Firefox and enter about:config in the address bar. Dismiss any warnings that appear. In the search bar, enter negotiate. Double-click the network.negotiate-auth.trusted-uris preference.  This preference lists the trusted sites for Kerberos authentication. In the dialog box, enter the Gallery domain, such as example.com. Click the OK button. The domain that you just entered in the network.negotiate-auth.trusted-uris should now appear in Value column.  
View full article
Question How do you reserve port 80 on a server for a reverse proxy that Alteryx Server would sit behind?  Ideally, anything off the box could still connect using 80, but locally it would be configured it to use a different port. Answer The Service Port can be currently only be modified by manually editing a key configuration file called "RuntimeSettings.xml."  It's important to note that there are two files with this name installed on a Server:   There is a read-only file called RuntimeSettings.xml installed in the root Alteryx installation folder, which by default is C:\Program Files\ Alteryx\bin\RuntimeData\RuntimeSettings.xml .  This is the  core settings  configuration file used by Alteryx and must never be edited . There is a second file called RuntimeSettings.xml located at C:\ProgramData\Alteryx\RuntimeSettings.xml.  This file is created and modified by the Alteryx System Settings dialog, and contains settings overridden from the base configuration file in (1). **Please note that the settings should only ever be modified using the Alteryx System Settings dialog, as incorrect or incomplete settings could prevent your server from running correctly.**   Please reach out Alteryx prior to performing any manual modification of your Server configuration.  This is especially important if you are running a multiple-node Server installation, as all nodes will need their Controller information updated.  Similarly, Alteryx Designer users using the Scheduler will also be impacted by the change.   If you "must" change the Service Port be sure to: Schedule planned Server downtime with your Server users Stop the Server (using the Service Control Manager or Services tab in Task Manager) Navigate to C:\ProgramData\Alteryx\ Create a copy of the file RuntimeSettings.xml A an Administrator, start Notepad and open RuntimeSettings.xml Under the "Controller" section of the XML, add the tag <ServicePort>your_desired_service_port</ServicePor t> Save the RuntimeSettings.xml file Open Alteryx System Settings and add the port to the Base Address like so: http://localhost:your_desired_service_port/gallery/ Start the Server  (using the Service Control Manager or Services tab in Task Manager) Verify Server operation
View full article