Adobe Experience Platform Launch is being rebranded as a suite of data collection technologies in Experience Platform. These changes will be rolling out across all product documentation in the coming weeks. Please refer to the following document for a consolidated reference of the terminology changes.
A library is a set of instructions for how extensions, data elements, and rules interact with one another after they are deployed.
When creating a library, you specify the changes you want to make to your library.
At build time, these changes are combined with everything that has been submitted, approved, or published in previous libraries.
Libraries contain the addition or removal of:
Libraries must be assigned to an environment before they can be compiled into a build.
Libraries are approved or rejected as a whole. You cannot approve or reject individual items within a library.
A library moves between several environments as it makes its way through the publishing workflow.
Open the Publishing tab.
The Publishing page lists the Dev libraries and provides the means to submit them for approval, move them to staging, or publish them to production.
Select Add New Library.
Name the library.
Assign the library to a Dev environment.
Add a change to the library.
To add an item, select Add a Change, then choose the items you want to add. Any item that has been edited or deleted is available to add to the chosen library.
You can add the following to your library:
To add any resources that have changed, select Add All Changed Resources.
Select Save or Save and Build for Development.
Deploying compiles a build and deploys it to the assigned environment.
Once a library is created, use the drop down menu for that library to select one of the following options:
Change the library configuration.
Build for Development
Compiles a build and deploy it to the assigned environment.
Submit for Approval
Make the library available for an Approver to move it to the next step in the publishing process
Remove that library from the publishing process.
Changes to the library are shown in the Library Contents change log.
Data elements can depend upon extensions. Rules can depend on both data elements and extensions. If you do not include all the necessary components in your library, the build will fail at build time and you’ll need to add the necessary components before you complete a successful build. A future release will check dependencies when making changes to a library.
To remove something from a library, you must deactivate it and then publish the deactivated state.
Choose a library and select Edit to view library changes. All changes are shown in the Library Contents list.
Select a change to view and select a revision.
Select whether to show all items or changed items.
Select the revision, then select Select Revision.
Select either Add a Change or Add All Changed Resources.
Libraries encapsulate a set of changes you’d like to make to your deployed code. Active Library makes this easier, allowing you to rapidly iterate through changes and see the impact.
You can save new and existing extensions, rules, and data elements directly to the library you’re working on and, if desired, immediately kick off a build. You can also create a new library from the Active Library drop down.