Skip to main content
  • 2024.2
  • Server
  • What's New in Server 2024.2

What's New in Server 2024.2

Version: 2024.2

Release Date: October 30, 2024

Go to the complete Server 2024.2 Release Notes.

New Features

UI Filter and Sort for Workflows, Schedules, and Jobs

We improved our searching and sorting capabilities on Server for both admin and non-admin users, enhancing the overall experience of the Server UI. Now you can do the following with ease:

  • Filter by AMP or E1 on the Schedules page and My Workspace (My Files, Shared With Me, Public).

  • We’ve added an Engine column to Admin homepage > Jobs where you can filter by AMP or E1.

  • We’ve enabled Type field sorting in Server UI > My Workspace (My files , Shared With Me, Public), and on Admin homepage > Workflows.

  • We’ve added Engine filter on Admin homepage > Workflows (Private, Public, All).

For more information, go to Search for Assets.

Display Recent Workflows in the Add Workflow Dropdown

When you add a workflow to a collection, you will now see a list of your most recently uploaded workflows in the 'Add Workflow' dropdown menu.

  • When you open the "Add Workflow" pop-up, a drop-down menu appears showing the 10 most recent workflows until you start typing in the search bar.

  • The workflows are sorted based on the last uploaded date, ensuring that the most recent and relevant workflows are easily accessible.

For more information, go to Add Workflows to a Collection.Add Workflows to a Collection

File Browse Improvement in Analytic Apps

If you upload an XLSX file larger than 200 MB via the File Browse tool in Analytic Apps, it might cause performance and loading issues. The following message will be displayed to inform you of potential performance issues: Large file sizes are more likely to experience performance/loading issues in Server when using File Browse. This might cause the application to error.

Ability to Resize the System Settings Window

We enhanced the System Settings window. You can now use the following resizing options:

  • Easily maximize the System Settings window to full screen or minimize it to the taskbar using the newly added buttons located at the top right corner of the window.

  • Adjust the size of the System Settings window by dragging the edges or corners with the resizing arrows.

For a more user-friendly experience, we have optimized the initial behavior of the System Settings window. The first time you open System Settings, it will automatically open at a size that fits your screen perfectly and will be centered on your screen. No buttons will be hidden.

New Admin Settings: Timeout to Cancel Jobs

We added new options in Settings in Server UI: Cancel Scheduled Jobs Running Longer Than and Cancel Manual Jobs Running Longer Than. As an admin, you can specify timeout values after which scheduled and manual run jobs should get canceled. To do so, go to Admin > Settings > Assets.

We enabled the System Settings for manual run jobs as well. Previously, it was allowed only for scheduled jobs. Now, these added admin settings are applied at system level. We continue to have the timeout values in System Settings (under Worker > General > Cancel jobs running longer than (seconds)) which is useful in a multi-node environment. If a timeout value has been configured on the Server UI, this will be set across all workers. However, if a timeout value has been set on the System Settings on a particular worker, this will override the UI values.

For more information, go to Alteryx Server Settings and Worker.

Migrate Data Connections and Workflows to DCM

To simplify the shift from Data Connections to DCM Connections, starting with the Server 2024.2 release it is possible to migrate all Data Connections and respective workflows to be replaced by DCM Connections. First, it is necessary to migrate each data connection and then trigger the migration of workflows. Checking our Maveryx Community blog post How to migrate Server Data Connections to DCM might help you understand the journey better.

For more information, go to Data Connections.

Server API Updates

New API Endpoints for Subscriptions (Studios)

We've given admins the ability to manage studios using Server V3 API endpoints. These APIs will help you edit studios in bulk and provide you with the ability to move individual users back to individual studios.

  • GET /v3/subscriptions: This API endpoint enables to retrieve all subscription records. As an admin, you will be able to fetch the data based on optional input parameters such as Subscription Name , Shared Schedules Enabled (true or false), Default Workflow Credential ID, Number of Workflows, and Number of Users.

  • GET /v3/subscriptions/{subscriptionId}: This API will help admins to look for an existing subscription. To search for a subscription, you need a subscription ID.

  • DELETE /v3/subscriptions/{subscriptionId}: As an admin, you can now delete subscriptions using the DELETE /v3/subscriptions/{subscriptionId} API endpoint.

  • PUT /v3/subscriptions/{subscriptionId}: As an admin, you can update existing subscriptions using the PUT /v3/subscriptions/{subscriptionId} API endpoint by specifying input parameters.

  • POST /v3/subscriptions: To create a new subscription, use the POST /v3/subscriptions endpoint. As an admin, you can create a new subscription with the following details: Subscription Name, Shared Schedules Enabled (true or false), and Default Workflow Credential ID. Once this API is executed, a subscription is created.

  • PUT /v3/subscriptions/{subscriptionId}/users: As an admin, you can move users (multiple as well) across studios using the PUT /v3/subscriptions/{subscriptionId}/users API endpoint.

