×

    Filters

    Didn't find what you were looking for?

    Extend your Search in Community

    Questions?

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

Results

Tagged Libraries Overview

   MaestroPreviously known as Transact Maestro.  |   Form Builder |   v18.11 This feature was introduced in v18.11.

As a general good development practice, you will want to have known good quality versions of all libraries that Form Builders and others depend on to do their work. Having good quality library versions provides these users with a level of confidence that any issues they encounter are likely to be caused by what they are doing, not by the dependent libraries they rely on. Dependent library versions, therefore, need to be immutable, and tagging a library version satisfies this requirement.

A tagged library version is a read-only library version that prevents any changes from being saved to the library. Tagged library versions provide an effective way of keeping a clean, final record of a library. Note that once a tagged library version is created, it is still possible to create new library versions based on the tagged version.

A tagged library version:

  1. Cannot have assets published to it.
  2. Cannot be deleted by non-administrator users.

Tagged libraries can, however, be exported, viewed, and used as the library version for a project.