Hi philiplawrence reasoning is we've dealt with some IT deptartments
who won't serve over certain small sites over SSL due to this vuln
Heartbleed - Wikipedia I know it sounds weird, but I've gotten this as
direct feedback regarding some active/live properties which don't have
any material information disclosure.
FYI, we have a specific property which is never intended to be served
over HTTPS for security reasons. It works fine with DTM, but with
Launch, it doesn't not properly downgrade to HTTP, which means we cannot
transition it cleanly to Launch.
This is a major point. Right now, we have to resort to having a separate
sandbox account so we can test for 1st level effects of these upgrades.
That said, we do not always have time to do that, which means we
delay/defer upgrading as long as possible. Tools upgrades are a major
concern for us as we have custom code in the analytics extension which
could run into issues depending upon what changes happen in the tool
thebenrobb Great, will watch for future updates - this is a crucial,
pain-reducing feature. Not having it tends to make one reluctant to use
Launch until rollback is available. Do you think it would be available
before the July DTM sunset on new property add capability?
Definitely 2nd this - we use the notes field to comment on requestor/BU
who exist outside of the marketing cloud, and also possible future time
boundaries for a rule decommission, and other not so obvious
requirements. This is a crucial capability across over 20 domain
properties managed under DTM. As of now, when we migrated assets to
Launch, it did not bring the DTM notes over, which is a big loss!!!