We've had a session yesterday talking about the studios removal and everything going to the collections in the Alteryx gallery. Also, if I'm not mistaken, a lot of standard configurations are going to be controlled directly by user groups and it will have a personal space for each user to use.
For me, the main concern are related to migration of bigger server structures with a lot of studios and collections and also the admin control of all the personal space .
What is your opinion? Do you see any negative sides to it? I think this is an optimal opportunity to talk about it and to give Alteryx dev team our opinion as well.
Thanks for posing this question @fmvizcaino ! I think about this topic every day, since I'm the PM for Server. Any feedback to make sure we have all the bases covered would be appreciated. We really want this to be a seamless transition to a better management model for you.
With regard to large installations, is your concern about how to automate the migration of those studio users into groups and those assets into a collection? We plan to offer some management API endpoints, along with some sample scripts, to help with automating this effort.
Or is there a different concern around those larger structures?
You also mention the admin control of the personal space...what are your concerns there?
I'd love to hear from other customers who are concerned with the new management model as well...let me also mention that I presented a session on this topic if you're interested.
Hi @JohnPelletier ,
That's so great that you are here! This was exactly what I was aiming for. Now we only need customers opinions as well. 😁
Since all is done with an API, I'm sure there will be a lot of insecurities in our customers related to the migration success.
The concern about migration is mainly related to the migration homologation. Here in Brazil, it is pretty common for companies to have a single-node production server with no test server, so it end up being a licensing concern, will Alteryx provide a trial license to help with the homologation process?
About the personal space, we have one customer that doesn't want their artisans to have a private studio for each one to use, so they have inserted all of them in a single studio and control all of them with a customized usage report in QlikSense. The suggestion here is to have a global button to eliminate personal spaces in the gallery.
@fmvizcaino To be honest, I had to look that word up, since I'd never heard it before (homologation). Essentially, you need to prove & certify that the conversion from private studio to user group was done correctly, am I right? I think it should be possible with the API that's coming soon...you can generate a report of which users are in the Private Studio and then another of the users that are in the resulting User Group, and compare the list. Will that work?
>>About the personal space, we have one customer that doesn't want their artisans to have a private studio for each one to use, so they have inserted all of them in a single studio and control all of them with a customized usage report in QlikSense. The suggestion here is to have a global button to eliminate personal spaces in the gallery.
Do they want to do this because they're afraid that too many workflows will remain un-shared? Is this a house-cleaning requirement, where your customers don't want workflows to be orphaned when a user stops using Server? What kind of usage are they trying to control? Sorry for so many questions, but this is challenging to understand...and I love a challenge.
And thanks for my Word of the Day: Homologate!
Hi @JohnPelletier ,
I think that would work, my only concern is related to those customers that needs to validate everything since it is a structure change. But if the API generates a quick report showing what was and what has become, we shouldn't have any problem.
Personal space question:
Yes! They don't want users to use the personal space as a production personal space. All the personal workflows will remain in their machine. The gallery will be IT controlled and they only want workflows aproved by them. I think a configuration button to globally remove the personal space would be enough, but I know this is a bit specific.
Here in Brazil it is a pretty common word and the literal translation is homologation, but I think the proper word is QA.
It would be great for you to present that in a session for the ACEs and get all their feedbacks. In my opinion, it would help you see the customer and partners side as well! What do you think @LeahK and @JohnPelletier ??