Adobe Launch Publishing Flow

Table of Contents

Update time: August 1, 2023

We have deployed the library code to the website, now we need Library Publishing and Testing so that all the code libraries can be accurate and effective.In Launch is Publishing

The release of Library Code needs to go through Development、Submitted、 Approved and Published，Different people have different permissions to operate and approve, there are three levels of permission that are important for the approval workflow:

The develop right: Includes the ability to create libraries, build for development, and submit for approval
The approve right: Includes the ability to build for staging and approve
The publish right: Includes the ability to publish an approved library

The entire release process looks like this:

Adobe Launch permissions are very complicated, we will explain in another article, here we assume you already have sufficient permissions. you must be granted all three rights within a given property. Now let ’s look at the entire testing and release process,

Development

Libraries are created in Development. Any changes to a library must be made while the library is in Development. When development and testing are completed, the library is submitted.

There are three entrances to create a Library, as shown below:

You can choose any method at will, as shown below:

Name: Customize a name or version number
Environment: Only Development can be chosen because we are generating libraries in the development environment.
RESOURCES UPSTREAM: The existing configuration or library. Click on the downward-facing corner icon to pop up and display it.Click on this location：

Then it will pop up:

To show the existing configuration, you can retract it by clicking on the one below.

RESOURCE CHANGES: Some new configurations can be added through v and Add All Changed Resource.
Add a Resource: You can choose the configuration you want to publish this time.
Add All Changed Resource: All changes are automatically added.

Generally speaking, all are added, we add all here, the specific configuration is as follows, and then click “Save & Build for Development” in the upper right corner：

After completion, you can see a library under Development：

You will click on the location shown below, a pop-up menu will pop up：

Available actions for a library in Development state are:

Edit——Use the library Edit screen to add or remove components from a library.
Build for Development——Create a build for the library. The build is compiled and deployed to the environment the library is assigned to. This step fails if the library has not been assigned to an environment.
Submit for Approval——Unassigns the library from its development environment and moves the library to the submitted column for an Approver to work on.
Delete ——Deleting a library removes it from Launch. It does not remove the build from the environment,

If the development is completed, confirm that there is no problem, we click “Submit for Approval”, and then confirm：

The library is submitted to the Stagging environment.

Submitted

An Approver tests the library in a staging environment. When testing is completed, the library is approved or rejected. Rejected builds go back to Development so changes can be made before the approval flow starts over again.

You will click on the location shown below, a pop-up menu will pop up：

Available actions for a library in Submitted state are:

Open——View the contents of the library. Changes are not allowed. If changes are needed, the library should be rejected so changes can be made in Development.
Build for Staging——Assigns the library to the staging environment and deploys it.
Approve for Publishing——Moves the library to the Approved column for a Publisher to publish
Reject——Unassigns the library from the staging environment and moves the library to the Development column for changes.

We can first open the library to check the Library. If there is no problem, build for staging to test. If there is no problem, apply for publishing.

Build for Staging and Approve for Publishing are in order. You must first build for Staging before Approve for Publishing. Let’s build for Staging first，Click it：

Then wait for a while, wait for it to tagging, Until here it became Stagging：

You can click on Approve for Publishing：

Upon completion, it enters the Approved phase.

Approved

The library is waiting to be published. A Publisher can publish or reject the library. Rejected builds go back to Development so that changes can be made before the approval flow begins again.

You will click on the location shown below, a pop-up menu will pop up：

Available actions for a library in Approved state are:

Open——View the contents of the library. Changes are not allowed. If changes are needed, the library should be rejected so changes can be made in Development.
Build and Publish to Production——Unassigns the library from the staging environment, assigns the library to the production environment, and deploys it.
Reject——Unassigns the library from the staging environment and moves the library to the Development column for changes.

If there is no problem, click Build and Publish to Production directly to publish to the Production environment

Upon completion, it enters the Published phase.

Published

The library is live in the production environment. This column shows which libraries have been published and their publish dates. You can look at these libraries, but you cannot make changes. If you want to change what’s in your production environment, you’ll need to create a new library and push it through the approval process.

After publishing, you can verify that it has taken effect. Open the website http://www.bbccss.com, and then open the Adobe Experience Cloud Debugger: