Some Background
My organisation migrated to Adobe Launch from Adobe DTM in 2019.
There are typically 3-4 people working on the same Property at any given time.
In DTM, our "rule" for editing was: do not edit any Resource (Rule, Data Element, etc.) where "Status" is "Unapproved"
In essence, this enforces the idea that an Approved change to a Resource can only come from a single Editor at a time.
Adobe Launch
When we started working with Adobe Launch, we assumed there was no longer any need for "manual" rules like our DTM example, because the separate DEVELOPMENT environments would keep changes to a single Resource on different "branches" (to borrow a term from versioning systems).
This assumption was proven to be wrong (everyone is always editing the same instance of each Resource, albeit creating new versions as they go), and the need for a manually-enforced approach is still there.
The Problem
In Adobe Launch, the unanticipated problem we encounter (with multiple Editors in a single Property) is this: we cannot find an indicator that a Resource is in some "edited" state.
Bear with me while I describe a scenario that leads to a Resource being in what I've dubbed an "edited" state and how this has dangerous consequences:
We've been dancing around this limitation for a while now, but when we discovered "unapproved" code had made it into our Production deployment, it was clearly time to look for a better approach.
The Question
Really, I have two questions:
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.