New JO: log to timeline all emails by default

Related products: CS Journey Orchestrator, Email & Notifications

I came against this hidden “log to timeline” issue again... In the new UI the menu is hidden and very easy to miss (issue already flagged in this idea)

Wouldn't it be more effective if each program had a switch to turn on ALL emails on the timeline by default? See my awesome mockup as reference:
 



If we want just some of them, we can leave that turned off, and select the ones we want to log in one by one (hopefully, in a “in your face” way like we had in the old UI so we don’t miss it)
 



 

+1. Painful on very long programs. There’s also an issue whereby this setting (and all the items in the contextual menu) are on a different layer (it seems) to step updates. I’ve had issues where I enable log to timelines and I save, and if I save the program again after that, it crashes and tells me “the program has already been saved by another user”. I’m not 100% sure on the why, but it seems like there’s a clash with program save, and these settings that save at another level to the program. 


🤔 Oooh… what if there was a popup (depending on whether this conceptualized “log all emails to timeline” feature was enable/not enabled) during the publish process that said something like:

“These emails will be logged/will not be logged to the timeline. Are you sure you want to proceed?”


🤔 Oooh… what if there was a popup (depending on whether this conceptualized “log all emails to timeline” feature was enable/not enabled) during the publish process that said something like:

“These emails will be logged/will not be logged to the timeline. Are you sure you want to proceed?”

I LOVE THIS @dayn.johnson! Great idea! 


@romihache -- worth a standalone idea?

Thinking on it more, it could be very useful to have a sort of “order confirmation” screen that was part of the publish process that showed key program information. I’m sure there are other settings that are frequently missed/hidden beyond log to timeline.


@romihache -- worth a standalone idea?

Thinking on it more, it could be very useful to have a sort of “order confirmation” screen that was part of the publish process that showed key program information. I’m sure there are other settings that are frequently missed/hidden beyond log to timeline.


Absolutely @dayn.johnson !
Useful fail-safe measures are always welcome!