CoE Admin | Welcome Mail - Default vs Production Env

(0) Share

Report

Posted on by Pitfrog91

Hi Guys,

I am currently implementing the CoE and trying to understand everything.

Right now we want to onboard our new makers when the created something on the Default Env as well and not only on a Prodcution env. Unfortunately, the flow that is premade contains an If-Statement whether the environment is of type Production when a new record in the table "Maker" was created.

First of all: why is this so? Wouldn't it be better to onboard every new maker to guide him and to expose him to the internal maker community? I mean most of new makers will tinker on the Default env to try some stuff out.

So, a simple question is the Default env a production env? If not, will this flow still send the mail to new makers who have created something on the Default env?

Thanks for your help 🙂

BR Pitfrog

Categories:

Governance & administering

I have the same question (0)

All responses (5)

Answers (1)

Devikumari Krishna 988 Super User 2024 Season 1 on at

Like (0)

Report

Hi @Pitfrog91 ,

Default environment is usually a sandbox environment and not production environment.
To avoid email triggers from Default environment - Simply disable the plugin/workflow/ power automate flow which is triggering the email.
You can have the email generated on Production alone by leaving the trigger enabled.

------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give kudos.
My Blog: Dynamics 365 Key Topics – https://d365topicsbydk.com/
My Youtube Channel : https://www.youtube.com/channel/UCxSIryP2ah2VpEFr-Z72t1A

Regards
Devi

Was this reply helpful? Yes No
Pitfrog91 18 on at

Like (0)

Report

Hi @DeviKrishna ,

I want that this flow triggers as well on the default environment. How to achieve this?

Was this reply helpful? Yes No
Binaryjam 6 on at

Like (0)

Report

The Welcome Email fires every time a Maker is Added. Makers Are Added whenever it discovers one of the resources, like a flow app pva custom connector. They all ahve to have associated Makers. This is done for every environment, Including the default envronment, its type is "Default" it is not a sandbox its considered production.

When the Welcome Email is checking for "Production" it is looking at the Environment Variable in the Environment that the COE Toolkit is installed in , not the environment of any app or flow, If this is set to production then the users get emails, if its not production then the Admin User (another env var) is going to get MailBombed.

You might have an older version, than I'm checking, ensure you are on the v3 version as thats being supported by the COE team if there are bugs, you can report them on the github repo.

If you are on the later version V3, then you can check the Environment Variables are all set, if you have missing variables, it might cause the flow to fail. Use the Command Centre - Admin power app and check the variables and check the variables are correct.

You can check the flow runs to the welcome emails in the core solution. It might be failing cos those vars are not configured. The Solution should tell you this also with warnings.

Was this reply helpful? Yes No
Devikumari Krishna 988 Super User 2024 Season 1 on at

Like (0)

Report

Hi @Pitfrog91 ,

Add the flow to a solution. Export the solution and import it in default environment.
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

My Blog: Dynamics 365 Key Topics – https://d365topicsbydk.com/

My Youtube Channel : https://www.youtube.com/channel/UCxSIryP2ah2VpEFr-Z72t1A

Regards
Devi

Was this reply helpful? Yes No
Verified answer

Hamish Sheild 3,005 Most Valuable Professional on at

Like (0)

Report

Hi @Pitfrog91

I'm not sure if you have got the answers you need from the replies above. Hopefully this will give some clarity...

@Pitfrog91 wrote:

Right now we want to onboard our new makers when the created something on the Default Env as well and not only on a Prodcution env. Unfortunately, the flow that is premade contains an If-Statement whether the environment is of type Production when a new record in the table "Maker" was created.

First of all: why is this so? Wouldn't it be better to onboard every new maker to guide him and to expose him to the internal maker community? I mean most of new makers will tinker on the Default env to try some stuff out.

The Admin | Welcome Email v3 sends emails to all makers who create an app, flow, custom connector, or environment (of any type) for the first time. The Production env if statement in the flow is considering whether the environment that your CoE toolkit is installed in, and hence that the Admin | Welcome Email v3 flow is currently running in, is a Production environment or not. By default this Environment Variable is set to true but some organisations will have Dev and Test CoE environments and they will not want welcome emails sent from those environments, so the Production Environment Environment Variable is set to false in those environments.

@Pitfrog91 wrote:

So, a simple question is the Default env a production env? If not, will this flow still send the mail to new makers who have created something on the Default env?

The Default environment is NOT a Production environment. The Admin | Welcome Email v3 flow does send emails to makers who create items in the Default environment.

Let's break down the flow....

1. Flow is triggered when a Maker is created - a Maker is created when a Power Platform component (app, flow etc.) is created in any environment.

2. The variable is set to whether the current environment that this flow is running in is a prod environment or not (as determined by the Production Environment environment variable your CoE environment)

3. The email is sent to the Maker if the current environment that this flow is running in is a prod environment

Was this reply helpful? Yes No