What's New
Visit Alteryx Help and Documentation to access all Alteryx documentation and Release Notes.
2022.2 Alteryx Designer-FIPS Release
2022.2 Alteryx Designer Release: FIPS Only
The 2022.2 release is an Alteryx Designer-FIPS release only. Please note that there is not a 2022.2 release for the non-FIPS version of Alteryx Designer.
The most up-to-date version of Alteryx Designer (non-FIPS) is 2022.1.
New Features
Designer-FIPS Interoperability with Server-FIPS
With the release of Alteryx Server-FIPS 2022.2, you now have access to these options via Designer-FIPS 2022.2:
- Open a workflow from Server-FIPS.
- Save a workflow to Server-FIPS. Note that the Lock Workflow feature is not available in Designer-FIPS and thus is not an option via the Save Workflow modal.
- Add a new Server-FIPS connection via Designer-FIPS.
- Access System Settings via Designer-FIPS. Go to Options > Advanced Options > System Settings.
- Schedule workflows. Go to Options > Schedule Workflow.
- Synchronize DCM between Server-FIPS and Designer-FIPS in the Connection Manager. Go to Designer > File > Manage Connections to open Connection Manager and select Synchronize in the menu.
FIPS-Capable Python SDK
The Python SDK is now FIPS capable.
Important
The Python SDK version 2.1.0 is FIPS-capable as delivered, when used with Designer or Server FIPS version 2022.2. However, you must install and use it as such to maintain FIPS operation.
If you choose to add modules or dependencies to your SDK integrations, it's your responsibility to determine whether those modules and dependencies are themselves FIPS-capable or if they could jeopardize your system’s overall FIPS posture, for instance by providing access to cryptographic primitives implemented someplace other than within the logical boundary of a NIST CMVP-certified cryptographic module.
Unlocked Tools for Designer-FIPS 2022.2
With the release of Alteryx Designer-FIPS 2022.2, you now have access to several tools that were not available via the Alteryx Designer-FIPS 2022.1 release.
These tools are now available:
- In/Out Tools: The Map Input tool is now available.
- Interface Tools: The Map tool is now available.
- Connectors Tools: These Connectors are now available:
- Microsoft Azure Data Lake Input and Microsoft Azure Data Lake Output
- OneDrive Input and OneDrive Output
- PowerBI Output
- SharePoint Input (formerly SharePoint Files Input including list reading functionality)
- SharePoint Output (formerly SharePoint Files Output including list writing functionality)
Restart Alteryx Designer-FIPS 2022.2 after you finish the installation of connectors.
To fully leverage the unlocked connectors, you need to enable DCM and select Allow or AllowAll in User Settings > DCM > SDK Access Mode and restart Designer to apply changes.
Alteryx Designer-FIPS 2022.2 requires all workflows that use the Community Data Connectors above to also use Alteryx Multi-threaded Processing (AMP)—which is the default engine for all new workflows. If you plan to use these updated connectors in older workflows, you might need to enable AMP via Workflow - Configuration > Runtime > Use AMP Engine.
Results Grid Accessibility
We’ve made updates to the user interface of the Designer Results grid to improve accessibility via screen readers and other assistive technology. Buttons and controls that were previously only visible under certain conditions are now always visible, though inactive if not applicable.
Compare Workflows Enhancements
We've made improvements to the Compare Workflows feature. When you compare 2 workflows with container tools, if their enabled and disabled states are different, the Compare Workflows functionality identifies them as different.
Proxy Support in AMP
You can now have proxy enabled with AMP, including SFTP support, so that you can use AMP with or without proxy, as needed. In addition, you can now specify the protocol type when using proxy with both AMP and the original Engine.
App and Macro Debug Run with AMP
Debug mode for Analytic Apps and Macros is available with AMP.
Display Updates in Maps
The Mapbox logo and attribute text now appear at the bottom of the basemaps.