We're in the process of implementing Control Groups in our environment. To start, I've created a global "Second Stage" control group, that essentially acts as a default for internal staff. I'm trying to lock down some elements for rental clients, so we can't simply revert back to "Default Control Group." However, we are now experiencing problems with our triggered email campaigns that are referencing output sets in this new control group. Manual emails are firing just fine when using an output set with the new control group, but the lists aren't importing properly for triggered campaigns associated with the Second Stage control group.
My Wordfly Service user in Security is still setup in the Default Control Group, and a part of the System Administration and Web API user groups. The System Administration user group is associated with the Second Stage control group and is set as the default. The Web API user group is also associated with the Second Stage control group, but there IS NOT a default selected. Should it be? Would setting a default have catastrophic implications on our website? I can make this switch in test, but that won't help us in testing the Wordfly issue - as we only have one instance.
ANYWAY if anyone has extensive experience with WF triggered emails and control grouped elements, I would love to hear from you. We're self-hosted on v15.1.3 if that has any impact on things...
Thank you!
Emily,
Welcome to control groups! They take a little setting up to get going, but are highly useful once you get them going. We use them both from a consortium standpoint as well as to separate things like Development data from Box Office data (e.g. not ALL staff need to know exactly what amounts our highest level donors have been giving us).
As for setting a default, unless you have a very strange web set-up indeed, that should not matter at all for your website. Typically, all the default control group does is become the selected choice in the "control group" dropdown when creating something new (e.g. creating a new list would then have the Second Stage control group selected by default, and to go back to the "default" group, one would have to manually change the selection). So, for your users, it might make sense to have their default control group set as the Second Stage one, but having a default is not necessary for the WebAPI. Ours certainly has no default; as long as it has access to the control group, which it sounds like yours does, you should be good there in terms of access.
I do not have tons of experience with Wordfly triggered e-mails, though, so I cannot help you much there. Regarding your Wordfly Service user Control Group assignment, my understanding is that that is only used in solicitor/user dropdowns and so should not matter here either. So this may not help with the Wordfly side of your question, but hopefully that at least helps with the control groups part. I suppose if you can log in via the Wordfly user and verify that all the data you want to get out is still there, that would be my starting place.
Best of luck,
John
Thanks for the information, John! Per your post a support ticket, I did try ticking the default box for the Web user, but we're still having issues with our triggered campaigns. :( I'm back-and-forth with both the network and Wordfly support now.