Now that you have implemented some key solutions of the Adobe Experience Cloud in your Development environment, it’s time to learn the publishing workflow.
Adobe Experience Platform Launch is being integrated into Adobe Experience Platform as a suite of data collection technologies. Several terminology changes have rolled out in the interface which you should be aware of while using this content:
Your Launch user account needs permission to “Approve” and “Publish” in order to complete this lesson. If you are unable to complete any of these steps because the user interface options are not available to you, reach out to your Experience Cloud Administrator for access. For more information on Launch permissions, see the documentation.
At the end of this lesson, you will be able to:
Now that you have created and validated your library in the Development environment, it is time to publish it to Staging.
Go to the Publishing page
Open the dropdown next to your library and select Submit for Approval
Click the Submit button in the dialog:
Your library will now appear in the Submitted column in an unbuilt state:
Open the dropdown and select Build for Staging:
Once the green-dot icon appears, the library can be previewed in the Staging environment.
In a real-life scenario, the next step in the process would typically be to have your QA team validate the changes in the Staging library.
To Validate the Changes in the Staging Library
In your Launch property, open the Environments page
In the Staging row, click the Install icon
to open the modal
If you use a different workspace for your Staging app, you would need to make sure that this workspace has all of the Pods and app updates that you made throughout this tutorial. At this point, the only difference in the installation instructions from your development environment is the Launch reference in the Core Configuration, as highlighted in the screenshot above. You would need to update the corresponding line in your AppDelegate.h file and rebuild your app.
In real-life, once your QA team has signed off by reviewing the changes in the Staging environment it is time to publish to production.
Go to the Publishing page
From the dropdown, click Approve for Publishing:
Click the Approve button in the dialog box:
The library will now appear in the Approved column in the unbuilt state (yellow dot):
Open the dropdown and select Build and Publish to Production:
Click the Publish in the dialog box:
The library will now appear in the Published column:
Again, notice that the Production environment uses a Launch reference in the Core Configuration, as highlighted in the screenshot below. If you use a different workspace for your Staging app, you would need to make sure that this workspace has all of the Pods and app updates that you made throughout this tutorial.
The next time you make changes to your Launch configuration you will need to create a new Library in the Development environment. Remember, that adding and removing extensions will require updates to the app itself. Be careful about keeping your Launch environments and app code in sync with each other to avoid issues.
That’s it! You’ve completed the tutorial and published your first mobile property in Launch!