Server 2023.1 Release Notes
Release Note Product Versions | |||
|---|---|---|---|
Version | Date | Release | End of Support |
2023.1.1.123 | May 17, 2023 | Major | May 17, 2025 |
2023.1.1.200 (Minor) 2023.1.1.1.200 (Patch 1)* | June 21, 2023 | Minor/Patch | May 17, 2025 |
2023.1.1.247 (Minor) 2023.1.1.2.247 (Patch 2)* | August 14, 2023 | Minor/Patch | May 17, 2025 |
2023.1.1.281 (Minor)* 2023.1.1.3.281 (Patch 3) | October 11, 2023 | Minor/Patch | May 17, 2025 |
2023.1.1.306 (Minor) 2023.1.1.4.306 (Patch 4) | November 21, 2023 | Minor/Patch | May 17, 2025 |
2023.1.1.336 (Minor) 2023.1.1.5.336 (Patch 5)* | January 16, 2024 | Minor/Patch | May 17, 2025 |
2023.1.1.361 (Minor) 2023.1.1.6.361 (Patch 6) | March 7, 2024 | Minor/Patch | May 17, 2025 |
2023.1.1.392 (Minor) 2023.1.1.7.392 (Patch 7) | May 16, 2024 | Minor/Patch | May 17, 2025 |
2023.1.1.422 (Minor) 2023.1.1.8.422 (Patch 8) | July 18, 2024 | Minor/Patch | May 17, 2025 |
2023.1.1.437 (Minor) 2023.1.1.9.437 (Patch 9) | August 8, 2024 | Minor/Patch | May 17, 2025 |
2023.1.1.460 (Minor) 2023.1.1.10.460 (Patch 10) | October 3, 2024 | Minor/Patch | May 17, 2025 |
Upgrade Considerations
*All 2023.1 Patch Releases: When upgrading to 2023.1.1.200 Patch 1 (and all subsequent 2023.1 patches), please note that the database version is updated from version 44 to version 45. As a result, a rollback to 2023.1.1.123 is not possible without restoring a database backup from before the update. If a database backup is not available, please contact Support for assistance.
Please note that due to the cryptography migration in 2022.3, only Server versions 2021.2 and newer are supported to upgrade to 2023.1. If you have a version older than 2021.2, upgrade to 2021.2 or a newer release before upgrading to 2023.1.
As of version 2023.1, Designer versions older than 2022.3 Patch 3 will NOT be able to publish workflows from Designer to Server. For older versions of Designer you will need to upload those workflows to Server 2023.1 using the Administrator UI or API. To maintain compatibility with Server, download the latest version of Designer. The latest version of Designer that is backwards compatible with Server 2023.1 is Designer 2022.3 Patch 3.
Important: Alteryx Connect Customers
If you are an Alteryx Connect customer, please feel free to upgrade to Alteryx Server version 2023.1 Patch 1—previous issues with compatibility between Server and Connect have been rectified.
When upgrading Server, please be sure you’re downloading and installing the latest version of Server 2023.1 which includes Patch 1 as indicated on the Downloads portal by a Last Updated date on or after June 21, 2023.
Important: Predictive Tools for Server
Starting with 2023.1 Patch 1, a newer version of R is available on the Downloads portal. The version of R (v4.1.3) installed with Server will continue to support workflows with predictive tools. If you want the latest R version, you can download it from the Downloads portal.
Migration Prep Tool
To use the latest and best cryptography throughout Server to protect data at rest and data in flight, you now have a way to get your crypto migrated to the most modern algorithms without taking a lot of downtime and interrupting your business.
As part of the move to more modern, FIPS-capable cryptography, we prepared a Migration Prep Tool to mitigate the maintenance window downtime required to get all your workflows migrated to the new crypto standard.
The Migration Prep Tool for Server is a separate command line utility that allows pre-migration of a database of workflows and apps to migrate faster to the new AES256 standard.
This tool is optional and only needs to be run once before upgrading any prior Server version to Server 2022.2.x (FIPS build), 2022.3.x (FIPS or general availability builds) or beyond. However, we recommend you run the Migration Prep tool in some cases.
For more information about this tool, visit the Migration Prep Tool help page.
Upcoming Changes to the Timestamp Format
In a coming release, all timestamps in the Server databases will be converted to the UTC format. There will be no change in functionality in the front-end Server user interface and all times will be displayed as expected per the Server configuration settings. If you are taking timestamps directly from the Server database, these timestamps will be migrated to UTC format for standardization across the product and to alleviate daylight savings time issues.
Upcoming Deprecation of OS Support
As part of the deprecation of Windows Server 2012 on October 10, 2023, Alteryx Server will no longer be supporting this operating system as of the 2023.2 release later this year.
If you operate Alteryx Server on Windows Server 2012, we encourage you to upgrade to a supported version of the OS prior to upgrading to Alteryx Server 2023.2. The reason is that MongoDB upgrades in the 2023.2 release will render Alteryx Server unusable if installed on a system running the Windows Server 2012 operating system. Alteryx Server versions 2023.1 and prior will continue to operate on Windows Server 2012. For more information on this topic, please go to FAQ: Alteryx Server and MongoDB 4.2 Community article.
Required Password Reset for Built-In Authentication
If you use built-in authentication and you upgrade from a version lower than 22.1, you need to reset your password due to security improvements. If you didn't reset your password in version 22.1, you need to have SMTP enabled. This is so users can reset their password via the forgot password functionality or so that an admin can trigger password resets for all users via the UI or API. For more information on how to reset your Server password after an upgrade to 22.1, visit the Reset a User's Server Password help page.
Important
The Alteryx Server version 2023.1 offers separate GA and FIPS 140-2 capable products. Please note that these standards are developed by the US National Institute of Standards and Technology (NIST) for use by US government agencies and contractors. For more information about FIPS, go to the NIST FIPS FAQ page.
The general (non-FIPS) release version of Alteryx Server is not capable of FIPS operation. A separate release (and installer) is available under separate license terms, for our FIPS 140-2 customers. Contact your Alteryx Sales Representative for more details.
Feature Differences
Server-FIPS 2023.1 has a few features that are not available or limited in function when compared to the non-FIPS Server releases. See Alteryx Server and Server-FIPS Feature Differences for reference.
New Features
Azure Active Directory Group Support with SAML Authentication
Admins can now sync users and group access to Server using Azure Active Directory (Azure AD) and the SCIM protocol. This allows admins to manage user and group permissions and Server access from their identity provider as single source of truth. Users and groups are automatically synced from Azure AD to Server, making it faster to onboard or offboard Server users and groups.
This functionality is available if you are using SAML as your authentication method. Any identity provider that supports SCIM can use this functionality, but official support is limited to Azure AD, which is the only provider we tested. To read more about the Azure AD group with SAML authentication and SCIM support, go to Configure Alteryx Server Authentication and Alteryx Server Settings.
New API Endpoints
Added new API endpoints to add and delete an Active Directory (AD) group via the admin API.
To add an AD group to a custom Server group, use the following admin API endpoint:
POST/v3/usergroups/{id}/activedirectorygroups.To delete an AD group from a custom Server group, use the following admin API endpoint:
DELETE/v3/usergroups/{userGroupId}/activedirectorygroups/{adGroupSid}.
For more information about these endpoints, visit the User Group Endpoints help page or access the Swagger documentation by selecting the question mark icon in the upper right corner of Server interface.
Updates to API Endpoint for Uploading New Workflow Versions
We introduced the /v3/workflows/{workflowId}/versions API to allow admins and users to upload new versions of existing workflows. Additionally, we updated the Admin Upload Workflow so .yxzp workflows uploaded this way can now be versioned as changes are made in Designer or uploaded via the new API. For more information, go to Workflow Endpoints and Workflows: Admin Interface, or access the Swagger documentation by selecting the question mark icon in the upper right corner of Server interface.
Please note that any versions created using the old (v3) version API will continue to be unusable. For example, if you had a workflow and created a second version using the previously released version of /v3/workflows/{workflowid}/versions API, and then you created a third version using the NEW /v3/workflows/{workflowid}/versions API, only the original version and the third version will be usable.
Language and Region Updates
With 2023.1, we extended the language support to the entire Alteryx Server interface available in Chinese, French, Italian, Japanese, German, Spanish, and Portuguese. Additionally, Server Help documentation is available in the supported languages. For our global users, this improves your experience by making it easier for you to access and understand Alteryx Server in your native or preferred language. For information on how to select your preferred language and region, visit the My Profile help page.
Server UI Redesign
Redesigned the Server admin and user interfaces for the pages listed below. The functionality of these pages remains the same.
Login screen: In this release, we have made some cosmetic changes to the login page which provides a fresher look and feel.
Admin and Home screen: Starting with this release, Curators will now see the Home (user) and Admin tabs on the top bar of the application. This change streamlines administrative tasks and improves the user experience by reducing the number of clicks required to access these important administrative features.
Analytic apps: When you run an analytic app, the option to name the job, set the priority, and assign a worker now appears in a pop-up window after you select the Run button.
For non-chained analytic apps, the Re-Run option is only available for the last job run for workflows and analytic apps. Please note that if you refresh your browser, the Re-Run option will no longer be available.
For chained apps, you can navigate back and forth between tabs within each analytic app and edit the information on those tabs. However, you CAN'T navigate back to a previous app if there are multiple chained apps because that app has already been run.
Notifications: Redesigned the Notifications experience for admins and users. To access them, select the bell from the menu bar in the upper right corner. It also includes an unread notifications counter. The Notifications dropdown summarizes the latest notifications, including their details, and allows you to quickly view them or redirect to the asset that was updated. For more information, go to Notifications.
Global Search: The global search bar has moved to the top right corner of the application window to provide a more intuitive and user-friendly interface. You can search Workflows, Insights, Districts, Pages, and we’ve added the ability to search for Collections. You can search individual or multiple asset types at a time by selecting the asset type in the filter box. You can navigate through the search results using the pagination at the bottom of the page. For more information, go to Search for Assets.
Additionally, we replaced Lucene search with a custom search provider. This improves search accuracy, expands search capabilities, and provides more thorough search results across the entire Server, while delivering equal or better performance. With this change, the AlteryxGallery_Lucene database and schema are now obsolete. See MongoDB Schema Reference for specific changes.
Links: To find the Community and help page links, as well as API documentation for users with API access, select the question mark icon at the top right corner of the navigation bar.
These UI changes should improve your user experience with Alteryx and make it easier and more intuitive for you to stay on top of important updates and changes.
Block DCM Connections from Syncing from Server to Designer
As an admin, you can now block the DCM connections synchronization from Server to Designer and from Designer to Server for the entire environment. This feature is useful to ensure that DCM connections in production environments connected to production data sets are not used to create new workflows in Designer. With this feature, you can restrict access to DCM connections for data sets in production environments, while allowing users to sync DCM connections between Server and Designer in development or test environments. To disable sync, go to System Settings > DCM and select the checkbox Block DCM Connections Synchronization between Server and Designer. To allow the synchronization, leave the checkbox unselected. For more information, go to DCM - Server.
Allow Access to Workflows Without Shared Credentials
Added a new feature under Admin > Settings > Configuration > Assets. To allow users to run workflows they have access to, without access to shared credentials, enable the Allow Access to Workflows Without Shared Credentials setting.
When enabled, users can create Designer workflows using Server connections and data sets shared with them. Similarly, analysts (non-admins) can run workflows using those connections. However, users cannot use those connections for other purposes or data sets. Visit the Alteryx Server Settings help page for more information.
Unique Connection Strings for Workers
Added the ability for each worker to define how it connects to the database. Remote worker nodes can optionally set a connection string independently from the controller. This allows a worker to set their own options or credentials.
Worker nodes can now connect directly to MongoDB using an override connection string defined within runtimesettings.xml. This string differs from the controller connection string and other worker connection strings. It allows the worker to use a configurable connection when communicating directly with MongoDB so that workers can use unique credentials that admins can audit. Currently all connections are either sent through the controller or use the same connection the controller has.
For more information, visit the MongoDB Advanced Connection Strings help page.
Update of the Server UI Page in Alteryx System Settings
We updated Alteryx System Settings to put emphasize the Default Run Mode setting. You can now find this setting at the top of the Server UI > General page instead of at the bottom. We also updated the help information for this setting to clarify what this setting does and why it is important. For more information, go to Server UI.
jQuery Removed
We’ve completely removed jQuery v1.9 from Alteryx Server interface.
File Browser Tool Improvement
Improved File Browser tool user experience when selecting large files. We've added a loading bar to indicate the user that a large file is processing in the background. This was previously unavailable, confusing users about the progress. This feature is available from 2023.1 Patch 3.
CLI Option to Connect to Remote Controller
As an administrator, you can now securely transfer encryption keys from your existing environment to migrate Server to a new host or mitigate an outage.
For more information, go to Encryption Key Transfer Process.
Timezone for Schedules in Server API V3
Added timezone for the following API V3 endpoints:
POST /v3/schedules: This endpoint has been updated to allow you to set the time and timezone for schedules.
For example, if you want to set a schedule for 5:00 PM Mountain Time, you should be able to set the schedule to 5:00 PM and select Mountain Time as the timezone. The timezone option is optional, and if you don’t specify the timezone, the default timezone will be UTC time.
PUT /v3/schedules: This endpoint has been updated to allow you to update existing schedules created using the API and add a timezone selection if you choose.
For example, if you created a schedule using the API endpoints and the time had to be set in UTC, you should be able to update the schedule and change the time and timezone.
However, existing schedules will continue to run as expected if you choose not to add a timezone.
GET /v3/schedules/{id}: This endpoint has been updated you can view the timezone for an existing schedule filtered by Id.
GET /v3/schedules: This endpoint has been updated so you can view the timezones for all the existing schedules.
For more information about the endpoints, access the Swagger documentation by selecting the question mark icon in the upper right corner of Server interface. For valid timezones to use in the above API endpoints, see the Schedules Endpoints help page.
Crypto Migration Improvements
We've made the following improvements to the crypto migration process:
Migration Prep Tool Improvements
To evaluate any anticipated issues you might need to address prior to upgrading to 2022.3 or later, run a pre-flight check with the Migration Prep Tool.
During the pre-migration or full migration process, you will be able to see improved error logs that allow you to resolve the issues yourself. This enables you to take recommended action to ensure the full migration is completed successfully despite any errors. Check the logs for any records that have been deleted as part of the successful migration.
We have added 3 new run options when running the Migration Prep Tool:
Default: Run the pre-migration and pre-migration check simultaneously (-p)
Run just the pre-migration (apps) (--appsonly)
Run just the credential validation step (--credonly)
While running the Migration Prep Tool, you must provide the controller token (-t) and hostname/IP Address (-i) of the controller. This also means you can now run the Migration Prep Tool on a multi-node setup by providing the controller's hostname/IP address and controller token.
Please note that 2 instances of the Migration Prep Tool tool cannot run simultaneously for the same controller.
Improved Error Messages
Example of an improved error message:
2024-02-28 10:06:38.038910;3;Error parsing xml file 'C:\ProgramData\Alteryx\RuntimeSettings.xml': char position=0; Message=File was not found
2024-02-28 10:06:38.038834;3;<Error parsing xml file 'C:\ProgramData\Alteryx\RuntimeSettings.xml': char position=0; Message=File was not found>. Please verify <"C:\ProgramData\Alteryx\RuntimeSettings.xml"> exists.
For more information about the pre-flight check, go to Run the Migration Prep Tool.
Fixed and Known Issues
Fixed Issues
Fixed Major Release Version 2023.1.1.123 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-6264 GCSE-339 | Users are not shown in the Add User dropdown of Data Connections when the username consists of Japanese characters only. | 2023.1.1.123 | Fixed |
TGAL-6357 GCSE-412 | Open Workflow From the Server UI window immediately exits. | 2023.1.1.123 | Fixed |
TGAL-6749 | When you update the Account Lockout Time under Admin > Settings > Configuration > Security, the Account Lockout Time value is reset to default after reloading this page. | 2023.1.1.123 | Fixed |
TGAL-6751 | Admin login page using SAML doesn't display the SAML login screen. | 2023.1.1.123 | Fixed |
TGAL-6754 | When you replace a workflow with another workflow, the version tracking doesn’t work if both workflows were uploaded via the API or from the Admin Server UI. | 2023.1.1.123 | Fixed |
TGAL-6756 | When a user with Curator (admin) rights attempts to use the Replace Workflow button to replace a Designer-uploaded workflow with an API or Admin UI-uploaded workflow, the user gets an error. | 2023.1.1.123 | Fixed |
TGAL-6761 GCSE-803 | The PUT /v3/schedules/{id} endpoint fails when updating a custom schedule using Last in the Days parameter. | 2023.1.1.123 | Fixed |
TGAL-6769 | The connection is only shared with direct members of the User group on Alteryx Server, not with members of the AD group that is part of this User group on Alteryx Server. | 2023.1.1.123 | Fixed |
TGAL-6794 | When you save a new version of a workflow that already has a schedule, the new version runs only once and then the schedule switches back to the previous version of the workflow. | 2023.1.1.123 | Fixed |
TGAL-6807 | If the pre-migration process is interrupted, the created files are not deleted after the premigration is completed successfully. | 2023.1.1.123 | Fixed |
TGAL-6825 | The Migration Prep Tool accepts multiple inputs on the initial prompt for input, reading them in sequence. Thus “yy” can approve multiple commands without the user’s knowledge. | 2023.1.1.123 | Fixed |
TGAL-6836 | When a workflow is added via the v3 API endpoint and is public, the DateMadePublic attribute is not being populated. | 2023.1.1.123 | Fixed |
TGAL-6909 | Corrected an issue where the installer wasn't recognizing the version of MongoDB properly during an upgrade if a patch had been applied to update MongoDB from 4.2.15 to 4.2.22. This caused the installer to incorrectly report an error indicating the user was attempting to upgrade from an unsupported version of MongoDB. | 2023.1.1.123 | Fixed |
TGAL-6916 | When editing a schedule via the PUT to /v3/schedules/id endpoint, it fails with the error "This workflow requires credentials". | 2023.1.1.123 | Fixed |
TGAL-6934 TMEE-880 | Server Admin interface: When you try to delete a workflow as an admin, the snackbar message "Workflow deleted" appears, but the same workflow reappears in the list. If you try to delete it again, you will see a red error banner stating that it failed to delete. | 2023.1.1.123 | Fixed |
TGAL-6965 GCSE-954 | The POST admin/v1/workflows/ endpoint breaks the ability to run a workflow if this workflow has a different name than the originally uploaded workflow. | 2023.1.1.123 | Fixed |
TGAL-7009 | When using the POST /v3/workflows endpoint, the sourceAppId argument behaves improperly - it doesn't work as an overwrite. Each time it's called, even if the sourceAppId doesn't change, it creates a new workflow and returns a new unique id. | 2023.1.1.123 | Fixed |
TGAL-7017 | Anonymous users (not logged in) are unable to run public workflows even when the “Unregistered Users Can Run Workflow on the Homepage” setting has been enabled. | 2023.1.1.123 | Fixed |
TGAL-7036 | Addressed a potential race condition when retrieving a key. | 2023.1.1.123 | Fixed |
TGAL-7060 TPRI-912 | For the workflows which are changed to public, the date is not displayed in the table in the column Made Public under Admin > Workflows. | 2023.1.1.123 | Fixed |
TGAL-7078 GCSE-1069 | The Limited Availability 2022.3 Server workflows fail to re-upload after encryption. | 2023.1.1.123 | Fixed |
TGAL-7080 | Unable to delete user via API. | 2023.1.1.123 | Fixed |
TGAL-7291 GCSE-1121 | Users cannot add a new data connection for Microsoft SQL Server with Windows Authentication via Server admin interface. | 2023.1.1.123 | Fixed |
TGAL-7350 | Workflow revisions display as version 0 in the Server UI. | 2023.1.1.123 | Fixed |
TGAL-7411 | Admin credentials: Unable to create credentials in FIPS environment. | 2023.1.1.123 | Fixed |
TGAL-7425 | Unable to create DCM Credential, DCM Vaults, and DCM Data Source in FIPS environment. | 2023.1.1.123 | Fixed |
TGAL-7785 | Designer can’t connect directly to a remote controller to create or manage schedules (Desktop Automation/Scheduler). | 2023.1.1.123 | Fixed |
TPRI-713 GCSE-637 | Output messages on Analytics Apps run in Server are not being displayed correctly. | 2023.1.1.123 | Fixed |
TPRI-772 GCSE-726 | When you edit a weekly schedule in 2022.1, it selects all days instead of the days you had previously selected. Also, the "No ending date" checkbox is not prepopulated. | 2023.1.1.123 | Fixed |
TPRI-816 TGAL-6801 | Sidebar: My Workspace tab item is not getting highlighted when selected, while being actually active. | 2023.1.1.123 | Fixed |
TPRI-849 GBETA-330 | Server UI/UX Improvements: Menu items are not translated to Japanese. | 2023.1.1.123 | Fixed |
TPRI-859 GBETA-342 | Server UI/UX Improvements: "Asset Management" message is not translated. | 2023.1.1.123 | Fixed |
TPRI-860 GBETA-343 | Server UI/UX Improvements: Excerpt text in Districts > Create District has an editing issue. When you add a character to the middle of the text, the cursor automatically goes back to the end of the text. | 2023.1.1.123 | Fixed |
TPRI-933 | In versions 2021.4+, only the workflow owner and curators can access Workflow Settings. In the previous releases, all users with access to the workflow could access Workflow Settings. | 2023.1.1.123 | Fixed |
TPRI-935 | Unable to add Users to a Subscription on a Server configured for Windows Authentication. | 2023.1.1.123 | Fixed |
TPRI-1071 | When you attempt to run a version of a workflow other than the latest (most current version), the workflow is not being run correctly. Server is not sending the correct version to be run. | 2023.1.1.123 | Fixed |
TPRI-1487 | When owners of a workflow or app manually run a workflow in Server immediately after changing the published version to a version that differs from the latest (or newest) version of that workflow, Server will run the published version on the first manual run as opposed to the latest version. Subsequent manual runs will execute the latest version as expected. | 2023.1.1.123 | Fixed |
Fixed Minor Release Version 2023.1.1.200 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-7677 | Global search fails if the workflow / insight / districts / collection name contains special characters. | 2023.1.1.200 | Fixed |
TGAL-7708 | The "in beta" text in the notification about 7 language support has to be removed. | 2023.1.1.200 | Fixed |
TGAL-7709 | Update copy/text in System Settings > Engine > General > Run engine at a lower priority. | 2023.1.1.200 | Fixed |
TGAL-7825 | Insights might not render in multi-node environments and display the message "Error rendering insight. If this problem persists, please contact your Systems Administrator." To work around this issue, please ensure the Insights worker is enabled on your controller. | 2023.1.1.200 | Fixed |
TGAL-7846 | When Administrators upload workflows using the "+New" button in the Admin UI, workflows are not being validated as they were in previous versions of Server. | 2023.1.1.200 | Fixed |
TGAL-7851 | Alteryx Server public endpoint /admin/v1/workflows/jobs only returns a maximum of 15 jobs. The endpoint should be capable of returning a job for each workflow without limit. | 2023.1.1.200 | Fixed |
TGAL-7868 | Global search issues: When you search with a full name, the search doesn't match any records. When you search for a workflow / insight / collection that contains special characters, the results don't match either. The term is passed through the Sanitize function unnecessarily. | 2023.1.1.200 | Fixed |
TPRI-1575 GCSE-1302 | System messages do not appear when first logging in to Server. | 2023.1.1.200 | Fixed |
TPRI-1695 TCPE-692 | Regression issue: PCXML previews are not rendering URLs in Server 2022.3+. | 2023.1.1.200 | Fixed |
Fixed Minor Release Version 2023.1.1.247 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-7926 | Pagination is not working as expected for these modules: Admin (Workflows, Users, Subscription, Tags, and Pages), Home (Districts and Workflows). | 2023.1.1.247 | Fixed |
TGAL-8049 | API calls to Admin V1 API are intermittently failing. | 2023.1.1.247 | Fixed |
TPRI-1797 | Data Connections Admin Screen is missing an 's' in Connection in the title of the page. | 2023.1.1.247 | Fixed |
TPRI-1825 | Nested radio button is failing to retain the user selected values in an analytic app while re-run. | 2023.1.1.247 | Fixed |
TPRI-1976 TCPE-720 | When running an analytic app with "Generate field map" enabled in File Browse Tool and "Output File Name as Field" selected in Input Data Tool, it provides different UI in Designer and in Server. | 2023.1.1.247 | Fixed |
TPRI-2018 GCSE-1467 | Tree Interface tool doesn't display all custom XML in Gallery 2023.1 | 2023.1.1.247 | Fixed |
TPRI-2019 GCSE-1469 | Hide Control option within a Text Box Interface tool doesn't work when run in Gallery 2023.1 | 2023.1.1.247 | Fixed |
TPRI-2043 GCSE-1437 | Drop Down and List Box Tools return NAME from NAME:VALUE pair rather than VALUE. | 2023.1.1.247 | Fixed |
TPRI-2045 | Type column filter in Admin > Users > Groups displays ActiveDirectory instead of Active Directory. | 2023.1.1.247 | Fixed |
TPRI-2080 | When using the Re-Run button after running an analytic app in Server UI, the NULL values that were previously selected are not retained in the Interface tool textbox. | 2023.1.1.247 | Fixed |
TPRI-2120 | When you select an Excel file with multiple sheets and select one sheet to get the output, the workflow crashes. | 2023.1.1.247 | Fixed |
TPRI-2128 | When using the Re-Run or back button after running an analytic app (with Tree tool interface) in Server UI, the values that were entered are not retained in the Tree tool. | 2023.1.1.247 | Fixed |
TPRI-2233 | Re-run: File Browse issue with Field Mapping option: Different UI in Designer versus Gallery for specific tool configuration. | 2023.1.1.247 | Fixed |
TPRI-2411 GCSE-1438 | Server 2023.1 Analytical App Date tool: When you choose a date, it picks the previous day. | 2023.1.1.247 | Fixed |
TPRI-2493 GCSE-1524 | File Browse in Server with a list of sheets selected outputs the first sheet, not sheet names. | 2023.1.1.247 | Fixed |
TPRI-2820 | Re-Run isn't retaining for List Box analytical app when "All checked by default" option is selected. | 2023.1.1.247 | Fixed |
Fixed Minor Release Version 2023.1.1.281 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-8569 | DCMKey transfer via the CLI doesn't work on all keys. | 2023.1.1.281 | Fixed |
TPRI-2945 | Default dropdown value set for dropdown Interface tool is not working in Server. | 2023.1.1.281 | Fixed |
TPRI-3273 | Output of the dropdown Interface tool with default dropdown value is giving wrong output in Server. | 2023.1.1.281 | Fixed |
TPRI-3283 GCSE-1651 | When running an analytic app, the job status message under Output Preview and the green status pop-up display conflict. | 2023.1.1.281 | Fixed |
TPRI-3349 | When running an analytic app, edited values in a nested checkbox are not retaining their values when selected. | 2023.1.1.281 | Fixed |
Fixed Minor Release Version 2023.1.1.306 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-597 GCSE-1178 | Exception thrown when asserting SAML response from IDP (when using Meta or x509). | 2023.1.1.306 | Fixed |
TCPE-648 GCSE-1295 | Telemetry XML generated for unsaved workflow runs picks up the WorkflowFilePath of a previously run, saved workflow in customer managed Telemetry XML. | 2023.1.1.306 | Fixed |
TDT-1842 TSPA-986 | App re-run functionality is failing for Map tool. | 2023.1.1.306 | Fixed |
TDT-1869 | Server Map Analytic App: Re-run on Map Input and File Browse doesn’t repopulate original values. | 2023.1.1.306 | Fixed |
TDT-1892 | Analytic App with map example and Group Box is failing to select the reference layers/points/area comparing with the selected sample data file. | 2023.1.1.306 | Fixed |
TGAL-8978 | In Designer, collection owners are unable to see the workflows added by other users. | 2023.1.1.306 | Fixed |
TPRI-1602 | When you save the Credential Type as Custom under Home > My Profile > Workflow Defaults, a double snack bar appears instead of one. | 2023.1.1.306 | Fixed |
TPRI-1993 | Analytic app example of List box is failing when you upload a file to Connect to an upstream tool to populate. | 2023.1.1.306 | Fixed |
TPRI-3321 GCSE-1666 | File Browse Tool: Unable to configure analytic app in Server if File Browse Tool sits outside of app interface Group Box. | 2023.1.1.306 | Fixed |
Fixed Minor Release Version 2023.1.1.336 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-8733 GCSE-1694 | Index rebuild process fails in 2023.1 when Server data connection ConnectionString character length exceeds MongoDB index key limit of 1024 bytes returning an error "Index key too large to index" and causes Users/Subscriptions page to be blank. | 2023.1.1.336 | Fixed |
TPRI-2072 | Nested Group boundary lines are overlapping on other question in analytical apps. | 2023.1.1.336 | Fixed |
TPRI-2273 | Users can’t copy the text from the messages of the Job Results. | 2023.1.1.336 | Fixed |
TPRI-3661 GCSE-1757 | In the Date Tool, you can only select the year when you drill down and not the month. For the month, you must navigate right and left until the required month is selected. | 2023.1.1.336 | Fixed |
TPRI-3662 GCSE-1758 | In the File Browse Tool, when you are mapping fields to an app, it is not as visually distinct as in previous Server versions. | 2023.1.1.336 | Fixed |
TPRI-3839 GCSE-1743 | After selecting a date in the Date Tool on Alteryx Server, the format of the display date changes from DD/MM/YYYY in previous versions (for example, 2021.3) to MM/DD/YYYY. | 2023.1.1.336 | Fixed |
TPRI-4100 GCSE-1822 | Chained applications require manual run for each analytics app even if the app does not require any user input. | 2023.1.1.3316 | Fixed |
Fixed Minor Release Version 2023.1.1.361 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-921 GCSE-1888 | The POST /admin/v1/workflows endpoint is returning "An item with the same key has already been added." exception message for specific YXZP files. | 2023.1.1.361 | Fixed |
TGAL-8184 TCPE-740 | Certain CredentialPasswordID values are causing MongoDB migration to schema 42 to fail and preventing successful upgrade to 2022.3+. | 2023.1.1.361 | Fixed |
TGAL-9760 GCSE-1830 | Controller token and MongoDB password is intermittently becoming corrupt causing service issues as a result. | 2023.1.1.361 | Fixed |
TPRI-2807 GCSE-1555 | When adding an URL to the metadata of a workflow, it is getting prefixed by the app URL. | 2023.1.1.361 | Fixed |
Fixed Minor Release Version 2023.1.1.392 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-940 GCSE-1916 | After upgrade to Server 2022.3+ with SAML authentication, the ACS endpoint is exposed as lowercase (/saml2/acs) compared to uppercase (/Saml2/Acs). This causes issues during login and startup. | 2023.1.1.392 | Fixed |
TCPE-952 GCSE-1926 | Upgrade MongoDB Database tools version to v100.7.0 for Mongo 4.2 and 4.4: MongoDB restores fail with some frequency by overloading memory. | 2023.1.1.392 | Fixed |
TCPE-957 GCSE-1936 | Performance issue with the DELETE /v3/workflows/{workflowId} endpoint. If the database has only a few thousand schedules, this results in an unreasonable amount of time to perform even for workflows without set schedules. | 2023.1.1.392 | Fixed |
TCPE-1026 GCSE-2017 | Workflow comments added via Designer are not being returned by the /v3/workflows/{workflowId} endpoint. | 2023.1.1.392 | Fixed |
TCPE-1075 GCSE-2106 | Chain app in Server doesn't work, returning the error message "The job XXX has failed.". The Server log displays the error "Invalid answer for question." | 2023.1.1.392 | Fixed |
TGAL-10747 | Clearing "Run As" credentials allows the workflow to run as default user even when the setting has been set to Require Credentials. | 2023.1.1.392 | Fixed |
TPRI-1927 GCSE-1429 | After upgrading from 2022.1 to 2023.1, the Tree Interface tool is not working when running in a chained app. | 2023.1.1.392 | Fixed |
TPRI-3074 | When you select the "All checked by default" option after clearing the existing selected options for an Analytic App, the previously made changes for list box are not retained on Re-run. | 2023.1.1.392 | Fixed |
TPRI-5145 GCSE-2082 | Chained apps on Server are run despite errors. | 2023.1.1.392 | Fixed |
TPRI-5380 GCSE-2151 | Under Interface Designer > On Success > No Output Files Message, No Output Files Message doesn't appear when running an Analytic App on Server. | 2023.1.1.392 | Fixed |
Fixed Minor Release Version 2023.1.1.422 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-11090 | When using a shared Run As credential, clearing the Run As checkbox and adding new credentials results in using the old credentials instead of the supplied ones. | 2023.1.1.422 | Fixed |
TPRI-5661 GCSE-2007 | The third chained app does not load the output file generated by the first app when running on Server. | 2023.1.1.422 | Fixed |
Fixed Minor Release Version 2023.1.1.437 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
GENG-3676 GCSE-2001 | Running a workflow with a Join tool as an Analytic App generates an error and crash report if the AMP engine is disabled in the Runtime settings. | 2023.1.1.437 | Fixed |
TCPE-1111 GCSE-2229 | After upgrading Server from version 2022.3 or lower to 2023.1 or higher, customers encounter the following error "Error running Event #1: Func 'curl_easy_perform' failed, ret = 8, desc = Weird server reply" for workflows with email event. | 2023.1.1.437 | Fixed |
TGAL-10286 GCSE-2039 | Workflows and analytics apps which includes macro gets converted into macro while publishing them using the following Server API endpoints: POST /admin/v1/workflows and POST /v3/workflows. | 2023.1.1.437 | Fixed |
TPRI-5954 GCSE-2346 | Tree tool in a chained app does not work when running on Server 2023.1 Patch 7. | 2023.1.1.437 | Fixed |
Fixed Minor Release Version 2023.1.1.460 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-1080 GCSE-2138 | When switching to different subscriptions and returning to the original one, existing schedules encounter an error stating: "You do not have access to this workflow. To request access, please contact the author or your administrator." | 2023.1.1.460 | Fixed |
TGAL-11282 GCSE-2344 | Crypto Migration Summary counts for PackageDefinitions and AppChunks do not match as expected. | 2023.1.1.460 | Fixed |
TGAL-11715 GCSE-2272 | Designer login to Server is not sending cookie or user data (user-agent) within request headers to certain endpoints for SAML authentication, including /aas/sessions. | 2023.1.1.460 | Fixed |
TPRI-5918 GCSE-1508 | Theme colors apply to curators only. | 2023.1.1.460 | Fixed |
Known Issues
Known Major Release Version 2023.1.1.123 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TCPE-373 GCSE-589 | Regression issue: PCXML previews are not rendering URLs in Server 2022.3+. | 2023.1.1.123 | Known |
TCPE-672 GCSE-1329 | Server UI Error on Japanese, Chinese, French, and Italian Operating Systems: An HTTP 500 error displays when you open the Server UI (for example, HTTP500 Internal Server Error: Cannot show this web page.) To work around this issue, change the language setting on the non-English operating system to English and install Alteryx Server. Change the language back to your preferred language after installation. | 2023.1.1.123 | Known |
TCPE-980 GCSE-1961 | Server UI is not able to display a preview for PCXML file if a URL or hyperlink is output to a Render tool. The following error occurs: "Error: Unable to Load Preview". | 2023.1.1.123 | Known |
TCPE-1231 GCSE-2488 | When editing existing scheduled workflows created a day before the current date, users are presented with an error. | 2023.1.1.123 | Known |
TCPE-1263 GCSE-2602 | Redirection for direct URL of workflow from "#!app” to “#!/app" does not occur at the first time access. | 2023.1.1.123 | Known |
TCPE-1295 GCSE-2690 | The POST /user/v2/inputfiles endpoint returns the error 'The Requested format is not supported.' when attempting to upload a file in PDF format. | 2023.1.1.123 | Known |
TCPE-1296 GCSE-2699 | Background color of timeslot details in Schedules > Forecast > timeslot is affected by Side Navigation Background. | 2023.1.1.123 | Known |
TDT-1842 TSPA-986 | App re-run functionality is failing for Map tool. | 2023.1.1.123 | Known |
TGAL-6394 GS-610 | Daylight Saving Time (DST) alters future interval scheduling of jobs/workflows. They are being pushed to the top of the hour when scheduled during the DST window of 2AM - 2:59AM. For more information about the DST change, visit Schedules: Time Zone Support. | 2023.1.1.123 | Known |
TGAL-6467 GCSE-464 | Daylight Saving Time (DST) is causing schedules to run at incorrect time in Server - schedules are shifted an hour forward or backward during the Daylight Saving Time. For more information about the DST change, visit Schedules: Time Zone Support. | 2023.1.1.123 | Known |
TGAL-6745 GCSE-723 | Server API V3: Setting “application/xml” or “text/xml” in the Accept header of the API request returns an error or does not return the results in the XML format. | 2023.1.1.123 | Known |
TGAL-6852 | Insights are not rendering on multi-node environments. When you open an insight and run a workflow in Designer and then want to publish it in Server UI, the URL link shows that the insight is not rendering and an error message is displayed. | 2023.1.1.123 | Known |
TGAL-6964 | When you re-run a Chained App on Server with the Re-Run button, the first app in the chain is shown instead of the last app in the chain. Before the fix to the Re-Run button, the last app in the chain was displayed and changes could only be made to the final app. | 2023.1.1.123 | Known |
TGAL-7052 TGAL-7018 | When you add or delete insights, the results counter is displaying incorrect count in the table. | 2023.1.1.123 | Known |
TGAL-7677 | Global search fails if the workflow / insight / districts / collection name contains special characters. | 2023.1.1.123 | Known |
TGAL-7825 | Insights might not render in multi-node environments and display the message "Error rendering insight. If this problem persists, please contact your Systems Administrator." To work around this issue, please ensure the Insights worker is enabled on your controller. | 2023.1.1.123 | Known |
TGAL-7846 | When Administrators upload workflows using the "+New" button in the Admin UI, workflows are not being validated as they were in previous versions of Server. | 2023.1.1.123 | Known |
TPRI-1298 | The View in Browser functionality is breaking from Designer after saving the workflow to Server due to a problem with token-based authentication. | 2023.1.1.123 | Known |
TPRI-1320 | Admin Jobs page is empty with no tabs. When a job is kicked off in Server, the job doesn't automatically appear on the Admin Jobs page in real time. In order for the job to appear, you must manually refresh the page to see the new job added to the queue. | 2023.1.1.123 | Known |
TPRI-1409 TGAL-7449 | The table height on the Admin Subscriptions page doesn't adjust automatically. | 2023.1.1.123 | Known |
TPRI-1481 | Link and Image Properties in Rich Text Editor under Admin > Pages and Admin > Districts are not localized. | 2023.1.1.123 | Known |
TPRI-1492 | App Re-Run button appears on all Job Runs instead of the latest job run. | 2023.1.1.123 | Known |
TPRI-1575 GCSE-1302 | System Messages do not appear at the very first login by a User. | 2023.1.1.123 | Known |
TPRI-1695 TCPE-692 | Regression issue: PCXML previews are not rendering URLs in Server 2022.3+. | 2023.1.1.123 | Known |
TPRI-3012 | The Cancel button functionality is not retaining the original values for the Single selection Tree tool before running the app for the first time. | 2023.1.1.123 | Known |
Known Minor Release Version 2023.1.1.200 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-8117 | Insights might not render in multi-node environments with the latest build of 2023.1 (Patch 1) and display the message "Error rendering insight. If this problem persists, please contact your Systems Administrator." To work around this issue, restart Alteryx Service. | 2023.1.1.200 | Known |
TGAL-8841 GCSE-1622 | Excel file output appears to be corrupt when retrieved from Server API call GET /v1/jobs/{id}/output/{outputId}. | 2023.1.1.200 | Known |
TPRI-2128 | When using the Re-Run or back button after running an analytic app (with Tree tool interface) in Server UI, the values that were entered are not retained in the Tree tool. | 2023.1.1.200 | Known |
Known Minor Release Version 2023.1.1.247 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-8244 | Admin Jobs Count is displayed inconsistently. | 2023.1.1.247 | Known |
TPRI-2444 GCSE-1519 | File Browser Tool: When using File Input, there is a noticeable delay in the Table/Sheet selection prompt without any indication that a large XLSX file is loading in the background. | 2023.1.1.247 | Known |
Security Updates
Fixed Major Release Version 2021.3.1.1.123 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-2207 | To be disclosed.* | 2023.1 | 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. More information will be made available once the vulnerability has been fixed for all supported versions known to be affected.
Fixed Patch/Minor Release Version 2023.1.1.281 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-8405 GCSE-1571 | Potential exposure of SMTP service credential within backend logs. | 2023.1.1.281 | Fixed |
TGAL-8498 GVM-584 | Potential XSS in Designer/Server Open Workflow interaction. | 2023.1.1.281 | Fixed |
Fixed Patch/Minor Release Version 2023.1.1.331 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TBO-1139 | Updated embedded OpenSSL versions to 3.0.8 (Engine, AMP) and 1.1.1t (v1 SDK). Addresses the following CVEs:
Go to https://www.openssl.org/news/openssl-3.0-notes.html and https://www.openssl.org/news/openssl-1.1.1-notes.html. Note: Alteryx Server relies upon the native Windows SChannel implementation for inbound TLS/HTTPS and TLS Service Layer communications. In a networking context, OpenSSL is used only in 1) outbound connections occurring as a result of Engine/AMP/SDK-tool execution during workflow runs, and 2) outbound connections to http://alteryx.com and http://flexnetoperations.com for licensing and activation. | 2023.1.1.331 | Fixed |
Fixed Patch/Minor Release Version 2023.1.1.392 | |||
|---|---|---|---|
ID | Description | Version | Issue Status |
TGAL-7140 | To be disclosed.* | 2023.1.1.392 | 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. More information will be made available once the vulnerability has been fixed for all supported versions known to be affected.