Free Trial

Analytics

News, events, thought leadership and more.
_PavelP
Alteryx
Alteryx

In the ever-evolving landscape of data analytics, managing connections across different server environments can be a complex and time-consuming challenge. We understand the pain points when transitioning workflows through your SDLC pipeline. That’s why we’re thrilled to introduce a powerful feature in the 2024.1 release, Environment Connection Handling in the Data Connection Manager (DCM). This feature is a game-changer for managing connections across different server environments, making it easier than ever to transition your workflows across the Alteryx SDLC pipeline. 

 

What is Environment Connection Handling? 

 

Environment Connection Handling allows you to define connection rules specific to each server environment. Whether you’re working in Alteryx Designer or deploying workflows to various servers, this feature ensures that your connections are dynamically adjusted based on the environment. Let’s dive into the details: 

 

  1. Seamless Transition: Easily transition your workflows across different environments without disrupting connections, saving you time and reducing the risk of errors.  
  2. Centralized Management: Define and manage all your connection rules from a single location, providing a unified view of your entire environment landscape. 
  3. Increased Productivity: By automating connection adjustments, you can focus on delivering value instead of managing repetitive tasks. 

 

🎥 Watch the demo video to see Environment Connection Handling in action:

 

 

Get Started Today 

 

Ready to streamline your connection management and accelerate your SDLC pipeline? Start leveraging this feature right away!  

Update your Alteryx Server to version 24.1, set up your rules, and experience the benefits firsthand. 

 

Learn more about Environment Connection Handling 

 

Stay connected for more exciting updates and enhancements from Alteryx as we continue to revolutionize the world of data analytics! 

 

Comments
Yongcan
8 - Asteroid

That's killing feature which means when migrate the workflow with data connection between environments won't require 'Find and Replace' , cause now the  'Find and Replace' is performed during gallery run.

 

Haven't get chance to play on 2024.1 yet:

1.How is could help during Designer run as mentioned in Demo?

2.Any other environment related entry are supported like the system connection? and is it possible for other entries like net share drive path?

 

 

_PavelP
Alteryx
Alteryx

Hello @Yongcan ,

Thank you for your enthusiasm about the new Environment Connection Handling feature in Alteryx 2024.1! I’m glad to hear that you recognize the potential of this feature to simplify the migration of workflows with data connections between environments.

To address your questions:

  1. Designer Workflow Execution: When running workflows in Alteryx Designer, the Environment Connection Handling feature doesn’t apply, so workflows will indeed run with the referenced DCM connections.

  2. Supported Connections: As of the 2024.1 release, the Environment Connection Handling feature supports DCM Database connections. Other types of entries, such as system connections or net share drive paths, are not currently supported by this feature.

I hope this helps clarify your queries. I encourage you to update your Alteryx Server to version 24.1 to set up your rules and experience the benefits firsthand. Stay connected for more updates and enhancements from Alteryx!

simonaubert_bd
13 - Pulsar

Hello @_PavelP 

I'm trying to use the DCM Connection Handling but I don't understand how you configure the source connection id
image.png

From the documentation, it's Enter Source Connection Id - the Connection Id present in the workflow. It doesn’t have to be present on the current environment. It can’t be used in any other rule as either source or target connection.

But correct me if I'm wrong, the ids are technical (and not even visible, so I guess we have to go in the xml to find it??) and several users can have the same id for totally different connection ? (let's say user A has id 1 : sql server and id 2 oracle..... user B can have id 1 postgresql and id sql server) Am I wrong somewhere? Really unclear for me.
Best regards,

Simon