Connect 2021.4 Release Notes
|Release Note Product Versions|
|Version||Date||Release||End of Support|
|2021.4.4.a6331280||February 2, 2022||Major||August 2, 2023|
|2021.4.5.cdab664b||March 17, 2022||Minor||August 2, 2023|
|2021.4.5.10a1771c*||May 12, 2022||Minor||August 2, 2023|
*Fix for CVE-2022-22965 Spring4Shell Vulnerability
You can find more information on the CVE-2022-22965 Spring4Shell vulnerability in the Community article Alteryx’s Response to CVE-2022-22965 Spring4Shell Vulnerability. We upgraded the Apache Tomcat Server to version 9.0.62 in Connect version 2021.4.5.10a1771c.
Security Configuration Update for SAML
Connect is now using SHA-256 algorithm for SAML by default. For more information about SAML, visit the Settings help page.
XLSX Export Available
You now have the option to export your data not only as XLS files but as XLXS files as well. The XLSX export is available for Advanced Search, in the three-dot menu for each asset, and in Nexus. Note that if you export larger data sets, the operation may have a timeout of up to 8 minutes. For such exports we recommend you to use XML export. For more information, visit the Search for Data and Contribute to Data help page.
The following third-party software—jQuery, moments.js, and bootstrap—has been upgraded to the latest stable release.
In the Admin Menu, the Single Sign-On tab in the Settings section has been updated: The option Actions for each of the configured SAMLs has been removed and replaced by the three-dot menu.
Connect received a new logo.
Power BI Loader Lineage
After removing the DataMashup file by Microsoft for the newly created Power BI reports, the possibility to create a lineage for new Power BI reports has been lost. In case you can't see the lineage for your report, republish the report for the lineage to be corrected and re-run the PowerBI metadata loader. Check the Load Metadata from Microsoft Power BI help page for more information.
Fixed and Known Issues
In 21.4, Connect temporarily does not support new API endpoints metadata registration and lineage metadata for dynamic named files.
Major Release Version 2021.4.4.a6331280
|TCON-534||Saving changes in SAML causes the "Access denied." error message.||2021.4.4.a6331280||Fixed|
|TCON-542||Error occurs when Tableau password contains special character.||2021.4.4.a6331280||Fixed|
|Asset Details tags are not saved correctly if the tag name is enclosed in double quotes.||2021.4.4.a6331280||Fixed|
|TCON-545||Adding an image to a Glossary is impossible when the image file extension is written in upper case.||2021.4.4.a6331280||Fixed|
|TCON-553||The ‘Save as Virtual Folder’ button doesn't store asset type.||2021.4.4.a6331280||Fixed|
|TCON-554||Some special characters in an asset name are not allowed.||2021.4.4.a6331280||Fixed|
|TCON-559||Bulk actions "Select all entities" doesn't work.||2021.4.4.a6331280||Fixed|
|TCON-561||Export to XML: Header info isn't in the XML format.||2021.4.4.a6331280||Fixed|
|Date-Picker field: Unable to clear the ‘Date Created At’ and ‘Updated At’ fields once selected.||2021.4.4.a6331280||Fixed|
Minor Release Version 2021.4.5.cdab664b
|TCON-612||The configuration field 'Maximum number of elements in Nexus' in Settings was not applied and therefore the Connect performance has dropped.||2021.4.5.cdab664b||Fixed|
|The icon field from the graphical element 'Plus X more' in Nexus was removed to have a better overview.||2021.4.5.cdab664b||Fixed|
Major Release Version 2021.4.4.a6331280
|TCON-552||Timeout in case of exporting larger data sets using XLS/XLSX export.||2021.4.4.a6331280||Known|
|Server API Endpoints GET Workflows and GET Jobs with no search criteria return nothing.||2021.4.4.a6331280||Known|
Minor Release Version 2021.4.5.10a1771c
|To be disclosed. (*)||2021.4.5.10a1771c||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, 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.