Library is a collection of resources (
DataElements that represent the desired behavior of a
The publishing process in Launch consists of building a
Library, testing the resulting
Build in an
Environment, and promoting that
Library to the next stage of the process until it finally reaches the Production
There are two basic things to think about:
Library has a
state that identifies what stage of the process it is at. The
state also determines the available
actions and assignable environments.
Library is transitioned to different
states of the workflow by supplying an
action in the
meta of a request.
Depending on the
Environments of different types can then be assigned to the
Library can be built and tested, and then moved to the next stage in the workflow.
|Library State||Description||Can Add Resources||Available Actions||Assignable Environments|
You may only add resources to a
Library which is
Libraries may be transitioned to
Libraries may be transitioned back to
development for additional changes and submitted for an other review.
Putting this altogether, a sample publishing flow might look something like this:
Librariesare created in the
Libraryto any available Development
Libraryto the Staging
Libraryto the Production
Note: Building to the Production environment will automatically transition the Library to
state, you do not have to transition it manually.
Library belongs to exactly one
Property can have many
You can read more about
Libraries and their
states in the Approval Workflow section of the Launch user docs.