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.
There is a known issue (TGAL-6268) with the Alteryx Gallery loader used to download workflows to Connect. When you try to load data from Alteryx Server using the GET admin/v1/workflows API endpoint, you get no results.
To edit the person record selected in a custom field, use the Edit button first and then pick the new person from the drop-down list. Inline editing by an Administrator will change the profile name of the selected person rather than picking a new one.
Alteryx Connect's Entity ID is the unique identifier for Alteryx Connect as a service provider.
This article will go through the steps to update the Alteryx Connect Entity ID if you wish to change from the default Entity ID provided.
If you see this warning when attempting to collect metadata from your Alteryx Private Gallery, verify that the version of Alteryx Server and the version of Alteryx Connect match. That is a requirement for proper function.
With version 2019.1, you can make Connect run on https protocol and make the communication between client and server much more secure. This is an enhancement from the previous version, when you had to manually change configuration files, download SSL tools and execute several of commands. Now you can do it in a user friendly way just by using the Installer.
In this article you'll find detailed information about the loader categories and which exact information is extracted by each of the loaders we support. Each type differs in the object hierarchy, structure of the objects, and detail of the objects.
Have you ever wondered what are the limits of Connect? How many entries can you store in Connect? Great questions! In fact, no hard limit on the number of entries is set. The number around 2M entries is the number on which the performance tuning in the 2019.1 release was done.
This article provides instructions for adding an issued SSL certificate to the web page hosted by Alteryx Connect so that the page is served securely.\n \n Note: This article is intended for trusted certificates in your environment. You must have a copy of the certificate (such as .crt) and the signing key (such as .key), or a combined certificate file (such as .pfx or .p12) in order to complete this process. This certificate must be installed on all machines you intend to use with Connect as a trusted certificate if these machines are to be used in conjunction with Alteryx Connect, such as loading metadata with Alteryx Designer or search results from Alteryx Connect displayed within Alteryx Designer.
This article provides instructions for adding a self-signed SSL certificate to the web page hosted by Alteryx Connect so that the page is served securely.\n \n Note: This article is only intended for Self-Signed Certificates. A self-signed certificate is not recommended to be used for production purposes. This is because self-signed certificates must be installed on all of the machines you intend to use with Connect as a trusted certificate. This includes any machines that will use Connect applications like loading metadata in Alteryx Designer or using search results from Connect Designer.\n
This article is intended to assist with inserting a certificate to be used to validate a SAML signature from a SAML Identity Provider (IDP) when used with Alteryx Connect. This article will only be needed if your IDP is signing assertions or other traffic with a specific cert that may be self-signed or not trusted by a widely trusted Certificate Authority (CA).
Alteryx Connect has the ability to interface with a number of identity providers that support the SAML 2.0 standard, and recently we stood up an ADFS test server and set it up with Alteryx Connect successfully. The following information will assist with configuring Alteryx Connect to be functional with ADFS.