For more information about these endpoints, go to Subscription Endpoints.

Workflow Endpoints Updates

In order for users to maintain provenance of workflow changes, we now return SourceAppId in the response body of the following API calls:

  • GET/v3/workflows

  • GET/v3/workflow/{workflowID}

  • GET /admin/v1/workflows/migratable

Furthermore, non-Curators can successfully make the GET v3/workflows/{workflowId} call for workflows they have access to. Previously, this was limited to Curators only. For more information, go to Workflow Endpoints.

Share Workflow Job Messages to Curators via API

We updated API endpoints to enable Server admins (Curators) to help their Alteryx users with troubleshooting failed workflow jobs.

  • When querying the GET v3/workflows/{workflowID}/jobs endpoint, users can now optionally filter by status and resultCode to get back a list of jobIds that correspond to these filters.

    • status: The overall status of the job execution. A completed job might still have failed. Allowed values are: "Complete", "Error", "Running", and "Queued".

    • resultCode: The result code of the execution of a workflow. This can indicate a failed workflow, but a successful job. Allowed values are: "Success", "Error", and "Warning".

  • Once a jobId is identified, a Curator can call the new API endpoint GET /v3/jobs/{jobId}/messages and use the jobId as an input parameter to retrieve the corresponding messages for that job. Only Curators can use this new endpoint.

  • To mirror functionality between the Server API and UI, we updated the GET /v3/jobs/{jobId} endpoint so users can see the jobs that have been shared with them via Collections.

For more information, go to Workflow Endpoints and Job Endpoints.

New API Endpoint to Update Schedules

We created a new API endpoint PATCH /v3/schedules/{scheduleId} to make it possible to update a schedule without having to populate several required fields to make a single change. For more information, go to Schedules Endpoints.

New Admin Setting: Restriction to Make Workflows Public

We added the Restrict Public Workflow (Global) setting under Admin > Settings > Security. Admins can now control the way workflows are getting published - either publicly or non-publicly. To control workflows availability to other users, select or clear the Restrict Public Workflow (Global) checkbox. For more information, go to Server Settings.

Bulk Delete for Workflows, Workflow Results, Schedules, and Collections

We added the Bulk Delete functionality for Workflows, Workflow Results, Schedules, and Collections. This allows you to delete multiple records at once. This functionality is added to the following pages:

  • Workflows and Workflow Results

    • Admin homepage > Workflows > available for all three tabs: Private, Public, and All

    • User homepage > My Workspace > available for My Files (not available for Shared With Me and Public)

  • Schedules

    • Admin homepage > Schedules > available for Schedules and Designer Migrations

    • User homepage > Schedules

  • Collections

    • User homepage > Collections

You are now able to multi-select a workflow, workflow results, schedules, or collections using the checkbox present in each row and delete them from the page.

Before you delete the records, an alert pop-up appears for final confirmation. Once selected records have been deleted, a snack bar message displays confirming that the selected records have been successfully deleted.

Please note that users are only able to delete workflows and schedules to which they have ownership rights. Admins can delete any workflow and any schedule. If you select multiple records, the 3-dot icon present on all records will not be displayed.

For more information, go to Delete a Workflow, Delete a Workflow, Delete, Disable, or Re-Enable a Schedule, Edit or Delete a Schedule, and Delete a Collection.

New Configuration Setting: One User per Studio

For admins, we added the option to turn off shared studios by limiting the users in a studio to one. As an admin, you can now easily transfer asset ownership by transferring the workflow from one studio to another. You can then track the workflow sharing through credentials.

To limit the number of members in a studio to one user, go to Admin > Settings > Configuration > Users. Then select the Limit Studio to 1 User checkbox. For more information, go to Server Settings.

Toggle to Show Read and Unread Notifications

We’ added a new functionality to Notifications in the upper right corner of Server UI. If you want to show only unread notifications, select the Only show unread toggle. For more information, go to Notifications.

“AMP” Column Name Renamed to “Engine”

We updated the AMP column present on various pages (such as Workflows, Schedules, and Workflow Results) to “Engine“. This column now displays the name of the engine: AMP or E1. In the previous versions, this column depicts whether a workflow is AMP enabled or not.

Loader/Spinner on Output Window While Running Analytical App

We’ve added a loader/spinner icon to the output window while running an analytical app. This depicts that job is in progress and running.

In this section: