Agree with the idea of having the possibility to use a variable instead of a hard-coded flag.

Hi João,

Thanks for your feedback.

In which use case you would log the email content but after a X period of time you don't want anymore that log? Is that in a scenario of new application and for the first couple of months you want a log?

Thanks

Hi Fernando,

That scenario that you suggest is a valid one. The after go live of a functionality or application is a moment with more monitoring. When you are in a DevOps reality these type of agility is even more appreciated. 

An expression instead a direct yes/no option gives, imho, more agility. Imagine a scenario where the same email works as a template and renders different content depending on some ruling. You can apply that behavior also on the decision of logging the email.

João 

Hi Fernado,

If you feel that can help, let’s schedule a session where we could brainstorm better this functionality.

João.

Hi João,

Thanks for your availability, at this moment I would like to understand if the community see this idea as a good improvement or would be more hassle to have another configuration. 

I do understand your constraint of having to deploy to affect that hardcoded value. But unless we get some more votes on this idea we cannot give this idea a higher priority.

Regarding the final solution maybe could be a setting on Service Center, similar with what we have currently for integrations, where the user can choose to log detailed information regarding integrations (rest, soap, sap).

Hi, 

I also thought about that solution, but wouldn't fit on the "... as result of an expression." part.

However, that would be a huge improvement to the functionality.

Thanks.

Please implement this! It would mean the world for me :)

Hello everyone, I subscribe this ideia, and I understand that there is no priority, but anyway, 4 years later, I'll follow up on this one.

In my opinion doesn't make sense that, after the monitoring period I am forced to deploy the application again just to change this hardcoded value to stop consuming unecessary space at the environment.

In a context of high volume emails sending, this have a significant impact.

Thank you, guys for the amazing work, as usual! 

I wholeheartedly agree that the Log Content flag should not be a hard-coded value and changed to a input Boolean, so that depending on the environment or any other business-logic, the email content would be saved or not.

CA