You’re offline. This is a read only version of the page.
I have CoE setup in both a prod env and a test env. The "ProductionEnvironment" flag is set to Yes in prod env and No in test env. Everything in test env checks out and is working. Now I'm doing some final setup in prod env but don't want to accidentally turn on flows and accidentally find that I've sent thousands of emails of all sorts (welcome, governance, cleanup, no-owner etc...) and was thinking about setting ProductionEnvironment var in the prod env to No also, since the CoE describes the purpose of the flag to suppress email going in (and in some cases redirecting it to the PP Admin (me). Has anyone done this? Does anyone see a problem with it? It seems a lot easier to turn that one variable from Yes to No (and then back when 100% ready to go live) then to try and hunt down each and every flow that might send email. Any thoughts on that approach? Seems it would allow final prod setup and checkout of all flows, without danger of sending emails before we want them to go out (after the official launch of the CoE to all). Does that ProductionEnvironment flag affect anything that I would care about for the few days it will be changed?
Hi,
both approaches are correct. Set this Env variable to No is helpfull to review the mails that will be sended to end-users and confirm that will be correct. It's very important as you know don't disturb our users with incorrects mail or without information to the steps to follow when are received.
Other strategy like comment @ptansey is to gradually open the environments to the coe solutions.
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Regards
Alberto
Great question and I'll be interested in what other more experienced members have to say if any chime in.
I wrestled with the same concerns about flipping the switch and going live in production. What I chose to do was Exclude all but one or two environments from the governance flows and left the Welcome email flow off until I'd tested with a handful of users. Once I confirmed the compliance and inactivity processes were working, did some training with our most active Makers and have a heads up to our IT department, I flipped the switch and went live.
No idea if that's typical but it worked well for us as far as I know. I'm not getting a flood of issues from our users. Apps/flows are being approved for deletion, compliance details are being updated, etc. Seems good so far!
#1
bscarlavai33
5
Super User 2025 Season 1
#2
Michael E. Gernaey
4
Super User 2025 Season 1
#3
Vince_K
2
Share
Report
All responses (
Answers (
