Alteryx SDLC Collection Organization for Migration

[alishadhillon__]

Hi, 

I'm trying to figure out the best way to organize the server collections to both meet the needs of DevOps and the business user.

We are migrating workflows from the

1. Local machine > pre prod server (Collection QA)

2. Pre prod server (Collection QA) > Prod server (Collection UAT)

3. Prod server (Collection UAT) > Prod server (Collection Prod?)

Rather than having a single collection at each stage or even prod, I'd like to separate it to several collections by business unit as this makes the most sense with permissions and organization. This feels like a must have at the final stage where the business user interacts with a workflow at most. I don't quite know how this will impact the DevOps SDLC life cycle across the different environments and migration.

Can anybody offer any advice?

[fmvizcaino · Accepted solution]

Hey @alishadhillon__ ,

There is no impact on having a set of additional collections on your prod server.

You will only need to be aware of the data connections and credentials being used on a workflow. And for that, I suggest managing through user groups (one user group per business unit + one for DevOps) to make it easier.

Your DevOps team will still have access to the workflow through the Collection UAT and the business users through their specific collections.

If your DevOps team is updating a workflow already shared with a business rule, they need to know the following rule:

https://help.alteryx.com/20221/server/workflow-version-history

You can have the published version used by the business users and the latest version tested by the developers simultaneously. For all developers to have access to the latest version of the workflow while testing, they MUST be in the same private studio/subscription (this is something being removed from Alteryx Server soon and maybe another feature will replace it)

https://help.alteryx.com/20221/server/subscriptions-studios

Best regards,

Fernando Vizcaino