This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We are updating the requirements for Community registration. As of 7/21/21 all users will be required to register a phone number with their My Alteryx accounts. If you have already registered, you will be prompted on your next login to add your phone number.
Hey there, it’s the Product Team at Alteryx! Did you hear @russell_christopher, Senior Director of Product Management, talk about Server.Next at Inspire this year?
We’d love to know what excites you the MOST when it comes to Server.Next? Below is a small sample list of features (don’t worry if you don’t see something, this is just a sample). Which one will make the most impact if your team had Server.Next today?
Sites: A collection of users, groups, and assets that provides complete data segregation for an organization. While a user may be a member of multiple sites, assets are never shared between sites.
Virtual File System: Able to save workflows and apps on in the system and also share those folders with groups or individuals
Custom Roles and Permissions: The ability to customize roles and permission for groups or individuals
Enhanced Search Capabilities: Easily search for assets, data, and apps across the site.
Share Workflows and Apps
Modern Tech Stack: PostgreSQL, not Mongo
Metadata Loaders and Data Cataloging: Unified and user friendly way to extract metadata from a data sources
Designer Integration: Seamless transition from Server.Next to Designer (i.e. Take a workflow from Server.Next and use it in designer with 1 click)
User Management: Easily manage users on a site through a comprehensive user interface.
Bringing the powerful features from various Alteryx products into Server.NEXT is a massive step forward! Modern tech stack and search & collaboration features known from Alteryx Connect sound really exciting.
I agree with @patrick_digan - moving to a relational data store is the biggest piece for us from this list - also hoping for strong SDLC support; unified version repository across dev/uat/prod; and canvas-level-dependency management for shared assets in later versions.
@cgoodman3- the current Server product utilizes an analytic app to display that information. In Server.Next, it will be similar, but not utilize a workflow to obtain that information (likely built in a diagnostic view). How often do you utilize this functionality? How would you like to use it in the future? Thanks for commenting on our post!