What are you looking for?

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

Maestro Topics

Maestro Libraries Overview

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

A Maestro library is a collection of resources that can be made available to Maestro forms, components, and templates. A library can be created for an organization or project, and then resources published to that library can be shared by anyone with access to the organization or project.

Many types of resources can be published to a library including:

By using libraries, Template Designers and Form Builders can avoid resource duplication, streamline resource reuse, and effect changes to multiple forms in a single action thereby promoting a consistent user experience.


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

Resources are stand-alone objects which can be contained by assets like shared components and templates. Resources are identified by their name and, during standard template development, it is easy to end up with multiple resources with the same name but with different values. 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).

Why Libraries?

To understand why libraries exist and what problems they solve, consider the following examples.

Example #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.

Example #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.

Viewing Resources

You can view the list of resources published to a library. Follow these steps:

  1. Use the Navigator pane to select a Libraries item in an organization or project. A list of library versions is displayed.
  2. Double-click a library version to open it.
  3. Switch to the Resources tab. A list of resources is displayed grouped by resource type:

You can't open a release library, so if you don't have any user-created libraries, create one with the Create Library button.

Validating Resources

From the Resources tab, you can validate the resources within a library. During this process, Maestro runs a set of validation scripts to ensure that all resources (for example, styles and scripts) have valid structure and syntax. You may want to do this if some resources are not being included properly and to ensure there are no issues with the library.

To validate a library's resources:

  1. Navigate to a library's Resources tab.
  2. Click Check All Resources.

When the validation is complete, a success or error message is displayed:

Next, learn about library scopes.


Did this topic provide the information you need or leave you wanting to know more? Is there some way we can make this topic better? Let us know how we can improve this documentation.

Contact Us


Our Community is a dynamic, user-driven source of information that provides a home for sharing Journey platform knowledge where you can ask questions and get answers quickly.

Explore Community


Temenos is committed to supporting our customers with Journey platform solutions installed in the cloud or on premise. Learn more about our Customer Care Team, and its policies, procedures, and processes.

Learn More