Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.

Upgrade to 2023.1 - And DCM question

summarizer
9 - Comet

We are about to upgrade to 2023.1 in 2 weeks.  I have read that any non-AMP workflows will still run on the new AMP-enabled Gallery (yes, we will have AMP on).  Has anyone else gone through this transition and could you list any major issues you might have seen?  We're upgrading on a Friday night and I am hoping scheduled workflows (non-AMP) will work like normal come Monday morning.  We understand some users will want to update workflows to AMP and review and reconcile the behavior differences caused by certain tools.

 

Also, we have never used DCM and thinking we might try it.  Most of our data connections are unique to the user, so the idea of "sharing" them does not fly.  Do you love it, hate it? Why?

 

Appreciate any insight. Thanks!

 

3 REPLIES 3
fmvizcaino
17 - Castor
17 - Castor

Hi @summarizer ,

 

Just a few questions before my answer.

What version are you upgrading from?

As for data connections, are you using the Gallery Data Connections or does each user create his own DSN connections?

Are the users sharing workflows with data connections through collections?

 

Best,

Fernando Vizcaino

summarizer
9 - Comet

Thanks for the reply.  We are upgrading from 2022.1.  And each user has their own connection that uses a unique password, so no sharing.  And while a workflow may be in a Collection to be shared amongst members of a team, a user would have to download it and change to their connection(s) to use it.

fmvizcaino
17 - Castor
17 - Castor

Hi @summarizer ,

 

The AMP engine became the default engine on 22.1 but that only means that the engine will be enabled by default. If your server is already configured to use both engines (AMP and E2), all your workflows will run as they should.

 

As for DCM,

  • Each artisan has his own DCM to manage and they can share their connections with other users, but only to run workflows on the gallery, these users can`t use the connections on designer.
  • Curators have no way of knowing what the users are doing with their own connections, so you lose a little of governance there.
  • Databases and credentials are now two different things, so let`s say a user has 20 connections and needs to change his password. With DCM, you only have to do it once.
  • It is not only for ODBC and OleDB connections but also for the cloud connectors. Not only passwords but tokens, secret keys, etc

 

Best,

Fernando Vizcaino