MaestroPreviously known as Transact Maestro. | Form Builder | 5.1 & Higher This feature is related to 5.1 and higher.
The Temenos Journey platform provides you with the Maestro Native Component Development Toolkit to simplify the creation of custom native components through the use of templates, and automated tasks. This toolkit is based on the gulp automation tool, which executes custom tasks defined in a
To install the toolkit:
npm installand wait for the npm installer to finish.
You can define the following tasks:
new– Generate a new component in the
srcfolder, based on files in the template folders.
zip– Create a Maestro Library in the dist folder by bundling all files in the
srcfolder into a Zip file.
watch– Helps automate the code generation and packaging process. It continuously monitors all files in the
srcfolder structure and runs the zip task to generate a Maestro library, if it has been changed. It also continuously monitors
new-component.propertiesand runs the new task to generate a new component if it has been changed.
redist– Create a new toolkit distribution file by packaging all of the templates into a new toolkit. This is useful if you customize your templates and want to share them with others.
To run any of these tasks in the toolkit installation folder, type
gulp <task>. A few examples are provided below:
gulp new gulp zip gulp watch
gulp new task takes an optional parameter to identify which template to use as a model for your new component. Usage is
gulp new -templateName, where
templateName is the name of a sub-folder in the template folder. If you don't supply this optional parameter, a default (
-default) is assumed, which uses the component template files in
gulp new task regenerates your component's source files from the files in the template folder that overwrites any changes in the '
src/<componentName> directory. To avoid this, change the value of the '
component_filename property in the '
new-component.properties file immediately after you generate a new component, so the
gulp new task uses the
component_filename and it won't overwrite your original code.
To generate a new Maestro library with the default example component provided with the toolkit:
To create a new component with customized
metadata, follow the steps below:
new-component.propertiesto set your preferences.
Next, learn how to create a native component library automatically.