Maestro Libraries Overview

   MaestroPreviously known as Transact Maestro.  |   Form Builder  |   v18.05 This feature was updated in v18.05.

Journey Maestro uses the concept of libraries, where a library is a collection of resources that can be made available to Maestro's forms, components, and templates. Resources can be:

Maestro defines resources as stand-alone objects contained by assets like shared components and templates. Resources are identified by their name and by their values, if there are multiple resources with the same name. The version of the resource that is ‘live’ and shared across forms and templates is the last version to be published to a library (taking into account precedence rules).

You can create libraries for organizations or projects and add (publish) resources to these libraries. This allows anyone with access to these organizations or projects to share and reuse the resources. Maestro comes with the editor that is easy to use when you want to view and manage resources in a library.


A resource must be published to a library to make it available to forms, components, or templates that use that library.

We encourage template designers and form builders to use libraries to avoid resource duplication, streamline resource reuse, and promote changes to multiple forms in a single action thereby enforcing a consistent user experience.

To emphasize the importance of libraries, consider the following use cases.

Use Case 1: Template Designer

As a Template Designer, you want to ensure that corporate branding is consistent across a project or organization. If the resources that implement your brand are used in many different places, it's easy for those resources to diverge as branding guidelines evolve.

To solve this problem, a Template Designer can create a library named "Corporate Brand", for example, containing resources that implement the corporate brand, and make that library available to the organization. This library acts as a single source of truth for corporate branding. All templates, forms, and components within that organization use the resources in the "Corporate Brand" library, thereby ensuring compliance with branding guidelines. If the guidelines change, the Template Designer need only publish the changes to the library for them to be reflected throughout the organization.

Use Case 2: Form Builder

As a Form Builder, you want to ensure that form elements are laid out correctly, behave correctly across multiple device types, and accurately validate a range of data types. If an organization has a number of forms that ask for the customer's address, for example, it makes sense for the form fields that ask for the address to always look and behave the same way. If they don't, the inconsistency can lead to a frustrating user experience.

To solve this problem, a Form Builder can create a range of components that behave as desired and save those components to a common library. This library can be attached to an organization or project, and if those components ever need to be updated, the changes only have to be made once in the library rather than everywhere the components are used.

Next, learn how to view libraries.