In this release, we are excited to announce the features that matter the most to our customers. In 24.2, we focused on 3 key themes:
- Enhancing our scheduling capabilities
- Empowering Admins to manage access to Server assets while providing greater transparency
- Showing some love to our Server UI
Showing some love to our Server ideas! (Source: GIPHY)
So let’s get into it...
How are we enhancing our scheduling capabilities on Server?
First mentioned on Community in 2017 by @The_Dev_Kev_Env, users can now use the existing V3 schedules API to create a schedule for Analytic Apps with input parameters. Save time by creating one schedule to give back the results that you care about. Set your parameters once and schedule to run at the times you need it the most!
To simplify the updating of a schedule via API, we have created a new Patch API that allows users to update a specific field they want without having to update others. For example, you can now choose to enable or disable a schedule without having to input the iteration details. This will reduce the time needed to make simple schedule updates.
How are we empowering our admins?
Control Server resources by setting a “Timeout for manually ran jobs” as described in this Community idea from @joanatpsantos. We are giving admins the power to manage the jobs queue and effectively deal with jobs that are “stuck.” On top of the current timeout setting for scheduled jobs, users can now set a timeout period for jobs manually run on Server, including those triggered by APIs.
Admins (like @AnupD) have also been asking for a feature to limit users when publishing public workflows. You can now lock down all workflow-related data and control user permission to make a workflow public with the new “Global restriction for public workflows” setting. This also allows Server admins to protect sensitive information contained in the workflow metadata from unauthenticated users.
You can also now retrieve all Server job messages through our new API: /v3/jobs/{jobId}/messages. We are eliminating the barriers Server admins face when accessing workflow results in troubleshooting workflow errors. This API provides the level of control and visibility needed to effectively manage their Alteryx Server. As part of this work, we have also added a Status filter to our existing GET v3/workflows/{workflowId}/jobs API, making it easier for our admins to identify erroneous jobs.
We have released a series of exciting new APIs related to studio management to support Community requests such as this one from @craigbloodworth. Amongst other things, Server admins can use these to migrate from a studio-based approach to a collection-based approach for sharing and simplify the transfer of asset ownership.
Giving some love to our Server UI
Our Community has been actively engaged and has become a rich resource for ideas in improving our Server Product Quality.
With ideas such as this one from @markashman, we have included a Read/Un-read Toggle to improve the visibility and management of Server notifications. Now, users can easily differentiate between new and old notifications, improving our customers’ overall user experience.
We have also introduced bulk operations, starting with bulk delete (as discussed here). Instead of using APIs or deleting one workflow/schedule/collection at a time via the UI, users can multi-select their desired assets and delete them in one click.
When an admin changes the configuration of Server, they can now navigate System Settings more efficiently with more resizing options. This is especially valuable when using VMs to host the Server with various screen resolutions and sizing settings.
With our commitment to improving our search and sort capabilities on the Server UI, we are focusing on the Engine this time. With the introduction of AMP, we are making it easier for admins to understand the impact this might have on Server resources.
With 24.2, we show a list of recent workflows when adding workflows to a collection via the dropdown option. With this new feature, customers won’t need to think about the name of workflows; instead, they will be prompted with various options, creating a smoother experience.
We are so excited for our customers to try out these new features in 24.2. Please continue to engage with us on Community through the Server ideas forum!
