Copy configurations between sandboxes

Transcript

In this video, we will showcase how Sandbox Tooling can drastically help you reduce time to value and optimize your development lifecycle, enabling customers and implementation teams to replicate successful configurations across multiple sandboxes effortlessly. In the typical development cycle, you often create objects like schemas, audiences, and journeys. Unfortunately, replicating those objects from the development sandbox to other sandboxes is painstakingly manual and repetitive. But by introducing the Sandbox Tooling in Adobe Realtime CDP and Adobe Journey Optimizer, we bring you an innovative solution, packages. These packages allow for a smooth and seamless export and import of objects you add to them between different sandboxes. Now, let’s dive into a practical demonstration. ImagineLuma, a global airline company, is interested in sending a promotional email to their US Gold loyalty members, who have visited their website but have yet to book a ticket. Start in Luma development sandbox. Once data engineers and marketers build and test the required artifacts for the promotional email, I can create a package and start adding loyalty schemas to it. I can also keep adding artifacts to the package as needed, such as the PromotionJourney object. Once I have added all artifacts to the package, I can now go to the package inventory page and review it. Then, when I confirm all my artifacts are there, I can publish the package to make it ready for import into other target sandboxes. The package is available on the organizational level to be imported to various target sandboxes that are representing different business units, brands, teams, and geographies. I will switch to the Luma UI sandbox to import this package into the production sandbox. Click Import Action on the package. In the import workflow, select the target sandbox as Luma US. In the next step, I can review all assets included in the package. And what’s even more powerful, the system will auto-detect the dependent objects that are required for importing the selected artifacts. I can also choose to replace the dependent objects with an existing one in the target sandbox. This is important to help reduce object proliferation when not necessary. Monitoring and alerts are enabled to provide transparency for both package export and import jobs. I will also get a notification. When I see the package is successfully imported to Luma UI sandbox, I can go to the Schema, Audience, and Journey Browse pages to validate all artifacts are successfully created. Also worth noting is that all governance and consent labels added on schemas and audiences are copied over in the same import job. All export import operations are recorded in the audit log, ensuring your business is effectively compliant with corporate data stewardship policies and regulatory requirements. Sandbox tooling is a foundational capability that supports both real-time CDP and Journey Optimizer objects. Thank you for watching this demo.