I have a question about how everyone is managing the creation of new stuff in Customer Insight - Journey, the best way to use it is following all the DevOps processes (Dev-QA-Production) for the content, but the Marketing area is having questions about whether this is time-effective because of all the things that the Module has for testing (like email test send).
If you ask me, It should be a middle point, having stuff that needs to go through the lifecycle and others not depending on their complexity, just imagine Marketing wants to send an Email and that has to go through dev-qa until prod or qa-prod...
What are your guy's guidelines for your Marketing users? What they can do directly in production and what not?
The Customer Insights - Journeys app is built on top of the Dynamics 365 platform. Follow the environment and development strategy recommended by the Dynamics 365 platform when adopting Customer Insights - Journeys. You can find more details about Dynamics 365 platform administration and environment strategy in this Power Platform Admin and Governance whitepaper [section: Platform architecture].
Customer Insights - Journeys customers often maintain a development environment, a test environment, and a prod environment. The various environments help to:
Set up security boundaries and provide environments with flexibility for change management. For example, in a development environment, you might allow multiple customizations. But in prod, customizations are restricted to ensure a fully stable environment.
Test upcoming features in a non-prod environment.
Address DevOps issues without putting the prod environment at risk.
I hope you can mark my answerverifiedif it is helpful! If you have any questions, please feel free to contact me.
Regards,
Leah
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
3
Share
Report
All responses (
Answers (
