MaestroPreviously known as Transact Maestro. | Form Builder | 5.1 & Higher This feature is related to 5.1 and higher.
Journey Maestro defines a project as an entity, which sits underneath an organization, that allows you to build your form application's structure. Each organization can have many projects. A project contains assets and resources, which can be:
You can manage and configure them at the project level, as opposed to the organization level.
All project level assets are stored in one of the following folders within the project:
You can edit assets within these project folders without affecting the published versions of these assets.
Maestro allows you to access the areas within the project by selecting the folders from the Navigator or by using the tabs at the top of the window.
This displays a list of all available forms in the project. The forms folder is the development area for forms. It is from the forms folder that you can create new forms or edit existing forms. Once forms are ready to be deployed, the form version needs to be built and imported into Journey Manager. For more information on forms, see Forms Overview.
This displays a list of all editable components in this project. The components folder is the development area for components. It is from the components folder that you can create new components, share components or edit existing components. Components are not available to forms until they are published to a library. For more information on components, see Components Overview.
This displays a list of all editable templates in this project. The templates folder is the development area for templates. It is from the templates folder that the Template Designer can create new templates or edit existing templates. Templates are not available to forms until they are published to a library. For more information on components, see templates overview.
After you have created and configured your organization for the first time, which includes creating the style and shared component libraries, what you need to do is simply set up a new project for new forms.
If you want to address a real-world client requirements, we recommend creating the following project structure:
If this is too much, you can create at least three projects within your organization, including:
You need a shared components project to keep all your shared components. For more information, see resource management.
However, from a Maestro technical perspective, it's not actually necessary for having a working project, so it is enough if you add only one project as you go.
Next, learn how to create a project.