Basic Flow

Building forms with the Maestro Offline Build (MOB) tool is a two-stage process.

1. Clone the project and related libraries to the local file system. The following commands support cloning of projects and libraries:
   • Clone Project
   • Clone Organization Library
   • Clone Release Libraries
2. Build the form(s) using the cloned files. The following commands support building forms:
   • Build Project Forms
   • Build Form
   • Build Form List

Libraries

In order to build a form, all of the required libraries must be available on the local file system. These include:

• The Project library the form belongs to.
• Organisation libraries containing shared assets (such as templates, components, and entity models).
• The core Maestro Release libraries.

Downloading and managing these libraries is discussed further in Clone Project.

Output formats

The MOB tool can produce built assets in three formats:

• ZIP file: (Default) The standard build asset, one file per form. This is the same format that the Maestro UI produces, and can be imported directly into Journey Manager or deployed through the JM SDK.
• FAR file: A Form archive file, one file per form. FAR files can be used in Journey Manager to update any existing published form version.
• Expanded: The expanded version of the FAR file, with the raw contents of the built form extracted into a set of folders.