To Check or not to Check Data Connections in "Manage workflow assets" while Saving

[dataguyW]

I have asked a few different sources from consultants to Alteryx pre-sales and have yet to get a definitive answer on this so I'm hoping someone can provide some insight.

When you save a workflow to the gallery there are options at the bottom of the screen to "Manage workflow assets."    There can be many components here, but  just focusing on Gallery Connections, it will show a line with a checkbox for all gallery connections used within the workflow.    I can understand the file connections showing if used by in-db connections and since files normally need to be saved with the workflow.   C:\[whatever] that Alteryx would assume that this will not be on the server and bring a copy when publishing.   This is not a problem if accessing the file over a network share and this piece I do understand.

That being said, an Alteryx Gallery Data Connection is created with the intent that the connection details always come from the server at runtime.   My question is does it matter if this is checked or unchecked, because the action should be same regardless as in the code checks if the runner of the code has permissions on that connection and then it grabs the latest and greatest version before opening the connection.

Is there a difference or is there any possible way you could store a cached version of a connection with a workflow?

[jrlindem]

From what I understand:

Leaving it checked is going to use connections that are available on the server side.  So it's more referencing the "alias" of the connection but the actual connection info is on the server.  Connection alias needs to match up.

If you uncheck it, it's pulling the connections details along with your workflow at the time of running in accordance to what the user permissions are.

Regarding your cache'ing question...  I don't believe so.  It's either referential from the gallery or pulls the connection permissions for the user at the time of need.

Hope that helps, -Jay

[dataguyW]

I think it just feels backwards from in interface design standpoint.   A gallery connection by its nature is not up for discussion as to how/when connection details should be retrieved from the server.  If the user can truly embed the user/pass and other details this completely negates the usefulness of the connection.  From an administrator's standpoint the organization may end up with locked database accounts due to exceeding failed password attempts if a user "stores" a temp copy.

Files - Checked equals include file as part of workflow package while saving.

Macros - Checked equals include file as part of workflow package while saving.

Gallery Connection - Checked means it DOESN'T include connection as part of the workflow package while saving.

1. This may be my minor in human interface design, but I would argue the logic is backwards if it truly makes any difference at all.

2. There should never be a case where gallery connection information can be stored(cached) while saving so don't show it the assets as an option.

[jrlindem]

Can't say I disagree with you!  Just one of those quirks to get used to!  -Jay

[dataguyW]

Agreed!   I guess it along the same lines as Alteryx boolean return values that can be 0, 1 or -1.   I may never know what the build team was thinking.

[jrlindem]

hahaha, yes!  So true.  Another head scratcher, for sure.