Connect 2020.4 Release Notes

Version:
2020.4
Last modified: June 23, 2022
Release Note Product Versions
Version Date Release End of Support
2020.4 November 18, 2020 Major May 18, 2022
2020.4.9.2ed821e6* June 23, 2022 Minor May 18, 2022

*Fix for CVE-2022-22965 Spring4Shell Vulnerability

More information on the CVE-2022-22965 Spring4Shell vulnerability you can find in the Community article Alteryx’s Response to CVE-2022-22965 Spring4Shell Vulnerability. In this Connect version we upgraded the Apache Tomcat Server to version 9.0.62. 

New Features

Advanced Search: Save Query as Virtual Folder

Connect now allows you to create a virtual folder directly from Advanced Search. Specify the filter by selecting the appropriate fields and select the Save Query as Virtual Folder button. For more information, see the Virtual Folders article.

Notification Queue

Notification Queue allows you to decide what operations you can perform with the items in your queue. For example, you can clear, stop, or restart the queue. To access and set the Notification Queue, navigate to Admin Menu > Maintenance > Notification Queue. To check the Notification Queue status, go to Admin Menu > Settings > SMTP Settings. See Maintenance for more information.

New Custom Field Type: Link Field

From the version 20.4, you can use a new custom field type - Link field. By using it, you will be able to add a custom link that behaves as an active HTML link. See Asset Configuration to get more insight about the custom field types.

See the following short video demonstration about the new custom field type.

Alteryx Designer Tool Details Available for Analytic Workflows 

You can check four Designer tools mostly used in analytic workflows (Join, Formula, Filter, and Summarize tool) and their configuration in Connect, and utilize the power of Connect search across multiple workflows. To see the details, navigate to the Alteryx Designer Tool Details section. For more information, check the Analytic Workflows article.

Metadata Loaders

Alteryx Gallery Loader: Creating Database Objects

To quickly get an overview about used database data sources, especially in case of a new Connect deployment, use the Load Database Objects option when loading the objects from the AYX Gallery. 

When you use the AYX Gallery loader, the workflow objects are created in Connect. If you enable the Load Database Objects option, the loader will try to also create the database objects. The input tool has to provide full information about the object (servername, catalog name, schema, and table; columns are not supported). These objects will be visible after loading in Data Sources > Databases

More information about this new feature can be found in the Load Metadata from an Alteryx Server Gallery article.

Alias Manager

Use Alias Manager in case you don't have an associated lineage in Connect due to a different server name or IP some users might have entered. To help complete the lineage information, enter the (server)alternate name on the server level. For more information about Alias Manager, see the Maintain Data Lineage article.

Amazon Athena Loader

You can now upload metadata to Connect from Amazon Athena. Check the Load Metadata from Amazon Athena article for more information.

Azure Data Lake Store Gen2 Loader: Authentication via Certificate 

For ADLS Gen2, you can newly authenticate via Client certificate. It means that from now on you can decide between the Client secret and the Client certificate. For more information how to setup the Client certificate see the Load Metadata from a Microsoft Azure Data Lake Store Gen2 page.

Python Upgrade for Metadata Loaders 

Make sure you have Designer version 20.4 as the Python engine was upgraded.

Additional Enhancements

Active Directory Loader Enhancements

From now on you can define the way how Full Name and XID of a user will be constructed. You can use any LDAP attribute. To specify the Full Name, navigate to AD loader, then Full Name and enter, for example, ${displayName} (${sAMAccountName}). User will be displayed as John Doe (jdoe). Additionally, in the Other section of the AD loader you can enter XID Definition. For example, ${mail} will create an XID john.doe@mail.com for the user with the email john.doe@mail.com. See Settings for more details.

Boolean Fields Representation 

Boolean fields are now represented as checkboxes. For example, in user profiles in People (Notify changes). 

 

Fixed and Known Issues

Major Release Version 2020.4

Fixed

ID Description Version Issue Status
DE26377 Not enough information in EVEMT_AUDIT when using Winauth and LDAP. 2020.4 Fixed
DE26427 Connect Loaders: Failed to update from version 2020.2 to 2020.3. 2020.4 Fixed
DE26601 LDAP synchronization creates a new version of a user, even when no attribute was changed. 2020.4 Fixed
DE26624 Example missing in Swagger for Custom Filed endpoint. 2020.4 Fixed
DE26674 Request gives 200 Ok if non-existent Custom Field is assigned to an entry type through API. 2020.4 Fixed
DE26786 Missing creation date and time in notification emails header. 2020.4 Fixed
DE27074 Wrong number in the ActiveUsers count (removed as obsolete). 2020.4 Fixed
DE26555 Alteryx Gallery Loader: Not able to see lineage to DB inputs after upgrade to 2020.1. 2020.4 Fixed
DE26698 DB Loaders: Error because of non-existent schema. 2020.4 Fixed
DE27023 Oracle Loader: Field length issue. 2020.4 Fixed
DE27209 Impala Loader generates error because of Impala implementation on KUDU. 2020.4 Fixed
DE27364 Snowflake Loader: acc_usage missing view columns. 2020.4 Fixed
DE27403 Snowflake Loader: Issue with external tables. 2020.4 Fixed

Known

ID Description Version Issue Status
DE27521 Failure when adding DB technology icon. 2020.4 Known
DE27550 Notification emails are not created for entries with long name. 2020.4 Known

Security Updates 

Fixed

Minor Release Version 2020.4.9.2ed821e6

ID Description Version Issue Status
TELC-2814
GCSE-422
To be disclosed.* 2020.4.9.2ed821e6 Fixed

*In accordance with security best practices and to prevent potential manipulation by bad actors, Alteryx does not disclose the details of any open vulnerability until all supported versions are updated with a fix. Beginning with 21.4.2, releases will become available this month, continuing through June, until the fix has been applied to all versions. To ensure that all versions you use are promptly fixed, regular updates during this period are strongly recommended. More information will be made available once the vulnerability has been fixed for all impacted versions.

Was This Page Helpful?

Running into problems or issues with your Alteryx product? Visit the Alteryx Community or contact support. Can't submit this form? Email us.