Logical or Physical partitioning of workflows and data in Server

[vam_15]

Hi,

Is there any way we can segregate the workflows and data of Alteryx Server based on user groups / user accounts ?

Use case:

We have 2 user groups: Each user group shouldn't see or access other user groups workflows and data.

Its confidential data hence need segregation?

AS-IS:

Its Single AWS instance only, cannot change physical instance.

User size : one UG - 2 users

                   another User Group - 5 users 

Is there anyway we can do physical or logical partitioning ?

Any reference material will be helpful.

Thank you,

Regards,

Vam

[CiaranA]

What version of Alteryx Server are you on?

In the pre 2022 versions you were able to use Private Studios (Subscriptions) controlled via RBAC / AD Groups / Service Accounts set up as run as on the Studio level which meets this requirement. Collections should also have this capability I am assured post 2022 versions (as Studios are being merged into Collections)

[FlorianC]

Hi @vam_15,

@CiaranA is correct and the proper method to segment workflows is to use collections. Those will essentially act as a file system with separate folders for each user group.

In your example, you would create two user-groups as well as two corresponding collections, then assign permissions so that each group only has access to their respective collection.

[vam_15]

Thank you Florian!!

Question 1: 

I have another query, currently our Alteryx solution is managed by third party  in AWS.

We want to migrate the workflows from third party AWS Alteryx server(server ver 2021.1.2) to in-house AWS Alteryx server(ver 2019.1.4)

If we migrate the workflows from higher version alteryx server to older version alteryx server , will it work ?

Constrains:

We cannot upgrade our 2019.1.4 version server

Even if we are able to migrate to older version, our users desktop designer has ver 2021.1.4, will this works ?

Question 2:

In one thread, saw there is an Gallery endpoint API to migrate workflows, can we migrate from one third party server account to in-house server account, both servers are in 2 different AWS accounts. BUT both AWS accounts are connected via transit gateway.

 Need your valuable inputs, Thank you in advance.

Regards,

Vam

[CiaranA]

RE Question 1 - No the workflows need to be downgraded from my understanding (especially as there is quite a big gap between 2021.3 version and 2020.4). You can download all workflows in one API call, then edit xml of each workflow (either in batch or individually) then republish manually or programmatically. If any workflows are using tools that are edited / new in version 2021.3 then the downgrade will not work. 

[FlorianC]

Hi @vam_15,

@CiaranA is right again. Using the Alteryx Server API, you can design a process to retrieve all workflows from the third-party instance, update the workflow file (YXMD) to replace the version number, then publish the files to the target instance. As long as you have access to the two instances, you will be able to achieve this.

Note that this is not a small task and will require significant effort to build and test before deployment.

The main issue is that because there is a mismatch in version between your Designer clients and Server, users will not be able to publish workflows unless they manually repeat the same step to update the version number in the underlying XML (assuming again that there are no new tool or feature being used).

Could you please elaborate on the reason why you cannot upgrade from 2019.1.4? We would advise to have the entire estate running the same version, but also to upgrade to version 2022.1 which comes with a lot of improvements both in terms of performance and user experience.

Please do reach out to your account representative and we can help you define a strategy to move forward.