Publish playbook-generated assets to other sandboxes publish-to-other-sandboxes

Use case playbooks are marketing templates designed to generate assets such as audiences, schemas, or journeys for common marketing use cases. You can test the assets created by playbooks in the inspirational sandbox and when you are ready, you can import the assets into other developement sandboxes for further testing with the data that you have available in those sandboxes. When satisfied with the testing, you can then move the assets from development sandboxes into production sandboxes.

However, in certain cases, you may have already set up your own schemas, fields, and field groups in other development sandboxes. This could make some of the assets generated by the use case templates, such as journeys, incompatible with your data. To understand how to use data awareness functionality to better align and complement the generated assets with your existing assets, read this tutorial.

Prerequisites prerequisites

Before reading this tutorial, browse the available use case playbook templates and create an instance of a preferred playbook.

Creating an instance generates a set of assets such as journeys, segments, schemas, and messages in the inspirational sandbox. Read on to learn how you can copy these assets into other sandboxes.

Create and publish a package create-publish-package

You can import packages only into other development sandboxes. Once you make all the necessary changes or updates, then you can import the assets or packages from those development sandboxes into production. You cannot import directly from the Use Case Playbooks sandboxes to production.
  1. To import objects from the inspirational sandbox into another sandbox, browse to a desired instance of a use case playbook, and select Publish to a different sandbox to export the artifacts as a package.

    GIF showing the different use case instances

  2. Once you select the Publish to a different sandbox button, a modal appears. Fill in the name and optional description and select Create. This step bundles the generated assets into a package that can be imported into a different sandbox.

    A modal for creating a package

  3. Navigate to the Sandboxes page in the left side navigation and select the Packages tab, find your package, and publish it. To publish a package that is in draft state, follow the steps in the sandbox tooling document.

    Package in draft or unpublished state

    Publishing the package

  4. After the publish succeeds, on the packages browse page you should see a + button enabled next to the name.

    Packages tab in the Sandboxes page

    note note
    The package cannot be imported while it is still in draft mode, so open the package detail page and publish the package.
  5. Select the + control and start the workflow to import the assets generated by the use case playbook into the Target sandbox. Select a target sandbox and confirm the package name that you want to import using the dropdown. Add the job details such as job name and job description before proceeding to the next step.

    Initiate import workflow, select target, confirm package, add job details.

  6. In the View dependencies step, you can map schemas and copy other assets from the inspirational sandbox into the target sandbox. The Finish button is disabled until you map each schema.

    Map schemas in the 'View dependencies' step, enabling Finish button.

Map schemas map-schemas

  1. Map the first schema. The schema mapping dialog displays a drop-down to select the target schema. If the source schema is a profile schema, then there are no other target schema options besides the individual union profile schema. You can see automatically generated mapping recommendations between Source Data and Target Fields when the page is first displayed. You can edit the mappings by selecting the target field and then selecting a new field. If you modify the suggested mappings, use the Validate button to validate the new mappings and display any errors that may be linked to the new mappings. Select Save once the mapping is complete.

    Schema mapping dialog with a dropdown to select a target schema.

  2. Continue mapping all the fields in the schemas. If the schema is an event schema, the dialog shows a dropdown where you can view all the event schemas in the target sandbox.

    Select a target schema from dropdown

  3. Select a schema from available schemas in the Target sandbox.

    Select a schema

  4. Complete the mapping and select Save.

    Save mapping

  5. Once you’ve completed mapping all the fields in the schemas, select Finish to complete the import workflow.

    Finish the flow

    note note
    You can’t modify any assets except for the schemas as this is an inspirational sandbox but they do show up as they are dependencies of the package.

Import status import-status

  1. You are automatically redirected to the Imports page where you can see the progress of your import.

    Page showing import progress

  2. While the package is importing, the assets of the package are being created in the target sandbox. Once complete, they reference the fields that you mapped during the import process. The process is now complete and the assets from the inspirational sandbox are now also present in your target sandbox for you to test.

    Generated assets in the target sandbox

Next steps

After reading this guide, you now have a better understanding of how to leverage use case playbooks along with sandbox tooling to create executable journeys that reference your schemas. Learn more about the common Real-Time CDP use cases.